The mail will beĪutomatically processed and checks will occuer to see if the match already was recorded. If we store the infoĪlso to file we can later mail it to the league site. When thisįails, it is handy to have a backup system in place. The scores and a lot more of info to the league site in realtime. The logfile will store all the official played matches. Path to the log file that stores the results of the played matches. The logging section deals with the configuration of the log path. The default is 3600 seconds and ONLY when there is a player on the server. The interval at which the plug-in will refresh his cached version of the welcome and motd message. We don't have to annoy server owners when we want to change them. It ensures that welcome messages across 1vs1 are all the same. Both the motd & welcome message make centralized management possible from league site. When set to true the welcome message set at the 1vs1 league site will be displayed when a player joins. It is also possible the change the motd from within the game if you have the OVSO_CFG permission set. When set to true the motd at the 1vs1 league site will be displayed when a player joins. Is the URI at which the plug-in communicates with the 1vs1 league site. This part mainly deals with plug-in and 1vs1 league site communication. To issue a match, we use the in-game /ovso match. With different keyword and distinguish that way what kind of match it was. When there is a new contest for example, we can add a contest command After an official match the keyword also wilīe send to the 1vs1 league site. Keyword name that will be send to the league site and log.įor now we only need 'official'. It is possible to define your own 'match' commands like this : key The /official command got superseded by the command /ovso match official. Mainly to stay compatible with the old version and to not annoy players. Is a flag that when true still allows the use of the /official command. Which style gets reported to the 1vs1 league site after an official match was played. For the 1vs1 league this has to be set to 10. The general section contains the most obvious config settings. The main purpose of the ini file is to make the plug-in more customizable andĪ INI configuration file has 4 sections which each hold different parameters loadplugin /myplug-indir/OneVsOne.so,/myconfigdir/ovso.iniĪ little more info about the plug-in and the ini configuration file.Įxample INI files for different styles can be found in the examples directory.
#Strayer bzflag code#
InĬase no INI file is provided it falls back to basic mode and all theġvs1 league integration code is deactivated. The plug-in takes a ini based configuration file as a parameter. The plug-in is compatible with the latest stable BZFLag release (2.4.x). No extra libraries are necessary to get it compiled, it all uses standard stuff. The plug-in is released under the following license: It is ofcourse always possible to write this from scratch.
#Strayer bzflag full#
To use the full feature set of the plug-in the league code is mandatory. That code is independenlty developed by strayer ( BZBB profile).
The plug-in does NOT contain any 1vs1 league site specific code which
During the years a lot of extra features were added
#Strayer bzflag Patch#
The plug-in was initially heavily based on a bzfs 1vs1 patch from BZFlagĭeveloper Pimpinella. The plug-in enhances player vs player gameplay in BZFlag, allows in-gameĬommunication with the league site and provides real-time match reporting. The OneVsOne plug-in is a bzfs plug-in specially created for one of the