Keep the next operation predictable.

A small command vocabulary

Examples here use the host entry point ./alphagsm. In the Docker-manager workflow, use ./alphagsm-docker with the same server command arguments. Consult the complete command reference and ./alphagsm mymc --help for exact options.

Inspect before changing

./alphagsm mymc status
./alphagsm mymc query
./alphagsm mymc info --json
./alphagsm mymc doctor
./alphagsm mymc logs -n 200
./alphagsm '*' list

Quoted '*' selects this user's managed servers rather than shell filenames. Use the game's diagnostic output and tracker notes together. For the subprocess backend, connect follows logs; use send for console input.

Discover settings instead of guessing

./alphagsm mytf2 set --list
./alphagsm mytf2 set gamemap --describe
./alphagsm mytf2 set gamemap --values
./alphagsm mytf2 set gamemap cp_dustbowl

Settings are module-specific. Use --describe before changing a value. Minecraft Vanilla version and download URL are setup options, rather than arbitrary set keys.

Update the game and the manager separately

Steam game files

./alphagsm mytf2 update
./alphagsm mytf2 update -v -r

A normal Steam update stops a running server and leaves it stopped. -v validates files and -r restarts afterwards. The flags and update path vary for non-Steam games.

AlphaGSM itself

./alphagsm self-update --check
./alphagsm self-update

Tracked stable Git checkouts update by fast-forwarding; the updater refuses dirty, diverged, detached, or development-branch checkouts. Standalone releases follow their own asset/checksum path. Read the update guide before changing an installation.

Backups, restore, and world management

./alphagsm mymc backup
./alphagsm mymc restore
./alphagsm mymc restore backup-filename.zip

The first restore command lists available backups. A restore stops the server and restores the selected ZIP archive; treat it as a state-changing operation. Keep a separate copy of valuable data before recovery. Backup hooks vary by module: TF2 exposes the shared command but currently has no backup hook.

Server-side mods and plugins

The reproducible TF2 example uses AlphaGSM's checked-in manifest after completing server setup:

./alphagsm mytf2 mod add manifest metamod
./alphagsm mytf2 mod add manifest sourcemod
./alphagsm mytf2 mod apply
./alphagsm mytf2 mod list

mod add records desired content; mod apply installs it and tracks owned files. mod cleanup removes AlphaGSM-owned addon files. Supported providers and content types vary by module. TF2 accepts validated multiplayer maps from Workshop items and collections, applies them through its native loader, and selects them with set map workshop/ITEM_ID; cosmetic uploads are rejected. Mod installation covers manifests, plugins, providers, and cleanup. Anonymous Workshop has the per-game commands for the 21 process and Docker passes. The upstream reference remains Installing Mods. Framework packs such as Oxide/uMod, Carbon, BepInEx, and CounterStrikeSharp are module-specific; use the matching game guide for installation and runtime requirements. To have Cursor, Claude, or Codex run these commands, start from the AI agent skill catalogue.

Share a server on Sector Alpha

Make a publicly reachable game server discoverable through the Sector Alpha setup wizard. Sign in, add the game, public hostname and query port, complete the SA- ownership check, then choose List in directory. Supported games need an anonymous status protocol that Sector Alpha can query.

Sector Alpha queries the game endpoint to check its status. Verification and publication are separate steps. Follow the server listing guide for the challenge field and player-port settings, or browse the public server directory.

Troubleshooting by symptom

Still blocked? Write a useful issue report with the command, module, runtime, versions, and redacted logs.