Skip to content

Arma 3 Setup

Host your Arma 3 milsim server with HeadlessClient support, mission management, and mod synchronization. This guide covers setup, persistence frameworks (Exile/Epoch), and performance optimization for large-scale operations.


PlanBest ForPlayer Capacity
StarterTraining ops, small co-op, optional single HC~10-20 players
ProSurvival mods (Exile/Epoch), database provisioning~30-50 players
PremiumBattalion-sized milsim, heavy AI, multiple HCs~60-80 players

  1. Create your server

    Go to panel.mambahost.comCreate ServerArma 3

  2. Choose your plan and deploy

    Select your plan and region — deployment completes in about 2 minutes

  3. Retrieve your credentials

    Find SFTP and RCON info in the console output

  4. Configure backups and schedules

    Enable automated backups and set scheduler jobs for restarts and mission rotations

  5. Upload missions and connect

    Upload your mission PBOs and connect to test your server


  1. Upload mission files to /mpmissions

  2. Upload mods to /steamapps/workshop/content/107410 or /mods

  3. Reference mods in startup using -mod=@ace;@rhs;@cba_a3

  4. Add Workshop collection IDs in the panel for automatic mod sync on restart

  5. Update signature keys — keep .bikey files in /keys updated when adding mods


HeadlessClients (HCs) offload AI processing from the main server.

  1. Enable HC slots (available on Pro+ plans)

  2. Configure your server config:

    headlessClients[]={"127.0.0.1"};
    localClient[]={"127.0.0.1"};
  3. Set HC password to match your server password

  4. Monitor HC connectivity and schedule tasks to restart dropped HCs


  1. Request MySQL credentials from support

  2. Configure database DSNs in your mod configs

  3. Import the framework’s SQL schema

  4. Schedule regular database dumps before wipes for backup


MaxMsgSend=1024;
MinBandwidth=131072;
MaxBandwidth=10000000000;
RecommendationWhy
Set view distances per role2-4 km infantry, 6-12 km air
Offload AI to HeadlessClientsReduces main server load
Schedule weekly restartsClears memory and prevents drift
Create pre-op backupsQuick rollback if missions break

FilePurpose
server.cfgServer name, passwords, admin settings
basic.cfgNetwork and bandwidth configuration
beserver.cfgBattlEye anti-cheat settings

Create separate panel/RCON accounts for different roles:

  • Zeus operators
  • Server admins
  • Mission developers

ProblemSolution
Mission fails to loadEnsure clients and server have identical mod lists and requiredAddons references
HC won’t connectVerify firewall allows loopback, HC password matches, and loopback = true
Desync/warpingLower view distance, reduce ambient AI, tune basic.cfg bandwidth values
Signature kicksUpdate .bikey files when mods change; remove outdated keys
Database issues (Exile/Epoch)Check MySQL credentials, enforce indexes, schedule dumps before wipes