Here's an example of things that can only be in the runtime
Code: Select all
//Votes
// Can people hold votes to change levels?
"sv_vote_issue_changelevel_allowed" "0"
// Can people hold votes to kick players from the server?
"sv_vote_issue_kick_allowed" "0"
// Allow players to extend the current map?
"sv_vote_issue_nextlevel_allowextend" "0"
// Can people hold votes to restart the game?
"sv_vote_issue_restart_game_allowed" "0"
// Can people hold votes to scramble the teams?
"sv_vote_issue_scramble_teams_allowed" "0"
// Can people hold votes to surrender?
"sv_vote_issue_surrrender_allowed" "0"
// Can people hold votes to swap the teams?
"sv_vote_issue_swap_teams_allowed" "0"
// How long should a kick vote ban someone from the server? (in minutes)
"sv_vote_kick_ban_duration" "5"
You can find a list of cvars at this link
http://forums.alliedmods.net/showthread.php?t=186668
Anything marked "locked" in the cvar list there needs to be set at run time.
Here's the series of a server launch
command line (runtime) -> gamemodes.txt (runtime) -> gamemodes_server.txt (runtime) -> autoexec.cfg (before mapload) -> gamemodes_gametype.cfg (after mapload) -> gamemodes_gametype_server.cfg -> server.cfg (after everything)
Locked CVAR's can ONLY be set in the runtime, this means, HPE did not resolve the issue they claimed to be resolving with adding in these gamemode_gametype and gamemods_gametype_server config files, all they did was add another layer which only separates configuration more making it more confusing.