Renegade X servers host game sessions in which 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, however you can host a server locally as well by following the same process below as this will work for both Local servers and Dedicated Hosts.
Renegade X is a UDK game port, which by default uses the User Datagram Protocol (UDP) on port 7777, however can be configured to use another port.
To begin the process of setting up your own Renegade X server, you will need to follow the process as outlined below.
- 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 (using either "Launch Game" or "Launch Server" from the launcher, or by running the UDK.exe found in the Win32/Win64 folder). (This can be found by going into the Binaries folder).
- Close the client after it loads up (you're running it once to setup the UDK config files).
Recommended Minimum Specifications for Dedicated Server Hosting
Please take the following specifications as guidelines, more than exact hosting requirements, as your performance may vary due to a large amount of factors in play.
- Low Population (Sub 30) - High Single Core Performance with a minimum recommended 2.7 GHz core.
- Medium Population (Up to 40 Players and vehicles) - High Single Core Performance with a minimum recommended 3.2 GHz core.
- High Population (Up to 50 players and Vehicles) - High Single Core Performance with a minimum recommended 3.5 GHz core.
- Mainstream Server (64 Players and maximum vehicles) - High Single Core Performance with a minimum recommended 3.8+ GHz core, but high as you as can possibly go is better, with the diminishing returns at 4.2~4.4GHz where you tend not to notice any better performance.
Starting up your server
Before starting up your server we need to change some settings to make sure we can identify the server.
- Navigate to the config folder which is found in \UDKGame\Config
- Open the UDKGame.ini file.
- 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)
- Start the server by either using the launcher and clicking "Launch Server" or using a .bat file (an example .bat file will be shown below)
- Try connecting to your server
An example of a common .bat file for starting a server is:
@echo off cd /d "C:\Renegade X\Binaries\Win32" start UDK.exe server CNC-Field?maxplayers=64 -port=7777
Replace the information with the valid path for your Renegade X install. All the sections such as ?maxplayers= and -port= can be excluded or changed as you require.
If you change the port, you will also need to ensure that you complete the port forwarding and add exceptions to the Firewalls as necessary.
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.
- AdminPassword (is important if you want to manage your server)
- GamePassword (Not necessary, but can be set if you want to restrict access to the Game Server to only those with this password)
- GameSpecificMapCycles (This is the Map Rotation list, you can add more maps to the server rotation by adding their names to this list)
- ModPassword (This allows you to have moderators log into the server, giving them the ability to use AdminKick to remove players from the server)
- TimeLimit (set to 0 for unlimited time)
- NetWait (This is the period of time before the level starts, where you fly around in a spectator camera mode, this can be useful in situations where you want to allow everyone to join before beginning, since extending this will make it last longer)
- DonationsDisabledTime (In Seconds, this allows you to prevent donations from occuring before this amount of time has passed after the level begins)
- TeamMode (Determines how teams are organized between matches. 0 = static, 1 = swap, 2 = random swap, 3 = shuffle, 4 = traditional (assign as players connect))
- bIsCompetitive (This can be used to enable Competitive Mode, limiting certain actions by players (such as Name Changing))
- bFixedMapRotation (If set to True, this prevents the end of round voting from occuring, as the next map will be the one which appears next in the "GameSpecificMapCycles" from UDKGame.ini)
- RecentMapsToExclude (This is how many maps must be played before the map becomes available to be voted for again)
- MaxMapVoteSize (This is how many maps will be available for voting after the round ends)
- InitialCP (This is the starting point for Commander Points)
- Max_CP (This is the max limit for Commander Points to accrue up to during the match)
- bBotVotesDisabled (This setting allows you to prevent the Vote: "Add Bots" from being used
- AirdropCooldownTime (This allows you to alter (in Seconds), the amount of time you must wait before being able to call in another vehicle after the Airstrip or Weapons Factory has been destroyed.)
- GDIItemPrices and NodItemPrices (These 2 values change the price of the Repair Tool item, if you set to 0 (free), the Repair Tool is free, but you still need to have the 200 credits available before being able to buy one.)
- Crate settings
For the full setting list see: Full Settings List
The most popular form of server administration is powered by the 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.
Lua error: Internal error: The interpreter exited with status 127.