Running your own ARMA 3 server puts you in control of the mission, the mods, and the rules for your unit or community. This guide walks you through deploying your server, connecting to it, editing your settings, and installing Steam Workshop mods.
Deploy your ARMA 3 server
After you order an ARMA 3 server, it deploys automatically and installs the ARMA 3 dedicated server files from Steam on first boot. That first install pulls around 15GB, so give it a few minutes before the server shows as online in the panel.
Pick your RAM based on player count and your modlist. A vanilla server for 32 to 64 players runs comfortably on 4 to 6GB, while a heavy modlist built around RHS and ACE3 wants 8GB or more. Use the ARMA 3 RAM calculator to size it, and upgrade anytime from the control panel without wiping your setup.
Connect to your server
Your server's IP and port are shown on the panel dashboard. There are two easy ways in:
- ARMA 3 Launcher (recommended for modded servers): open the Launcher, find your server under Direct Connect or add it to Favorites by IP and port. The Launcher loads the matching mods before it joins, so a modded server connects in one step.
- In-game: open ARMA 3, go to Multiplayer, and use Direct Connect with your IP and port, or find your server by name in the community browser.
A modded server only appears in the browser once its mods have finished installing, so give a new server a few minutes after its first mod download.
Configure your server
Most ARMA 3 settings live on the Startup tab of your panel:
- Server Name and Max Players set your identity and player cap.
- Server Password gates access (leave it blank for a public server).
- Mission selects what runs, whether that is Antistasi, King of the Hill, or a custom scenario.
- Headless Client slots offload AI to a separate process to keep large missions smooth.
For deeper changes, full FTP access lets you edit server.cfg and basic.cfg directly, tune difficulty, and drop custom missions into the mpmissions folder.
Install Steam Workshop mods
ARMA 3 has a massive Steam Workshop mod scene. To add mods to your server:
- Subscribe to the mods you want in the ARMA 3 Launcher and export a modlist (modlist.html), or note each mod's Workshop ID.
- On the panel Startup tab, add the mod IDs, or upload your exported modlist.html.
- Restart the server. It downloads and loads the mods automatically.
Popular picks include CBA_A3 (the framework most mods depend on), RHS (Red Hammer Studios weapons and vehicles), ACE3 (advanced realism and medical), and total conversions like Antistasi. Server-side-only mods go in the separate server mods field, so clients do not need to download them.
Common issues
- Server stuck on install: the first boot downloads the full ARMA 3 server from Steam, around 15GB. Wait a few minutes and watch the console log for progress.
- Players cannot find the server in-game: a modded server only lists after its mods finish downloading. Use the ARMA 3 Launcher, which matches mods automatically.
- Mods will not load: confirm the Workshop IDs are correct and that you restarted the server after adding them. CBA_A3 must load before mods that depend on it, and the console log names any mod it could not find.
- BattlEye kicks players: keep BattlEye enabled consistently, or disable it in your config if you run mods that it flags.