Dedicated server guide

ET: Legacy

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

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

Host process

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

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

This guide covers the etlegacyserver module in AlphaGSM.

etlegacyserver 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
Stock Wolfenstein: Enemy Territory multiplayer packs in etmain/
- Required files: etmain/pak0.pk3, etmain/pak1.pk3, and etmain/pak2.pk3
- setup stages only those three packs from the official Splash Damage freeware archive
- pak0.pk3 alone is not enough

Quick Start

Create the server:

alphagsm myetlegacy create etlegacyserver

Run setup:

alphagsm myetlegacy setup

Start it:

alphagsm myetlegacy start

Check it:

alphagsm myetlegacy status

Stop it:

alphagsm myetlegacy stop

Setup Details

Setup configures:

the game port (default 27960)
the install directory
downloads and extracts the ET: Legacy engine archive
stages etmain/pak0.pk3, etmain/pak1.pk3, and etmain/pak2.pk3 from the official Splash Damage freeware full-game archive
does not install the original client, PunkBuster, videos, or etkey tools
installs the public ET: Legacy engine and legacy/ mod bundle

This server is supported in ENABLED (BYO) mode. The engine download does not include the stock packs. setup copies only the three multiplayer packs out of the official freeware archive. A tree that contains pak0.pk3 without pak1.pk3 and pak2.pk3 is still rejected. Without etmain/pak0.pk3, the dedicated server exits at FS_InitFilesystem: Original game data files not found.

A local process run on 2026-10-16 answered Quake status on UDP 57831 (oasis, hostname ET: Legacy Host, 0/24) and stopped. Docker was not rerun. The stock multiplayer maps in those packs are battery, fueldump, goldrush, oasis, radar, and railgun.

Useful Commands

alphagsm myetlegacy update
alphagsm myetlegacy backup
alphagsm myetlegacy set servername "AlphaGSM ET"
alphagsm myetlegacy set port 27961

set servername and set port rewrite etl_server.cfg immediately through the schema-backed config-sync path.

Mod Sources

ET: Legacy content management currently targets the active fs_game directory under the server root. By default that is legacy/, 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/etlegacyserver/.
The first ET: Legacy slice intentionally stops at .pk3 content and does not try to install arbitrary extracted scripts or binaries.

Examples:

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

Notes

Module name: etlegacyserver
Default port: 27960

Server variables

After create etlegacyserver, 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
`configfile`	—	string	Server config file to exec on startup.
`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. Example: `baseq3`.
`hostname`	servername, name	string	The advertised server name.
`port`	gameport	integer	The game port for the server.
`url`	—	string	Download URL for the server archive.
`version`	—	string	Requested upstream release version.

Developer Notes

Run File

Executable: etlded.x86_64
Location: <install_dir>/etlded.x86_64
Engine: Custom
Stock packs staged by install: etmain/pak0.pk3, etmain/pak1.pk3, and etmain/pak2.pk3 from the official Splash Damage freeware archive. pak0.pk3 alone is rejected.

Server Configuration

Config file: etl_server.cfg
Template: See server-templates/etlegacyserver/ if available
Schema-backed sync: AlphaGSM keeps sv_hostname and net_port aligned with set

Maps and Mods

Map directory: <fs_game>/ (default legacy/)
Mod directory: <fs_game>/ (default legacy/)
Mod notes: AlphaGSM can now track direct .pk3 and archive url entries for ET: Legacy, install approved .pk3 payloads into the active fs_game directory, and clean up only AlphaGSM-managed files from .alphagsm/mods/etlegacyserver/.
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. This module has an allowlisted local import recipe. Use its source instructions to prepare the required data before importing. See BYO files and private SteamCMD acquisition.

Configuration templates

Reference files from this source revision. Review paths, passwords and game-specific settings before use.

etl_server.cfg

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 ET: Legacy?

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

Which runtimes can run ET: Legacy?

Declared runtimes: Docker or a Linux host process.

Which ports does ET: Legacy use?

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

Can I add mods to ET: Legacy?

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

How should I back up ET: Legacy?

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