Quote:
Originally Posted by KubeDawg
Ok thanks. Is there anything specific I need to have in this cfg file other than the code I posted?
And squeek, I think that would be how it should work, server.cfg would still always be there (UNLESS) the map lua first specifies the limit. What would be the negative cost if that were the case?
|
But the map Lua
always specifies the limit, even if it's just the default limit of 0. There might be a decent way to resolve conflicting class limits, but simply having the Lua setting take precedent is not the solution (especially if you want a Lua limit of 0 to override the server cvar settings, which would mean the server cvars would become useless).
Map cfgs work just like any other config and is loaded after the default server.cfg. A single "cr_engineer 0" line inside cfg/mapname.cfg will only affect that map as long as you have the default cr_engineer setting in server.cfg.