Dedicated server guide

Space Engineers

Manage seserver with AlphaGSM. Choose a runtime supported by the recorded module capabilities.

Recorded lifecycle pass · Support evidence: 2026-10-16.

Anonymous Workshop Process and Docker load passed for public dedicated-server content. Mod installation explains add, apply, and cleanup.

Build setup commands

Runtime familywine-proton

Declared runtimes: Docker or a Linux host process. This module declares the Wine/Proton compatibility family.

Network bindings

27016/UDP. Named port values remain unknown; review the game guide and configuration for additional requirements.

Mods and plugins

For Workshop content, use the setup builder with an actual game-compatible item ID; review supported content types in the guide. Anonymous Steam Workshop content for this module passed both process and Docker load. After setup, record an item with mod add workshop using a numeric ID or Steam Workshop URL, then run mod apply.

Backup hook

A module-specific backup hook is declared. Review the game guide for its scope, restore procedure and shutdown requirements.

Choose a supported runtime

Linux and Docker quickstart

Review the game guide for installation, account, licensing and runtime prerequisites before setup.

Docker

Complete interactive setup and review game-specific configuration before starting the server. Review the game guide for installation, account, licensing and runtime prerequisites before setup.

Start the Docker manager ./alphagsm-docker start
Create the game instance ./alphagsm-docker my-seserver create seserver
Complete interactive setup ./alphagsm-docker my-seserver setup
Start the game server ./alphagsm-docker my-seserver start
Check the instance status ./alphagsm-docker my-seserver status

./alphagsm-docker start
./alphagsm-docker my-seserver create seserver
./alphagsm-docker my-seserver setup
./alphagsm-docker my-seserver start
./alphagsm-docker my-seserver status

Host process

Complete interactive setup and review game-specific configuration before starting the server. Review the game guide for installation, account, licensing and runtime prerequisites before setup.

Create the game instance ./alphagsm my-seserver create seserver
Complete interactive setup ./alphagsm my-seserver setup
Check the host prerequisites ./alphagsm my-seserver doctor
Start the game server ./alphagsm my-seserver start
Check the instance status ./alphagsm my-seserver status

./alphagsm my-seserver create seserver
./alphagsm my-seserver setup
./alphagsm my-seserver doctor
./alphagsm my-seserver start
./alphagsm my-seserver status

This guide covers the seserver module in AlphaGSM.

seserver retains its prior PASSED support classification. GitHub validation uses the supported Docker wine-proton runtime. AlphaGSM passes Z:\srv\server as Wine's data directory so the dedicated server reads and writes inside the mounted installation.

Keen's dedicated-server guide defines -path as the directory used to load configuration and store server files. In Docker, this directory maps to the AlphaGSM installation on the host, so configuration, saves, and logs remain accessible there.

Workshop validation checkpoint

Native Workshop process and Docker integrations passed on 15 October 2026 in CI run 38748333313. Anonymous downloads succeeded for consumer app 244850, including the public Modular Encounters Systems server framework (31,485,392 bytes). Focused Docker integration and smoke subsequently passed the complete modded lifecycle; the later full run also passed process execution.

The adapter manages Steam mod references in the configured world's Sandbox.sbc and Sandbox_config.sbc, preserving operator entries. A missing default world is seeded from the dedicated server's own Empty World template; existing saves are preserved. Native world paths must stay inside the installation.

Process CI on 14 October reached the engine but stopped with a missing Visual C++ 2015–2019 x64 runtime message. Its fresh Proton prefix had bypassed the prepared Wine prefix in the runtime image. Process startup now prefers Wine and seeds only a fresh private prefix from /opt/wine when available; existing operator prefixes are preserved. Linux uses the vendor-supported -noconsole option. The correction still needs a fresh CI lifecycle pass. Existing Proton compatibility directories keep Proton when available; Wine fallback opens their existing inner pfx directory.

Focused Docker integration and Workshop smoke passed the strict execution checks on 14 October 2026. Process CI progressed past the runtime check but exited during Steam initialization after binding its port. Process launch now uses xvfb-run and the same X11/SDL drivers as the passing Docker runtime; CI run 38655040006 still exited before Game ready after that correction. CI run 38702811625 confirmed the passing Docker runtime uses the same Windows 7 and Mono 6.13.0 identity. Both failing process cases reported a missing Wine LocalAppDataLow folder followed by a handled access violation; no native crash dump was produced. The prepared prefix retained the image builder's .update-timestamp, which can cause Wine to skip shell-folder setup when the copy runs under another account. Fresh template copies now discard that copied marker so Wine initializes the receiving user's profile normally; the template and existing operator prefixes retain their markers. This correction passed process baseline and native MES integration in run 38748333313. See Wine's prefix update logic and shell-folder creation.

Workshop integration and opt-in smoke require both Game ready and the MES script's own MES Spawner / Startup: Active Debug ... initialization message. An item ID, mod name, download, or world configuration alone does not prove engine execution. Both runtime integrations passed these strict checks in run 38748333313.

Requirements

Docker
Python packages from requirements.txt

For a Linux process server, install Wine, xvfb-run, and the upstream Visual C++ runtime prerequisites in its private prefix. The AlphaGSM runtime image already prepares these prerequisites in /opt/wine; another prepared template may be selected with ALPHAGSM_WINEPREFIX_TEMPLATE. Existing prefixes are not changed by template seeding. Integration and smoke honor ALPHAGSM_TEST_RUNTIME_BACKEND=process|docker; public Workshop validation additionally requires ALPHAGSM_RUN_WORKSHOP=1.

Quick Start

Create the server:

alphagsm myseserver create seserver

Run setup:

alphagsm myseserver setup

Start it:

alphagsm myseserver start

Check it:

alphagsm myseserver status

Stop it:

alphagsm myseserver stop

Setup Details

Setup configures:

the game port (default 27016)
the install directory
SteamCMD downloads the Windows dedicated server files

Useful Commands

alphagsm myseserver update
alphagsm myseserver backup

Notes

Module name: seserver
Default port: 27016
Current validation status: PASSED 2026-05-31. Fresh focused integration now proves the old missing-binary disable note was stale in a narrower way: anonymous SteamCMD setup for app 298740 installs the real Windows dedicated payload, AlphaGSM launches the server through the shared Docker wine-proton runtime, and query, info, and info --json all succeed on the current generic udp health surface at the managed main game port.

Server variables

After create seserver, inspect or change these with set:

alphagsm myserver set --list
alphagsm myserver set KEY --describe
alphagsm myserver set KEY VALUE

This module does not declare schema-backed keys. set --list after create is still the live source of truth.

Developer Notes

Run File

Executable: DedicatedServer64/SpaceEngineersDedicated.exe
Location: <install_dir>/DedicatedServer64/SpaceEngineersDedicated.exe
Engine: Windows dedicated server via Wine/Proton
SteamCMD App ID: 298740

The validated Linux support path runs through AlphaGSM's Docker-backed wine-proton runtime image rather than a host screen session. The current checked-in integration and smoke coverage launch the Windows dedicated server from its required DedicatedServer64 working directory with -noconsole on Linux, -path, and -port, then validate the live contract on the managed main game port: query, info, and info --json all succeed as generic udp.

Server Configuration

Config files: generated by the dedicated server under the managed data path
Template: see the dedicated server's generated config after first launch

Maps and Mods

Map directory: Check game documentation
Mod directory: Check game documentation
Workshop support: Native world activation is implemented; live lifecycle validation is pending.

Configuration templates

Reference files from this source revision. Review paths, passwords and game-specific settings before use.

Share your server

Sector Alpha server directory

When your server is ready, you can publish its connection details and community information on Sector Alpha. Review your listing and keep the information current.

Find a community

Browse the directory for game servers and their published connection details.

Browse server directory

Publish your server

Prepare a name, address and description for your listing.

Publish a server

Manual server sharing instructions

Frequently asked questions

What support evidence is recorded for Space Engineers?

Recorded lifecycle pass. Review the game guide for installation, account, licensing and runtime prerequisites before setup.

Which runtimes can run Space Engineers?

Declared runtimes: Docker or a Linux host process. This module declares the Wine/Proton compatibility family.

Which ports does Space Engineers use?

27016/UDP. Named port values remain unknown; review the game guide and configuration for additional requirements.

Can I add mods to Space Engineers?

How should I back up Space Engineers?

A module-specific backup hook is declared. Review the game guide for its scope, restore procedure and shutdown requirements.

Source and support evidence

This guide mirrors AlphaGSM’s upstream documentation at 32cef5ba9e03053c8e461fffa0ba133b160b528d. Commands and prerequisites can change. Check current support notes before installation.

All game guides