Repository navigation
Aloftserver
This guide covers the aloftserver module in AlphaGSM.
aloftserver 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-server-tree
prerequisite, while local runs remain process-backed by default unless you opt
into the Docker backend.
screen- an owned Aloft dedicated-server tree
- Python packages from
requirements.txt
Create the server:
alphagsm myaloftser create aloftserverRun setup:
alphagsm myaloftser setupaloftserver is supported in ENABLED (BYO) mode. Before setup or start,
copy an owned Aloft server tree into your chosen <install_dir>/ so
<install_dir>/AloftServerNoGuiLoad.ps1 exists.
Start it:
alphagsm myaloftser startCheck it:
alphagsm myaloftser statusStop it:
alphagsm myaloftser stopSetup configures:
- the game port (default 0 unless you set one explicitly)
- the install directory
Suggested flow:
alphagsm myaloftser create aloftserver
alphagsm myaloftser setup -n 27015 /path/to/aloftserver
# copy the owned Aloft server files into /path/to/aloftserver/
alphagsm myaloftser startalphagsm myaloftser update
alphagsm myaloftser backup- Module name:
aloftserver - Default port:
0unless explicitly set during setup
After create aloftserver, inspect or change these with set:
alphagsm myserver set --list
alphagsm myserver set KEY --describe
alphagsm myserver set KEY VALUEThis module does not declare schema-backed keys. set --list after
create is still the live source of truth.
-
Executable:
AloftServerNoGuiLoad.ps1 -
Location:
<install_dir>/AloftServerNoGuiLoad.ps1 - Engine: Custom
- Config file: See game module source
- Template: See server-templates/aloftserver/ if available
- Map directory: Check game documentation
- Mod directory: Check game documentation
- Workshop support: No
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.