This guide covers the ecoserver module in AlphaGSM.
Status: PASSED on 2026-05-29 via the shared steamcmd-linux Docker runtime.
GitHub CI keeps one Docker-default lifecycle because a stock Ubuntu 24.04
process host without libgdiplus correctly fails the runtime preflight.
Requirements
docker for the validated Linux runtime path
- For local process launches on Linux, install
libgdiplus plus the usual SteamCMD runtime libraries (lib32gcc-s1, lib32stdc++6)
- Python packages from
requirements.txt
Quick Start
Create the server:
alphagsm myecoserve create ecoserver
Run setup:
alphagsm myecoserve setup
Start it:
alphagsm myecoserve start
Check it:
alphagsm myecoserve status
Stop it:
alphagsm myecoserve stop
Setup Details
Setup configures:
- the game port (default 3000)
- the install directory
- SteamCMD downloads the server files
- AlphaGSM writes
Configs/Network.eco so the managed main port stays in sync with Eco's derived web, RCON, and Steam side ports
Useful Commands
alphagsm myecoserve update
alphagsm myecoserve backup
Notes
- Module name:
ecoserver
- Default port: 3000
- AlphaGSM launches Eco in
-offline mode for anonymous SteamCMD installs
query, info, and info --json use Eco's live generic tcp surface on the managed main port
- The current validated stop path may fall back to AlphaGSM's built-in forced kill after the normal grace period if Eco ignores the generic console shutdown command
Server variables
After create ecoserver, 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:
EcoServer
- Location:
<install_dir>/EcoServer
- Engine: Custom (SteamCMD)
- SteamCMD App ID:
739590
Server Configuration
Maps and Mods
- Map directory: Check game documentation
- Mod directory: Check game documentation
- Workshop support: No
Frequently asked questions
What support evidence is recorded for Eco?
Recorded lifecycle pass. Review the game guide for installation, account, licensing and runtime prerequisites before setup.
Which runtimes can run Eco?
Declared runtimes: Docker or a Linux host process.
Which ports does Eco use?
3000/UDP, 3000/TCP, webport/TCP, rconport/TCP, steamport/UDP. Named port values remain unknown; review the game guide and configuration for additional requirements.
Can I add mods to Eco?
No mod support is declared in this snapshot; review the game guide before adding mods.
How should I back up Eco?
A module-specific backup hook is declared. Review the game guide for its scope, restore procedure and shutdown requirements.