ArmA 3 server hosting

ArmA 3 has no hard engine cap I'd ever hit in practice – maxPlayers in server.cfg will happily accept 100+, and public servers have run 80 or 90. What actually matters is the mission itself: maxPlayers in description.ext and the number of playable units the mission creator placed both act as caps, so if the mission was built for 32 players, ordering a 64-slot server won't give you more bodies. Size against the mission you plan to run first, then scale up. You can pick anything from 10 to 120 slots on the ArmA 3 pricing page.

Yes – ACE, RHS (AFRF/USAF/GREF/SAF), CUP, CBA, Antistasi, and every other Workshop mod work on LOW.MS. The Mod Manager in your control panel at control.low.ms handles Workshop IDs directly: paste the ID, hit install, and the mod is loaded into your server's -mod= line for you. For mods that aren't on Workshop (private community packs, pre-release builds), upload the PBOs through File Manager or SFTP. One caveat worth flagging: .dll uploads are blocked on our platform, which is a rare issue for Arma 3 but occasionally trips up people trying to use server-side extensions like Intercept Core – open a ticket and we'll place those server-side.

Yes – Arma 3 mods are loaded client-side, so every player has to have each mod installed and enabled in their launcher before they can join a modded server. That's how the engine works, not a LOW.MS restriction. The best way to handle this is to publish your modset as a preset: the official Arma 3 Launcher has a Share button that generates a .html file. Send that to your group and they import it once, and the launcher downloads everything from Workshop automatically.

No – Arma 3 is PC-only, with no console version and no crossplay. Every Arma 3 server (ours and every other host's) serves PC clients over Steam exclusively. If you're specifically looking for console support, you're thinking of Arma Reforger, the precursor to Arma 4, which does support PC/Xbox/PS5 crossplay.

BattlEye ships with the Arma 3 dedicated server files and is enabled by default – you don't have to install anything. On LOW.MS you can toggle it from the Commandline Manager in your control panel if you ever need to disable it for a closed testing session, but for any public or modded server you should leave it on. BattlEye runs transparently; your players won't see anything unless they try to cheat.

The base LOW.MS plan includes 10 GB of RAM, which is plenty for a vanilla 32-slot server and comfortable for medium mod packs like ACE + CBA + a single faction pack. Once you start stacking RHS + CUP + ACE + mission mods (Antistasi-style setups), or pushing past 40 players, add more – I'd jump to 15 GB at 40 slots with a full mod pack, and 20 GB if you're running Antistasi or a heavy milsim. You can add RAM at checkout or upgrade later from the panel.

By default the game port is 2302/UDP (which also carries VON voice), Steam query runs on 2303/UDP, Steam master on 2304/UDP, and BattlEye client traffic on 2306/UDP. BattlEye RCON sits above that – on LOW.MS we put it on game port + 10 (so 2312/TCP for a default server). Your exact ports show up in the control panel under Service Settings, and each additional server on the same box shifts the block by +20.

All seven Creator DLCs work on LOW.MS: Global Mobilization, S.O.G. Prairie Fire, CSLA Iron Curtain, Western Sahara, Spearhead 1944, Reaction Forces, and Expeditionary Forces. Creator DLC works on a 'one player on the server owns it' basis, meaning any connected client who owns the DLC unlocks its content for the session. Realistically, if you're running a Prairie Fire or Spearhead 1944 mission the whole server should own it, or half your players will be stuck with unarmed placeholder characters. Drop the DLC's mod ID into the server's mod line like any other mod.

Yes – headless client is supported. You run a second Arma 3 instance (the HC) that offloads AI computation from the main server, which is the standard setup for anything AI-heavy like Antistasi, Liberation, or a big Zeus op. In your server.cfg you'll want headlessClients[] = {"127.0.0.1"}; and localClient[] = {"127.0.0.1"}; so the HC can connect with unlimited bandwidth. If you need a hand setting one up on LOW.MS, open a ticket and we'll walk you through the panel side of it.

Set passwordAdmin in your server.cfg (it's separate from the normal password key for joining), then in-game open chat and type #login yourpassword. You'll get a confirmation message and then you have access to the admin menu: kick, ban, mission selection, restart, and Zeus slot on compatible missions. There's no 'first player gets admin' fallback – if you don't set passwordAdmin, no one can be admin that session.

Once every 6 to 12 hours is the sweet spot for most missions. Arma 3's scripting engine leaks memory on long sessions – AI spawns, vehicle wrecks, and JIP data all accumulate – and frames start to stutter after a few hours on heavy modpacks. We expose Scheduled Tasks in the control panel so you can set a daily or per-mission restart cycle without logging in. For Antistasi and similar persistent campaigns, consider saving the mission state before the restart.

Your ArmA 3 is set up instantly after payment, allowing you to start hosting without delays.

Yes! Our user-friendly control panel gives you full control over game modes, maps, and server configurations over your ArmA 3 server.

We provide 24/7 support for your ArmA 3 server through live chat and email to assist you with any questions or technical issues.

Absolutely. If you're not satisfied with your ArmA 3 server, we provide a full refund within the first 5 days.

Our ArmA 3 servers use top-tier Intel or AMD hardware to ensure your server runs super smoothly!