Repository navigation
Codwawserver
This guide covers the codwawserver module in AlphaGSM.
Status: PASSED on 2026-05-30
- Docker recommended on Linux: branch-local or published
alphagsm-steamcmd-linux-runtime - Host/process fallback:
screen - Python packages from
requirements.txt
New AlphaGSM servers default to Internet dedicated mode (dedicated=2). Existing
servers without this setting retain their prior native launch behavior. The server
uses DemonWare authentication in this mode, so its DNS and service availability
can prevent startup before a playable map exists. For a local LAN server, select
the engine's supported LAN mode explicitly:
alphagsm mycodwawse set dedicated 1Use set dedicated 2 to restore Internet mode. These native mode values follow
GameServerManagers' CoDWaW configuration.
The disposable smoke and integration cases select LAN mode and still require
real Quake status on the exact managed port, mp_airfield, positive capacity,
and complete shutdown. These checks do not validate Internet authentication,
public listing, or remote-player joining. The LAN smoke passed in
run 38812335342,
after run 38775144746 reported a DemonWare DNS/authentication failure in the
implicit Internet mode.
Create the server:
alphagsm mycodwawse create codwawserverRun setup:
alphagsm mycodwawse setupStart it:
alphagsm mycodwawse startCheck it:
alphagsm mycodwawse statusStop it:
alphagsm mycodwawse stopSetup configures:
- the game port (default 28960)
- the install directory
- downloads and extracts the server archive
- the current validated Linux lane runs through the Docker-backed
steamcmd-linuxruntime
alphagsm mycodwawse update
alphagsm mycodwawse backup- Module name:
codwawserver - Default port: 28960
- Current supported validation lane on Linux: Docker-backed
steamcmd-linux -
query,info, andinfo --jsonuse the native Quake-style UDP status protocol on the managed game port.
After create codwawserver, 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 |
|---|---|---|---|
dedicated |
— | integer | Dedicated mode: 1 for LAN, 2 for Internet (default). Applied at launch. |
dir |
— | string | Install directory for the server. |
download_name |
— | string | Cached archive filename. |
exe_name |
— | string | Server executable filename. |
hostname |
servername, name | string | The advertised server name. |
moddir |
— | string | The active Call of Duty: World at War mod directory. Example: baseq3. |
port |
gameport | integer | The game port for the server. Example: 27960. |
startmap |
map, gamemap, level, world | string | The startup map. |
url |
— | string | Download URL for the server archive. |
-
Executable:
codwaw_lnxded -
Location:
<install_dir>/codwaw_lnxded - Engine: Custom
-
Config file:
<moddir>/server.cfg(defaultmain/server.cfg) -
set servername,set moddir, andset maprewrite<moddir>/server.cfgimmediately through the schema-backed config-sync path. - Runtime note: CI requires a native UDP status response for both process and Docker launches; a TCP listener does not establish game readiness.
- Template: See server-templates/codwawserver/ if available
-
Map directory:
<install_dir>/<moddir>/ -
Mod directory:
<install_dir>/<moddir>/ - Workshop support: No
Call of Duty: World at War supports AlphaGSM-managed direct url mod sources for content-only .pk3 payloads.
Supported payload shapes:
- a direct
.pk3URL - an archive containing bare
.pk3files at the archive root - an archive containing
<moddir>/<name>.pk3
AlphaGSM installs approved .pk3 content into the active moddir directory, tracks only the files it owns, and adds that active content directory to the managed backup targets.
Examples:
alphagsm mycodwawse mod add url https://example.com/mappack.pk3
alphagsm mycodwawse mod add url https://example.com/custom-content.zip
alphagsm mycodwawse mod apply
alphagsm mycodwawse mod cleanup