中文
Back Server setup guides
RimWorld server hosting8 min

RimWorld Together Dedicated Server Setup and ServerConfig.json Guide

Deploy the RimWorld Together multiplayer dedicated server (RTServer.exe), forward TCP 25555, coordinate client Mod 3005289691, and use open-source LGSM management.

RimWorld supports multiplayer through the open-source RimWorld Together mod. According to the mod author's description, players maintain independent colonies and their own pace on the same planet, interacting through trade, visits, and more. This article covers dedicated server setup. Configuration examples follow the project's 26.8.31.1 release; for other versions, consult their generated configuration files.

1. Architecture and multiplayer principles

RimWorld Together uses a client/server architecture for isolation and coordination:

  1. Server (RTServer.exe on Windows): Runs independently, handling player connections, authentication, and data exchange between colonies.
  2. Client mod (RimWorld Together Mod): Installed through Steam Workshop (Mod ID: 3005289691), providing multiplayer access in each player's game. Everyone keeps their own colony and progress; game clocks do not need to stay synchronized.

2. Runtime and resource planning

Download the package for your operating system from the project releases. The project provides Windows and Linux execution options and container deployment instructions; do not assume Linux needs a Mono/Wine approach for the Windows executable.

Configuration Checks
Operating system Use a release matching the OS and processor architecture; start with the included instructions
CPU and memory Allow headroom based on online players, save sizes, and actual monitoring; first test with your group's planned saves and mods
Disk Reserve space for saves, logs, and retained backups
Network port Default TCP 25555; configure inbound rules and router forwarding for public access

3. Network port and firewall rules

RimWorld Together uses a single efficient TCP channel by default:

Port Protocol Purpose Firewall and forwarding policy
25555 TCP Game data synchronization, account authentication, and world event exchange Core port; allow it in the router and firewall

Allow the port in Windows PowerShell:

PowerShell
New-NetFirewallRule -DisplayName "RimWorld Together Server" -Direction Inbound -LocalPort 25555 -Protocol TCP -Action Allow

4. Main configuration: ServerConfig.json

On first startup, the server creates basic configuration in Configs/ServerConfig.json. Stop the server, back up the original file, merge the fields you need to change, and restart. This is a configuration excerpt; do not use it to overwrite other generated settings:

JSON
{
  "Name": "My RimWorld Together Colony",
  "Description": "Multiplayer server for our group's colonies",
  "IP": "0.0.0.0",
  "Port": 25555,
  "MaxPlayers": 16,
  "UseUPnP": false,
  "EnableServerBrowser": false
}
  • Name, IP, Port, and MaxPlayers set the server name, listening address, port, and player limit respectively. IP is the bind address, not the public address advertised to players.
  • Private groups can set EnableServerBrowser to false to hide from public listings. This does not replace a join password or network access restrictions.
  • Set the join password with the server console command setpassword <password>; the program writes it to Configs/PasswordConfig.json. Commands such as op <username> manage administrator permissions. There is no shared "administrator password" field.
  • Automatic backups use fields such as AutomaticBackups and IntervalHours in Configs/BackupConfig.json. Keep an additional backup before updating and verify the restoration process.

Fields and paths follow the project's ServerConfig definition, configuration loading entry, password handling, and backup configuration. This version has no PauseOnEveryoneOffline field; adding it cannot enable pausing when everyone is offline.

5. DLC and mod compatibility checks

  1. Match game, mod, and server versions first: Choose matching versions according to current release notes; do not apply conclusions about older game versions to every newer version.
  2. Check the server's mod rules: The project supports multiplayer with different DLC and mod combinations; players do not always need identical DLC and mods. Actual joining and exchange of specific content still depend on server rules and the mods' documentation.
  3. Validate your group's actual combination: Check joining, trading, visiting, and other required features before starting the main save. Back up before changing large content mods, retaining original versions and load order for recovery if compatibility issues occur.

6. Open-source LGSM management

Managing RTServer also requires tracking version and client mod compatibility. You can use LanGame's open-source LanGame Server Manager (LGSM) (repository: GitHub - SZSLGJCOM/LanGame-Server-Manager).

  1. One-click template startup: LGSM's built-in RimWorld Together template deploys in one click and serializes ServerConfig.json parameters automatically.
  2. Port conflict prevention: Detects occupancy of 25555 and redirects smoothly.
  3. Colony backup management: Schedule save backups and check backup files and restoration results to reduce data loss after updates or unexpected exits.

7. Client connections and remote networking

  1. Prepare the client: Subscribe to RimWorld Together (Mod ID: 3005289691) in Steam Workshop, install dependencies, and arrange load order according to that version's instructions.
  2. Join the game: Click Together in the main menu and enter the server's public IP:25555 and your registered account credentials.
  3. Networking without a public IP: For campus or private networks, use LINK in LanGame OS Orbit to establish an encrypted P2P tunnel, then enter the virtual adapter IP for low-latency multiplayer on an alien world.