How to Host a Barotrauma Server
Hosting a Barotrauma server lets your crew run persistent submarine missions behind a dedicated host, whether for friends or a public crew. This guide explains system requirements, step-by-step setup, configuration options, port settings, and common troubleshooting so your server stays stable and easy to join. By the end, you will have a clear, repeatable process for running a Barotrauma server that minimizes downtime and maximizes playtime.
Barotrauma Server Hosting Overview
Barotrauma uses a client–server model where the host runs the simulation and clients connect over TCP or UDP. Understanding this model helps you anticipate bandwidth, latency, and firewall needs. A server can host a single dedicated instance or multiple submersibles in an extended campaign. Key goals are stability, consistent tickrate, and straightforward join flow for your crew.
Server vs. Peer-to-Peer Play
In peer-to-peer, one player hosts the game and acts as a client at the same time, which can cause lag, desync, or kickouts if that host’s connection fluctuates. A dedicated server removes the client side, dedicating hardware to simulation and reducing common netcode pitfalls. For regular crews, a dedicated server is generally more reliable and easier to manage long term.
Minimum System Requirements for Hosting
Barotrauma server performance depends on sub complexity, crew count, and entity density. Use these baselines to decide whether a machine is suitable, and plan upgrades when needed.
| Component | Minimum | Recommended | Notes |
|---|---|---|---|
| CPU | Dual‑core 2.0 GHz | Quad‑core 3.0+ GHz | Server tick is single‑threaded; faster single‑core speed helps more than extra cores. |
| RAM | 4 GB | 8–16 GB | Budget 1–2 GB per 10 players plus OS overhead. |
| Storage | 10 GB SSD | 20 GB SSD | SSD reduces map‑load latency and backup copy times. |
| OS | Windows 10 64‑bit | Windows 10/11 64‑bit or Linux via Steam Runtime | Linux hosting is possible but may need extra steps for dependencies. |
| Network | Broadband with 1 Mbps up | 5+ Mbps up, low latency | Bandwidth is modest; stability and low ping matter more. |
Step‑by‑Step Server Setup
- Install SteamCMD and the Barotrauma Dedicated Server build from the Barotrauma branch.
- Create a dedicated folder and deploy files, then craft a start script with appropriate parameters.
- Set server name, password, game mode (e.g., campaign vs. sandbox), and required sub.
- Forward necessary ports on your router and configure firewall rules for TCP and UDP.
- Start the server, verify logs for successful tick, and test join from an external client.
Key Launch Parameters
- Port: default 14265 for hosting; query port default 14267.
- MaxPlayers: set to your server’s capacity, typically 8–20 depending on sub and entity count.
- Save interval and backup schedule: adjust to protect progress.
- Mods: list compatible server mods and disable client‑side only mods to avoid desync.
Configuration and Server Settings
Barotrauma offers server cfg files and in‑game commands to tune difficulty, enemy spawns, oxygen rates, and more. Editing settings before first launch helps align the experience with your crew’s expectations. For public servers, clearly document rules, voting options, and escalation procedures to maintain order.
Common Configuration Options
| Setting | Typical Value | Effect |
|---|---|---|
| GameMode | Campaign or Sandbox | Campaign uses mission scripts; Sandbox is freeplay. |
| Submarine | Filename, e.g., Hammerhead.xml | Determines layout, systems, and difficulty. |
| EnableVoting | true/false | Allows crew to propose and execute server changes. |
| KickAFKTimeout | 300–600 seconds | How long before idle players are removed. |
| SaveInterval | 300–600 seconds | How often the server state is written to disk. |
Port Forwarding and Network Checks
For players to join reliably, forward the hosting port and query port on your router and point them to the server machine’s local IP. On the server, confirm the Windows or Linux firewall allows inbound TCP/UDP on those ports. Use an online port checker from an external location and ask a friend to attempt a join; this catches NAT and ISP restrictions before your crew arrives.
Quick Port Checklist
- Router port forward: hosting port TCP/UDP (default 14265)
- Query port forward: default 14267 TCP/UDP
- Server firewall allow: same ports for the server executable
- Test from outside your LAN: use a friend or a portable hotspot device
Troubleshooting and Maintenance
Logs are your primary diagnostic tool; timestamped entries reveal tick freezes, mod load failures, or bandwidth spikes. Regular backups of the saves folder protect against corruption. If the server becomes unresponsive, a controlled restart with a fresh script usually clears stuck states. Keep the server build and mods updated in a test environment before applying changes to your main campaign server.
Signs of Trouble
- Clients unable to see server: check port forwarding and firewall, verify server is listening on the correct interface.
- Frequent ticks drops: reduce entity count, lower view distance, or upgrade CPU/RAM.
- Desync or kicks: ensure server and clients run the same mod list and same Barotrauma version.
Best Practices for Stable Sessions
Run the server process under a process monitor or a simple startup wrapper so it auto‑restarts on crash. Schedule regular backups and keep at least a few restore points. Use a consistent internal IP for the host to avoid address churn. For larger crews, consider a hosting provider that supports Linux and offers DDoS protection and automated backups, especially for public servers.
Wrap‑Up
Hosting a Barotrauma server is straightforward if you match hardware to your crew size, forward ports correctly, and keep mods and saves managed. Follow the step‑by‑step setup, tune settings for your playstyle, and watch logs to keep downtime low. With a stable server running, your crew can focus on exploration, engineering, and surviving the depths without interruptions.