This is only a partial list of the administrative options available in Excessive Plus.  Furthermore, several examples such as the Map Rotation no longer work in the latest version of Excessive Plus (2.2b). Updates will be made very soon. Please check back or E-Mail Killer@GoQuake.com for information.

Notice: Although you can bypass the complexity of configuring a server by downloading one or more Instant Servers, I strongly suggest that you read the Excessive Plus 2.0a OpenArena Client Guide and this "Server Guide" so that you can, at least, familiarize yourself with the basics of administering/modifying a Server and Game Style configuration.

Unlike Quake III, "autodownloads" is disabled by default in OpenArena.  I do not know whether this is a decision by the OpenArena developers or by the ioQuake3 developers upon which OpenArena is based.

Consequently most noobs are unable to connect to many Mods or to Servers running Custom Maps until they enable this option or manually download the Mod and Maps.  You see them trying to connect to the server over and over again.  However, Excessive Plus (E+) can be played server-side only - that is, without any software download.  Players who do not download the Mod from the web site or a game server will still enjoy the benefits of the server-side options listed below.

CronTab:
A crontab is a list of commands that are executed at a given date and time.  Admins can set the xp_crontab command in the server's server.cfg - /set xp_crontab "crontab.txt" - or the server's q3config_server.cfg - /seta xp_crontab "crontab.txt".

    Usage:

    Each line has the format: minute  hour  day  month  day-of-week    /command
    For any of the above values, an asterisk (*) can be used to specify all valid values.
    That is, an asterisk for the month value means execute the command every month within the constraints of the other values.

    A hyphen (-) between integers specifies a range of integers.
    That is, 1-4 means the integers 1, 2, 3, and 4.

    A list of values separated by commas (,) specifies a list.
    That is, 3, 4, 6, 8 indicates those four specific integers.

    A forward slash (/) can be used to specify step values and the value of an integer can be skipped within a range by following the range with /"integer".
    That is, 0-59/2 can be used to define every other minute in the minute field.
    Step values can also be used with an asterisk.  For instance, the value */3 can be used in the month field to run the task every third month.

    Any lines (or part of a line) that begin with a hash mark (#) or a double slash (//) are comments and are not processed.
    You can colorize text using the format provided in the Excessive Plus Client Guide.

    Examples:

    * * * * *  /say Welcome!    //this is executed every minute!
    * * * * 1  /say Have a Great Week!    //this is executed every minute but only on Mondays!
    0 0 * * *  /exec your-midnight-fun.cfg    //this changes the server's game style configuration every night at midnight.

    Sample Crontab:
*/3 * * * *  /say Players can change configs and maps ==> /callvote conf plusN
*/3 * * * *  /say /callvote conf plusC or plusD or plusR
*/3 * * * *  /say /callvote map park   /callvote nextmap   /callvote map_restart
*/4 * * * *  /say Get Help, your STATS and more @ GoQuake.com
*/4 * * * *  /say Set your SNAPS to 20
*/4 * * * *  /say Server IP & Port are: 67.231.251.90:27980
10 5 * * *   /cp Server will shut down and reboot in 5 minutes
12 5 * * *   /cp Server will shut down and reboot in 3 minutes
14 5 * * *   /cp Server will shut down and reboot in 1 minute

The first 3 lines above print information in the console every 3 minutes.
The next 3 lines print information in the console every 4 minutes.
The last 3 lines print directly to the monitor screen (imposed on the map) that the server will shutdown.
The first shutdown message is at 05:10, the second shutdown message is at 05:12, and the final shutdown message is at 05:14.


Ban System:
Admins and Refeeres (if allowed) can ban players by criteria, by name, by IP, or by GUID on a permanent or temporary basis.  Admins can set the xp_bans command in the server's server.cfg (set xp_bans "bans.txt") or the server's q3config_server.cfg (seta xp_bans "bans.txt").

    Example:

    Name {
       "*your_name*" { // ban all who use 'your_name' as their name
         IP: 92.18.0.4    // allow your IP to be excluded from the ban!
         Password: "test"    // also exclude if this password matches!
         Reason: "Sorry, 'your_name' is a protected name!  Please use a different name!"
         }

       " "    { // ban players who try to use no name
         Reason: "Sorry, players without names are not allowed on this server!"
         }
    }

    IP {
       172.23.3.56 { // ban this IP
         Name: "Dragon*"    // but allow if the name begins with 'Dragon'
         Reason: "Dude, you are not a member of the Dragon Clan!"
         }

       207.46.* { // ban all players from this IP Block
         Reason: "Microsoft's Corporate IP Block is banned for life!"
         }
    }


Map Rotation System:
Admins can make one or more static rotation files or even make rotation files that rotate maps randomly.  Admins should set the xp_rotation command in the server's server.cfg - /set xp_rotation "rotation.txt" or /set xp_rotation "r1.txt".

While playing or spectating Admins and Referees can change rotation files by using commands similar to:   /rcon xp_rotation rotation2.txt   or   /ref xp_rotation rotation9.txt   or   /rcon xp_rotation r2.txt   or   /ref xp_rotation r9.txt.

You can have dozens of these files if you like.  Create new rotation files for different game types like CTF and FFA, for FragFests and Tournaments, and for Fun Wars, Clan Wars and Clan Practices.  Example, r2.txt, r3.txt, etc.  The shorter the name, the easier to type while playing.

To change to the next map within a Rotation File, use commands similiar to:   /rcon nextmap   or   /rcon rotate   or   /ref nextmap   or   /ref rotate.

To change to any map within a Rotation File, use commands similiar to:   /rcon rotate "x"   or   /ref rotate "x".  Where "x" represents the number of maps you would like to skip ahead.  For E+ Veterans, this is very different from E+ 1.03 where "x" was the order number of the map in the Rotation File.  Personally, I hope WaspBeast (The lead E+ Developer) reverts back to the old rotate system (or provide the option) as it is easier to remember the map order in terms of the Rotation File than it is to remember the map order in relation to each map.

Sample Map Rotation File for a mixed FFA/TDM Server:
You can colorize text using the format provided in the Excessive Plus Client Guide.  Example, when the first map below loads, players will see a "Message of the Day" Announcement telling them the Current Game Type and which map will be next.  ^5 will display Game Type: as Aqua Text, ^3 will display Team Death Match - as Yellow Text, ^4 will display Next Map: as Blue Text, and ^2 will display 1++ as Green Text.

q3dm14+ { g_motd: "^5Game Type: ^3Team Death Match - ^4Next Map: ^21++"
    g_gametype: 3
    g_warmup: 30
    timelimit: 10
    fraglimit: 150
    g_friendlyFire: 1
    xp_suddenDeath: 1
    /load conf/plusR.cfg
}

1++ { g_motd: "^5Game Type: ^3Team Death Match - ^4Next Map: ^26++"
}

6++ { g_motd: "^5Game Type: ^3Team Death Match - ^4Next Map: ^27++"
}


7++ { g_motd: "^5Game Type: ^3Team Death Match - ^4Next Map: ^2Q3DM8+"
}

q3dm8+ { g_motd: "^5Game Type: ^3Team Death Match - ^4Next Map: ^213Base"
}

13base { g_motd: "^5Game Type: ^3Free For All - ^4Next Map: ^2CPM9"
    g_gametype: 0
    g_warmup: 30
    timelimit: 10
    fraglimit: 35
    g_friendlyFire: 0
    xp_suddenDeath: 0
    /load conf/plusC.cfg
}

cpm9 { g_motd: "^5Game Type: ^3Free For All - ^4Next Map: ^2CPM14"
}

cpm14 { g_motd: "^5Game Type: ^3Free For All - ^4Next Map: ^2Bunker"
}

bunker { g_motd: "^5Game Type: ^3Free For All - ^4Next Map: ^2MiniManQ3"
}

minimanq3 { g_motd: "^5Game Type: ^3Free For All - ^4Next Map: ^2Park"
}

park { g_motd: "^5Game Type: ^3Free For All - ^4Next Map: ^2Q3DM14+"
}


Multiarena (Virtual) Game Server E+ 1.03 only:
Please note that this feature is only available in E+ version 1.03.  It was removed from version 2.0a and may or may not return in future versions.

It is a pity that this is one of the least used server-side features in Excessive Plus.  Essentially, a single Game Server can have a lobby area and separate rooms.  Each room can have its own maps, gametype, fraglimits, timelimits, maximum clients, etc.

When a player joins this type of Game Server, he finds himself in an open area.  He then chooses to enter one of several doors.  Each door leads to a separate virtual Game server.  Excessive Plus has had this feature since 2005.

MultiArena (Virtual) Game Servers are configured similar to single Game Servers with the following differences.  First, the Map Rotation file must be placed in excessiveplus/arenas.  Second, the Map Rotation file has to use a syntax that idicates the configuration of each virtual game server.

Please remember that OpenArena is based on ioQuake3 which in turn is based on Quake III.  So, if you do not set a maximum client limit per virtual server, the maximum number of players/bots that you can have on the MultiArena Game Server is 64.

The example below shows a MultiArena Server containing 3 Virtual Game Servers each having 3 maps.  The 1st virtual game server, denoted by the number 1, is a CTF Server, the 2nd virtual game server, denoted by the number 2, is a FFA Server, and the 3rd virtual game server, denoted by the number 3, is a Freeze Tag Server.

1 { 13vast { g_motd: "^5Game Type: ^31 Flag Capture the Flag - ^4Next Map: ^2mapel4b"
    g_gametype: 6
    g_friendlyFire: 0
    g_warmup: 30
    timelimit: 15
    capturelimit: 8
    xp_suddenDeath: 0
    /load conf/plusD.cfg
    /kick allbots
    /bot_minplayers 2
}

mapel4b { g_motd: "^5Game Type: ^3Capture the Flag - ^4Next Map: ^2oasago2"
    g_gametype: 4
    g_friendlyFire: 0
    g_warmup: 30
    timelimit: 15
    capturelimit: 8
    xp_suddenDeath: 0
    /load conf/plusC.cfg
    /kick allbots
    /bot_minplayers 2
}

oasago2 { g_motd: "^5Game Type: ^3Return the Flag - ^4Next Map: ^213vast"
    g_gametype: 5
    g_friendlyFire: 0
    g_warmup: 30
    timelimit: 15
    capturelimit: 8
    xp_suddenDeath: 0
    /load conf/plusR.cfg
    /kick allbots
    /bot_minplayers 2
} }

2 { 6++ { g_motd: "^5Game Type: ^3Free For All - ^4Next Map: ^213base"
    g_gametype: 0
    g_friendlyFire: 0
    g_warmup: 30
    timelimit: 10
    fraglimit: 35
    xp_suddenDeath: 1
    /load conf/plusR.cfg
}

13base { g_motd: "^5Game Type: ^3Free For All - ^4Next Map: ^2minimanq3"
    g_gametype: 0
    g_friendlyFire: 0
    g_warmup: 30
    timelimit: 10
    fraglimit: 40
    xp_suddenDeath: 1
    /load conf/plusC.cfg
}

minimanq3 { g_motd: "^5Game Type: ^3Free For All - ^4Next Map: ^26++"
    g_gametype: 0
    g_friendlyFire: 0
    g_warmup: 30
    timelimit: 10
    fraglimit: 45
    xp_suddenDeath: 1
    /load conf/plusD.cfg
} }

3 { ermap3 { g_motd: "^5Game Type: ^3Freeze Tag - ^4Next Map: ^2ospra3map1"
    g_gametype: 8
    g_friendlyFire: 0
    g_warmup: 30
    timelimit: 15
    fraglimit: 15
    xp_suddenDeath: 1
    /load conf/plusR.cfg
}

ospra3map1 { g_motd: "^5Game Type: ^3Freeze Tag - ^4Next Map: ^2q3dm11+"
}

q3dm11+ { g_motd: "^5Game Type: ^3Freeze Tag - ^4Next Map: ^2ermap3"
} }


Server Variables and Commands:

RoundLimit:
A roundlimit is a predetermined number of frags/captures that comprise a Match.  This command can be used in place of the fraglimit and capturelimit commands.  To enable the "roundlimit" command enter /set roundlimit x at the console.  The match will end after "x" rounds are played.  This command overrides the "SuddenDeath" command and therefore the round can end in a tie.  Also, the "roundlimit" command will not work unless the "xp_matchmode" command is enabled.

xp_Referee:
A Referee is like a junior administrator.  Referees have administrative priviledges on the server but these are limited to those commands that are authorized by the server admin.  Admins can enable the "xp_referee" command at the console but because of the number of commands it is better to edit one of the server's configuration files.  Examples:

    server.cfg:
set xp_referee "addbot,bot_minplayers,capturelimit,cp,fraglimit,forceteam,g_warmup,g_friendlyfire,ipdb,k,lock,map,map_restart,mute,nextmap,rotate,s,timelimit,unlock,unmute,vote,w,xp_matchmode"


    q3config_server.cfg:
seta xp_referee "addbot,bot_minplayers,capturelimit,cp,fraglimit,forceteam,g_warmup,g_friendlyfire,ipdb,k,lock,map,map_restart,mute,nextmap,rotate,s,timelimit,unlock,unmute,vote,w,xp_matchmode"

Please note that there is a character limit to any OpenArena or Quake III configuration line.  Consequently, because I like my Referees to have as much authority as possible (except ban), I need to use the short commands for the following:

Long Command Name        Short Command Name

    CenterPrint                        cp

    Kick                                   k

    Status                                s

    Whois                                w


Referees can display the list of commands that the Server Admin has authorized by entering the following command /ref at the console.

refereePassword:
Admins can enable the "refereePassword" variable by entering /set refereePassword password at the console.  If this variable is not used or used without a password then Referees are not allowed to administer the server.

xp_unlagged:
This variable - /set xp_unlagged 1 - enables an E+ optimized version of the "Unlagged Mod" technology.  However, please note that this can be changed by a Game Style Configuration.  Therefore, it is recommended that you place this variable in server.cfg instead of enabling it only from the console which places it in q3config_server.cfg.

xp_physics:
This variable - /set xp_physics 1 - enables the physics environment and movement control used within Excessive Plus.  However, please note that this can be changed by a Game Style Configuration.  Therefore, it is recommended that you place this variable in server.cfg instead of enabling it only from the console which places it in q3config_server.cfg.

    Where x is 1, 2, or 3:
    1 will enable only forward movement.
    2 will enable forward and sideways movement.
    3 will enable only sideways movement.

xp_solids:
This variable - /set xp_solids 1 - enables players to walk through "player clips."  That is, it permits players to camp and access parts of a map (like walking on parts of the roof, ledges, and walls) that is usually not possible.  This variable is disabled - /set xp_solids 0 - on most Excessive Plus servers.  However, please note that this can be changed by a Game Style Configuration.  Therefore, it is recommended that you place this variable in server.cfg instead of enabling it only from the console which places it in q3config_server.cfg.

xp_vote:
This variable permits players to vote on various game options.  Admins enable the variable and options (separated by commas or semicolons) by adding a line such as the following to the server.cfg file:

    set xp_vote "conf,map,map_restart,nextmap,rotate"

    Please note that you can permit many commands to be voted on, such as g_gametype, fraglimit, etc.

xp_voteconf:
A Vote Configuration is an Admin created text file in the server's excessiveplus directory (folder) which contains a list of Game Style Configurations that players are allowed to implement by a majority vote.  Admins enable the Vote Configuration file by adding the following to the server.cfg file:

    set xp_voteconf "voteconf.txt"

    Example of a voteconf.txt file:

    // Add Game Style Configurations that players may change by majority vote
    // Usage,    /callvote conf plusD

    plusC.cfg
    plusD.cfg
    plusN.cfg
    plusR.cfg


xp_chatProtection:
This variable - /set xp_chatProtection x - enables chat protection once a player has chatted for at least x seconds.  If you enable this variable, do not set the chat protection to less than 3 seconds as players will begin chatting simply to aviod being killed or frozen.  However, please note that this can be changed by a Game Style Configuration.  Therefore, it is recommended that you place this variable in server.cfg instead of enabling it only from the console which places it in q3config_server.cfg.

xp_muteSpectators:
This variable - /set xp_muteSpectators 1 - prevents Spectators from chatting with Players.  Spectators will still be able to chat with other Spectators but Players will not see the chat.

xp_inactivitySpectator:
This variable - /set xp_inactivitySpectator xxx - automatically forces Players away from the map (that is, they become Spectators) after they have been inactive for a certain number of seconds.  If these Spectators return to the map before it ends they regain their score and frags.  The reason for this variable is because many players simply step away from their computer to answer the phone or door without using the /away command.

xp_matchmode:
The Commands for Clan Wars or Fun Wars are only available if the Server has /set xp_matchmode x enabled.

    Where x is 0, 1, 2, or 3:
    0 will disable the matchmode commands.
    1 will enable the matchmode commands.
    2 will enable the matchmode commands + enable the roundlimit.
    3 will enable the matchmode commands + enable roundbased gameplay + display the scoreboard at the end of each round.

There are 8 MatchMode Commands: /lock, /unlock, /joinword, /invite, /timeout, /ready, /notready, and /teamready.  Please refer to the Excessive Plus 2.0a OpenArena Client Guide for usgae of these commands during Clan Wars, Fun Wars and Tournaments.

xp_holyshit:
This variable - /set xp_holyshit 1 - enables the "Holy Shit!"  (OpenArena changes this to "Holy Crap!") audio file that all Players and Spectators hear when a player or bot is killed or frozen by a direct BFG hit.

xp_validTLD:
This variable - /set xp_validTLD 1 - is suppose to force the real Country Flag of a Player even if he has setup a fake Country Flag.

xp_userdb:
This variable - /set xp_userdb 1 - enables a database of player aliases.  That is, it tracks all the names that a player uses.  Useful for Server Administration as well as for tracking player statistics with VSP.

xp_motd:
This variable - /set xp_motd "motd.txt" - enables a Message of the Day announcement and also indicates its filename.  Any E+ Server that has enabled a Message of the Day will display it when a player connects to the Server and at the start of every map change.  Example:

    ^7Hello $(name).

    ^5Welcome to ^2^1E+ TDM

    ^7Please comply with the following rules:
    ^7Failure to do so WILL result in a KICK or a BAN.
    ^7o ^3Racist or disrespectful comments will NOT be tolerated.
    ^7o ^3Cheating or game exploits will NOT be tolerated.

    ^7Administrators:
    WaspKiller, WaspBeast and Dakini

    ^7Referees:
    WASP Clan Members

xp_suddenDeath:
This variable - /set xp_suddenDeath 1 - enables "Sudden Death."  Sudden Death forces a Tournament, Free for All, or a Team Match from ending in a tie (draw) by extending the timelimit/fraglimit/capturelimit until there is a winner.

xp_teamBalance:
Players constantly join and leave servers which can cause teams to have an unequal number of members and, more importantly, members who are less skilled or more skilled than the members on the other team.  This variable - /set xp_teamBalance 1 - attempts to balance team members and skill levels after each map so the next map can be fair.

g_maxTeamClients:
This variable - /set g_maxTeamClients x - sets a per team member limit.  Consequently, matches on Public Servers will become team tournaments and not merely a RED Team vs Blue Team affair.  The loosing team will be forced to spectate and a new team will automatically be built from players who spectated the previous map.


Kick:
This is an advanced /kick and /clientkick in one command.  Admins and Referees (if authorized) can kick players who are cheating or being assholes by using the following commands:

    /rcon kick <expression> [<reason>]   or   /rcon k <expression> [<reason>]
    /ref kick <expression> [<reason>]   or   /ref k <expression> [<reason>]

    Examples:

    /rcon kick 2 "I warned you not to curse!"
    /rcon k wasp*
    /ref kick BadAssBob "The next time you cheat you will be banned!"
    /ref k 7


Please note that the 2nd example - /rcon k wasp* - means that all players whose names begin with the word wasp will be kicked.


Ban:
Admins and Referees (if authorized) can ban players who are cheating or being assholes by using the following commands:

    /rcon ban <expression> [<reason>]   or   /ref ban <expression> [<reason>]

    Examples:

    /rcon ban 2 "Get your cheating ass out of here!"
    /rcon ban 200.47.214.* "Get your cheating ass out of here!"
    /ref ban 3FB86096A39462FB64D4898BD153092E "Get your cheating ass out of here!"
    /ref ban BFN* "BFN Clan not allow here!"


Please note that the 3rd example - /ref ban 3FB86096A39462FB64D4898BD153092E "Get your cheating ass out of here!" - uses the player's GUID to enforce the ban.  Bans are added to the "bans.txt" file in the excessiveplus directory (folder).


Lock and UnLock:
Although Admins and Referees (if authorized) can lock and unlock teams, I recommend - based on many years of competitive ranked matches - that teams lock and unlock themselves.  However, the Admin and Ref commands are:

    /rcon lock <red/blue> [<password>]   or   /ref lock <red/blue> [<password>]
    /rcon unlock <red/blue> [<password>]   or   /ref unlock <red/blue> [<password>]

    Examples:

    /rcon lock red paradise
    /rcon lock blue
    /ref lock red hellfire
    /ref lock blue


Please note that if lock is used without a password that the system will generate a random password.


Mute and UnMute:
Admins and Referees (if authorized) can mute players or spectators so that they cannot chat with other players or spectators.  This is typically used to forcibly silence an annoying player.

    /rcon mute <clientNum>   or   /ref mute <clientNum>
    /rcon unmute <clientNum>   or   /ref unmute <clientNum>

    Examples:

    /rcon mute 2
    /rcon unmute 2
    /ref mute 6
    /ref unmute 6



Vote:
On Public Servers where players are permitted to vote, Admins and Referees (if authorized) will sometimes need to override or cancel a vote.

    /rcon vote <yes/no>   or   /ref vote <yes/no>

    Examples:

    /rcon vote yes
    /ref vote no



Status:
This is an advanced /rcon status.  Admins and Referees (if authorized) can display the clientNum, IP Address and GUID of players by using the following command:

    /rcon status <clientNum>   or   /rcon s <clientNum>
    /ref status <clientNum>   or   /ref s <clientNum>

    Examples:

    /rcon status 2
    /rcon s 2
    /ref status 6
    /ref s 6



Whois:
Admins and Referees (if authorized) can display the three most used aliases of all players or all aliases of an individual player by using the following command:

    /rcon whois [<expression>]   or   /rcon w [<expression>]

    Examples:

    /rcon whois
    /rcon w 2
    /ref whois 6
    /ref w



Forceteam:
Admins and Referees (if authorized) can force players or spectators to join a specific team (free, red, blue, or spec) by using the following command:

    /rcon forceteam <expression> <team>   or   /rcon forceteam <expression> <team>

    Examples:

    /rcon forceteam 2 red
    /rcon forceteam *wasp blue
    /ref forceteam 3 spec
    /ref forceteam bfn* free



CenterPrint:
Noobs often seem clueless about the scrolling console messages, so Admins and Referees (if authorized) can superimpose a message on the screen of all players and spectators by using the following command:

    /rcon centerprint <message>   or   /rcon cp <message>
    /ref centerprint <message>   or   /ref cp <message>

    Examples:

    /rcon centerprint Server will shut down and reboot in 5 minutes
    /rcon cp Server will shut down and reboot in 5 minutes
    /ref centerprint Server will shut down and reboot in 5 minutes
    /ref cp Server will shut down and reboot in 5 minutes



IPDB:
Admins and Referees (if authorized) can query the IP-to-Country Database that is included with Excessive Plus to check the origin of IP addresses by using the following command:

    /rcon ipdb <ip address>   or   /ref ipdb <ip address>

    Examples:

    /rcon ipdb 200.47.214.7
    /rcon ipdb
    /ref ipdb 200.47.214.7
    /ref ipdb



Load:
Admins and Referees (if authorized) can load specific Game Style Configurations by using the following command:

    /rcon load <configuration path/file>   or   /ref load <configuration path/file>

    Examples:

    /rcon load conf/plusR
    /ref load conf/plusD



==============================================================================

Document Name: Excessive Plus 2.0a Admin Guide
Author: WaspKiller
Date: March 2010
Notes: This guide used some text from the E+ 1.03 Admin Guide.

==============================================================================



    Top

    Home Page