Make UI hardcoded so it cannot be changed with menu-pack addons.
What we could do is to create a cvar, e.g.
ui_lockMenu. That way users would be able to control if they want to allow mods to change menu or not. Also, we have to do something about this
Could you explain how would that work?
I mean that most mods wouldn’t work properly if you create such a cvar, because for example silEnT uses its own redesigned UI.
Menu loading is part of the mod code ...
- Target version changed from 2.70rc1 to 2.75
Moving to 2.80 (it’s a new feature)
I don’t think we should finally do this. It would break 2.60 compatibility and ET is grown to such a popular game because admins are able to customize. New path structure & #53 will do the trick.
- Category changed from Client to Mod UI
So how about at least "hardcoded" UI for legacy mod? As ET:L loads it on startup by default this would be the best idea.
- Status changed from New to Invalid
- Target version changed from 2.75 to 2.71rc2
If you want to ensure a more or less clean ET:L on startup just add '+exec clean_simple.cfg’ (or clean_full.cfg) to your client command line.
Struggling with custom menus is history since we have the clean command and a clicky generation solution in the menus.
- % Done changed from 0 to 100
I’d like to say that some rules for clean_simple need a closer look.
clean all z*.pk3
(will also remove maps that names start with 'z’)
clean all *z*.pk3
(I don’t get why this was added, it will remove all maps with 'z’ in the name...)
I’d add these as a replacement for above 2:
clean all z*_*.pk3
clean all zz*.pk3
I’m pretty sure that’s going to guarantee cleaning user’s installation of all unwanted stuff.
That’s what I said, but IR4T4 asked me which maps start with the letter Z. Sure enough, I couldn’t remember any.
However, there is a bug with the
clean command, so I am going to commit this change with the fix.
Actually you can count the maps starting with a 'z’. These aren’t very popular or trickjump maps.
On the other hand 95% of custom pk3s start with a 'z’. What we can do is to add z-maps to the whitelist.
Discussion should continue here: #53
Also available in: Atom