This guide covers the battlecryoffreedomserver module in AlphaGSM.
battlecryoffreedomserver is currently PASSED on the documented Ubuntu 24.04 Linux baseline. The current GitHub integration lane still exercises both process and Docker runtime selection, and the validated Linux lifecycle stays aligned across both backends while local runs remain process-backed by default unless you opt into the Docker backend.
Requirements
screen
- Wine or Proton-GE on Linux
xvfb-run on Linux process runtimes
- SteamCMD runtime libraries (
lib32gcc-s1, lib32stdc++6)
- Python packages from
requirements.txt
Quick Start
Create the server:
alphagsm mybattlecr create battlecryoffreedomserver
Run setup:
alphagsm mybattlecr setup
Start it:
alphagsm mybattlecr start
Check it:
alphagsm mybattlecr status
Stop it:
alphagsm mybattlecr stop
Setup Details
Setup configures:
- the game port (default 8262)
- the configured query port (default 8263)
- the install directory
- SteamCMD downloads the server files
Useful Commands
alphagsm mybattlecr update
alphagsm mybattlecr backup
Notes
- Linux process launches require
xvfb-run during Wine initialization; the
shared Wine/Proton Docker image supplies the matching virtual display.
Native port configuration still needs verification against the shipped
ServerConfiguration.ini and launcher.
- Module name:
battlecryoffreedomserver
- Default game port: 8262
- Default query port: 8263
query, info, and info --json use the validated TCP health surface on
the managed game port.
Server variables
After create battlecryoffreedomserver, 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.
Developer Notes
Run File
- Executable:
BCoF.exe
- Location:
<install_dir>/BCoF.exe
- Engine: Custom (SteamCMD)
- SteamCMD App ID:
1362540
Server Configuration
Maps and Mods
- Map directory: Check game documentation
- Mod directory: Check game documentation
- Workshop support: No
Frequently asked questions
What support evidence is recorded for Battle Cry of Freedom?
Recorded lifecycle pass. Review the game guide for installation, account, licensing and runtime prerequisites before setup.
Which runtimes can run Battle Cry of Freedom?
Declared runtimes: Docker or a Linux host process. This module declares the Wine/Proton compatibility family.
Which ports does Battle Cry of Freedom use?
queryport/UDP, queryport/TCP, 8262/UDP, 8262/TCP. Named port values remain unknown; review the game guide and configuration for additional requirements.
Can I add mods to Battle Cry of Freedom?
No mod support is declared in this snapshot; review the game guide before adding mods.
How should I back up Battle Cry of Freedom?
A module-specific backup hook is declared. Review the game guide for its scope, restore procedure and shutdown requirements.