Alpha Game Server Manager

Dedicated server guide

BattleBit Remastered

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

Authentication required · Support evidence: 2026-10-16.

Build setup commands
Runtime familywine-proton

Declared runtimes: Docker or a Linux host process. This module declares the Wine/Proton compatibility family.

Network bindings

29992/UDP, 29992/TCP. Named port values remain unknown; review the game guide and configuration for additional requirements.

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

Authentication is required before installation; follow the game guide for credentials, ownership and login prerequisites.

Docker

Complete interactive setup and review game-specific configuration before starting the server. Authentication is required before installation; follow the game guide for credentials, ownership and login prerequisites.

  1. Start the Docker manager ./alphagsm-docker start
  2. Create the game instance ./alphagsm-docker my-battlebitserver create battlebitserver
  3. Complete interactive setup ./alphagsm-docker my-battlebitserver setup
  4. Start the game server ./alphagsm-docker my-battlebitserver start
  5. Check the instance status ./alphagsm-docker my-battlebitserver status
./alphagsm-docker start
./alphagsm-docker my-battlebitserver create battlebitserver
./alphagsm-docker my-battlebitserver setup
./alphagsm-docker my-battlebitserver start
./alphagsm-docker my-battlebitserver status

Host process

Complete interactive setup and review game-specific configuration before starting the server. Authentication is required before installation; follow the game guide for credentials, ownership and login prerequisites.

  1. Create the game instance ./alphagsm my-battlebitserver create battlebitserver
  2. Complete interactive setup ./alphagsm my-battlebitserver setup
  3. Check the host prerequisites ./alphagsm my-battlebitserver doctor
  4. Start the game server ./alphagsm my-battlebitserver start
  5. Check the instance status ./alphagsm my-battlebitserver status
./alphagsm my-battlebitserver create battlebitserver
./alphagsm my-battlebitserver setup
./alphagsm my-battlebitserver doctor
./alphagsm my-battlebitserver start
./alphagsm my-battlebitserver status

This guide covers the battlebitserver module in AlphaGSM.

Support Status

battlebitserver is supported in ENABLED (AUTH) mode.

AlphaGSM can:

  • install the BattleBit dedicated payload anonymously from SteamCMD app 689410
  • manage the Linux runtime through the shared Docker-backed wine-proton lane
  • start the real Windows dedicated binary BattleBit.exe

The remaining prerequisite is provider-backed BattleBit community-server provisioning. Before start, you must provide:

  • apiendpoint set to the BattleBit community-server API host:port
  • optionally apitoken if your community-server API requires token-based verification
  • a host that is already approved for BattleBit community-server hosting under the current BattleBit agreement/TOS flow

Quick Start

Create the server:

alphagsm mybattlebi create battlebitserver

Run setup:

alphagsm mybattlebi setup

Set the required BattleBit community-server API endpoint:

alphagsm mybattlebi set apiendpoint HOST_OR_IP:PORT

If your provider flow requires a token, set it too:

alphagsm mybattlebi set apitoken YOUR_OPTIONAL_API_TOKEN

Start it:

alphagsm mybattlebi start

Check it:

alphagsm mybattlebi status

Stop it:

alphagsm mybattlebi stop

Requirements

  • Docker for the supported Linux runtime path
  • SteamCMD
  • BattleBit community-server provisioning/approval
  • a reachable BattleBit community-server API endpoint

Setup Details

Setup configures:

  • the main game port (default 29992)
  • the install directory
  • the Windows dedicated payload from Steam app 689410

The supported Linux path then runs BattleBit.exe under the shared wine-proton runtime.

Provider Prerequisites

BattleBit now installs anonymously, but a fresh server still will not boot through AlphaGSM without a real community-server API endpoint.

AlphaGSM expects:

  • apiendpoint
  • optional apitoken

Set them with:

alphagsm mybattlebi set apiendpoint HOST_OR_IP:PORT
alphagsm mybattlebi set apitoken YOUR_OPTIONAL_API_TOKEN

If apiendpoint is missing, AlphaGSM fails fast at start with an ENABLED (AUTH) message instead of pretending the server is unsupported.

Useful Commands

alphagsm mybattlebi update
alphagsm mybattlebi backup
alphagsm mybattlebi set apiendpoint HOST_OR_IP:PORT
alphagsm mybattlebi set apitoken YOUR_OPTIONAL_API_TOKEN

Notes

  • Module name: battlebitserver
  • Steam App ID: 689410
  • Default game port: 29992
  • Default executable: BattleBit.exe

Server variables

After create battlebitserver, 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
apiendpoint — string BattleBit community server API endpoint in host:port form.
apitoken — string Optional BattleBit community server API token. Stored as a secret.
dir — string Install directory for the server.
exe_name — string Server executable filename.
maxplayers users integer The maximum number of players.
port gameport integer The game port for the BattleBit community server.
servername name, hostname string The advertised BattleBit community server name.

Developer Notes

Run File

  • Executable: BattleBit.exe
  • Location: <install_dir>/BattleBit.exe
  • Engine: Windows dedicated payload run through the shared Wine/Proton runtime on Linux
  • SteamCMD App ID: 689410

Runtime Notes

  • The old “missing Linux dedicated binary” disabled note was stale: the anonymous payload is real, but it is Windows-only.
  • The supported Linux contract is the shared Docker-backed wine-proton runtime, not a fake native binary.
  • BattleBit community-server provisioning remains the blocker to a fully green automated lifecycle.

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 BattleBit Remastered?

Authentication required. Authentication is required before installation; follow the game guide for credentials, ownership and login prerequisites.

Which runtimes can run BattleBit Remastered?

Declared runtimes: Docker or a Linux host process. This module declares the Wine/Proton compatibility family.

Which ports does BattleBit Remastered use?

29992/UDP, 29992/TCP. Named port values remain unknown; review the game guide and configuration for additional requirements.

Can I add mods to BattleBit Remastered?

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

How should I back up BattleBit Remastered?

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