Dedicated server guide

Call of Duty 2

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

Operator-provided prerequisites required · 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

Operator-provided game files, runtime or other prerequisites are required; follow the game guide before setup.

Docker

Complete interactive setup and review game-specific configuration before starting the server. Operator-provided game files, runtime or other prerequisites are required; follow the game guide before setup.

Start the Docker manager ./alphagsm-docker start
Create the game instance ./alphagsm-docker my-cod2server create cod2server
Complete interactive setup ./alphagsm-docker my-cod2server setup
Start the game server ./alphagsm-docker my-cod2server start
Check the instance status ./alphagsm-docker my-cod2server status

./alphagsm-docker start
./alphagsm-docker my-cod2server create cod2server
./alphagsm-docker my-cod2server setup
./alphagsm-docker my-cod2server start
./alphagsm-docker my-cod2server status

Host process

Create the game instance ./alphagsm my-cod2server create cod2server
Complete interactive setup ./alphagsm my-cod2server setup
Check the host prerequisites ./alphagsm my-cod2server doctor
Start the game server ./alphagsm my-cod2server start
Check the instance status ./alphagsm my-cod2server status

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

This guide covers the cod2server module in AlphaGSM.

cod2server is currently ENABLED (BYO) on the documented Ubuntu 24.04 Linux baseline. The current GitHub integration lane still exercises both process and Docker runtime selection around that owned-base-assets prerequisite, while local runs remain process-backed by default unless you opt into the Docker backend.

Requirements

screen
owned base-game multiplayer assets that include main/localized_*.iwd and main/default_localize_mp.cfg
Python packages from requirements.txt

Quick Start

Create the server:

alphagsm mycod2serv create cod2server

For an owned Steam copy, sign in once and let setup acquire the declared files:

alphagsm steam-auth login owned your_steam_username
alphagsm mycod2serv setup --auth-profile owned

Enter credentials only at the local SteamCMD prompts. For an existing local Steam library, use setup --steam-dir /path/to/SteamLibrary/steamapps instead. Local process setup with an entitled profile was validated on 2026-10-16. Query and info use Quake UDP getstatus on the game port. Docker was not rerun.

Start it:

alphagsm mycod2serv start

Check it:

alphagsm mycod2serv status

Stop it:

alphagsm mycod2serv stop

Setup Details

Setup configures:

the game port (default 28960)
the install directory
downloads and extracts the official Linux dedicated-server archive
still requires copied retail/localized multiplayer assets before the server can finish startup

cod2server is supported in ENABLED (BYO) mode. AlphaGSM installs the Linux dedicated binary for you, but the official archive still does not include the localized retail files the server expects at startup.

If using setup without an asset source or saved profile, before start copy the required owned files from a legitimate Call of Duty 2 installation into the AlphaGSM server tree:

<install_dir>/main/localized_*.iwd
<install_dir>/main/default_localize_mp.cfg

Manual-copy alternative:

alphagsm mycod2serv create cod2server
alphagsm mycod2serv setup
cp /path/to/cod2/main/localized_*.iwd <install_dir>/main/
cp /path/to/cod2/main/default_localize_mp.cfg <install_dir>/main/
alphagsm mycod2serv start

If startup still reports missing localized assets, check that the files landed under the server's main/ directory, not a mod directory such as uo/ or a custom moddir.

Useful Commands

alphagsm mycod2serv update
alphagsm mycod2serv backup

Notes

Module name: cod2server
Default port: 28960
Current blocker for anonymous installs: the official dedicated archive does not ship main/localized_*.iwd or main/default_localize_mp.cfg

Server variables

After create cod2server, 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.
`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 2 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: cod2_lnxded
Location: <install_dir>/cod2_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.
Setup stages the upstream gcc 3.2 libraries beside cod2_lnxded and starts it with LD_LIBRARY_PATH=., fs_basepath ., and fs_homepath . so the dedicated server does not use ~/.callofduty2.
Owned base assets still required: main/localized_*.iwd, main/default_localize_mp.cfg
Copy target before first start: <install_dir>/main/
Template: See server-templates/cod2server/ if available

Maps and Mods

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

Mod Sources

Call of Duty 2 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 mycod2serv mod add url https://example.com/mappack.pk3
alphagsm mycod2serv mod add url https://example.com/custom-content.zip
alphagsm mycod2serv mod apply
alphagsm mycod2serv mod cleanup

BYO file helper

Inspect this game's required files, source instructions and destinations with alphagsm <server-name> assets requirements; check the declared files with alphagsm <server-name> assets check. File checks do not establish game readiness. The preferred Steam-owned path is alphagsm steam-auth login owned <username>, then alphagsm <server-name> setup --auth-profile owned. Setup remembers the profile name and fetches missing required files before installing the engine. Use setup --steam-dir /path/to/SteamLibrary/steamapps to import from an existing Steam library instead. Direct file acquisition remains available through assets fetch steam-owned --auth-profile owned. Authenticated downloads remain unverified here. See BYO files and private SteamCMD acquisition.

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 2?

Operator-provided prerequisites required. Operator-provided game files, runtime or other prerequisites are required; follow the game guide before setup.

Which runtimes can run Call of Duty 2?

Declared runtimes: Docker or a Linux host process.

Which ports does Call of Duty 2 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 2?

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

How should I back up Call of Duty 2?

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