Swarm Hosts / Guides

OpenTTD

The managed image includes OpenTTD 15.3 and the OpenGFX 8.0 base set. It runs in dedicated server mode with persistent configuration and saves under /home/steam/openttd-data; no Steam account is required.

Quick facts

  • Gameplay: 3979/tcp
  • Discovery: 3979/udp
  • Persistent data: /home/steam/openttd-data
  • Minimum resources: 1 CPU and 512 MB RAM
  • Runtime: OpenTTD 15.3
  • Base graphics: OpenGFX 8.0

The guided launch form sets the initial server name, password, maximum clients, and public-listing choice. Existing openttd.cfg edits are preserved across restarts. After the file exists, change these values through Files & Backups → File Manager while the server is stopped; changing the initial form values does not rewrite the existing file.

Launch

  1. Open Launch and choose OpenTTD.
  2. Set the server name, optional player password, and maximum client count.
  3. Disable public listing if you do not want the server advertised in the server browser. Set a password to restrict who can join.
  4. Choose a healthy Swarm Host with at least 1 CPU and 512 MB RAM, then launch the server.

The first empty-volume start creates the persistent configuration and initial map automatically. Later starts preserve the existing configuration and saves.

Connect

After the Swarm Server becomes Running, copy its player hostname or IP and port from the connection details. In OpenTTD 15.3, open Multiplayer, choose Add server, and enter that host:port. The same assigned port carries TCP gameplay traffic and UDP discovery traffic.

Server Actions

OpenTTD does not currently offer game-specific Server Actions. Raw console and admin-protocol input are also unavailable.

Use the existing platform controls for:

  • resource settings and version management;
  • persistent-file access and backups;
  • logs and monitoring; and
  • start, stop, restart, and delete lifecycle operations.

Mods & Content

Manage NewGRF and scenario files manually. Check their licences and compatibility before uploading them, and keep a backup of the working setup. Automatic content discovery and updates are unavailable.

Troubleshooting

  • If the first start takes longer than expected, review the log for map generation and confirm the server eventually reports multiplayer online.
  • If direct entry cannot connect, verify the displayed player hostname and port and confirm the Swarm Server still reports Running.
  • Server Actions intentionally show as unavailable. Use typed settings, backups, files, logs, monitoring, and lifecycle controls instead of raw admin protocol input.