Addon Details

This mod allows you to set scripts to load and config files to execute on a prefix basis... This uses the event est_map_end to load/unload your scripts, so the scripts will be ready from the word go on the next map rather than loading on es_map_start. To add configs, just follow the advice in [b]../addons/eventscripts/server_manager/prefix_manager.cfg[/b]: [syntax="es"] // Server Manager release 1.0.0 by Steven Hartin // ./addons/eventscripts/server_manager/prefix_manager.cfg // This file allows you to set up prefix's for maps.. There // are 3 commands, but you must always add the prefix first. // With this you can set up cfg's to load when a certain // map prefix is loaded, likewise with scripts. // The 3 commands are as follows: // addprefix ["script 1; script 2; ... script n"] ["config 1; config 2; config 3"] ["start/end"] [load from ../cfg/?] // // o Prefix - The prefix that the maps type starts with... e.g., de_, cs_, gg_, scoutz // o Scripts - The scripts that you want to load when the map type with the prefix loads // This is optional. Seperate multiple scripts with semi-colons ( ; ) // o Configs - The config files that you want to load (.cfg files). Like the scripts, // this is optional, but if you want to load the config files, and not any // scripts, then you need to use a value of 0 for the scripts paramater. // o Start/End - This determines when the config file will execute, at the end of that map type, or at the begining. // Generally you should make 2 executes, one to run at the start, and one to run at the end... // o Load - If you leave this blank, then the default file directory that the scripts will load from is // ../cfg/server_manager/. If you want to load anything from the main ../cfg/ // file then you must place a 0 here... e.g. if you wanted to load autoexec.cfg from inside // ../cfg/ then you'd put a 0 here. // // An example of this command is if you wanted to exec server.cfg and autoexec.cfg upon de_ maps at the start this is what you'd put... // addprefix "de_" 0 "autoexec; server" "start" 0 // addscript // // o Prefix - The prefix that the map type starts with... e.g., de_, cs_, gg_, scoutz // o Scripts - The scripts that you want to load when the map type with the prefix loads // Seperate multiple scripts with semi-colons ( ; ) // // An example of this command is if you wanted to load gungame4 on gg_ maps youd to the following: // addscript "gg_" "gungame4" // addconfig [load from ../cfg/?] // // o Prefix - The prefix that the map type starts with... e.g., de_, cs_, gg_, scoutz // o Configs - The config files that you want to load (.cfg files). Seperate multiple .cfg files via a semi-colon // o Start/End - This determines when the config file will execute, at the end of that map type, or at the begining. // Generally you should make 2 executes, one to run at the start, and one to run at the end... // o Load - If you leave this blank, then the default file directory that the scripts will load from is // ../cfg/server_manager/. If you want to load anything from the main ../cfg/ // file then you must place a 0 here... e.g. if you wanted to load autoexec.cfg from inside // ../cfg/ then you'd put a 0 here. // // E.G If you wanted to load autoexec upon de_ files at the start of the map you'd write this: // addconfig "de_" "autoexec.cfg" "start" 0 // // If you wanted to load de.cfg from ../cfg/server_manager/ at the end of the map you'd put this: // addconfig "de_" "de" "end" addprefix "gg_" "gungame4" addconfig "gg_" "gungame_start" "start" [/syntax] Don't forget to w00t