looks like the script is pretty stable. No crash for more than a week so far. But of course this is caused that the script reboots itself after each map played.
-day (or potd - player of the day) - a new command which is almost ready to go will be implemented in next days. This command will display the best player of the day. This statistic is gathered from a separate database that i created and that is reset each early morning. So far you can see the html version of this statistic at
http://mexus.sk/vspd/pub/themes/bismarck/index.php?
if this list is empty that means no games have been played since reset.
Also server can broadcast this players name let say each hour.
I am thinking about to add my old rotation script which could take care about the maps change. So no more "vstr nextmap" lines in cfg. just pure map names. This could also dramatically improve map voting abilities. Here are my ideas about improvements
- script will read simple file with only map names. Each line one map and set the nextmap according to it. So any map could be voted and not need to vote like "callvote vstr <mapname>". Also not need to create vstr mapname variables to be able to load a custom map which is not possible to create for every map on the server because of max number of variables limitation of q3 engine.
- script will read the map file after each map to check if there is no update (maps added or removed). So no more reboots to apply new rotation settings. Actually no more exec map cfgs.
- script will remember the last played map so after a voting to some different map that is not in rotation it will set the nextmap to the nextmap in rotation. (rotation will continue where it stopped)
- after each vote pass with a map change the script will disable voting for 1 or 2 maps so this would prevent the spammers for keep voting for only 1 map (actualy this will be pretty tricky to code because it is hard to detect if the vote passed or not
![Very Happy :D](./images/smilies/biggrin.gif)
but i think its not impossible).
and now the most coolest idea what could be implemented. (yeah it is not my idea but what ever
![Very Happy :D](./images/smilies/biggrin.gif)
)
when one of the teams score reaches let say 8, the system will broadcast 3 map names with corresponding number and everyone could vote for the nextmap by typing the corresponding map number using say command (like it is used now for stats and other custom commands). The map with most votes will be set as a nextmap. Each player could vote only once this is not hard to do, each player can correct his vote by typing new number. The last number before the end of the map will be taken as a final. Also there is possibility to create some threshold, if not enough players vote, a default nextmap will be set. This could replace the whole rotation file with a dynamic rotation system. A file with all available maps will be created so not all maps on server will be considered as playable (some maps are weird and does not fit to daily game-play. ). I am think about that 1 map could be the same as the last if players want to play again the same map and the rest two would be random maps from this map file. Also there is possibility to create some protection, if a map has been played 2 times in a row, it wont be showed as a possibility in the next vote.
If you have any (better) ideas, just let me know
![AngelO :)](./images/smilies/angel.gif)