Installing the server Edit
Installing is quite easy, just download the server package from here and extract it to any directory you like. There are precompiled binaries for both Windows and Linux, if you use a different operating system (or those binaries really don't work), you'll have to compile the server yourself.
There is a folder called "config" containing all the configuration files. Remember to make a backup before you start playing with the options or make an update!
The most important file is called "default.servercmdline.txt". It contains all the important server switches.
Rename it to "servercmdline.txt".
If you open this file you should see an example configuration, fell free to modify the settings to your needs.
The other files in here are quite well commented and control stuff like admin passwords and map rotations.
Some nice examples can be found at the homepage of AssaultCube (without "Reloaded"), although some settings are different.
Forwarding your ports Edit
Your firewall may interfere with the server as it needs to listen for incoming connections.
You need to forward two consecutive User Datagram Protocol ports, your server ports and its subsequent port.
The default port is 28770 which means you have to forward UDP ports 28770 AND 28771 (or change the default values).
As (nearly) any firewall between you and the internet blocks unkown connections by default, you should probably look at the hints below:
To forward ports on your router:
- Search the manual for things like "Port Forwarding", "NAT" or "Virtual Servers".
- Otherwise search online for help for your router, don't forget to specify the full name (usually found at the bottom of the router or so).
- Look at the web interface of your router for things like "Port Forwarding", "NAT", "Virtual Servers", "Firewall" and so on.
To forward ports on your computer:
- Many modern operating systems (like recent versions ofWindows) have a firewall enabled by default. Again, search for help online, there are lots of tutorials. Especially Windows tends to block anything unknown, so try this first if you get errors.
- If you have another firewall (like f. e. ZoneAlarm or a firewall included in your anti-virus program) enabled, don't forget to create the neccessary open ports here, too.
Registering on the Master Server Edit
If you do not forward your ports correctly, your server will not be registered until you fix it. If there is another error, it will be displayed on the output. If it is registered successfully, it will tell you.
- A processor better than Pentium III 500MHz. It's no longer the 20th century! The Pentium 4 went out in 2000! We obviously exceed this requirement.
- About 2 to 20MB of RAM (usually around 5MB) is sufficient to run the server. Anyway, modern computers have that much power (and AC(R) is very client-orientated) that you usually don't even notice a server running in background.
You do not need to fulfill these requirements, but they guarantee minimal lag.
Most home users have ADSL, so the downlink (download speed) is faster than the uplink (upload speed)! Do not mix up the two, or your server will probably lag so bad everyone rage-quits until you resolve it! If you are unsure if your speed is enough, use SpeedTest.net.
These theoretical maximum values are in megabits; divide by eight (8) for megabytes. 1 Byte = 8 bit
Don't be shocked; these traffic values are calculated for a 24/7 server being full all the time.
|used slots||total uplink bandwidth||total downlink bandwidth||monthly traffic|
|4||.118 Mbit/sec||.054 Mbit/sec||52 GB|
|5||.188 Mbit/sec||.068 Mbit/sec||77 GB|
|6||.274 Mbit/sec||.082 Mbit/sec||107 GB|
|7||.375 Mbit/sec||.095 Mbit/sec||142 GB|
|8||.493 Mbit/sec||.109 Mbit/sec||182 GB|
|9||.626 Mbit/sec||.122 Mbit/sec||226 GB|
|10||.776 Mbit/sec||.136 Mbit/sec||275 GB|
|11||.942 Mbit/sec||.150 Mbit/sec||329 GB|
|12||1.123 Mbit/sec||.163 Mbit/sec||388 GB|
|13||1.321 Mbit/sec||.177 Mbit/sec||452 GB|
|14||1.534 Mbit/sec||.190 Mbit/sec||520 GB|
|15||1.764 Mbit/sec||.204 Mbit/sec||594 GB|
|16||2.010 Mbit/sec||.218 Mbit/sec||672 GB|
|17||2.271 Mbit/sec||.231 Mbit/sec||755 GB|
|18||2.549 Mbit/sec||.245 Mbit/sec||843 GB|
|19||2.842 Mbit/sec||.258 Mbit/sec||936 GB|
|20||3.152 Mbit/sec||.272 Mbit/sec||1033 GB|
Every second, any player will send the server up to
1000 Bytes data plus 700 Bytes protocol overhead = 1700 B (1.66 KiB) per player per second
The server will send the data of every player to all other players, so every additional player will increase the amount of data and the number of recipients. This means that the server uplink bandwidth increases with the square of the player number. A doubled number of players will quadruple your uplink bandwidth needs.
n = number of players
Average Incoming Data: n * 1700 Byte/s = total Byte/second downloaded
Average Outgoing Data: n * ( ( n - 1 ) * 1700 ) Byte/s = total Byte/second uploaded
Data size InfoEdit
If you still don't understand any of the terminology, or are completely confused, you should probably reconsider hosting servers.
More info is below on data and data sizes.
Table on data sizes: Quantities of Bytes
Deeper explanation of data sizes: Order of Magnitude