Dedicated server guide

Call of Duty: World at War

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

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

Runtime familysteamcmd-linux

Declared runtimes: Docker or a Linux host process.

Network bindings

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

Mods and plugins

Mod support is declared; review the game guide for its providers and activation requirements.

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-codwawserver create codwawserver
Complete interactive setup ./alphagsm-docker my-codwawserver setup
Start the game server ./alphagsm-docker my-codwawserver start
Check the instance status ./alphagsm-docker my-codwawserver status

./alphagsm-docker start
./alphagsm-docker my-codwawserver create codwawserver
./alphagsm-docker my-codwawserver setup
./alphagsm-docker my-codwawserver start
./alphagsm-docker my-codwawserver 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-codwawserver create codwawserver
Complete interactive setup ./alphagsm my-codwawserver setup
Check the host prerequisites ./alphagsm my-codwawserver doctor
Start the game server ./alphagsm my-codwawserver start
Check the instance status ./alphagsm my-codwawserver status

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

This guide covers the codwawserver module in AlphaGSM.

Status: PASSED on 2026-05-30

Requirements

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 1

Use 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.

Quick Start

Create the server:

alphagsm mycodwawse create codwawserver

Run setup:

alphagsm mycodwawse setup

Start it:

alphagsm mycodwawse start

Check it:

alphagsm mycodwawse status

Stop it:

alphagsm mycodwawse stop

Setup Details

Setup 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-linux runtime

Useful Commands

alphagsm mycodwawse update
alphagsm mycodwawse backup

Notes

Module name: codwawserver
Default port: 28960
Current supported validation lane on Linux: Docker-backed steamcmd-linux
query, info, and info --json use the native Quake-style UDP status protocol on the managed game port.

Server variables

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.

Developer Notes

Run File

Executable: codwaw_lnxded
Location: <install_dir>/codwaw_lnxded
Engine: Custom

Server Configuration

Config file: <moddir>/server.cfg (default main/server.cfg)
set servername, set moddir, and set map rewrite <moddir>/server.cfg immediately 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

Maps and Mods

Map directory: <install_dir>/<moddir>/
Mod directory: <install_dir>/<moddir>/
Workshop support: No

Mod Sources

Call of Duty: World at War supports AlphaGSM-managed direct url mod sources for content-only .pk3 payloads.

Supported payload shapes:

a direct .pk3 URL
an archive containing bare .pk3 files 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

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 Call of Duty: World at War?

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

Which runtimes can run Call of Duty: World at War?

Declared runtimes: Docker or a Linux host process.

Which ports does Call of Duty: World at War use?

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

Can I add mods to Call of Duty: World at War?

Mod support is declared; review the game guide for its providers and activation requirements.

How should I back up Call of Duty: World at War?

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