BlinkY wrote:
do you mean the map_voting_sys or really the mapcycle_cron ?
I don't remember which one wurst told me to look into, I just remember it looked very dense
BlinkY wrote:
a generall question before: when the cycles are updated, i think b3 needs a restart, or the poweradmin plugin a new initial.
do you have any suggestions for this wonder outgoing from unix console?
another solution could be a timer for b3? but i don't now how
maybe a weekly reinitial for the poweradmin plugin by b3?
also i will change the srv "restart" from (think) 4 to 7am on fridays
do you have any suggestions for this wonder outgoing from unix console?
another solution could be a timer for b3? but i don't now how
maybe a weekly reinitial for the poweradmin plugin by b3?
also i will change the srv "restart" from (think) 4 to 7am on fridays
Hmm in fact I'm not sure we need to restart anything. Your voting page just write the 3 mapcycleX.txt right ? Here is the code inside B3 poweradmin plugin when mapcycle changes :
self.console.setCvar('g_mapcycle', rotation), "rotation" being the name of the txt file. So I guess B3 doesn't even cares about what is inside the file, and urt server loads it on the fly. For what I know, the only time B3 looks into it is when you type the !map command.
If it doesn't work, I could set a weekly cron into B3 to restart/kill it.
About the vote in itself, I know there are already some posts about that, but I think we shouldn't make 3 different votes. A single vote implies that the big mapcycle for example could only have few maps, but could be filled with medium sized map (if people don't vote for some big maps, well they don't want to play on it, no way to force them...) With 3 different mapcycles, I also think we should increase the maximum number of maps you vote for.
natirips wrote:
So, do we (I) start voting now, or not yet?
For the first time since we use 3 mapcycles, I voted for real, knowing that Blinky will save us
