Dedicated server guide

GoldenEye: Source

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

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

Build setup commands

Runtime familysteamcmd-linux

Declared runtimes: Docker or a Linux host process.

Network bindings

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

Mods and plugins

No mod support is declared in this snapshot; review the game guide before adding mods.

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

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

Host process

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

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

This guide covers the goldeneyesourceserver module in AlphaGSM.

goldeneyesourceserver is ENABLED (BYO). AlphaGSM can run a complete operator-staged GoldenEye: Source dedicated server tree through either the process or Docker runtime, but it does not download that tree during setup. This status does not claim a current integration pass. query and info use A2S.

Why Setup Is BYO

The previously automated download path is not a usable server artifact in CI:

the official /go/ endpoint returns a 241-byte HTML meta-refresh in both process and Docker CI
the authoritative ModDB release endpoint returns Cloudflare HTTP 403
the signed official object endpoint returns HTTP 401

AlphaGSM therefore does not substitute browser endpoints or attempt to resolve the official redirect during setup.

Required Tree

Stage one complete directory containing both parts of the official server installation:

the Source SDK Base 2007 Dedicated Server files from Steam AppID 310
the complete GoldenEye: Source 5.0.6 gesource content directory
a top-level steam_appid.txt containing exactly 310 as a required operator marker
an executable top-level srcds_run launcher

The important top-level layout is:

<install_dir>/
|-- srcds_run
|-- steam_appid.txt
|-- bin/
|-- hl2/
`-- gesource/
    |-- gameinfo.txt
    `-- maps/
        `-- ge_archives.bsp

Do not leave the Source 2007 base or gesource content under an extra archive wrapper directory. steam_appid.txt must contain only 310 (a trailing newline is fine). It is an accidental AppID mismatch guard and does not authenticate asset provenance or prove the staged base came from AppID 310. Providing the complete AppID 310 base remains the operator's responsibility. Setup also checks the other marker paths, executable permission, and realpath containment under <install_dir>; the operator-supplied tree must still contain the rest of the preserved server content.

Internal relative symlink chains are supported because they retain process/Docker parity. AlphaGSM deterministically inspects every symlink in the complete staged tree without following symlinked directories. Every link hop must remain inside <install_dir>; absolute links, cycles, and relative paths that leave the tree before re-entering it are rejected, including links outside the required marker paths.

Artifact Check

The known GoldenEye: Source dedicated-server artifact is version 5.0.6 with this SHA-256 digest:

79643189e9d6549e13ed9545d2277cb34bac05fff645d44d9de1f0ab030610d3

Manually compare the artifact digest before extracting and staging its complete gesource directory. AlphaGSM does not verify the artifact or treat this hash as proof of provenance; the digest is operator guidance.

Quick Start

Create the AlphaGSM server entry:

alphagsm mygoldeneye create goldeneyesourceserver

After staging the complete tree, validate it through setup:

alphagsm mygoldeneye setup 27015 /srv/goldeneye-source

Start and inspect the server:

alphagsm mygoldeneye start
alphagsm mygoldeneye status
alphagsm mygoldeneye query
alphagsm mygoldeneye info

Stop it:

alphagsm mygoldeneye stop

Runtime Notes

Module name: goldeneyesourceserver
Default port: 27015 over UDP and TCP
Default map: ge_archives
Default maximum players: 16
Docker family: steamcmd-linux
Process and Docker use the same srcds_run -game gesource game command
Generic in-game broadcast messages are not currently supported

Server variables

After create goldeneyesourceserver, inspect or change these with set:

alphagsm myserver set --list
alphagsm myserver set KEY --describe
alphagsm myserver set KEY VALUE

This module does not declare schema-backed keys. set --list after create is still the live source of truth.

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 helper checks known sentinels only and directs you to stage the complete compatible distribution manually; managed import is unavailable for this recipe. 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 GoldenEye: Source?

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

Which runtimes can run GoldenEye: Source?

Declared runtimes: Docker or a Linux host process.

Which ports does GoldenEye: Source use?

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

Can I add mods to GoldenEye: Source?

No mod support is declared in this snapshot; review the game guide before adding mods.

How should I back up GoldenEye: Source?

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