Install a BattleBit Remastered server

Step-by-step installation

1. 1

   Read the official announcements and discussions (Steam, Discord) for the current procedure.

2. 2

   Choose: rent from a host or obtain community access from the studio.

3. 3

   Prepare your configuration with the site's checklist (name, region, players, rotation).

4. 4

   If you want modules, install BattleBit API Runner (community project) on a .NET machine.

5. 5

   Set strong passwords and restrict access to the API port.

6. 6

   Test from outside: the server shows up in the in-game browser.

7. 7

   Follow game updates and restart as your host instructs.

8. 8

   List the server on game-rank.com.

Requirements

According to unofficial host pages, a BattleBit server needs about 3.5 to 4 GB of RAM: an unverified figure, to confirm with your host. For the optional community API: the .NET runtime and a Windows or Linux machine. A Steam account with the game is useful for in-game testing.

Game server installation: not documented

No SteamCMD command, app ID, launch parameter or default port is given here: we found no official documentation and do not invent them. Use the files and instructions provided by the studio or your host.

BattleBit API Runner (optional, community)

Download the latest version from the Releases of the RainOrigami/BattleBitAPIRunner GitHub repository, extract it and run it; the game server then connects to it. Follow the “Hosting Guide” in its wiki for the listening address and port. Unofficial project, unrelated to the studio.

dotnet BattleBitAPIRunner.dll

Automatic start (systemd)

To keep the API Runner running on Linux, adapt this systemd unit (paths and user to adapt); for the game server itself, follow the studio's or host's instructions.

[Unit]
Description=BattleBit API Runner
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=battlebit
WorkingDirectory=/home/battlebit/apirunner
ExecStart=/usr/bin/dotnet BattleBitAPIRunner.dll
Restart=on-failure
RestartSec=15
LimitNOFILE=100000

[Install]
WantedBy=multi-user.target

Provider firewall and home router (NAT)

At OVH, Hetzner, Scaleway and similar providers, also open the same ports in the provider firewall (security group / panel firewall): it filters before the machine. For home hosting, create a NAT (port forward) rule on your router for each port to the server's local IP, with the right protocol. Test from outside (mobile network); never expose administration ports (RCON) without a strong password.

Listing and finding your server

Once the server is reachable from outside, add it on game-rank.com/jeux/battlebit-remastered (the owner's site) so players can discover it.

Troubleshooting

• Server not in the browser: wrong region, server not restarted after a patch, or the client is on a different version.
• The API Runner receives no connection: listening address or port differ from those declared on the game server, or a firewall blocks the port.
• A community module crashes the server: disable it, update the API Runner and check the logs.
• Can't obtain a server: community access may be limited; ask through official channels or rent from a host.
• Password or keys exposed: change them immediately, never publish them in a public channel or repository.

Frequently asked questions

What is the BattleBit server's SteamCMD app ID?

We found none documented, so we give none. Don't trust an unsourced ID.

Can I host from home?

It depends on the access the studio gives you; the ports to forward are not documented here. Use those given in the instructions you receive.

Is the API Runner official?

No: it is a community project (RainOrigami/BattleBitAPIRunner) that implements the official community server API.

Why is this guide so short?

Because nothing official and verifiable could be found on installation; we prefer to say so rather than invent. It will be completed if the studio publishes documentation.