Server-Side Setup:

cm_admins.cfg:

The very first thing you need to do is decide what admins you will give reserved slots to. Once you know who you want to assign reserved slot access to, add the "r" flag to the admin levels in cm_admins.cfg. If you skip this step, admins will never be able to used reserved slots. Only admins with the "r" flag may use reserved slots.

The next thing you need to do is turn the reservation system on. This is done by setting cm_reservation to the appropriate number. Below is a description of what options are currently available (more will come in the next update to ClanMod) and examples of how to use each.

cm_reservation 1:

Type 1 reservation is used to tell clanmod to reserve a set number of slots on the server. If you choose this type of reservation you'll also need to set cm_freeslots to the number of slots you would like to reserve. So if you only wanted to reserve 2 slots on your server, you would set these cvars as follows.

cm_reservation 1 cm_freeslots 2

If you use the setup shown above, ClanMod will reserve 2 (two) slots for admins to use.

cm_reservation 2:

Type 2 reservation is used to always keep one slot on your server free, so admins will never see "Server Full" when connecting. If the server is "full" (maxplayers minus the 1 free slot) and an admin connects, the player (non-admin) with the shortest connected time will be kicked to make room for the admin. You may not want the player to simply be kicked off the server. If you wish, you may set cm_redirect to the IP or hostname of your choice, and the player will be redirected to that server in place of being kicked.

This is true of players (non-admins) connecting to the full server and players who are already on the server and need to be moved to make room for admins. Here is an example of how cm_reservation 2 works, for our example we'll assume a 20-player server.

maxplayers 20 cm_reservation 2 cm_redirect "127.0.0.1" (this part is optional)

ClanMod will allow the server to fill up to 19 slots (20 � 1) including admins and non-admins. Once the server reaches 19 players, ClanMod will start checking any new clients that connect. If a non-admin tries to connect to the server, with 19 clients already connected, one of two things will happen. If cm_redirect is NOT set they will be told the server has no free slots available and to try again later. If cm_redirect is set, they will be sent to the IP address defined by cm_redirect (127.0.0.1 in the above example).

If an admin connects with 19 clients already on the server, ClanMod will again check if cm_redirect is set, if it is not set a player (non-admin) will be kicked to make room for the connecting admin. If cm_redirect is set to an IP or hostname of another server, the player will be sent there instead of just being kicked. If you do not want to redirect players anymore, simply set cm_redirect to "", like this�

(one) slot on the server "open" or "not used". There is no need to set cm_freeslots for this type of reservation. Also please keep in mind when picking what type of reservation to use, with type 2 reservation you do "lose" that one slot. The server's new max will be maxplayers � 1. This is because that one free slot is used for player checking. Unfortunately, there is no way around this in HL. If you always want admins to always be able to connect, this is your only option.

Another note on cm_redirect� It has come to our attention that some players DO NOT want to be redirected, regardless of what the server has set. So we have added another a check which will allow a player to bypass the redirect option. Keep in mind, the player WILL still be kicked if there is no room, but he/she will not be redirected�

To keep from being redirected on a ClanMod server, add this to your config.cfg

setinfo "_cm_noredirect" "dont"

However, there is one more thing you may or may not want to use. You may have noticed that sometimes when you join a server that seems to have open slots available, you get the message "There are no public slots available". This is because the server shows the number of "maxplayers" the server can hold, not the number of "public" slots. Meaning, if you have a 22 player server (maxplayers 22), and you have 2 reserved slots (cm_freeslots 2) the server will still show the outside world all 22 slots. When you have 20 (non-admin) players on the server, it will still show 2 more slots available. However if a non-admin attempts to connect to the server, they will not be able to enter the game, because "there are no public slots available". This can be annoying and can cause game browsers to keep attempting to connect to your server, even though there is no room for the player. This can be controled using a HL server cvar called sv_visiblemaxplayers. This cvar has nothing to do with ClanMod, again it is a HLServer cvar that controls how many slots are visable to the outside world (game browsers, etc) sv_visiblemaxplayers is used by setting it to the number of slots you would like to show the outside world. Using the example server above (22 player max, with 2 reserved slots) you would want to set the cvar like this... sv_visiblemaxplayers 20. This will show 20 slots to the outside world. Basically it lies about the number of maxplayers the server can hold, in effect making your reserved slots hidden.If you had a 16 player server, with 2 reserved slots you would set sv_visiblemaxplayers 14. This cvar can be turned off by setting it to -1. Which means if you wanted your 22 player server to show all 22 slots again, you would set sv_visiblemaxplayers like this. sv_visiblemaxplayers -1

So you will need to explain to your admins that even if the server shows as full (20 players connected) there are still 2 slots waiting for them, and they should connect anyway (admins WILL be able to get in)

If your admins have passwords set in cm_admins.cfg, they are required to use the setinfo method to login. Otherwise ClanMod will not know the connecting client is an admin, and they will not be allowed to use reserved access. Please see the LOGIN GUIDE for more information on logging in with setinfo.