Blade Symphony server

Run with Docker

First install Docker Engine and the Compose plugin on your Linux host. Run the commands below from your project directory with a user allowed to access Docker; otherwise prefix Docker commands with sudo. The container manages its own linuxgsm user.

The bs image has LinuxGSM and every dependency for Blade Symphony already installed on Ubuntu 26.04. On first start it downloads the game server, then keeps it updated.

1. Create compose.yaml

services:
  bsserver:
    image: ghcr.io/gameservermanagers/gameserver:bs
    container_name: bsserver
    restart: unless-stopped
    network_mode: host
    volumes:
      - ./bsserver:/data
    environment:
      - UPDATE_CHECK=60

Also published on Docker Hub as gameservermanagers/gameserver:bs. Prefer docker run? See Docker help.

2. Add your Steam login before the first start

Create the LinuxGSM config file inside the data directory. LinuxGSM reads it on first start and keeps it on updates.

mkdir -p bsserver/config-lgsm/bsserver
nano bsserver/config-lgsm/bsserver/common.cfg

steamuser="username"
steampass='password'
gslt="YOUR_TOKEN"

3. Start it

docker compose up -d
docker compose logs -f

The first start installs the server, which can take a while for large games. When it is ready the log shows the server details, including ports and passwords.

Ports

With network_mode: host the server uses the host's ports directly, so there is nothing to map. Open them in your firewall.

Defaults from the LinuxGSM config. Run details to see every port and its protocol.

Manage the server

Show details, ports and passwords

docker exec -it --user linuxgsm bsserver ./bsserver details

Copy

Open the live console (leave with CTRL+b then d)

docker exec -it --user linuxgsm bsserver ./bsserver console

Copy

Restart the game server

docker restart bsserver

Copy

Check for a game update now

docker exec -it --user linuxgsm bsserver ./bsserver update

Copy

Update the image

docker compose pull && docker compose up -d

Copy

Server files, configs and logs live in ./bsserver on the host: back up that directory. Docker help below covers permissions, environment variables and bridge networking.

docker run -d \
  --name bsserver \
  --network host \
  --restart unless-stopped \
  -v "$PWD/bsserver:/data" \
  -e UPDATE_CHECK=60 \
  ghcr.io/gameservermanagers/gameserver:bs

environment:
      - UID=1001
      - GID=1001

ports:
      - "PORT:PORT/udp"
      - "PORT:PORT/tcp"

Install on Linux

Install directly on a server running Ubuntu 26.04, Debian 11 or Enterprise Linux 8.

1. Create a user and log in

Creating users and installing system packages require administrator privileges. From your administrator account, use sudo below (omit it if already root). Install curl, tar and an editor such as nano with your distribution's package manager first.

sudo adduser bsserver

Give the user a strong password, then switch to its login shell:

sudo su - bsserver

Run all remaining commands as bsserver from its home directory, without sudo. On Enterprise Linux, create the account with sudo useradd -m bsserver and set its password with sudo passwd bsserver instead of adduser.

2. Download LinuxGSM

curl -Lo linuxgsm.sh https://linuxgsm.sh && chmod +x linuxgsm.sh && bash linuxgsm.sh bsserver

3. Add your Steam login

Create lgsm/config-lgsm/bsserver/common.cfg relative to the game-server user's home directory and add your dedicated Steam account:

mkdir -p lgsm/config-lgsm/bsserver
nano lgsm/config-lgsm/bsserver/common.cfg

steamuser="username"
steampass='password'

4. Install

./bsserver install

LinuxGSM checks dependencies and installs the game files. If this user has sudo access, it can install missing packages when prompted. Otherwise, ask an administrator to install the packages listed by LinuxGSM, then rerun this command as bsserver. Running ./bsserver install as root only installs dependencies, not the game server.

5. Set your GSLT

Create a unique token at Steam Game Server Account Management using the base game's App ID, not the dedicated server's App ID. Enter it when the installer asks, or set it in the instance config below after installation. Replace any existing gslt= line with your token:

nano lgsm/config-lgsm/bsserver/bsserver.cfg

gslt="YOUR_TOKEN"

The installer writes GSLT to this instance config, which overrides common.cfg; leaving the installer's token prompt blank can override a token saved in common.cfg. See the GSLT guide.

6. Configure and start the server

Review your LinuxGSM settings in lgsm/config-lgsm/bsserver/bsserver.cfg (instance settings) or lgsm/config-lgsm/bsserver/common.cfg (shared settings). Do not edit _default.cfg, which LinuxGSM updates automatically. Game settings use a separate config file; run ./bsserver details to find its path. Once configured, start the server explicitly:

./bsserver start

Common commands

Start the server

start

./bsserver start

Copy

Stop the server

stop

./bsserver stop

Copy

Restart the server

restart

./bsserver restart

Copy

Show details, ports and passwords

./bsserver details

Copy

Open the live console (leave with CTRL+b then d; CTRL+c stops the server)

./bsserver console

Copy

Update the game server

./bsserver update

Copy

Run in the foreground to debug

./bsserver debug

Copy

Back up the whole server

./bsserver backup

Copy

List every command

./bsserver

Copy

Automate with cron

Restart the server if it crashes, apply game updates and keep LinuxGSM current. Add these with crontab -e.

*/5 * * * * /home/bsserver/bsserver monitor > /dev/null 2>&1
*/30 * * * * /home/bsserver/bsserver update > /dev/null 2>&1
0 0 * * 0 /home/bsserver/bsserver update-lgsm > /dev/null 2>&1