How to Host an OpenRCT2 Server (Headless Multiplayer Guide)

To host an OpenRCT2 server that runs without anyone playing on it, start the command line build in headless mode with a park save: openrct2-cli host ./my_park.park --port 11753 --headless. Server settings such as name, password, player cap and autosave live in the [network] and [general] sections of config.ini in the user data folder. Open TCP port 11753, make sure every player runs the exact same OpenRCT2 version as the server, and give yourself admin in users.json.

OpenRCT2 is the open source rebuild of RollerCoaster Tycoon 2, and its multiplayer lets a whole group build one park at the same time. Hosting from inside the game works, but the park then only exists while the host plays. A headless server keeps it open for everyone.

What you need

The server does not draw anything, so it needs far less than the game does on a desktop. Very large parks with thousands of guests are the heaviest case, since the server simulates every guest.

Step 1: Install OpenRCT2 on the server

Download the release from openrct2.io or the GitHub releases page. Pick the same version your group plays on. This matters more than anything else in this guide: a client on a different build is refused with Incorrect Software Version (Server is using ...).

On Linux, extract the release:

mkdir -p ~/openrct2 && cd ~/openrct2
tar -xf OpenRCT2-<version>-Linux-bookworm-x86_64.tar.gz

On Windows, the normal install includes the command line program openrct2.com next to openrct2.exe, which runs in a console window.

Step 2: Pick a user data folder

OpenRCT2 keeps its config, keys, users, groups, plugins and autosaves in a user data folder. For a server, give it its own folder so it does not mix with a desktop install:

./openrct2-cli host ./ServerData/save/park.park --headless --user-data-path ./ServerData

The first start creates config.ini, users.json, groups.json and the keys, save and plugin folders inside ServerData.

Step 3: Upload a park

Copy the park you want to run into the save folder. To continue a park from your own game, find it in your OpenRCT2 user folder (on Windows, Documents\OpenRCT2\save) and copy the .park file. A fresh scenario works too: start it in single player, save straight away, and use that file.

If the park uses custom rides or scenery from the community and the server log complains about missing objects, copy those object files into the server's object folder too.

Step 4: Configure config.ini

Stop the server and edit ServerData/config.ini. The multiplayer settings are under [network]:

[network]
player_name = "Server"
default_port = 11753
default_password = ""
advertise = true
maxplayers = 16
server_name = "Thursday Park Build"
server_description = "Slow build, no ride crashes on purpose"
server_greeting = "Welcome! Ask an admin before demolishing anything."
known_keys_only = false
log_chat = false
log_server_actions = true
pause_server_if_no_clients = true

pause_server_if_no_clients is worth turning on for most groups: without it, the park keeps running overnight, guests keep spending, rides keep breaking down, and the loan interest keeps coming.

Autosave is under [general]:

[general]
autosave = 1
autosave_amount = 10

autosave picks the interval (0 is every minute, 1 every 5 minutes, 2 every 15, 3 every 30, 4 every hour, 5 never), and autosave_amount how many to keep.

Step 5: Open the port and start

OpenRCT2 multiplayer uses TCP. Forward TCP 11753 to the server and allow it in the firewall. The router side is in how to port forward a game server.

Start the server:

./openrct2-cli host ./ServerData/save/park.park --port 11753 --headless --user-data-path ./ServerData

The console prints Listening for clients on *:11753 when it is ready. Run it under tmux, screen or a systemd service so it keeps going.

To resume after a restart from the latest autosave rather than the original file, point host at the newest file in ServerData/save/autosave. Scripting that into your start command means a reboot never loses an evening of building.

Step 6: Join and take admin

Players open Multiplayer on the title screen, then either find the server in the list or click Add Server and enter the address. New players join in the Spectator group by default, which can only chat. To build together, someone needs admin first, and the admin then sets the default group or moves players into User. The full process, including editing users.json on a headless server, is in how to make yourself admin on an OpenRCT2 server.

The easy option

A GamezServers OpenRCT2 server installs the release you choose with the OpenRCT2 Version setting, so the server matches your group's build. The panel covers the save to load, whether to resume the latest autosave, autosave interval and count, max players, password, advertising, name, description, greeting, logging and pausing when empty. You upload parks and plugins through the file manager or SFTP, it stays online without anyone's PC, and friends can split the bill. If players get refused, see OpenRCT2 server version mismatch and desync fixes.

FAQ

What port does an OpenRCT2 server use?

TCP 11753 by default, set with default_port in config.ini or --port on the command line.

Can an OpenRCT2 server start a new scenario by itself?

No. It needs an existing save to host. Start the scenario in single player, save it, and give the server that file.

Do players need RollerCoaster Tycoon 2 to join?

Yes. OpenRCT2 uses the original game's files, so each player needs RCT2 or RCT Classic installed alongside OpenRCT2.

Why can my friends join but not build?

New players join the Spectator group by default. An admin needs to move them to User, or change the default group, from the multiplayer window.