Arma 3 Dedicated Server Setup Guide for 2026

Hosting Arma 3 for friends or a growing unit sounds simple until the lag starts, mods desync, and your server disappears from the browser. You hear people talk about running an Arma 3 dedicated server, but guides feel dated and scattered. 

This article cuts through that. You’ll see when a simple listen server is enough, when your own PC can handle a small persistent world, and when it makes sense to move up to real rented hardware. 

You’ll learn how to set up Windows and Linux servers with SteamCMD and modern tools, add missions and mods safely, open the right ports, and fix the common “can’t see or join” issues. 

If you want stable sessions for Antistasi, Exile, or big co-op nights, the next sections will walk you there step by step.

Key Takeaways

• An Arma 3 dedicated server is a headless instance that keeps your world running 24/7 and handles more players, mods, and persistence than a listen server.
• Use your home PC for 2–6 friends, a game panel for small public servers, and dedicated bare metal when you want stable 40–80 slot modded campaigns.
• Size your server around a strong single-core CPU, SSD or NVMe, enough RAM for your modset, and a solid upload line; you do not need a GPU.
• You install the server with SteamCMD on Windows or Linux, keep configs in server.cfg/basic.cfg, and always open or forward UDP 2302–2306.
• Mods and missions work cleanly when you use proper @mod folders, .bikey keys, correct -mod/-serverMod flags, and verifySignatures = 2 for public play.
• Stable sessions come from good mission design and tuning: control AI and vehicles, use headless clients when needed, and move to real dedicated hardware once home hosting or cheap VMs start dropping server FPS.

What an Arma 3 Dedicated Server Actually Is (And Why People Use It)

When you host from the in-game menu, your PC runs both the client and the server. That works for a quick session, but it breaks down once you add more players, heavy mods, or long campaigns.

A dedicated Arma 3 server is a separate, headless process that runs the mission even when no one is connected. It does not render graphics or play sound. It simply simulates, handles AI, and communicates with connected clients.

This gives you:

• Higher and more stable server FPS than a listen server on the same hardware.
• Full control over Arma 3 dedicated server mods, missions, and rules.
• Worlds that stay alive for weeks or months for Antistasi, Exile, Life, KOTH, Zeus, and milsim ops.
• Cleaner restarts and automation, because the server is not tied to one player’s game client.

You can run three basic modes:

• Listen server: you host and play on the same client. Fast, but fragile.
• Local Arma 3 LAN server: good for short sessions, often behind a router or VPN.
• Full dedicated server on Windows or Linux: home box, VPS, or bare metal.

Key takeaways:

• A dedicated server treats your Arma 3 world as a service, not a one-off lobby.
• It is the only reliable option for serious persistence, large player counts, and complex modpacks.

Quick Host Selector: Home PC vs Game Panel vs Dedicated Bare Metal

Before you touch configs, decide where you want to run your server. This choice matters more than any single tweak.

At a Glance: Hosting Options

These ranges are planning estimates, not guaranteed slot caps. Mission design, AI count, mod load, cleanup scripts, and view-distance choices matter more than the slot number alone.

When Each Option Makes Sense

Home PC

Choose this when:

• You just want to host a few co-op nights with 2–6 friends.
• You are fine with downtime when your PC is off.
• You want a form of “free Arma 3 server hosting” and accept that your ISP upload and router are the bottleneck.

This is what “arma 3 server hosting free” looks like in practice: your own machine doing double duty.

Game Panel / GSP

Use a game panel when:

• You want something that “just works” for a small public or semi-public server.
• You like browser-based controls and one-click installs more than SSH and RDP.
• You do not plan to push huge modpacks or 60+ players.

An “arma 3 server” GSP-style setup is fine for casual groups. The trade-off is shared CPU, strict slot tiers, and less freedom with mods and performance tuning.

Dedicated Bare Metal 

Pick a dedicated bare metal when:

• You want stable 40–80 slot servers with mods, AI, and persistent saves.
• You run modes like Antistasi, Exile, or Life and care about long uptimes.
• You want full control over the OS, files, ports, and performance.

Here, you are not just renting a slot. You rent hardware: high-clock CPUs, NVMe, big RAM, and strong uplinks. If you want hardware built for busy Arma 3 server hosting, high-clock dedicated servers with unmetered bandwidth from RedSwitches. This will give you more headroom than a shared game panel.

Arma 3 Dedicated Server Requirements (Hardware, OS, Network)

Before you touch configs or mods, you need to know if your hardware and connection can handle it. Most “lag” problems people blame on Arma 3 actually come from weak single-core CPU performance, low RAM, or poor upload speeds.

CPU, RAM, Storage – Slot-Based Examples

Arma 3 server code leans hard on one main core. Extra cores still help with the OS, logging, and headless clients, but strong per-core speed matters more than high core count.

Use this as a starting point:

A few simple rules:

• Aim for high base clock and strong single-thread benchmarks, not just “many cores”.
• Prefer SSD over HDD. For busy servers, NVMe cuts loading times and mission restarts.
• Size RAM by players and mods. Big modpacks, Antistasi, Exile, and Life missions all push RAM use up fast.
• You do not need a GPU on the server. Arma 3 dedicated instances do not render graphics.

If you want to grow to 40–80 players with heavy scripting and AI, a rented bare metal box will feel much smoother than any desktop that doubles as your gaming rig.

OS Choices

You can run your server on both Windows and Linux. Each has a clear role.

Windows Server / Windows 10 or 11

• Familiar for most players.
• Works well with tools like FASTER (link and description of FASTER in detail is given further in this article) and other arma 3 dedicated server tools with a GUI.
• Easy to manage via RDP if you rent a remote server.
• Good choice if you already know Windows but do not want to learn SSH yet.

Linux (Ubuntu / Debian)

• Lean OS with lower overhead.
• Great for long-running servers that need weeks of uptime.
• Strong control over services with systemd, firewalls, and automation.
• Fits well on rented VPS or bare metal where you want every bit of CPU and RAM for the server.

Network & Ports

Even a strong CPU will not save you if your connection cannot keep up.

Upload speed guidelines

These are rough but safe targets:

• Up to 10 players on light missions: 5 Mbps upload or better.
• 20–30 players with mods and some AI: 10–20 Mbps upload.
• 40–60 players with heavy AI or Exile / Antistasi: 20–30+ Mbps upload, ideally on a data center link.

Download speed matters less than stable upload, low jitter, and low packet loss. Home connections often claim high speeds but drop packets under load.

Ports you must open

Arma 3 servers need specific UDP ports:

• UDP 2302 – main game port.
• UDP 2303–2305/2306 – extra game and Steam query ports.

On Windows, allow arma3server.exe or these UDP ports through the firewall. On routers, forward the same UDP ports to your server’s internal IP if you want players to join over the internet.

Why some home ISPs block hosting

Two common blockers:

• CGNAT (Carrier-Grade NAT): your ISP hides many customers behind one public IP. Port forwarding stops working because that IP is not really yours.
• ISP firewalls and “no servers” policies: some ISPs silently block inbound traffic on the ports you need.

If you hit CGNAT or strict ISP rules, no amount of tweaking will fix public access. At that point, moving to a VPS or dedicated host with a real public IP is the clean path.

Windows Arma 3 Dedicated Server Setup (SteamCMD + FASTER)

Let’s walk you through a clean arma 3 dedicated server setup on Windows. You first install the server files with SteamCMD, then either run a simple batch file or manage everything through FASTER.

Install Arma 3 Dedicated Server With SteamCMD

1. Create two folders, for example:
   • C:\SteamCMD
   • C:\arma3server
2. Download SteamCMD for Windows from Valve’s site and extract it into C:\SteamCMD.
3. Run steamcmd.exe. In the SteamCMD window, enter:

login YourSteamUsername

force_install_dir “C:\arma3server”

app_update 233780 validate

quit

Use a Steam account that owns Arma 3, especially if you plan to pull Workshop mods or use tools like FASTER.

SteamCMD handles the arma 3 dedicated server download and places the files in C:\arma3server.

Inside C:\arma3server you will see:

• arma3server_x64.exe – main server binary.
• MPMissions\ – place multiplayer mission .pbo files here.
• keys\ – store .bikey files for mods.
• cfg\ or root folder – where you keep server.cfg and basic.cfg.
• A Users\ or custom profile folder once you run the server with -profiles.

This folder is your server root. Keep it separate from your normal Arma 3 game folder.

Basic Launch Script (No GUI)

You can start the server with a simple batch file before you bring in any Arma 3 dedicated server tool.

Create a file named start_arma3server.bat inside C:\arma3server:

@echo off

set PORT=2302

set CONFIG=server.cfg

set BASIC=basic.cfg

set PROFILE=serverProfile

arma3server_x64.exe ^

  -port=%PORT% ^

  -config=%CONFIG% ^

  -cfg=%BASIC% ^

  -name=%PROFILE% ^

  -profiles=”C:\arma3server\profiles” ^

  -autoInit

pause

Adjust paths and file names to match your setup.

This script gives you:

• Fixed port for firewall and port forwarding.
• Clean separation of config, basic network settings, and profile.
• Automatic mission start on boot (-autoInit).

Keep this script even if you switch to FASTER later. It is a good fallback when you need to debug.

Using FASTER As Your Arma 3 Dedicated Server Tool

FASTER is a Windows tool built to manage Arma servers with as little manual work as possible. It handles server updates, profiles, mod management, and launch parameters from one place.

First launch setup

1. Download the latest FASTER release from its GitHub page.
2. Extract FASTER.exe somewhere outside your game folder (for example C:\FASTER).
3. Run it and fill in:
   • Steam login – account that owns Arma 3.
   • Server install directory – C:\arma3server or any folder where SteamCMD placed the server.
   • Mod staging directory – a folder where FASTER downloads Workshop mods before deployment (for example C:\arma3mods_stage).

FASTER will then sync with Steam and check your server files.

Create a server profile

Inside FASTER:

1. Add a new profile and name it (for example MainPublicServer).
2. In the Server tab, set:
   • Server host name – what players see in the browser.
   • Join password – optional. Leave blank for public.
   • Admin password – for in-game admin login.
   • Max players – match your hardware and bandwidth.
   • Game port – usually 2302. Keep this consistent with your router and firewall.

Load a mission

1. Place mission .pbo files in C:\arma3server\MPMissions.
2. In FASTER, open the Missions tab and hit refresh.
3. Select one or more missions (Antistasi, Exile, KOTH, your own .pbo).
4. Set difficulty via presets or individual sliders.

FASTER will now know which mission to run when you start the profile.

Mods Inside FASTER (Arma 3 Dedicated Server Mods)

FASTER makes mod handling far easier than manual copying.

Add mods to the staging area

In the Mods tab you can:

• Paste Steam Workshop URLs.
• Add local mods from disk.
• Import mod preset files from the Arma 3 launcher.

Once you list the mods you want, click Update All. FASTER downloads each Workshop mod into the mod staging directory you set earlier.

Deploy mods to the server

Downloaded mods sit in staging until you deploy them:

1. Open the Deployment tab.
2. Set the Install directory to your server folder (for example, C:\arma3server).
3. Click Deploy All or choose mods one by one.

FASTER now creates @ModName folders inside your server directory and prepares them for use.

Mark required vs optional mods

Back in the profile:

• In the Mods section, each mod has checkboxes for:
  • Server – needed on the server.
  • Client – required on players’ clients.
  • Headless – needed on headless clients, if you use them.

If you are unsure at the start:

• Tick Server and Client for main modpacks.
• Leave Headless for later until you configure headless clients.

Keys and signatures

• Use the Copy mod keys action in FASTER or copy .bikey files by hand into C:\arma3server\keys.
• This allows the server to accept clients with those mods when verifySignatures is on.

This workflow covers most Arma 3 dedicated server mods setups without manual trial and error.

TADST As Legacy Tool 

TADST (Tophe’s Arma Dedicated Server Tool) still appears in older Steam guides and forum posts. It offers a graphical way to set ports, difficulty, missions, and mods, and some long-time admins still use it.

That said, FASTER is the stronger default for a new Windows setup because it has current releases, better Workshop-oriented workflows, and cleaner update handling. Keep TADST as an older compatibility option, not the main recommendation for a fresh server build.

FASTER has current GitHub releases, while TADST is better framed as an older community tool rather than something you should present as the modern default.

Arma 3 Dedicated Server Linux Guide (Ubuntu / Debian)

If you want a lean, long-running server, Linux is a strong choice. The process is the same whether you use a home box, a VPS, or a dedicated machine from RedSwitches. Here we will show you how to run an arma 3 dedicated server Linux setup on Ubuntu or Debian.

Prepare the Linux Host

Pick a modern LTS distro:

• Ubuntu Server 22.04 LTS
• Debian 12

Then:

Create a non-root user

sudo adduser arma3

sudo usermod -aG sudo arma3

Log in as this user:

su – arma3

Install basic tools and 32-bit libs

On Ubuntu / Debian:

sudo dpkg –add-architecture i386

sudo apt update

sudo apt install -y wget curl lib32gcc-s1 screen tmux

You now have a normal user that will own the server files and a few tools to manage sessions.

Install With SteamCMD on Linux

You can install SteamCMD in the arma3 user’s home directory.

Create folders

mkdir -p ~/steamcmd

mkdir -p ~/arma3server

Download SteamCMD

cd ~/steamcmd

wget https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz

tar -xvzf steamcmd_linux.tar.gz

Run SteamCMD and install the server

./steamcmd.sh

Inside the SteamCMD prompt:

login YourSteamUsername

force_install_dir ./../arma3server

app_update 233780 validate

quit

Use a Steam account that owns Arma 3 if you plan to download Workshop mods for the server.

You now have the dedicated server binaries in ~/arma3server.

Folder Layout and Config

Inside ~/arma3server you should plan a simple layout:

• arma3server_x64 – main server binary (may be named slightly different).
• MPMissions/ – for multiplayer mission .pbo files.
• keys/ – for .bikey files from mods.
• config/ – good place for:
  • server.cfg
  • basic.cfg

Create that config folder:

mkdir -p ~/arma3server/config

mkdir -p ~/arma3server/MPMissions

mkdir -p ~/arma3server/keys

Give your user ownership (if needed):

sudo chown -R arma3:arma3 ~/arma3server

Drop your server.cfg and basic.cfg into ~/arma3server/config. Place missions in MPMissions and keys in keys.

Create a systemd Service

A systemd service keeps your server running and restarts it if it crashes.

Create a start script

As the arma3 user:

nano ~/arma3server/start.sh

Example content:

#!/bin/bash

cd /home/arma3/arma3server

./arma3server_x64 \

  -port=2302 \

  -config=config/server.cfg \

  -cfg=config/basic.cfg \

  -name=linuxProfile \

  -profiles=/home/arma3/arma3server/profiles \

  -autoInit

Save and exit, then make it executable:

chmod +x ~/arma3server/start.sh

Create the systemd unit

Switch to root or use sudo:

sudo nano /etc/systemd/system/arma3server.service

Example unit file:

[Unit]

Description=Arma 3 Dedicated Server

After=network.target

[Service]

Type=simple

User=arma3

Group=arma3

WorkingDirectory=/home/arma3/arma3server

ExecStart=/home/arma3/arma3server/start.sh

Restart=on-failure

RestartSec=10

[Install]

WantedBy=multi-user.target

Save and exit.

Enable and start the service

sudo systemctl daemon-reload

sudo systemctl enable arma3server

sudo systemctl start arma3server

Check status:

sudo systemctl status arma3server

If the service is active and logs show the mission loading, your Linux server is now running under systemd.

Optional: Docker / Container Path

You can also run the server inside a Docker container.

When Docker helps

• You want clean isolation between the game and other services.
• You plan to move the server between hosts often.
• You like storing config and data in mounted volumes for easy backups.

You will find community Docker images that wrap SteamCMD and arma 3 dedicated server in one container. The pattern is:

• One container for the server process.
• One or more volumes for arma3server data and configs.
• Ports 2302–2306 exposed on the host.

When to skip Docker

• You aim for very high slot counts and heavy AI.
• You want to remove every bit of container overhead.
• You prefer direct access to the host for advanced tuning.

For most admins, a plain systemd service on a VPS or bare metal box gives the best mix of control and performance. Docker becomes useful when you run many game servers side by side and want a standard way to ship them around.

Networking: Ports, UPnP, Port Forwarding, and Arma 3 LAN Server With ZeroTier

You can have perfect hardware and still get kicked by networking. This section shows how to open the right ports, host for friends fast, and run a reliable Arma 3 LAN server with a virtual LAN.

Core Port Setup

Arma 3 servers use specific UDP ports:

• UDP 2302 – main game port.
• UDP 2303 – server query port.
• UDP 2304 – Steam master port.
• UDP 2305 – VoN reserved port.
• UDP 2306 – BattlEye traffic port.

On Windows Firewall:

1. Open Windows Defender Firewall → Advanced settings.
2. Add a new Inbound Rule:
   • Type: Port → UDP → ports 2302-2306.
   • Allow connection.
   • Apply to your network profiles.

On Linux with ufw:

sudo ufw allow 2302:2306/udp

sudo ufw reload

If you use another firewall (pfSense, iptables, router firewall), open the same UDP range to your server’s internal IP.

Method 1: UPnP (Quick Test For Friends)

UPnP lets some routers open ports automatically when a game asks for it.

For a quick test:

1. In Arma 3, open Multiplayer → Host Server.
2. Set the Type to Internet.
3. Tick the UPnP box.
4. Start the mission and ask a friend to search for your server.

UPnP is enough when:

• Your router supports UPnP and has it enabled.
• Your ISP gives you a normal public IP, not CGNAT.

Pros:

• No router login.
• Good for a fast “are we live?” test.

Cons:

• Some routers ignore UPnP or break it with firmware updates.
• You get less control and sometimes random port behaviour.
• Not ideal for a long-running arma 3 dedicated server.

If friends cannot see your server with UPnP, move on to manual port forwarding or virtual LAN.

Method 2: Manual Port Forwarding

Manual port forwarding is the classic way to make a home server reachable from the internet.

Steps:

1. Give your host a static IP
   • On Windows, set a static IPv4 or create a DHCP reservation on the router.
   • This keeps your PC on the same internal IP, for example 192.168.1.50.
2. Log into your router
   • Find the Port Forwarding or NAT section.
   • Add a rule:
     • Protocol: UDP
     • External ports: 2302–2306
     • Internal IP: your server’s IP
     • Internal ports: 2302–2306
3. Host with Internet type and UPnP off
   • In Arma 3 or your launcher: host as Internet, leave the UPnP box unchecked.
4. Open the same ports in your local firewall
   • Match the UDP 2302–2306 range.

Manual forwarding is the best long-term option for a home server when:

• You control the router.
• Your ISP gives you a real public IP.
• You want predictable behaviour without UPnP surprises.

If you have no access to the router (university, shared Wi-Fi, 4G/5G router), this path is blocked. Use virtual LAN instead.

Method 3: Arma 3 LAN Server With ZeroTier (Virtual LAN)

Virtual LAN tools create a private network over the Internet. Every PC acts as if it sits on the same router. That makes hosting an Arma 3 LAN server possible even when you cannot port forward.

What a virtual LAN does in simple terms

• Each PC joins the same virtual network ID.
• The VPN software gives them “virtual” IPs on that network.
• Games treat it as one local LAN, even across countries.

ZeroTier setup for Arma 3

1. Go to ZeroTier and create a free account.
2. Create a new network and copy the Network ID.
3. On each PC (host and friends):
   • Install the ZeroTier client.
   • Join the network using the Network ID.
   • Approve nodes in the ZeroTier web panel if needed.
4. On Windows, set that ZeroTier network to Private so local discovery works.
5. On the host PC:
   • Open Arma 3 → Multiplayer → Host Server.
   • Set the Type to LAN.
   • Start the mission.
6. On friend PCs:
   • Open Arma 3 → Multiplayer.
   • Go to the LAN tab and wait a few seconds.
   • Your arma 3 lan server should appear.

This bypasses router port forwarding entirely. Every player just needs the ZeroTier client and your Network ID.

Check That Your Server Is Visible

Once the server is running, you should confirm that others can see and join it.

Ways to test:

• Ask a friend to search for your server name in the browser.
• Use Direct connect with your IP and port 2302.
• Check a third-party browser like BattleMetrics or similar sites.

If your Arma 3 dedicated server is not showing up, common reasons are:

• Ports 2302–2306 UDP are still blocked by the firewall or router.
• You sit behind CGNAT, so port forwarding never reaches your machine.
• The server is bound to the wrong interface or IP.
• The server is still starting up or stuck loading a broken mission.

Work through these in order: firewall, router, ISP type, then mission and logs.

Arma 3 Dedicated Server Setup: Config Files & Launch Parameters

Config files control how your server behaves, how it talks to clients, and how it uses your network. Launch parameters tell the binary where those configs live. This section gives you a clean baseline for both.

server.cfg – Core Settings

server.cfg handles core gameplay and access rules.

Key fields:

• hostname – server name in the browser.
• password – join password, optional.
• passwordAdmin – admin password for #login.
• maxPlayers – hard slot cap.
• Voting and kicking settings.
• Mission cycle list.

Example minimal server.cfg:

hostname           = “My Arma 3 Server”;

password           = “”;                  // empty = public

passwordAdmin      = “ChangeThisAdminPass”;

maxPlayers         = 40;

verifySignatures   = 2;                   // only signed mods

BattlEye           = 1;

voteThreshold      = 0.33;

voteMissionPlayers = 1;

motd[]             = {

    “Welcome to the server.”,

    “Join our Discord for info.”

};

motdInterval       = 5;

// Mission rotation

class Missions

{

    class Mission1

    {

        template = “co40_Antistasi.Altis”;

        difficulty = “Regular”;

    };

};

You can expand this later with headless clients, custom difficulty classes, and VoN rules. Start simple, confirm it works, then add more.

basic.cfg – Network and Performance Tuning

basic.cfg focuses on network behaviour and packet sizes. These values decide how often the server sends updates and how large those packets can be.

Main settings:

• MinBandwidth and MaxBandwidth – expected range of your upload in bits per second.
• MaxMsgSend – how many messages the server can send per simulation frame.
• MaxSizeGuaranteed – max size of guaranteed messages (reliable).
• MaxSizeNonguaranteed – max size of non-guaranteed messages (position updates).
• MinErrorToSend and MinErrorToSendNear – how much a unit must move before the server sends an update.

What they do, plain language:

• Higher MinBandwidth and MaxBandwidth tell Arma 3 it can send more data per tick.
• Higher MaxMsgSend means more updates per frame but a higher risk of saturating weak links.
• Larger MaxSizeNonguaranteed packs more movement data into each packet.
• Smaller MinErrorToSend makes movement smoother but increases traffic.

Sample for a small home server (up to ~10 players)

MinBandwidth           = 131072;       // 128 kbps

MaxBandwidth           = 10485760;     // 10 Mbps

MaxMsgSend             = 128;

MaxSizeGuaranteed      = 512;

MaxSizeNonguaranteed   = 256;

MinErrorToSend         = 0.01;

MinErrorToSendNear     = 0.02;

maxPacketSize          = 1400;

Sample for a public ~40-slot server with good upload

MinBandwidth           = 10485760;     // 10 Mbps

MaxBandwidth           = 52428800;     // 50 Mbps

MaxMsgSend             = 512;

MaxSizeGuaranteed      = 1024;

MaxSizeNonguaranteed   = 512;

MinErrorToSend         = 0.005;

MinErrorToSendNear     = 0.01;

maxPacketSize          = 1400;

Treat these as starting points. Watch server FPS and player feedback, then adjust MaxMsgSend and MinErrorToSend up or down.

Profile, Logs, and Command Line

Launch parameters tie everything together and decide where Arma 3 writes logs and profiles.

Profiles

• -name=ProfileName tells the server which profile to use.
• -profiles=Path sets where the profile folder lives.

Inside that profile folder, you get:

• *.Arma3Profile files for difficulty and view distance.
• *.rpt log files with crash info, script errors, and startup messages.

Logs

On Windows, logs usually sit under:

• C:\arma3server\profiles\ProfileName\
• Or inside Users\ProfileName if you use default paths.

On Linux, they live in the profiles path you set.

When something breaks, the .rpt is your first stop.

Useful launch flags

Add these to your batch file or systemd script when needed:

• -filePatching – allow loading unpacked mission files and scripts. Use only on test servers or in controlled environments.
• -autoInit – start the selected mission as soon as the server boots and keep it running.
• -world=empty – skip loading a default map in the lobby and speed up startup.

A typical Windows command looks like:

arma3server_x64.exe ^

  -port=2302 ^

  -config=config\server.cfg ^

  -cfg=config\basic.cfg ^

  -name=MainProfile ^

  -profiles=”C:\arma3server\profiles” ^

  -autoInit ^

  -world=empty

Once you have these pieces in place, you control how the server looks in the browser, how it uses your network, and how easily you can debug issues when something goes wrong.

Mods, Missions, and Popular Gamemodes (Antistasi, Exile, KOTH)

Mods and missions are the reason most people bother with a dedicated server. Here we will give you a clear Arma 3 dedicated server mods workflow and shows how common modes fit into it.

Arma 3 Dedicated Server Mods Workflow

Use this pattern whether you run Windows or Linux.

1. Subscribe to mods

• On your main Steam account, subscribe to the mods you want in the Arma 3 Workshop.
• Steam downloads them into the Workshop folder for app ID 107410.

2. Find the mod folders

On Windows, you find Workshop mods under:

• …\Steam\steamapps\workshop\content\107410\<modID>\

Each <modID> is a number from the Workshop URL. Inside, you usually see an @ModName folder or the mod files directly.

3. Copy or link mods to the server

You have two options:

• Copy the @ModName folders into your server directory (for example C:\arma3server\@CBA_A3).
• Or use symbolic links so the server points to the Workshop folder. This saves disk space but needs a little care when paths change.

On Linux, you do the same with ln -s from the Workshop path into ~/arma3server.

4. Place mod keys in the keys/ folder

Most mods ship a .bikey file in a keys or similar folder. Copy these into:

• C:\arma3server\keys on Windows.
• ~/arma3server/keys on Linux.

This is how the server knows which signed mods it should allow when you turn on signature checks.

5. Add -mod and -serverMod flags

Tell the server which mods to load at start:

• -mod=@CBA_A3;@ACE3;@YourMap
• -serverMod=@serverTools;@ExileServer

You can add these flags in:

• Your Windows batch file.
• Your Linux start script.
• Or the Mods section in FASTER.

Client vs server mods

• Client mods: content that every player needs. Maps, gear packs, weapon mods, large frameworks. These go under -mod and must be on both client and server.
• Server-only mods: scripts, admin tools, Exile server code, logging tools. These go under -serverMod and do not need to be on players’ PCs.

If you are not sure, assume a mod is client-side content unless the author clearly marks it as server-only.

Signature Checks and Security

Signature checks stop random mods from joining your server.

The main setting is in server.cfg:

verifySignatures = 2;

With this:

• The server checks all .pbo files against .bikey files in the keys/ folder.
• Clients who run content without a matching key get kicked on join.
• You keep control over which workshop items run in your world.

Optional mods

You may want to allow some client-only mods without forcing them:

• Sound packs.
• UI tweaks.
• Small QoL changes.

To do this:

• Place the .bikey for the mod in keys/.
• Do not include the mod in your -mod line.
• Keep verifySignatures = 2; enabled.

That setup is usually enough for optional signed client mods. Older guides may mention equalModRequired, but it is legacy behaviour and should not be the main control you build around on a modern Arma 3 server.

What happens with extra mods

• Signed and allowed: player joins and plays.
• Unsigned or with a missing key: player gets a kick message on connect.
• Banned content: If you use ban filters or community tools, players with known cheat packs may be blocked.

For public servers, keep verifySignatures = 2 on. Turn it off only on private test boxes.

Missions and Gamemodes

Missions and modes are simple once you know where files belong.

Where mission .pbo files go

• Place all multiplayer missions in the MPMissions folder of your server.
• File names follow the pattern MissionName.MapName.pbo
  • Example: co40_Antistasi.Altis.pbo

The server reads this folder at startup.

Add missions to server.cfg rotation

Inside server.cfg:

class Missions

{

    class AntistasiAltis

    {

        template = “co40_Antistasi.Altis”;

        difficulty = “Regular”;

    };

    class KOTHAltis

    {

        template = “KOTH_Altis.Altis”;

        difficulty = “Veteran”;

    };

};

The server loads the first mission on boot and can cycle through the list if you add more.

Popular modes and what they need

• arma 3 antistasi dedicated server
  • Heavy AI and scripts.
  • Needs solid single-core CPU and decent RAM.
  • Works well from 20–60 slots on a tuned server.
• arma 3 exile server hosting
  • Needs the Exile server mod plus client mod.
  • Runs a database (MySQL or MariaDB) for persistence.
  • Best match for VPS or dedicated hosts, not weak home PCs.
• KOTH (King of the Hill)
  • Focus on PvP and performance with many players.
  • CPU pressure comes from players and vehicles, not just AI.
• Invade & Annex, Life servers, Wasteland
  • Mix of AI, players, and scripts.
  • Mission writers often include their own cleanup and spawn logic.

How mission complexity affects hardware

• More AI and vehicles → higher CPU load.
• Persistent wrecks and bases → more objects to track, slower server FPS.
• Heavy scripts and loops → more time per simulation tick.

If you see server FPS dropping into the teens, reduce AI, clean up wrecks, and trim the mission before blaming the game engine.

Performance and Scaling: Getting Stable FPS on Your Dedicated Arma 3 Server

Good hardware is only half the story. The way you build missions and run AI decides if your server feels crisp or sluggish.

Understand Server FPS and Load

Client FPS is what you see on your own PC. Server FPS is how fast the simulation runs on the host.

• High client FPS with low server FPS still feels bad. AI reacts late, shots trade oddly, vehicles rubberband.
• Aim for 30+ server FPS during busy fights. Brief drops are fine, constant 10–15 is not.

How to monitor

From the server console or as admin in game:

• Use #monitor 5 to print performance stats every 5 seconds.
• Watch server FPS and bandwidth use together.

If server FPS crashes whenever AI spawns, you hit CPU limits, not net limits.

AI Load, Vehicles, and Map Size

Arma 3 is CPU hungry because of AI and physics. You control that with mission design.

Key pressure points:

• Total number of active AI groups.
• Vehicles with active crews.
• Persistent wrecks, craters, and rubble.
• Huge draw distances on busy maps.

Practical tips:

• Use scripts that clean up wrecks and dead bodies after a delay.
• Keep ambient AI and patrols modest on full servers.
• Spawn AI near players, not across the entire map at once.
• Avoid stacking multiple heavy AI frameworks in the same mission.

Big maps like Altis and Tanoa with AI everywhere will punish even strong CPUs. Keep the action focused.

Headless Clients (HC)

A headless client is an extra instance of the game that connects as a special “player” and runs AI logic. It does not render; it just takes part of the load.

When to add one

• You run heavy AI missions like Antistasi or large Invade & Annex variants.
• Server FPS drops during AI-heavy moments even on good hardware.

Basic setup steps

In server.cfg, whitelist the HC IP. If the HC runs on the same machine, 127.0.0.1 may be fine. If it runs on another box, use that machine’s reachable IP:

headlessClients[] = {“127.0.0.1”};

localClient[]     = {“127.0.0.1”};

In the mission, add a Headless Client entity or use a framework that already supports HC offloading.

Run an extra Arma instance with the -client parameter and connect it to the server:

arma3_x64.exe -client -connect=YOUR_SERVER_IP -port=2302 -password=YourPass -name=HC1

Mission scripts or the mission framework, then hand AI groups over to the HC. The main server now spends less time on pathfinding and combat logic.

Start with one HC. Add a second only if you clearly see gains and know the mission supports it.

VM vs Physical Dedicated Servers

You can run Arma 3 inside a virtual machine, but there are trade-offs.

Why VMs struggle at high load

• Hypervisors squeeze several guests into one CPU.
• You compete for cores and cache with other VMs.
• Timer behaviour and scheduling can hurt a game that relies on tight ticks.

For small private servers, a VM on a decent node is often fine. Once you push 40–80 players with AI-heavy modes, a dedicated arma 3 server on real hardware will usually hold server FPS better.

When bare metal pays off

• Large Antistasi platoons with constant contact.
• Exile or Life with many players, vehicles, and persistence.
• Multi-squad co-op events where bad ticks ruin the night.

You pay more upfront, but you remove noisy neighbours and hidden throttles.

When you outgrow home hosting and light VPS plans, you want hardware that matches how Arma 3 behaves.

A box from a provider like RedSwitches can give you:

• High clock CPUs (modern Intel or AMD(EPYC or Ryzen)) with strong single-thread scores.
• 32–64 GB RAM for heavy modpacks and databases.
• NVMe storage for fast mission loads and restarts.
• Unmetered or high-capacity links so 40–80 players do not saturate the line.
• Global locations so your unit can pick a region that keeps ping low.

For Arma 3 itself, prioritize a CPU-focused dedicated server with strong single-core performance, enough RAM, and fast NVMe storage.

You do not need this on day one. It becomes the right move when your community fills servers, runs complex missions, and expects stable frames every weekend.

Wrap-Up And Next Steps 

You now know how Arma 3 dedicated server hosting works on Windows and Linux, how to size hardware, and how to keep missions and mods stable. 

You have a clear view of when a home box is fine, when a game panel covers casual play, and when dedicated bare metal makes more sense. 

If you are ready to move from small friend sessions to a stable public server, look at dedicated servers with strong single-core CPU performance, enough RAM, and fast NVMe storage.

You can start on a smaller box, then step up to stronger hardware when your unit grows.

FAQ

Q. Can you host an Arma 3 server for free?

You can get “free Arma 3 server hosting” by running the server on your own PC or a short-term VPS. You still pay with your power, bandwidth, and time.

Q. How many players can I run on a mid-range desktop?

A solid 4–6 core gaming CPU with 16 GB RAM and SSD storage can usually handle 10–20 players with light to medium mods, if your upload line is strong.

Q. Is Arma 3 dedicated server download separate from the game?

Yes. SteamCMD installs a separate Arma 3 dedicated server app (ID 233780). You do not need to copy your full client game folder to the host.

Q. Can I run Arma 3 dedicated server mods on Linux?

Yes. Arma 3 dedicated server Linux supports the same mod structure. You still use @ModName folders, .bikey keys in keys/, and -mod / -serverMod flags.

Q. Is GamePanel ARMA 3 server hosting enough for Antistasi?

For small Antistasi groups, a good game panel or “Arma 3 gameservers” style host can work. For 30–60 players with heavy AI, a dedicated Arma 3 server with a strong single-core CPU is safer.

Q. How do I move from home hosting to a dedicated ARMA 3 server?

Copy your arma3server folder, configs, missions, and database (for Exile or Life) to the new host. Open the same UDP 2302–2306 ports, test with direct connect, then point your group to the new IP.