diff --git a/docs/server.html b/docs/server.html index 4298488d..83937519 100644 --- a/docs/server.html +++ b/docs/server.html @@ -30,9 +30,9 @@ yet use very little cpu time and memory, so you can run one in the background, or at the same time with a client if you want to host a game. Server ports default to UDP 28763 (game) and 28764 (info). If you choose to set your own port as X - it will automatically use X+1 for the info port! - See the Get Started Guide to find out - how to join a server. + it will automatically use X+1 for the info port! + See the Get Started Guide to find out + how to join a server.

Main Configuration @@ -45,8 +45,8 @@
bin_win32\ac_server.exe -c8 -n"My AC Server"
- or -
+ or +
bin_unix/linux_server -c8 -n"My AC Server" -xADm1nP4ss -D3 -V -o"Welcome To My Server"

@@ -54,14 +54,19 @@ "commandline.html" shape="rect">command-line section of this documentation. Run the script to start the server.

+

+ Command line options can also be written to a file (one option per line). Use the -C + option to read the file. See config/servercmdline.txt + for examples. +

Maprotation

In the maprotation file specified on the command line (default: config/maprot.cfg), you can specify the map, mode, time and voting for - your server. Each line defines one round. The optional arguments of minplayer, maxplayer and skiplines - empower you to change which lines will be played when your server is rather empty or closer to full. + your server. Each line defines one round. The optional arguments of minplayer, maxplayer and skiplines + empower you to change which lines will be played when your server is rather empty or closer to full.

@@ -155,11 +160,11 @@ // ctf ac_mines:5:10:1 ac_depot:5:10:1 - + // ac_arctic ac_arctic : 0:10: 1: 4: 7: 1 // tdm, 10 minutes, 4..7 players ac_arctic :11:10: 1: 7: 0: 0 // tosok, 10 minutes, 8.. players - + // one short game on ac_snow, either osok or deathmatch (pseudorandom) ac_snow :10: 6: 1: 0: 1: 7 // osok, 6 minutes, 0..1 players ac_snow : 2: 6: 1: 2: 2: 6 // dm, 6 minutes, 2 players @@ -185,7 +190,7 @@

The last block will play only one match on ac_snow, but depending on the number of players with varying gamemode; - for less than 8 players and an even number it will be deathmatch, for uneven numbers osok, + for less than 8 players and an even number it will be deathmatch, for uneven numbers osok, with more than 8 players team deathmatch will be played.

@@ -251,6 +256,74 @@ dolor 0 Lorem is a less powerful password: it can only be used to connect to a server that has a pending ban on the user. This kind of password is useful, whenever a blacklist range ban affects innocent players.

+

+ Nickname Blacklist +

+

+ In the nickname blacklist file specified on the command line (default: + config/nicknameblacklist.cfg), you can configure the nickname blacklist and the nickname + whitelist. +

+

+ Whenever a player connects to a server (or changes his nickname), the nickname is compared to the + whitelist and the blacklist. First, the nickname (as a whole) is searched in the whitelist. If the + nickname is in the whitelist, the player's IP and password are checked (if required). If an IP range + or password requirement is not met, the player gets kicked. If the nickname is not in the whitelist, + it is checked, if any blacklist entries match. If a blacklist entry matches, the player gets kicked. +

+

+ To prevent whitelist entries to be misused by other players, each entry can be secured by one or more + IP ranges and one or more passwords. IP ranges are very convenient to use. For players with static IP, + this is a very secure method to prevent others from using the nickname. If the IP is dynamic, it + depends on how big the used IP range is. A single /16 range should be secure enough for most cases. + If the range is bigger, the IP range will not block others sufficiently. In those cases, passwords can + be used. +

+

+ The following commands can be used in nicknameblacklist.cfg: +

+
+
+ accept nickname [IP range ...] [password ...] +
+
+ Add nickname to the whitelist. IP ranges and passwords are optional; if IP ranges are + specified, only connects from that ranges are allowed; if one or more passwords are specified, + the connect password has to match one of them. +
+
+ block nicknamefragment1 [nicknamefragment2 ...] +
+
+ Block nicknames that contain all specified fragments (up to 5). +
+
+ blocki nicknamefragment1 [nicknamefragment2 ...] +
+
+ Block nicknames that contain all specified fragments (up to 5), ignore cases. +
+
+

Administration