[Help] Round time limit depending on game mode/ server pw

[Senshi]

Greetings again.

Another question. Maybe small, but I - as a python noob - was unable to solve it.

Is it possible to set up a time limit depending on the config?

Thing is: We have a skirmish campaign running, and thus have to put our gameserver for one hour weekly in private mode (PW). For this one, we set the ticket limit to 1000 and want a time limit of 1h. Now, timelimit is set in the config_common. We don't want this, as this would force us to replace the config all the time. I'd like to put it in config_private.

Now, as a real Python noob would approach this, I tried adding
PRTIMELIMIT = 3600
to the config_private.py

Weird thing: This worked once. When I fired up the server and my buddy connected, I saw the limit jump to the 60min. Perfect.
Next time we restarted the server, nada. 4h time limit. Weird. The other changed setting (1000 tickets worked just fine).

Any ideas?

[dbzao]

We could indeed add that option to the config files that overwrite that setting in common.

[Senshi]

That would be most appreciated . Any possibility that I can do that by adding some entry myself right now so we don't have to wait for the fix? Not to hurry or stress you, it's just that the campaign project is scheduled to start this wednesday, and having this method would be sweet.

I'm not firm with python modding, to be honest, so I can't say for sure if this is true for python as well, but I know from other script languages that if an existing setting/value is set again, it will overwrite the older setting.

As the init python files are encrypted .pyc, I can't verify how exactly the python loads in PR, but I expect the _private is loaded after the _common config file, correct?

I'm eager to get a working workaround/ solution because if we have to switch the _common all the time, this poses several dangers: 1) Possible screwups...yeah...it's not rocket science, but...Murphy's Law, you know? 2) To ensure that the campaign battles can be held on a regular and reliable base, it'd be necessary to have several people that have the possibilites to manage the gameserver for the event. Now, handing out server admin rights on BF2CC/RCON is no problem, but spreading FTP rights around so they can also switch the _common is. Our server admin would get a heart attack if he noticed that. But not before raging up his platoon of bear cavalry with thundering chainsaws to put us down. Not kidding there.