One point at the time (none of these are currently implemeted in my wrapper). Also note that my wrapper uses mysql for statistics output. This would have to be changed to be used in a wider audience.
- make game and quit?
Easy. I can just kill the server; or I think some option combination can archieve this.
- more involved stat output?
Currently, I'm only reading output from the game process. From that, very little information can be gathered. I'm hoping the --statfile option will give me some more input for putting into my little databases.
- is master password a switch? (I cant remember)
It is, but my wrapper script does not support it. I'm guessing the master password is for having games not joinable for all? My server will never support that by choice, but it's trivial to add.
Of these, the stat output and AI adding are the most interesting, IMHO. My todo is currently:
1. Support all gamerelated switches (I'm 30% there in my "beta" scripts)
2. AI support
3. Extra stats
4. Email notifications.
But that list will surely change before I get to 3, if not before
P.S: If anyone wants to help, I could probably make the source avaible. Perhaps I can even make a cvs server avaible
It's all written in Perl, and I would need to use an hour or so to prepare my scripts for publishing. The license will be (has to be) GPLv2.