Dedicated server guide

Return to Castle Wolfenstein

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

Operator-provided prerequisites required · Support evidence: 2026-10-16.

Build setup commands

Runtime familyquake-linux

Declared runtimes: Docker or a Linux host process.

Network bindings

Default game port: 27960. Protocols and additional port values are unknown; review the game guide.

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

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

Host process

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

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

This guide covers the rtcwserver module in AlphaGSM.

rtcwserver 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
Python packages from requirements.txt
Original Return to Castle Wolfenstein assets in main/
- pak0.pk3 (the retail pack; the dedicated binary refuses to start without it)
- mp_bin.pk3
- mp_pak0.pk3 through mp_pak5.pk3
- mp_pakmaps0.pk3 through mp_pakmaps6.pk3

Quick Start

Create the server:

alphagsm myrtcwserv create rtcwserver

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

alphagsm steam-auth login owned your_steam_username
alphagsm myrtcwserv 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. Authenticated setup and the native process lifecycle were validated locally on 2026-10-16; Docker was not rerun in that local test.

Start it:

alphagsm myrtcwserv start

Check it:

alphagsm myrtcwserv status

Stop it:

alphagsm myrtcwserv stop

Setup Details

Setup configures:

the game port (default 27960)
the install directory
downloads the ioRTCW Linux engine archive and installs its dedicated executable and multiplayer game module
keeps retail pak0.pk3 and the multiplayer PK3 set intact
omits the known loose client executables, renderers and client-only engine modules

The dedicated server answers Quake UDP getstatus on its game port. query and info use that protocol.

This server is supported in ENABLED (BYO) mode. When using setup without an asset source or saved profile, copy retail main/pak0.pk3 and the original RTCW multiplayer PK3 set into the install's main/ directory. The public ioRTCW engine release is not enough by itself. Do not merge all of patch-data-141.zip: an owned 1.41 install already contains the matching multiplayer packs, and that archive also includes PunkBuster and client binaries.

Useful Commands

alphagsm myrtcwserv update
alphagsm myrtcwserv backup

Mod Sources

RTCW content management currently targets the active fs_game directory under the server root. By default that is main/, but if you set a custom fs_game value, AlphaGSM installs into that directory instead.

Current mod source support is direct url entries only.
mod add url <https-url> accepts direct .pk3 URLs and supported archive URLs such as .zip, .7z, or tar variants when the payload exposes either <fs_game>/<name>.pk3 or bare .pk3 files at the archive root.
mod cleanup removes only AlphaGSM-tracked .pk3 files and keeps its cache/state under .alphagsm/mods/rtcwserver/.
The first RTCW slice intentionally stops at .pk3 content and does not try to install arbitrary extracted scripts or binaries.

Examples:

alphagsm myrtcwserv mod add url https://example.invalid/mappack.zip
alphagsm myrtcwserv mod add url https://example.invalid/pak-custom.pk3
alphagsm myrtcwserv mod apply
alphagsm myrtcwserv mod cleanup

Notes

Module name: rtcwserver
Default port: 27960

Server variables

After create rtcwserver, 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.
`fs_game`	—	string	The active game/mod directory.
`hostname`	servername, name	string	The advertised server name.
`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.
`version`	—	string	Requested upstream release version.

Developer Notes

Run File

Executable: iowolfded.x86_64
Location: <install_dir>/iowolfded.x86_64
Engine: Custom
Owned assets required before start: main/mp_bin.pk3, main/mp_pak0.pk3 through main/mp_pak5.pk3, and main/mp_pakmaps0.pk3 through main/mp_pakmaps6.pk3

Server Configuration

Config file: <fs_game>/server.cfg (default main/server.cfg)
set servername, set fs_game, and set map rewrite <fs_game>/server.cfg immediately through the schema-backed config-sync path.
Template: See server-templates/rtcwserver/ if available

Maps and Mods

Map directory: <fs_game>/ (default main/)
Mod directory: <fs_game>/ (default main/)
Mod notes: AlphaGSM can now track direct .pk3 and archive url entries for RTCW, install approved .pk3 payloads into the active fs_game directory, and clean up only AlphaGSM-managed files from .alphagsm/mods/rtcwserver/.
Workshop support: No

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 Return to Castle Wolfenstein?

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

Which runtimes can run Return to Castle Wolfenstein?

Declared runtimes: Docker or a Linux host process.

Which ports does Return to Castle Wolfenstein use?

Default game port: 27960. Protocols and additional port values are unknown; review the game guide.

Can I add mods to Return to Castle Wolfenstein?

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

How should I back up Return to Castle Wolfenstein?

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