Servers (Unreal Tournament)

UT Servers

The Unreal Tournament Alpha Servers are currently only available for Windows & Linux, and in this guide you will learn how to configure a custom map rotation, set custom player & spectator limits, add custom maps, set passwords, and configure automatic-restart scripts for either Windows or Linux, including handling multiple servers on the same machine.

You will need to create a forum account to get the download links, You can find those links Here once you have registered and logged in.

Please note there is another official guide under additional resources maintained by RZE. It contains some additional information if you have trouble. This forum thread may also have new useful information that may not be updated here yet.

Initial Windows Server Setup


Windows servers require both DirectX and Visual C++ Redistributable for Visual Studio 2015. Both packages are available for download on the Microsoft site.

Step 1 Download the Server

You can download the latest Server package from this thread:

Step 2 Extract the Server

Extract the zip file downloaded in step 1 into a folder somewhere on the computer that is running the server. For the rest of this tutorial we will consider that folder to be <HOME>. So if you install it in to C:\MyServer then when you see <HOME>\UnrealTournament this really means C:\MyServer\UnrealTournament.

Step 3 Initial Run

Before you begin to configure your server, you'll want to run it once so that it can create all of the needed config files for you to edit. It also allows you to respond to the EULA prompt and get it out of the way. Open a command prompt in your <HOME> directory and execute the following command:

WindowsServer\Engine\Binaries\Win64\UE4Server-Win64-Shipping.exe UnrealTournament UT-Entry?Game=Lobby -log

This will cause the server to create the following set of directories.


From here out, anytime you see <CONFIG> we are referring to the third item on the list. It's in this directory where all of your config changes go.

Initial Linux Server Setup

The UT Servers should support every conceivable variation of Linux to some degree, with the exception of x86 Linux, which may never be supported, anything in Bold under this heading is a shell command.

Step 1 Download the Server

You can download the latest Server package from this thread:

Step 2 Extract the Server

Extract the zip file downloaded in step 1 (unzip into a folder somewhere on the computer that is running the server. For the rest of this tutorial we will consider that folder to be <HOME>. So if you install it in to /MyServer then when you see <HOME>/UnrealTournament this really means /MyServer/UnrealTournament.

Step 3 Initial Run

Before you begin to configure your server, you'll want to run it once so that it can create all of the needed config files for you to edit. First, we need to set the UE4Server binary to be executable. Find it in <HOME>/Engine/Binaries/Linux So do this with: chmod u+x UE4Server-Linux-Shipping, and then execute a server to generate the config files with the command below. This first run of the server will crash, and this is okay. Press Ctrl-C to close the process.

/Engine/Binaries/Linux/UE4Server-Linux-Shipping UnrealTournament UT-Entry?Game=Lobby -log

This will cause the server to create the following set of directories.


From here out, anytime you see <CONFIG> we are referring to the third item on the list. It's in this directory where all of your config changes go.

Now that this is done, we need to make some required config changes with nano (or vi, if that's your thing), to do that type: nano ../../../UnrealTournament/Saved/Config/LinuxServer/Engine.ini and add these two lines:

bFirstRun = False

the bFirstRun parmeters determines if the game should show the EULA which was the cause of the crash in the above step. Your server is now ready to configure.

Community Memeber DDRRE has created a good tool/suite for running traditional Linux servers. Click here to go to the forums and read it.

Unreal Engine Configuration Files

When the Unreal Engine starts, it beings by loading a clean set of default config values. These values are cooked in to the pak and can not be directly modified. Instead, they can be overridden via the live configuration files. These files will be located in the <CONFIG> directory above and the engine will auto-generate them at first run.

By default, the engine will create a handful of empty inis but you will only be concerned with 3 of them. They are:

Config File Description
This file holds configuration information that directly impacts gameplay. Most of your changes will happen here.
This configuration file can be used to override the default set of game rules available to servers.
This is the main engine's configuration file. Only advanced users should be changing anything in here.

We will cover how to configure your server in a little bit.

Required Ports

UT Alpha uses the UDP Protocol for all of it's network connections. So in order for your server to be visible to other players, you will have to make sure the following ports are open and directing to the computer running your server. Click here to learn how to open ports on your router.

Require Ports for UT Alpha
Port Range Description
This is the port that the game will communicate with clients on. It can be overridden using the "-port=xxxx" command line switch.
This is the sever query port. When clients are looking to connect to your server, they will use this port to communicate with it. You can change this port in the Engine.ini file.
Hubs Only -- This is the instance communication port. Instances will talk back to their hub using this port.
Hubs Only -- Each instance will utilize one of these ports starting with 8000 to communicate on. You can strictly control which of these ports needs to be opened via configuration options. See "Setting up a Hub" further down on this page.

Setting up automatic restart scripts


This is a very basic script that will simply re-launch the process if it crashes, nothing more. In your <HOME> directory, create an empty text file called "RunServer.bat" Edit this file and add the following text:

   @echo off
   UnrealTournamentServer.exe UnrealTournament UT-Entry?Game=Lobby -log
   goto Start

Double clicking on this .bat file will start your server up and the batch file will restart the server if it happens to go down.


These are scripts that I have used in the past, they are relatively simple, but I will explain what each thing does and how it interacts.


   ps -eaf | grep UE4Server-Linux-Shipping | grep 7777
   # if not found - equals to 1, start it
   if [ $? -eq 1 ]
     /home/ut4/LinuxServer/Engine/Binaries/Linux/UE4Server-Linux-Shipping UnrealTournament UT-Entry?Game=Lobby -log
     | echo "The Server is already running"

CentOS 6.6

    ps auxw | grep UE4Server-Linux-Shipping | grep -v grep > /dev/null
    # if not found - equals to 1, start it
    if [ $? != 0 ]
      echo "Server is not running"
      echo "Attempting to start .. .. "
      /home/ut4/LinuxServer/Engine/Binaries/Linux/UE4Server-Linux-Shipping UnrealTournament UT-Entry?Game=Lobby -log
      echo "The Server is already running"

The one above is for you to copy/paste, the one below describes the lines which you may need to edit yourself to get desired results.

ps -eaf | grep UE4Server-Linux-Shipping | grep 7777 This is what the script uses to discover the correct server to make sure it's running, it first looks for the UE4Server-Linux-Shipping instance, and then it looks for port 8000, which is a duel server in this example.
# if not found - equals to 1, start it
if [ $? -eq 1 ]e
/home/ut4/LinuxServer/Engine/Binaries/Linux/UE4Server-Linux-Shipping UnrealTournamentServer.exe UnrealTournament UT-Entry?Game=Lobby -log This is the complete start path for the server, including mutators, ports, start map, and gametype
echo "The Server is already running" This will be echoed out to the console if you run this script manually.

Once you've setup your script how you want it with the correct details, save it as a .sh script ( and then type crontab -e, and add this to the bottom of the file:

*/1 * * * * bash /home/ut4/ > /dev/null

This will now automatically restart the server if it has crashed, once every minute. This will also restart the server in the event of a power failure, reboot, or even if you just kill the process yourself.

Hubs vs. Old School Servers

There are two types of servers supported in UT Alpha: Hubs which is the better new and improved way and Old School Servers for those that can't leave the 90's behind. Old School Servers run a single game mode (that can be modified with mutators) and have a list of maps that it cycles though. These are easier to admin and slightly easier on system resources. But they aren't nearly as flexible.

Hubs are our new way of running servers. Think of a Hub as your own little mini gaming network. The biggest benefit of a hub is it allows your servers to join, chat and then create matches in a wide variety of game modes to fit their current desire. Feel like playing CTF today, you can just start a CTF match and people can join. Want to Duel or Showdown? Leave your current match and go at it.

There are two portions to a hub. The Hub itself which is a chat room for setting up matches and the instances that it creates. That's right, the Hub will launch new servers on demand. This is a great way to maximize system resources as the Hub itself is fairly light weight.

While we still support old school servers, most of our new features (map vote is here, Hub leaderboards are coming) will be focused on Hubs.

Further down on this page, I'll cover how to configure a hub, but for now, let's look at settings common to all servers.

Custom Settings

The best way to setup your custom settings are to edit various values in the configuration files above. These settings will then be used whenever your server runs. Some of these settings can also be overridden using command line switches.

Command Server Settings

Let's start by setting up some information about your server that is used regardless to what game types are playing on them. These settings will go in your <CONFIG>\Game.ini file.

ServerName=Flak's Custom Sniper Server
ServerMOTD=<UT.Font.NormalText.Huge>WELCOME</>\n\n<UT.Font.NormalText.Medium>Headshots for everyone.</>
ServerDescription=This is my server, have fun

Parameter Description
This is the name of your server. It will be displayed in the server browser and at various points in the UI.
This is your server's Message of the Day. It will be displayed in the browser as well as in game. It supports the following rich text tags: <UT.Font.NormalText.Tiny>, <UT.Font.NormalText.Small>, <UT.Font.NormalText.Medium>, <UT.Font.NormalText.Large> and <UT.Font.NormalText.Huge>.All 4 have a .Bold (<UT.Font.NormalText.Small.Bold>) version and currently all 5 are white.
This description will appear at the bottom of the scoreboard.

You will also want to setup an RCON password for your server. These settings will go in your <CONFIG>\Engine.ini file.


Parameter Description
This is the password that will be used to admin your server. Please note that this password is stored in plain-text.
Individual Game Settings

Most of the game types themselves also have configuration values that you can set. If you are running a Hub then these values are controlled by game rules that we will explain later. If you are running a stand alone server, then you will want to set the various values in the <CONFIG>\Game.ini file.

TODO: Create a page with all of the known game options

Old School Server Map Rotations

If you are running an old school style of server (not a Hub) then you will want to setup map rotations for the game type you are running. You do this by changing the MapRotation values in the <CONFIG>\Game.ini. Here is an example of setting up the map rotation for a DM server.


If possible, it's always better to use the full name of the map otherwise, the engine will have to look it up which can cause a slight performance hitch.

Setting up a Hub

As I said earlier, Hubs are the shiny new hot server type that everyone's using. But they do require a little more setup and a little more work.

Ports and Instances

To start, let's setup some information that is needed for launching new instances. These settings will go in your <CONFIG>\Game.ini file.


These options are important to the running of a Hub. Let's look at what they do:

Option Description
Each instance needs it's own game port to talk on. By default we start at 8000.
Each time an instance is spawn (after the first) this value will be added to StartingInstancePort to generate the port for the instance.
This holds the maximum # of active instances that can be running at any one time.

How does this work together? Each time the Hub creates an instance, it will generate a new port number for it. It uses the following formula:

Port # = StartingInstancePort + ( (InstanceNumber-1) * InstancePortStep)
Joining dedicated servers to a HUB

To join a dedicated server to a HUB you need to create access keys to authenticate a dedicated server with the HUB. Each dedicated server requires it's own key. Accesskeys are configured in the HUBs Game.ini as following:


When launching the dedicated server add the following:


Game Rulesets: Overview

Hubs determine what type of game modes are available to play using a list of Game Rulesets. Currently, Epic has 12 different available rulesets for play. While you can change which rulesets are available on your Hub, if you allow an Epic ruleset, it will be forced to use the settings determined by Epic.

Game Rulesets: Configuring which rules appear

The list of rulesets that will appear in the game is determined by a config option in <CONFIG>\Rules.ini. It's important to note that if you make any changes here you have to include ALL of the rules you want to allow. Let's look at an example:


This will allow all of the normal Epic rules and one custom ruleset (MyCustomRuleTag). If you omit any of the original rules, they won't appear in the list. It's that simple.

Game Rulesets: Adding a new Rule

Since we added a new rule above, we need to create the rule definition for it. To do this, we add an entry to <CONFIG>\Rules.ini that defines the rule. Here is an example:

[MyCustomRuleTag UTGameRuleset]
Title=My Custom Rule's Title
Tooltip=Play this custom rules
Description=Custom Rules are really cool.\n\n<UT.Hub.RulesText_Small>TimeLimit : 2x 7 minutes</>\n<UT.Hub.RulesText_Small>Mercy Rule : On</>\n\nMaximum of 12 players allowed!

Let's Look at the various options defined here.

Option Description
This is a unique tag that will be used to identify this ruleset. NOTE: if you attempt to use one of the Epic rule tags, your settings will be blown out. But you can use it with CustomMapList to add maps to an Epic rule.
This is the title of rule that will appear in the UI.
This should be a short description of the rule that will popup when hovering over it in the UI.
This is a long description for this rule.
This is the Maximum # of players allowed in this game type.
This value locks the game from starting until it has this many players in it. I strongly suggest you leave it at 2 but it's your server.
This is a string reference to the texture to display when looking at the rule.
This is the game mode that will be used when launching the game (?game=xxxx) You can use the shortcut name if it's available or the long name.
This is a string options that will be passed to the instance. Here is where you setup the various game rules.
Rules get sorted in to various category tabs and you define those categories here. Each one should be added on a separate line:



This would cause the rule to appear on the two tabs.

If you are creating a rule for a team game you will want to set this to true. It will allow the match setup menu to have options for setting up the team, etc.
This is the section where you put all of your maps that are allowed with this ruleset. Each map should appear on it's own line (like Categories). You can use either the short name or long name for the map, HOWEVER if you use the short name, it will cause your server to hitch on start up while resolving the name.

One big important point to remember. The UniqueTag has to match in 3 places. It has to start the configuration section:

[MyCustomRuleTag UTGameRuleset] UnqiueTag=MyCustomRuleTag

It also has to match the value in the "AllowedRulesets"


These three values have to match for your rule to appear.

Game Rulesets: Adding new Categories

It's very easy to add new categories to your hub. Here is an example in <CONFIG>\Rules.ini:

RuleCategories=(CategoryName=TeamPlay,CategoryButtonText="Team Play")
RuleCategories=(CategoryName=SpeedRun,CategoryButtonText="Speed Rule")

This would add a custom SpeedRun category. Once added you can add custom rules that will appear under this tab. Like AllowedRulesets, you will need to include all of the default categories above if you add some. Just copy the above text as your starting point.

Custom Content on Servers

Custom content is supported using the redirectors. This is a way of using HTTP to download a pak that is needed to play. Currently, the following type of custom content is support:

Maps are supported on Old School Servers and Hubs Blueprint GameModes/Mutators and supported on Hubs (via rules only) but join in progress will not be supported. We are working hard at eliminating these limitations.

All custom content support starts with the RedirectReferences array. These settings will go in your <CONFIG>\Game.ini file. Here is an example:


All redirects go in this section. Let's look at the various sub values of each reference:

Parameter Description
This is the name of the package to be downloaded minus the .PAK extension. When the game needs a redirector, it will use this value to look it up in the reference table. It's important that this contains the full path to the package itself. Shortnames are not yet supported.
Typically this should be "http" or "https".
This is the actual URL needed to download the package without the protocol tag.
Holds the MD5 checksum for this package.

The UTGenerateRedirects commandlet is available to generate RedirectReferences entries. The commandlet generates the MD5 checksum so that you don't have to use a tool like WinMD5.exe or md5sum to calculate it.

Here's an example commandline to generate an entry for DM-NickTest2:

   UE4Server-Win64-Test.exe UnrealTournament -run=UTGenerateRedirects -Package=DM-NickTest2-WindowsNoEditor -WebAddress= 

When you connect an old school server that is running a custom map, the server will use this table to send the needed redirect information to the client. On hubs, you can use a custom ruleset to for a client to download gamemodes/mutator packages using this system. Let's look at an example:

Game Rulesets: Custom Content

Remember our custom ruleset we added above. There is another config property we didn't cover. These settings will go in your <CONFIG>\Rules.ini file. Let's look:

Option Description
Holds a list of packages that are required to play this ruleset. NOTE.. if you are including custom maps in this ruleset, you will need to include the packed name here. Here is an example of what I mean:


In future versions of UT this double definition won't be needed (though it won't hurt).

Find out the exact MapName

To find out the exact MapName, you have to start your Map once on your server or in a local game. After you've started the map, you can find the MapName in your UnrealTournament.log or in your Console output.

Remote Control

We have a page dedicated to Server Administration. For information on how to admin your server, go there.

Additional sources

Please use the Server Documentation Mega Thread on the forums