How to run a rune server Aug 20, 2014 12:49:10 GMT
Post by slade on Aug 20, 2014 12:49:10 GMT
Written by Testi in 2002, edited by slade
How to Set up a Rune Server
The purpose of this posting is to help people set up their own server for Rune. I will touch on various subjects ranging on hardware, ports and firewall, server tweaks, Rune.ini editing and admin tools. For most people, setting up the server is almost as simple as joining another server while others may need more work.
Here is a list of topics discussed here
- Hardware (Routers and Server Specs
- Rune.ini tweaks
- Web admin
Hardware and Stuff like that:
Routers and Firewalls
If you are using a router or a firewall, you may need to adjust that before you go any further. Some routers you need to open ports up while other routers you need to expose the computer in front of the built in firewall (DMZ). If you can, you may want to port forward the signal going to the server ports to the specific computer as well.
Some people might need to enable DMZ in order to make a server:
1. Search everywhere in the options of your router for DMZ. After you found it there should be somewhere a field where you can enter the digits behind the last period of your IP adress (i.e if your Ip adress is 192.168.120 then you enter 120 into the field. If your IP adress is 192.168.1.41 then you enter 41 into the field).
2. In some cases there is a option with that you need to enable DMZ. it should be at the same place where you have the field in that you enter the last digits of your Ip adress. Enable DMZ.
3. Click the "Apply" or "Save" button when there is one to save your just made settings.
Here is a list of ports you need to open:
7776 - 7781 UDP
27900 TCP & UDP
(you may want to add here the web admin port as well, web admin is talked about later)
MacClientRate and Tick rates
Below is a section from your Rune.ini file.
Your first adjustment you should do in your Rune.ini file is the MaxClientRate.
This entry is important because it allows fast downloads if you set it to a high value like 5000000, the default value of 20000 is outdated and new computers/internet connections can handle 5000000 easily.
There are a few more entries in this section you may be interested. NetServerMaxTickRate and LanServerMaxTickRate affect how many frames per second (or ticks) the server sends to the client. The lower the number the less server CPU is used but pings increase. Higher values will lower pings but increase CPU usage. Playing with this number will lead to increase server crashes and only experiment at your own risk.
If you install special mods or mutators, the client may need them so it would work properly.
In Game Admin
Please make the following changes in your Rune.ini file to customize your server information that is broadcasted to the master ping server
ServerName=<put your server nanme here>
ShortName=<put a small servername here in case you're using coadminz>
AdminName=<your name here>
AdminEmail=<give an e-mail so people can contact you>
MOTDLine1=<message of the day>
MOTDLine2=<message of the day>
MOTDLine3=<message of the day>
MOTDLine4=<message of the day>
AdminPassword=<your admin pass>
GamePassword=<Your pass if you wish>
IPPolicies listed here are your ban list. You can have up to 49 IP listed.
Webadmin is probably the best tool to manage your server. It is a web-based client where you can change almost anything about the server on the fly. All changes will take place on the next map change. No special programs are needed to run webadmin (it’s built into the game). To access web admin, open your browser and type this in:
Please change the bEnable to True
Then please put in an AdminUserName and password. You will need this to access it.
Now you may want to add in a special port number to make your server a little more secure. If you use Linux, you need to specify a port over 1024 otherwise you will not be able to access the web admin. You will also need to add this in the Rune.ini file at:
ListenPort=1025 (or Higher)
Now you're ports should be opened, but you'll have to uplink to the NEW MASTERSERVER instead of the dead gamespy one.
How that works: