Dedicated server guide

NS2: Combat

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

Not recorded in the support snapshot · Support evidence: 2026-10-16.

Build setup commands

Runtime familyunknown

Runtime support is unknown in this snapshot; review the game guide.

Network bindings

Port numbers and protocols are unknown in this snapshot; review the game guide and configuration.

Mods and plugins

Mod support is unknown in this snapshot; review the game guide before adding mods.

Backup hook

Backup hook support is unknown in this snapshot; review the game guide for backup and restore procedures.

Choose a supported runtime

Linux and Docker quickstart

This guide has no recorded support entry. Review the upstream guide and current support notes before attempting setup.

Use the upstream guide and support notes to review this module’s requirements before attempting installation or launch.

This guide covers the ns2cserver module in AlphaGSM.

The checked-in NS2: Combat lifecycle is wired for both process and Docker runtimes on the documented Ubuntu 24.04 Linux baseline. Its corrected launch/A2S contract is pending replacement GitHub validation, so no new PASSED tracker result is recorded for this change.

Requirements

Process runtime: screen
Docker runtime: Docker and the shared steamcmd-linux runtime image
SteamCMD runtime libraries (lib32gcc-s1, lib32stdc++6)
Python packages from requirements.txt

Quick Start

Create the server:

alphagsm myns2c create ns2cserver

Run setup:

alphagsm myns2c setup

Start it:

alphagsm myns2c start

Check it:

alphagsm myns2c status
alphagsm myns2c query
alphagsm myns2c info

Stop it:

alphagsm myns2c stop

Setup Details

Setup configures:

the game port (default 27015)
the install directory
SteamCMD downloads the server files
a per-instance config directory at <install_dir>/<server_name>/
a workshop storage directory at <install_dir>/<server_name>/Workshop
managed claims for game UDP, game + 1 UDP, and web-admin TCP

Useful Commands

alphagsm myns2c update
alphagsm myns2c backup

Notes

Module name: ns2cserver
Game: NS2: Combat
Engine: Spark
SteamCMD App ID: 313900
Executable: <install_dir>/ia32/ns2combatserver_linux32
Default map: co_core
Process and Docker launch identical game argv as ./ns2combatserver_linux32 from <install_dir>/ia32, which preserves the executable's ../bin/ship dependency lookup
AlphaGSM probes exact runtime-resolved A2S on game port + 1
Web admin is enabled by default on httpport 8080
Current correction status: replacement GitHub validation pending

Server variables

After create ns2cserver, 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.
`exe_name`	—	string	Server executable filename.
`httppassword`	—	string	Web admin password.
`httpport`	—	integer	Web admin port.
`httpuser`	—	string	Web admin username.
`maxplayers`	users	integer	Maximum allowed players.
`port`	gameport	integer	Primary gameplay port.
`servername`	hostname, name	string	The advertised server name.
`startmap`	map, gamemap, level, world	string	Startup map.

Developer Notes

Run File

Executable: ia32/ns2combatserver_linux32
Location: <install_dir>/ia32/ns2combatserver_linux32
Working directory: <install_dir>/ia32
Launch path: ./ns2combatserver_linux32
Engine: Spark
SteamCMD App ID: 313900

Server Configuration

Config path: <install_dir>/<server_name>/
Workshop storage: <install_dir>/<server_name>/Workshop
Runtime argv paths: ../<server_name> and ../<server_name>/Workshop
Key settings:
- port — Game port (default: 27015)
- httpport — Web admin port (default: 8080)
- maxplayers — Maximum players (default: 24)
- startmap — Starting map (default: co_core)

Maps and Mods

Map selection: via startmap
Mod directory: <install_dir>/<server_name>/Workshop
Workshop support: manual storage path only in this first AlphaGSM slice

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 NS2: Combat?

Not recorded in the support snapshot. This guide has no recorded support entry. Review the upstream guide and current support notes before attempting setup.

Which runtimes can run NS2: Combat?

Runtime support is unknown in this snapshot; review the game guide.

Which ports does NS2: Combat use?

Port numbers and protocols are unknown in this snapshot; review the game guide and configuration.

Can I add mods to NS2: Combat?

Mod support is unknown in this snapshot; review the game guide before adding mods.

How should I back up NS2: Combat?

Backup hook support is unknown in this snapshot; review the game guide for backup and restore procedures.

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