Voting Enhancements

Coliseum2 1.9 implements a new powerful voting system where the server admin can choose to enable almost any variable for voting or referee control.  Except for a handful of "protected" variables, two new commands called enable and disable can be issued to expose any variable for players to vote on.  These commands may be issued during run time at the console or be included in a config file to be excuted at server start.

Please see sections on referee and team captains for detailed information on these topics.

 

Activating Voting:

Regardless of the permissions set for commands and variables for voting (below sections), make sure that the variable g_allowVote is set to 1 to activate the voting subsystem.  Otherwise, voting will not be allowed no matter what the permissions for the individual commands and variables are.  Permissions set for referee, team captains and players are not affected by this variable.

 

With Power Comes Responsibility:

Server admins are cautioned to exercise extreme care in determining which command and variables they allow access to and to whom they allow access for.  Some variables and commands are "protected" for security reasons and to prevent players from willy-nilly changing something that may cause conflicts and cause unpredictable behavior--although the rcon command still allows complete access.  If you are unsure what you should enable and to whom, you can simply do nothing and let the defaults stay.

Refer to Appendix A for a table of commands, their allowable permission settings and default settings.

 

Enabling/Disabling Commands and Variables:

Commands enable and disable can be issued at the console or placed in config files to open commands and variables for voting, players, referee and/or team captain control.

Command Usage:

enable <command/variable> <permission>
enable allcmds <permission>
enable allvars <permission>

disable <command/variable> <permission>
disable allcmds <permission>
disable allvars <permission>

 

Permissions:

When enabeling a variable, two (2) allowable permissions are [r]eferee and [v]oting.
When enabeling a command, four (4) allowable permissions/roles are [r]eferee, [c]aptain, active [p]layer and [v]oting.

Please see sections on referee and team captains for detailed information on these topics.

Example1:  /enable g_spawnsafety v
This will enable the g_spawnsafety variable for voting.

Example2:  /enable g_warmup r
This will allow the referee to change the variable g_warmup duration.

Example3:  /disable map v
This will revoke command map from voting attempts.  Previously enable permission for other roles are still effective.

Example4:  /enable restart rcv; /disable restart cv
This will enable the custom map restart command for referee, team captains and voting.
Then access is revoked for team captains and voting.  The result is the restart command will still be enabled only for the referee.

Refer to Appendix A for a table of commands and their allowable permision settings.

 

Command Special Uses:

 

Voting Command Alias:

In addition to the original Quake3 callvote command, an alias shortcut has been added to reduce typing: v

Example:  /v g_dowarmup 1
This will issue a callvote to enable warmups and is equivalent to /callvote g_dowarmup 1

 

Adding Enable/Disable To Config Files:

The enable and disable commands can be entered at the console at any time to set the desired permission.  These commands can also be placed in config files so the desired permissions can be set right at server startup.

However, since enable and disable are commands as opposed to variables, they are valid only when entered after a map has loaded as with most other commands.  Therefore, make sure you add these commands in your config files after you have started your initial map.  Otherwise, you will get an unknown command error since there is no game running to accept them.

 

 

The following text is no longer valid as of version 1.9 and is retained for historical purposes:


Coliseum2 extends the voting options by additionally allowing players to vote on runes allowed, hook speeds, rails through walls, fraglimit, timelimit and capture limit where applicable.  Furthermore, servers admins also has the capability to select which voting options are enabled or disabled.  Each of the voting option is represented by a bit flag and is activated by adding the value of each desired option together and setting the variable to this sum value.

Please take note, the stock Id variable g_allowVote, previously set to either on (1) or off (0), has been extended to allow higher values--which can be the total sum of the selected bit flags, listed below, to allow voting on selected options only.

CVAR:  g_allowVote

Voting Command Value   Description
map 1   Immediately change to the desired map.
map_restart 2   Restarts the current map.
nextmap 4   Sets the next map to be played after the current one ends.
g_gametype 8   Changes the game type.
kick 16   Kick a player.
g_doWarmup 32   Specifies if a warmup time is allowed.  This will not set the warmup duration itself.
g_rune_allowed 64   Selects which runes are to be allowed in the game.  The value of this voting parameter is the total sum of all the desired rune bit flags.
g_rail_walls 128  

Allowing rails to go through walls can be a contensious issue. Players may vote this on or off by setting it to either:
      0 - Never
      1 - When having strength rune
      2 - Always

g_hook_speed,
g_hook_pullspeed

256   This will allow players to vote on both the hook fire and pull speeds.
fraglimit, timelimit,
capturelimit
512   Players can vote on how the match should end.

The programmed default value for g_allowVote is 1023, which indicates that all voting options are enabled.

However, many servers already have the variable set in the config files to 1 and the default values will not be used since the mod will assume that 1 is the desired value.  Previously, a value of 1 indicated that all original voting options are allowed.  However, with the new system, a 1 will now indicate that only map voting is allowed.  Server admins are encouraged to double check this variable to make sure that it is set properly according to the new usage.

Clients who wish to see which voting options are activated on a server may bring down the console and type /callvote.  A listing of all voting command syntax will be listed with disabled ones colored blue.

 


Table of Contents Deathmatch Flags (dmflags) Setting and Using Explicit Ready