Hammer
11-04-2003, 02:27 PM
Get the archive ==> HERE (http://www.mohaacrew.com/Hammer/MC_CoD_configs.zip) <== ::: all files must be placed under the server's main folder.
Here's the config files used on our MC Gamers' dedicated servers. The main file (called during server startup) is serverexec.cfg, it gets the config started and, as the last step, causes the map rotation to begin.
Each server, MC Gamers currently runs 2, has it's own con_local#.cfg file (where # is either 1 or 2). All servers have identical copies of all the files in the zip archive.
One file not in this archive, must be created for everything to work properly. This file, called con_private.cfg, should contain nothing more than an exec of the appropriate con_local#.cfg file. The purpose for this arrangement is that it allows for central maintenance of all (common) config files, without worrying about overwriting changes.
Here's what our con_private.cfg file has on server #1:
//
// Include server 1 settings
//
exec con_local1.cfg
//
// Done.
Here's a quick description of each file in the archive:
serverexec.cfg - primary config file: use in command line as
- +exec serverexec.cfg
- calls con_server.cfg and, as last step,
- starts map rotation
con_server.cfg - main config file dispatcher
- calls all other config files
con_common.cfg - common server settings shared by all servers
con_defaults.cfg - map default settings shared by all servers
con_password.cfg - rcon and server passwords
con_ban.cfg - for user/address banning (when it works)
con_games.cfg - map rotation and gametype assignments
con_local#.cfg - each server's unique settings config file
- assigns appropriate map rotation for each day
- called by con_private.cfg
con_special.cfg - other settings, i.e. match rotation, practices
con_linux.cfg - for the dedicated linux server, use in command
- line before any other +execs are performed.
Here's the config files used on our MC Gamers' dedicated servers. The main file (called during server startup) is serverexec.cfg, it gets the config started and, as the last step, causes the map rotation to begin.
Each server, MC Gamers currently runs 2, has it's own con_local#.cfg file (where # is either 1 or 2). All servers have identical copies of all the files in the zip archive.
One file not in this archive, must be created for everything to work properly. This file, called con_private.cfg, should contain nothing more than an exec of the appropriate con_local#.cfg file. The purpose for this arrangement is that it allows for central maintenance of all (common) config files, without worrying about overwriting changes.
Here's what our con_private.cfg file has on server #1:
//
// Include server 1 settings
//
exec con_local1.cfg
//
// Done.
Here's a quick description of each file in the archive:
serverexec.cfg - primary config file: use in command line as
- +exec serverexec.cfg
- calls con_server.cfg and, as last step,
- starts map rotation
con_server.cfg - main config file dispatcher
- calls all other config files
con_common.cfg - common server settings shared by all servers
con_defaults.cfg - map default settings shared by all servers
con_password.cfg - rcon and server passwords
con_ban.cfg - for user/address banning (when it works)
con_games.cfg - map rotation and gametype assignments
con_local#.cfg - each server's unique settings config file
- assigns appropriate map rotation for each day
- called by con_private.cfg
con_special.cfg - other settings, i.e. match rotation, practices
con_linux.cfg - for the dedicated linux server, use in command
- line before any other +execs are performed.