How to configure an Arma 3 server?

An Arma 3 server is configured mainly through one file: server.cfg, passed at launch with the -config= parameter. Here are the settings that really matter, and our recommended values.

The essential server.cfg settings

• hostname: the name your server displays in the game browser.
• password: connection password for a private server (leave empty for a public server).
• passwordAdmin: admin password, to use the #login command and manage the server in-game.
• maxPlayers: the number of slots. Match it to your RAM and CPU.
• verifySignatures: set it to 2 to allow only signed mods (anti-cheat security).
• motd[]: the welcome messages shown to players who connect.

Setting the mission rotation

The class Missions block defines which missions run and in what order. Drop your .pbo files into the mpmissions folder, then reference them by name. This is what allows scenarios to chain automatically.

BattlEye and security

Leave BattlEye enabled for anti-cheat protection, and combine it with verifySignatures = 2 to block unsigned mods. On a modded server, make sure all your mods have their .bikey signature files.

Loading mods at launch

Server config and mods are linked: mods are declared through -mod= on the command line, not in server.cfg. For the setup, see How to create an Arma 3 server?

After every change to server.cfg, restart the server to apply the changes.

Do it the easy way

On a Fly-Serv Arma 3 server, the FlyPanel edits server.cfg from a clear interface, manages the mods and restarts the server in one click, without touching the files by hand. Ideal for adjusting slots, missions or security on the fly. Discover our Arma 3 plans from 2.99 €/month.