This guide covers the wreckfestserver module in AlphaGSM.
Status: PASSED for stock and native Workshop process/Docker lifecycles.
CI run 38775144746 on PR head 6a446839 also passed complete Docker Workshop
smoke, including registry proof, connectivity, shutdown and cleanup.
Workshop validation checkpoint
Native Workshop support passed process and Docker integration validation on
15 October 2026. Anonymous consumer-app 228380 downloads and fresh native
console inspection establish registration of events from the public
Crazy 2025 track pack,
including crazy_2000_classic, its reversed event, and its deathloop event.
The adapter preserves operator mod folders and config entries while managing
its own native mods= entries.
On Linux, query and info check UDP reachability on the configured query port.
They do not report track or player information. A silent UDP probe means no
port-unreachable error was received; it does not prove an application response
or measure round-trip latency. Current remote
diagnostics receive no A2S response over IPv4 or IPv6; the native server uses
THQN networking. The baseline additionally requires a fresh native
Server connected. log and running runtime, so reachability alone cannot pass startup.
Stock process and Docker integrations plus Docker smoke passed these checks.
Workshop checks still require fresh native track-registry output beyond the
baseline connectivity check. Both process and Docker native Workshop integrations
passed in CI run 38748333313, including fresh capture and complete shutdown;
download, configuration and old console snapshots cannot satisfy that proof.
A Unix terminal and Docker console FIFO alone did
not expose Wreckfest's separately allocated Win32 console in CI. Native
Workshop validation now attaches a small Windows probe to the exact running
server executable inside its private Wine prefix. The probe clears old display
contents, sends only tracks, and writes newly produced console rows to a
unique evidence file. Validation still requires the exact
crazy_2000_classic registry row. Capture retains every newly rendered row even
when the input cursor moves backwards. Parsing accepts native prompt redraws
in earlier stock rows while requiring the exact, unmodified Workshop identifier.
The full Docker Workshop
smoke case passed in run 38775144746
on PR head 6a446839, including profile initialization, fresh registry proof,
query/info, shutdown and cleanup. The same run retained passing process and
Docker native Workshop integrations.
Shutdown checks include owned Wine processes and TCP/UDP port closure.
Newly created AlphaGSM servers use <install_dir>/savegame/ and pass
--save-dir=savegame to the native server in both runtimes. This keeps
dedicated.ddst and modlist.mods with the installation and its backups,
independent of a Wine user's default profile. Existing files are retained.
Servers created before this change retain their previous implicit AppData
profile; installation, updates and startup do not migrate or reset that profile.
The vendor's installed initial_server_config.cfg documents this save-directory
option and requires the directory to exist before launch; the
AMP template
also creates and selects a dedicated save directory.
On a fresh mod profile, Wreckfest can persist the enabled mod list during the
first launch and load its tracks only after a restart. A
dedicated mod author
documents this restart requirement. After applying Workshop content to a newly
created server, run one start, wait for Server connected., then stop
before the final start. The smoke and integration cases perform this initialization
once when savegame/modlist.mods is absent. They require a native profile to
be written, full listener shutdown, fresh final startup, and the exact
crazy_2000_classic track response. They never retry a failed registry assertion
or create the engine's binary mod profile themselves.
Requirements
- Docker and AlphaGSM's
wine-proton image for the Docker runtime on Linux
- SteamCMD access for app
361580 with anonymous login
For the process runtime on Linux, use Wine or Proton-GE, xvfb-run, and
script from the bsdutils/util-linux package. The runtime image includes
these tools for Docker.
Native Workshop validation also needs the compiled
wreckfest-console-probe.exe, supplied at
/usr/local/lib/alphagsm/wreckfest-console-probe.exe in the runtime and CI
images. A host process validation run may set
ALPHAGSM_WRECKFEST_CONSOLE_PROBE to its compiled copy of
src/gamemodules/wreckfestserver/console_probe.c. The helper observes the
running server; AlphaGSM still performs its complete lifecycle.
The baseline integration case honors ALPHAGSM_TEST_RUNTIME_BACKEND from CI;
the smoke runner accepts process, docker, or auto through the same
variable. It defaults to Docker in GitHub Actions or when a runtime image is
provided, and to process elsewhere; explicit auto uses Docker.
Public Workshop checks additionally require
ALPHAGSM_RUN_WORKSHOP=1; baseline checks do not install a Workshop fixture.
Quick Start
Create the server:
alphagsm mywreckfes create wreckfestserver
Run setup:
alphagsm mywreckfes setup
Start it:
alphagsm mywreckfes start
Check it:
alphagsm mywreckfes status
alphagsm mywreckfes query
alphagsm mywreckfes info --json
Stop it:
alphagsm mywreckfes stop
Setup Details
Setup configures:
- the main game port (default
33540)
- the Steam query port (default
27016)
- the Steam networking port (default
27015)
- the install directory
- the managed
server_config.cfg
On Linux, AlphaGSM downloads the Windows dedicated payload for app 361580,
launches Wreckfest_x64.exe through the shared Docker wine-proton runtime,
and seeds server_config.cfg from the vendor initial_server_config.cfg when
needed.
Useful Commands
alphagsm mywreckfes update
alphagsm mywreckfes backup
alphagsm mywreckfes set port 33541
alphagsm mywreckfes set queryport 27017
alphagsm mywreckfes set steamport 27018
alphagsm mywreckfes set servername "AlphaGSM Wreckfest"
alphagsm mywreckfes set maxplayers 16
AlphaGSM keeps these upstream config keys in sync inside server_config.cfg:
game_portquery_portsteam_portserver_namepasswordmax_players
Notes
- Module name:
wreckfestserver
- Main game port default:
33540
- Linux query/info uses the limited UDP reachability surface described above.
- Workshop tests require the fresh engine track registry from an AlphaGSM console command.
Neither a config echo nor an open TCP port satisfies the Workshop check.
Server variables
After create wreckfestserver, inspect or change these with set:
alphagsm myserver set --list
alphagsm myserver set KEY --describe
alphagsm myserver set KEY VALUE
| Key |
Aliases |
Type |
What it does |
dir |
— |
string |
Install directory for the server. |
exe_name |
— |
string |
Server executable filename. |
maxplayers |
users |
integer |
The maximum number of players allowed on the server. |
port |
gameport |
integer |
The main game port for the Wreckfest server. |
queryport |
— |
integer |
The Steam query port for the Wreckfest server. |
servername |
hostname, name |
string |
The advertised Wreckfest server name. |
serverpassword |
sv_password, password |
string |
Password required to join the Wreckfest server. Stored as a secret. |
steamport |
— |
integer |
The Steam networking port for the Wreckfest server. |
Developer Notes
Run File
- Executable:
Wreckfest_x64.exe
- Fallback executable:
Wreckfest.exe
- Location:
<install_dir>/Wreckfest_x64.exe
- Runtime: Docker
wine-proton on Linux
- SteamCMD App ID:
361580
Server Configuration
Maps and Mods
- Map rotation: configure through
server_config.cfg
- Mod directory:
<install_dir>/mods/
- Workshop support: use Wreckfest's native mod loading rules