Your own game server

Each download includes the game server (bv2dedicated) and the master server (bv2master) that feeds the in-game server browser. For an always-on host, use the Docker images.

Ports

Open inbound TCP 3333 (game) and, if you run a master, TCP 10207. All game traffic is TCP.

Quick start from a download

In the unpacked folder (Linux and macOS shown; on Windows double-click run-server.cmd):

./run-server.sh

Players join with the console command connect <your address>. The server reads your BaboViolent 2 maps from BV2_DATA_DIR (the folder that contains main/) and sends missing maps to players.

Docker

Images for amd64 and arm64: ghcr.io/hub-tansky/roboviolence2-server and ghcr.io/hub-tansky/roboviolence2-master. The compose example runs a master, a game server and a TLS proxy for the admin API:

git clone https://github.com/Hub-Tansky/RoboViolence2.git
cd RoboViolence2
docker compose -f packaging/docker/compose.example.yml --env-file ~/bv2-secrets.env up -d

Keep secrets in that env file, outside the repository:

# join password, empty for none
BV2_SV_PASSWORD=
# admin login and admin API token
BV2_ADMIN_PASS=
# master bans, at most 7 characters
BV2_MASTER_BAN_PASS=
# your public IPv4, so the server browser lists a reachable address
BV2_PUBLIC_ADDRESS=

The server runbook covers logs, the server console, upgrades, remote admin over HTTPS, original game data in containers and backups.