This guide covers the returntomoriaserver module in AlphaGSM.
Status: PASSED on 2026-05-29
The validated Ubuntu 24.04 path is one Docker-default wine-proton lifecycle.
The current Proton preference, readiness, and redacted-diagnostics correction
is pending replacement GitHub CI and does not record a new pass.
Both the process command wrapper and Docker container specification prefer the
same Proton launch policy, so the game module does not choose a different
Windows compatibility path based on the selected runtime.
Requirements
- Docker
- SteamCMD runtime libraries (
lib32gcc-s1, lib32stdc++6)
- Python packages from
requirements.txt
Quick Start
Create the server:
alphagsm myreturnto create returntomoriaserver
Run setup:
alphagsm myreturnto setup
Start it:
alphagsm myreturnto start
Check it:
alphagsm myreturnto status
Stop it:
alphagsm myreturnto stop
Setup Details
Setup configures:
- the game port (default 7777)
- the install directory
- SteamCMD downloads the server files
- AlphaGSM writes
MoriaServerConfig.ini before first launch and keeps ListenPort,
AdvertiseAddress, and the world name aligned with the managed datastore
- readiness first follows
Moria/Config/status.json reporting running, with
both filename casings and Moria/Saved/Config/status.json retained for
Windows/Linux and legacy-build variants,
then AlphaGSM validates the exact managed runtime-resolved udp port through
info --json
Useful Commands
alphagsm myreturnto update
alphagsm myreturnto backup
Notes
- Module name:
returntomoriaserver
- Default port: 7777
query, info, and info --json use generic UDP reachability on the managed game port
- AlphaGSM keeps
Console/Enabled enabled in its managed config because the server uses the interactive console while loading a world; the shared Xvfb runtime supplies the headless display in Docker and Status.json remains the readiness source.
- the default
AdvertiseAddress is local; for internet-hosted servers set it to auto
or your public IP before sharing the server externally
- Docker supplies a private Xvfb display for the Windows console payload; the
process command stays on the same Proton launch path.
- readiness failures print redacted managed-runtime diagnostics. Invite and
join codes from
Status.json are not retained in failure state or output.
Server variables
After create returntomoriaserver, 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:
MoriaServer.exe
- Location:
<install_dir>/MoriaServer.exe
- Engine: Custom (SteamCMD)
- SteamCMD App ID:
3349480
Server Configuration
- Config files:
MoriaServerConfig.ini
- Runtime status file: current builds write
Moria/Config/Status.json; older
builds may write Moria/Saved/Config/Status.json. Smoke and integration tests
accept both before validating AlphaGSM's runtime-resolved UDP health surface.
- Template: See server-templates/returntomoriaserver/ if available
Maps and Mods
- Map directory: Check game documentation
- Mod directory: Check game documentation
- Workshop support: No