Renegade X servers host game sessions which Renegade X players then join. Currently the only supported method of operating a server is to host a dedicated server, which are traditionally hosted on a server in a datacenter which is paid for and managed by the server owner.
The only port that needs to be open for Renegade X is the UDK game port, which by default is UDP port 7777.
This is a brief overview on how to setup a server, and will be expanded at a later date.
- Download Renegade X
- Install Renegade X
- Run the launcher to install the rest of the game client
- While you're waiting on the game client to install, forward UDP port 7777 through BOTH your router's firewall AND Windows firewall.
- Run the server once; close it after it loads up (you're running it once to setup the config files)
- Open UDKGame.ini
- Under [Engine.GameReplicationInfo], change the value of ServerName from Renegade X Server to what you want your server to be named (example: Jimmer Bob's Cool Server).
- Save the config file you just modified (UDKGame.ini)
- Run the server
- Try connecting to your server
Servers have many configurable options available to them, which are exposed through INI files in the UDKGame/Config directory. The most relevant customization options are located in UDKRenegadeX.ini, UDKXSettings.ini, and UDKGame.ini. DO NOT MODIFY ANY CONFIG FILES BEGINNING WITH DEFAULT. Default config files are used the generate the UDK config files the first time Renegade X is run; therefore, to generate the UDK config files, you must run your server at least once.
- TimeLimit (set to 0 for unlimited time)
- TeamMode (Determines how teams are organized between matches. 0 = static, 1 = swap, 2 = random swap, 3 = shuffle, 4 = traditional (assign as players connect))
- Crate settings
The most popular form of server administration is powered by Agent's Jupiter Bot, which provides a host of modular features including advanced ban and ban exemption systems, a moderator system, IRC logging, file logging, leaderboards, medals, player join messages, greeting messages, periodic announcements, in-game bot count regulation, and demo recording management. Configuration includes a series of INI files with common default options already in place.