{"name":"Arma 3: Dedicated Server","title":"Arma 3: Dedicated Server","type":"topic","url":"https://community.bistudio.com/wiki/Arma_3:_Dedicated_Server","revid":378682,"updated":"2026-05-22T16:14:01Z","aliases":["Arma 3 Dedicated Server","Arma 3 Dedicated Server (Chinese Simplified)","Arma 3 Dedicated Server (Chinese Traditional)","Arma 3: Dedicated Server (Chinese Simplified)","Arma 3: Dedicated Server (Chinese Traditional)","Server","server"],"markdown":"|  |  |\n|---|---|\n| > [!NOTE]<br>> **Arma 2:** For Arma 2/Arma 2:OA, see Arma 2: Dedicated Server. | > [!NOTE]<br>> For other titles, see Dedicated Server. |\n\nThis page contains useful information on how to install and configure an Arma 3 server and includes step by step guides of the install process. Also information on how to configure and run a server.\nThe majority of directories and paths are customisable, however those defined are all consistent with the tutorial instructions.\n\nMuch of the tutorial here was created using [this forum guide](https://forums.bohemia.net/forums/topic/139003-tutorial-installation-configuration-of-arma3-dedicated-server/).\n\n> [!NOTE]\n> About steamCMD utility: if you are using it on a dedicated host to install and update Arma 3 dedicated server, it is a good practice to create a separate steam account for that.\n> Arma 3 Dedicated server package is available for free (does not require regular Arma 3 to be purchased).\n\n### Simple Setup (Arma 3 v1.24)\n\nThe introduction of the Arma 3 Launcher with Arma 3 v1.24 made it easier to use the game's exe as a server with a simplified server mods configuration.\n\n- Start the Arma 3 Launcher from Steam\n- Go to the **PARAMETERS > All Parameters > Host** section and tick **Server**\n- In the **MODS** tab, select the server's wanted mods\n- Press \"Play\"\n\nThis starts a dedicated server with the selected mods. This is adapted for a small casual dedicated server.\n\n### Installation\n\n#### Requirements\n\n1. Steam Account\n1. Supported Operating System:\n   - Windows Server 2008 or later\n   - A modern Linux distribution\n1. Minimum Hardware:\n\n**[source](https://www.servermania.com/kb/articles/what-are-the-requirements-for-an-arma-3-server/)**\n\n| Part | Minimum | Recommended |\n|---|---|---|\n| CPU | 2.4 GHz Dual-Core | 3.5 GHz Quad-Core |\n| RAM | 2GB | 4GB |\n| Storage | 32 GB HDD | 32 GB SSD |\n\n> [!WARNING]\n> Arma 3 server does **not** support [IPv6](https://en.wikipedia.org/wiki/IPv6) or [DSlite IPv4 via IPv6 tunnel](https://en.wikipedia.org/wiki/IPv6_transition_mechanism#Dual-Stack_Lite_.28DS-Lite.29).\n> You **must** have a **real [IPv4](https://en.wikipedia.org/wiki/IPv4) connection**.\n> If you are in doubt, contact your Internet Service Provider.\n\n#### Instructions (Windows o/s)\n\nThe following instructions will guide you through setting up one Arma 3 server on 1 box, however they will also set the foundations for installing multiple servers on that same box:\n\n1. Install the latest version of [DirectX](http://support.microsoft.com/kb/179113)\n1. Create the following empty directories\n   - D:\\Apps\\Steam\n   - D:\\Games\\Arma3\\A3Master\n   - D:\\Games\\Arma3\\A3Files\n1. Download [steamcmd.exe](https://developer.valvesoftware.com/wiki/SteamCMD) and save it to your targetted Steam install directory (E.g `D:\\Apps\\Steam`)\n1. Run the steamcmd.exe. (This will download and install the required steam files to your custom steam directory)\n1. Create an Arma3server_steamcmd_example.cmd file and save it to D:\\Games\\Arma3\\A3Files\n1. Run the Arma3server_steamcmd_example.cmd file\n1. Just after logging into Steam, the console window will hang and ask for a validation key\n   - Steam will have automatically sent you an email with this validation code, which you then need to input at the command prompt\n   - The Update console window should then continue to run and install Arma 3 ((DEV or STABLE) version to the target directory as defined in the .cmd file) eg (D:\\Games\\Arma3\\A3Master)\n1. Create a shortcut for the Arma3Server.exe on the server desktop\n1. Add the following parameters to the Target Line in the shortcut tab of the newly created desktop shortcut\n   - -port=2302 (Required if running multiple server instances including any previous Arma 2 instances)\n   - \"-profiles=D:\\Games\\Arma3\\A3Master\"\n   - -config=CONFIG_server.cfg\n   - -world=empty\n     - so it looks something similar to the following\n     - \"D:\\Games\\Arma3\\A3Master\\arma3server.exe\" **\"-profiles=D:\\Games\\Arma3\\A3Master\" -port=2302 -config=CONFIG_server.cfg -world=empty**\n1. Setup the Port Forwarding in your firewall and/or router accordingly, also doesn't seems like implemented in some routers Port Trigger feature works with Arma 3 Server (tested with ASUS RT-N66U)\n1. Make sure you have:\n   - Network Discovery enabled for your network type (the setting can be found in [Control Panel\\Network and Internet\\Network and Sharing Center\\Advanced sharing settings]. If you have problem with its state reset on the interface reopen, check if all of the required for this feature services are running: DNS Client, Function Discovery Resource Publication, SSDP Discovery, UPnP Device Host; this makes the server accessible from internet\n   - Windows Media Player Network Sharing Service enabled (makes server joinable) ;\n\nIf you cannot connect to server through server browser try to use \"direct connect\":\nthis is a client side issue (doesn't mean other clients will have it too), reason for the issue for now unknown,\nI can say it is not related to: Windows services, Windows network settings, network routers, firewalls...\n\nDevice Host:\n(note: Changes to the above 2 settings require Arma relaunch to be applied, as for server same for client machines;)\nCreate a simple Notepad document called \"CONFIG_server.cfg\" and save it to the root folder of your Arma 3 install on the server `D:\\Games\\Arma3\\A3Master`\n\n1. Start up your shortcut, check the server runs. (You will see a console pop up in your desktop after a few seconds)\n1. Close the console window down, then you will need to edit the following files which will have been automatically created\n   - D:\\Games\\Arma3\\A3Master\\Users\\Adminstrator\\Administrator.Arma3Profile\n   - D:\\Games\\Arma3\\A3Master\\Users\\Administrator\\Arma3.cfg\n1. Restart the server\n1. Start up your client Arma3.exe (Running the same branch as the server, (eg Stable or DEV) and you should then be able to see your server in the server browser (Filters are available to reduce the server list)\n1. Login to your server using the password you defined in CONFIG_server.cfg by pressing <kbd>/</kbd> to open the chat window and then type `#login ADMINPASSWORD` followed by <kbd>Return ↵</kbd>.\n\n   > [!WARNING]\n   > Make sure to never forget the '#' in front of any server command!\n1. Once logged in you will be presented with a mission list, select one of the missions to start the game\n1. Prove the stability of your server by running BI missions initially before you start adding user made content\n\n#### Instructions (Linux o/s)\n\n##### Installation\n\nAs a security best practice, create a user to run steam instead of running as root or an administrator.\nThis way, if your Arma 3 server is compromised the attacker will find it more difficult to access the rest of the operating system.\n\n```\nuseradd -m -s /bin/bash steam\n```\n\nSwitch to the newly created steam user.\n\n```\nsudo -i -u steam\n```\n\nCreate a new directory for SteamCMD to avoid cluttering the home directory.\n\n```\nmkdir ~/steamcmd && cd ~/steamcmd\n```\n\nDownload the [SteamCMD for Linux](https://developer.valvesoftware.com/wiki/SteamCMD#Linux) tarball from the link at the Valve Developer Community page.\nUse a command line download tool such as `wget` or `curl`.\n\nExtract the tarball.\n\n```\ntar xf steamcmd_linux.tar.gz\n```\n\nExecute steamcmd.sh. It will install the rest of the Steam client and start the Steam client shell.\nIf this step fails on a 64-bit OS, you likely need to [install 32-bit libraries](https://developer.valvesoftware.com/wiki/SteamCMD#32-bit_libraries_on_64-bit_Linux_systems).\n\n```\n./steamcmd.sh\n```\n\nChange the directory SteamCMD will install the server in.\n\n```\nforce_install_dir ./arma3/\n```\n\nAt the Steam client shell, login with a valid Steam username and password.\nThe Valve Developer Community Wiki [recommends that you create a new Steam account for this](https://developer.valvesoftware.com/wiki/SteamCMD#SteamCMD_Login).\nSteamCMD will cache the login credentials and anyone who gains access to your server will be able to log into the account used here.\nIn addition, you cannot log into a single Steam account from two places at once. You do not need to have Arma 3 purchased on the Steam account used here to download the server.\nTherefore, you should create a new Steam account with no purchases only for use on this server.\n\n```\nlogin myusername\n```\n\nInstall the Arma 3 Linux dedicated server. The validate option will check for corruption.\n\n```\napp_update 233780 validate\n```\n\nExit SteamCMD.\n\n```\nexit\n```\n\nCreate the directories used to store the profile files and Arma3.cfg file.\n\n```\nmkdir -p ~/\".local/share/Arma 3\" && mkdir -p ~/\".local/share/Arma 3 - Other Profiles\"\n```\n\n##### Updating\n\nYou will have to update the server whenever a patch is released on Steam.\n\nIf the server is running, stop it by pressing Ctrl+C in the terminal (or screen/tmux instance) that the server is attached to. Otherwise, switch to the steam user.\n\n```\nsudo -u steam -i\n```\n\nLaunch steamcmd.\n\n```\ncd /home/steam/steamcmd\n./steamcmd.sh\n```\n\nSet the Arma 3 installation directory to the same directory used above.\n\n```\nforce_install_dir ./arma3/\n```\n\nLogin to the Steam account used in the installation section above.\n\n```\nlogin myusername\n```\n\nUpdate the Arma 3 Linux dedicated server. The validate option will check for corruption.\n\n```\napp_update 233780 validate\n```\n\nExit SteamCMD.\n\n```\nexit\n```\n\n##### Configuration\n\nYou will most likely want to customise your server's name, password, security settings, and so on with a server.cfg file. Change to the arma3 directory and create and edit your server.cfg file.\n\n```\ncd ~/steamcmd/arma3\nvim server.cfg\n```\n\nIf you don't know how to use vim, use nano instead.\n\n```\nnano server.cfg\n```\n\nSee server config for documentation and examples.\n\nThe first time you run the server it will auto-create a profile file at `~/.local/share/Arma 3 - Other Profiles/server/server.Arma3Profile`.\nEdit this file to customise difficulty settings.\n\n> [!IMPORTANT]\n> The `-profiles=` parameter is broken on Linux - you **must** place your profiles in this directory.\n\n##### Launching\n\nA Linux executable is provided to launch the server. Make sure that you are running it under the steam user and not root or another administrator!\n\n```\ncd /home/steam/steamcmd/arma3\n./arma3server_x64 -name=server -config=server.cfg\n```\n\nNB: If you are using the `-mod=` parameter, you must specify relative paths *within or below* the Arma 3 directory. Symlinks will work.\n\nThe arma3server_x64 process will attach to the current terminal.\nIf you are connected to the server over SSH, the server will stop when you disconnect.\nYou can keep the server running using a terminal multiplexeer like [GNU Screen](https://www.gnu.org/software/screen/) or [tmux](http://tmux.sourceforge.net/).\nThere are many tutorials online on how to use these programs to detach and reattach processes from and to a terminal.\n\nYou can safely stop the server by pressing Ctrl+C in the terminal (or screen/tmux instance) that the server is attached to.\n\nFor older 32-bit executable use ./arma3server instead of ./arma3server_x64.\n\n##### Case sensitivity & Mods\n\nSome mods such as CUP Terrains and @ALiVE will not function if there are capital letters in any of their file names. If you do not update your mods on a regular basis, you can just use the command\n\n```\nfind . -depth -exec rename 's/(.*)\\/([^\\/]*)/$1\\/\\L$2/' {} \\;\n```\n\nin the directory where your mods are located. This will recursively search the directory tree and make all the filenames lowercase.\n\nIf you regularly update your mods using, e.g. Arma3Sync, you will find that this will redownload any files/folders that have changed case every time you run it.\nThe solution to this is to use a package called \"ciopfs\" - Case Insensitive On Purpose Filesystem. You should first run the \"find . -depth...\" command mentioned above on your mod folder.\nThen, make an empty directory outside of the mods directory, e.g. mods_caseinsensitive. You then mount the directory with:\n\n```\nciopfs mods mods_caseinsensitive\n```\n\nand tell Arma3Sync to synchronise in the mods_caseinsensitive directory. Once it has finished, you can unmount the directory with:\n\n```\nfusermount -u mods_caseinsensitive\n```\n\nYou should find that all of the files in the original mods directory are lowercase.\n\n### Additional Info\n\n#### Useful Links\n\n##### Further Reading\n\n- [Steam Cmd Tutorial](https://developer.valvesoftware.com/wiki/SteamCMD)\n- [Dedicated Server Status (Linux info)](https://forums.bohemia.net/forums/topic/139605-dedicated-server-status/)\n- [Kelly's Heroes Dedicated server guide](http://www.kellys-heroes.eu/files/tutorials/dedicated/arma3dedicated.php#one)\n- In Game server commands\n- In Game admin commands\n- Command line params\n- Basic.cfg\n- Steam Difficulty settings\n- Server Configuration\n- [Sim-link GUI](https://code.google.com/p/symlinker/)\n\n#### File Locations\n\nSome files are automatically created when you use certain commandline parameters\nSome files have to be created manually.\nIf you have followed the instructions accurately, you will now have the following files and directories in addition to the clean install\n\n- D:\\Games\\Arma3\\A3Master\\Users\\Administrator\\**Administrator.Arma3Profile** *(Difficulty settings)*\n- D:\\Games\\Arma3\\A3Master\\Users\\Administrator\\**Administrator.vars.Arma3Profile** *(Some binarised content which you cannot edit)*\n- D:\\Games\\Arma3\\A3Master\\Users\\Administrator\\**Arma3.cfg** *(Bandwidth settings)*\n- D:\\Games\\Arma3\\A3Master\\**MPMissions\\** *(This is where custom made mission.pbo's need to be placed)*\n- D:\\Games\\Arma3\\A3Master\\**arma3.rpt** *(Debug Log, automatically created every time the arma3server.exe is started)*\n- D:\\Games\\Arma3\\A3Master\\**CONFIG_server.cfg** *(Manually created)*\n- D:\\Games\\Arma3\\A3Files\\**Arma3server_steamcmd_example.cmd** *(Manually created)*\n- D:\\Apps\\Steam\\\n\n#### Port Forwarding\n\nArma 3 uses the same default ports as Arma 2 with the addition of several ports. So if you intend running Arma 2 and Arma 3 servers on the same machine, you need to edit the ports used.\n**Default ports are all UDP** and as follows:\n\n**Incoming**\n\n- 2302 (default Arma 3 Game port) + (VON is now part of main gameport due to NAT issues)\n- 2303 (STEAM query, +1)\n- 2304 (Steam port, +2)\n- 2305 (VON port, +3 - not used atm. but allocated)\n- 2306 (BattlEye traffic, +4)\n\n**Outgoing**\n\n| DST Port | Protocol | Destination | Comment |\n|---|---|---|---|\n| 2344 | TCP + UDP | 81.0.236.111 | BattlEye - arma31.battleye.com |\n| 2345 | TCP | 81.0.236.111 | BattlEye - arma31.battleye.com |\n| 2302-2306 | UDP | any | Arma Server to Client Traffic |\n| 2303 | UDP | any | Arma Server STEAM query port |\n| 2304 | UDP | any | Arma Server to STEAM master traffic |\n\nTo define the Arma 3 Game port used,\nstate -port= **** in your command line arguments (Where **** is the new initial Arma 3 Game, e.g 2302)\n\nand to define your Steam ports\nadd the following lines to your CONFIG_server.cfg (editing the actual port numbers as required)\n\n> [!NOTE]\n> Steam ports are now linked to game-port as +1 for query and +2 to-master.\n\nIf you are running multiple servers, i would suggest the following format\n\n**SERVER 1**\n\n2302 UDP (gameport + VON)\n\n2303 UDP (STEAM query port)\n\n2304 UDP (STEAM master port)\n\n2305 UDP (VON reserved port but not used atm.)\n\n2306 UDP (BattlEye traffic port)\n\nso open ports 2302-2306\n\n... and leave at least **100** ports between the next 2nd server set\n\n**SERVER 2**\n\n2402 UDP (gameport + VON)\n\n2403 UDP (STEAM query port)\n\n2404 UDP (STEAM master port)\n\n2405 UDP (VON reserved port but not used atm.)\n\n2406 UDP (BattlEye traffic port)\n\nso open ports 2402-2406\n\nand leave at least **100** ports between the next 3rd server set, etc.\n\n##### NAT traversal\n\nUPnP allows you to automatically create port forwarding on your router to bypass NAT (UPnP enabled routers are required).\nThe functionality can be easily enabled in server config as described in the server.cfg page.\n\n#### Configuring for stable or Dev branch\n\nEdit the `Arma3server_steamcmd_example.cmd` as defined below then run it\n\n- To select Development version\n\n```\nSET A3BRANCH=107410 -beta development\n```\n\n- To select stable build (Dedicated server package)\n\n```\nSET A3BRANCH=233780 -beta\n```\n\n- To select stable build (Full client\\server package)\n\n```\nSET A3BRANCH=107410\n```\n\n**Important Feature**\n\nSince **12th March 2013** the development branch and the stable branch versions are no longer compatible. This means:\n\n- Only DEV clients can connect to a DEV server\n- Only Stable clients can connect to stable servers\n\n#### Advanced Configuration\n\n#### Bandwidth Optimisation\n\n#### Multiple Server configuration\n\nThere are various methods available to run multiple Dedicated Arma 3 servers on the same box.\nEach server instance requires:\n\n- Its own unique set of ports\n- Its own profile\n- Its own config\n\n[This post](https://forums.bohemia.net/forums/topic/139003-tutorial-installation-configuration-of-arma3-dedicated-server/?page=10&tab=comments#comment-2344472) explains it more in depth.\n\nEach method has some pro's and cons\nTo select the preferred methodology that suits your requirements you need to have considered the following\n\n- The useage of the \"Keys\" folder\n- The useage of the \"MpMissions\" folder\n- Available Hard drive space\n- Update management\n\n##### Method 1\n\nsee [THIS POST](https://forums.bohemia.net/forums/topic/139003-tutorial-installation-configuration-of-arma3-dedicated-server/?page=9&tab=comments#comment-2343865) for more detailed information\nThis is copy of the master install into a different directory\nAs may times as you have space for\n\n**Pros**\n\n- Most robust\n- Unique MpMissions folder\n- Unique \"keys\" folder\n- Allows ability to run separate instances of different branches of the game, (E.g Dev or Stable)\n\n**Cons**\n\n- Uses more drive space\n- Requires more effort to create and automate the updating process\n\n##### Method 2\n\nThis uses 1 master install folder and has renamed arma3server.exe's in sub folders of the master\nsee THIS POST for more detailed information\n\n**Pros** (Compared to Method 1)\n\n- Uses less space than Method 1\n- Updating will be easier\n\n**Cons** (Compared to Method 1)\n\n- Not very robust\n- Shares MPMissions folders with all the other exe's (Will create a very cluttered MpMissions folder and allows admins to select addon required missions for a mod this server instance isn't running\n- Shares \"keys\" folder with all other exe's (This can cause an issue when running various differing -mod servers)\n- Will not allow you to run separate instances of different branches of the game\n\n##### Method 3\n\nThis is a hybrid of method 1, in that it is essentially a \"Virtual\" copy of the master install in a different directory\nthe difference being that many folders are [symlinked](https://en.wikipedia.org/wiki/Symbolic_link) to the initial Master directory\nsymlink GUI:\n\n**Pros** (Compared to Method 1)\n\n- Uses less drive space (As you wont have multiple copies of the addons folder)\n- Allows for unique MpMissions folder if desired\n- Allows for unique \"keys\" folder if desired\n- Updating will be easier\n\n**Cons** (Compared to Method 1)\n\n- Requires more effort to initially create the symlinks and directories\n- Will not allow you to run separate instances of different branches of the game at the same time, (E.g Dev or Stable)\n\nFor example, on Linux, if you initially have the following folder layout:\n\n```batch\n ~/game_servers/\n    arma3server/\n    ...\n    mods # folder where you keep your mods\n    arma3server\n    ...\n```\n\nInstead of copying the folders as directed in (Compared to Method 1), run the following commands:\n\n```batch\ncd ~/game_servers/\nmkdir arma3server_2/\nln -sr arma3server/* arma3server_2\ncd arma3server_2\nrm keys mpmissions mods\nmkdir keys\nmkdir mpmissions\nmkdir mods\n```\n\nThen proceed with the rest of the instructions in METHOD 1.\n\n##### Method 4\n\nYou can of course mix and match all 3 previous methods to suit your specific requirements.\n\n##### Method 5 (Arma 3 v2.22)\n\nYou can combine the -port, -profiles, -mpmissions and -keysFolder startup parameters to run multiple servers from the same Arma 3 installation directory while using different ports and separate directories for profiles, missions, and keys.\n\nThis approach allows you to host multiple servers without using symbolic links or duplicating the entire server installation.\n\nExample batch script for running multiple servers:\n\n```batch\n@echo off\n\nrem Starting TvT server\nstart arma3server_x64.exe -port=2302^\n -name=TvT^\n -profiles=Profiles\\TvT^\n -mpmissions=Profiles\\TvT\\MPMissions^\n -keysFolder=Profiles\\TvT\\Keys^\n -cfg=Profiles\\TvT\\Configs\\Basic.cfg^\n -config=Profiles\\TvT\\Configs\\Server.cfg^\n -mod=\"@CBA_A3;@ace\"\n\nrem Starting PvE server\nstart arma3server_x64.exe -port=2402^\n -name=PvE^\n -profiles=Profiles\\PvE^\n -mpmissions=Profiles\\PvE\\MPMissions^\n -config=Profiles\\PvE\\Configs\\Server.cfg\n```\n\nBefore running the script, create the following directory structure:\n\n```\nArma 3 installation/\n├── Profiles/\n│   ├── TvT/\n│   │   ├── MPMissions/\n│   │   ├── Keys/\n│   │   └── Configs/\n│   │       ├── Basic.cfg\n│   │       └── Server.cfg\n│   │\n│   └── PvE/\n│       ├── MPMissions/\n│       ├── Keys/\n│       └── Configs/\n│           └── Server.cfg\n│\n└── arma3server_x64.exe\n```\n\n#### Dedicated Server & Client configuration\n\n> [!NOTE]\n> In order for the Arma 3 server to be able to connect to the Steam servers, the Arma 3 server has to be ping-able (ICMP 8 - Echo Reply) as well as opened TCP/UDP ports.\n\nThe only known issue, is to make sure you start the server up before you start the steam client\nFailing to do this causes steam port issues and your client will not be able to connect to the server\n\n#### Headless Client\n\n> [!NOTE]\n> See Arma 3: Headless Client for changes in headless clients.\n\nA Headless Client can be used by missions to offload AI processing to a dedicated client, freeing up the dedicated server process from most AI processing.\nThus more AI units can be spawned and the server process will be able to dedicate most of it is processing towards communication with the clients.\nFor a Headless Client/Dedicated Server to function together efficiently, they both need to be connected to each other via extremely low latency and high bandwidth.\nEffectively, they need to be on the same LAN at least, but preferably running on the same computer.\n\n##### Setup and Execution\n\n- Headless Client for Arma 3 requires a **valid active Steam account logged in** to function (see [Dwarden's post](https://forums.bohemia.net/forums/topic/140621-arma-3-headless-client/?page=5&tab=comments#comment-2481581))\n- A Headless Client is simply Arma3.exe run from the command line with parameters, for example:\n\n```cpp\narma3.exe -connect=localhost -port=2444 -client -nosound -password=some_server_password -name=HC -profile=HC -mod=@CBA_A3;@blah;@blah;@blah\n```\n\nIn the example above, the headless client is running on the same host as the dedicated server.\nIt uses a profile called **HC** and connects to the server with a password as required by the server (the password is for password protected servers, optional).\nThe server in this example is running on port 2444, alter this to the port of your server.\n\n- The Headless Client profile needs to be created like any other profile in Arma 3 (Note: It is best if you name this profile **HC**)\n\nNo configuration of the profile is necessary, but after creation, edit **HC.Arma3Profile** located in **C:\\Users\\yourusername\\Documents\\Arma 3 - Other Profiles\\HC** and add this line:\n\n```cpp\nbattleyeLicense=1;\n```\n\nAlternatively, you can use the full Arma 3 client to connect to any multiplayer server with BattlEye enabled and accept the BattlEye License Agreement,\nwhich will do the same thing as manually editing **HC.Arma3Profile**.\n\nOnce the profile is ready, copy the profile directory to **C:\\Users\\yourusername\\Documents\\Arma 3 - Other Profiles** on the server (if the profile was not created on the server).\nIf the profile was created on the server or is not going to run on the server and is already on the computer it is going to run on, then it is ready to go.\n\n- If the Headless Client is on the server, the server's cfg must have the local loopback address as seen below (e.g. A3Server.cfg):\n\n```cpp\nlocalClient[]={ \"127.0.0.1\" };\nheadlessClients[]={ \"127.0.0.1\" };\nbattleyeLicense=1;\n```\n\nDwarden suggests that **battleyeLicense=1;** be in the server's config, but it is unclear whether this is actually necessary.\n([Dwarden's post](https://forums.bohemia.net/forums/topic/150815-headless-client-battleye/?tab=comments#comment-2413319)).\n\n- If the Headless Client is running in the same network or the same computer, the server's config has to have the address in **localClient[]=x.x.x.x**.\n\nThis will allow the server to communicate with the Headless Client using unrestricted bandwidth. It is also required to add the adress to **headlessClients[]={ \"x.x.x.x\" };**.\nMultiple headless clients at different addresses can be added:\n\n```cpp\nlocalClient[]={ \"127.0.0.1\", \"192.168.1.10\", \"192.168.1.210\" };\nheadlessClients[]={ \"127.0.0.1\", \"192.168.1.10\", \"192.168.1.210\" };\nbattleyeLicense=1;\n```\n\n##### Headless Client on a Dedicated Server Notes\n\nIf the Arma 3: Headless Client and a Dedicated Server are running on the same Windows computer (VM or physical),\nit *may* be beneficial to set processor affinity to prevent execution intensive threads from being scheduled across the same (v)CPUs.\n\n> [!WARNING]\n> Do **not** use this if you do not know what you are doing, as performance may be strongly impacted.\n\nThe operating system will generally schedule threads efficiently, but manual CPU allocation is possible.\nThis can be achieved by right-clicking on the process (e.g. Arma3Server.exe(*32)) in the **processes tab** of the Windows Task Manager and selecting **Set Affinity...**.\nBe aware that on a physical intel CPU, the odd numbered CPUs are Hyper-thread cores.\n\n> [!NOTE]\n> You can use automated solution for affinity assign via batch file with commandline `CMD /AFFINITY HEXvalue` e.g. `CMD /C START /AFFINITY 0xF3 arma3server.exe`.\n\nIt has been observed that although the Arma server and client processes will kick off multiple threads, the bulk of processing is used up by only one or two threads.\nFor example, spawning 50 AI units does not generate 50 threads.\nThere is one thread in the process that handles all of the AI units, irrespective of how many have been spawned.\nIn this way, the ARMA server and client processes do not make maximal use of the processing capability found in modern processors and so AI counts do not scale easily.\nAs such, faster CPU core speed is king and offloading the AI to multiple headless clients on the same computer will probably produce the best possible results for complex missions involving many AI units (albeit an expensive way to get the results).\n\n> [!NOTE]\n> Read the complete and detailed HOW-TO guide on Headless Client: Arma 3: Headless Client.\n\n-\n\n#### Example Files\n\n##### Arma3server_steamcmd_example.cmd\n\n- Standalone Server Package (no need for game ownership on STEAM account)\n- Note: you might be asked to authorise your STEAM account due to STEAMguard (check email)\n- Note: it needs to be ran two or three times (1st authorise, 2nd STEAMcmd update itself, (when done, quit), 3rd update the Arma 3 Server data package)\n- Note: STEAMcmd needs to be in separate folder from STEAMclient (so always use unique folder like \"STEAMcmd\") to avoid file conflicts\n- Note: Arma 3 server data package needs to be in separate folder from Arma 3 client (so always use unique folder like \"A3server\" or \"Arma3server\") to avoid file conflicts\n- Code:\n\n  ```batch\n  @echo off\n  rem http://media.steampowered.com/installer/steamcmd.zip\n  SETLOCAL ENABLEDELAYEDEXPANSION\n\n      :: DEFINE the following variables where applicable to your install\n\n      SET STEAMLOGIN=mylogin mypassword\n      SET A3serverBRANCH=233780 -beta public\n          :: For stable use 233780 -beta public\n          :: For Dev use 233780 -beta development\n                  :: Note: quotation marks need to be wrapped around the entire \"+app_data......\"\n                  :: There is no DEV branch data yet for Arma 3 Dedicated Server package!\n\n      SET A3serverPath=D:\\Games\\Arma3\\A3Master\n          SET STEAMPATH=D:\\Apps\\Steam\n\n  ::\n\n  echo.\n  echo You are about to update Arma 3 server\n  echo     Dir: %A3serverPath%\n  echo     Branch: %A3serverBRANCH%\n  echo.\n  echo Key \"ENTER\" to proceed\n  pause\n  %STEAMPATH%\\steamcmd.exe +force_install_dir %A3serverPath% +login %STEAMLOGIN% +\"app_update %A3serverBRANCH%\" validate +quit\n  echo.\n  echo Your Arma 3 server is now up to date\n  echo Press \"ENTER\" to exit\n  pause\n  ```\n\n##### CONFIG_server.cfg\n\n```cpp\n//\n// server.cfg\n//\n\n// NOTE: More parameters and details are available at http://community.bistudio.com/wiki/server.cfg\n\n// STEAM PORTS (not needed anymore, it is +1 +2 to gameport)\n// steamPort        = 8766;        // default 8766, needs to be unique if multiple servers are on the same box\n// steamQueryPort    = 27016;    // default 27016, needs to be unique if multiple servers are on the same box\n\n// GENERAL SETTINGS\nhostname        = \"My Arma 3 Server\";    // Name of the server displayed in the public server list\n//password        = \"ServerPassword\";        // Password required to join the server (remove // at start of line to enable)\npasswordAdmin    = \"AdminPassword\";        // Password to login as admin. Open the chat and type: #login password\nmaxPlayers        = 40;    // Maximum amount of players, including headless clients. Anybody who joins the server is considered a player, regardless of their role or team.\npersistent        = 1;    // If set to 1, missions will continue to run after all players have disconnected; required if you want to use the -autoInit startup parameter\n\n// VOICE CHAT\ndisableVoN        = 0;    // If set to 1, voice chat will be disabled\nvonCodecQuality    = 10;    // Supports range 1-30, the higher the better sound quality, the more bandwidth consumption:\n                        // 1-10 is 8kHz (narrowband)\n                        // 11-20 is 16kHz (wideband)\n                        // 21-30 is 32kHz (ultrawideband)\n\n// VOTING\nvoteMissionPlayers    = 1;        // Minimum number of players required before displaying the mission selection screen, if you have not already selected a mission in this config\nvoteThreshold        = 0.33;        // Percentage (0.00 to 1.00) of players needed to vote something into effect, for example an admin or a new mission. Set to 9999 to disable voting.\nallowedVoteCmds[] =                // Voting commands allowed to players\n{\n    // { command, preinit, postinit, threshold } - specifying a threshold value will override \"voteThreshold\" for that command\n    { \"admin\", false, false},        // vote admin\n    { \"kick\", false, true, 0.51},    // vote kick\n    { \"missions\", false, false},        // mission change\n    { \"mission\", false, false},        // mission selection\n    { \"restart\", false, false},        // mission restart\n    { \"reassign\", false, false}        // mission restart with roles unassigned\n};\n\n// WELCOME MESSAGE (\"message of the day\")\n// It can be several lines, separated by comma\n// Empty messages \"\" will not be displayed, but can be used to increase the delay before other messages\nmotd[] =\n{\n    \"Welcome to My Arma 3 Server\",\n    \"Discord: discord.somewhere.com\",\n    \"TeamSpeak: ts.somewhere.com\",\n    \"Website: www.example.com\"\n};\nmotdInterval = 5;    // Number of seconds between each message\n\n// MISSIONS CYCLE\nclass Missions\n{\n    class Mission1\n    {\n        template    = \"MyMission.Altis\";    // Filename of pbo in MPMissions folder\n        difficulty    = \"Regular\";            // \"Recruit\", \"Regular\", \"Veteran\", \"Custom\"\n    };\n};\n\n// LOGGING\ntimeStampFormat    = \"short\";                // Timestamp format used in the server RPT logs. Possible values are \"none\" (default), \"short\", \"full\"\nlogFile            = \"server_console.log\";    // Server console output filename\n\n// SECURITY\nBattlEye                = 1;    // If set to 1, BattlEye Anti-Cheat will be enabled on the server (default: 1, recommended: 1)\nverifySignatures        = 2;    // If set to 2, players with unknown or unsigned mods won't be allowed join (default: 0, recommended: 2)\nkickDuplicate            = 1;    // If set to 1, players with an ID that is identical to another player will be kicked (recommended: 1)\nallowedFilePatching        = 1;    // Prevents clients with filePatching enabled from joining the server\n                                // (0 = block filePatching, 1 = allow headless clients, 2 = allow all) (default: 0, recommended: 1)\n\n// FILE EXTENSIONS\n\n// only allow files with those extensions to be loaded via loadFile command (since Arma 3 v1.20)\nallowedLoadFileExtensions[] =        { \"hpp\", \"sqs\", \"sqf\", \"fsm\", \"cpp\", \"paa\", \"txt\", \"xml\", \"inc\", \"ext\", \"sqm\", \"ods\", \"fxy\", \"lip\", \"csv\", \"kb\", \"bik\", \"bikb\", \"html\", \"htm\", \"biedi\" };\n\n// only allow files with those extensions to be loaded via preprocessFile / preprocessFileLineNumbers commands (since Arma 3 v1.20)\nallowedPreprocessFileExtensions[] =    { \"hpp\", \"sqs\", \"sqf\", \"fsm\", \"cpp\", \"paa\", \"txt\", \"xml\", \"inc\", \"ext\", \"sqm\", \"ods\", \"fxy\", \"lip\", \"csv\", \"kb\", \"bik\", \"bikb\", \"html\", \"htm\", \"biedi\" };\n\n// only allow files and URLs with those extensions to be loaded via htmlLoad command (since Arma 3 v1.28)\nallowedHTMLLoadExtensions[] =        { \"htm\", \"html\", \"php\", \"xml\", \"txt\" };\n\n// EVENT SCRIPTS - see http://community.bistudio.com/wiki/Arma_3:_Server_Side_Scripting\nonUserConnected        = \"\";    // command to run when a player connects\nonUserDisconnected    = \"\";    // command to run when a player disconnects\ndoubleIdDetected    = \"\";    // command to run if a player has the same ID as another player in the server\nonUnsignedData        = \"kick (_this select 0)\";    // command to run if a player has unsigned files\nonHackedData        = \"kick (_this select 0)\";    // command to run if a player has tampered files\n\n// HEADLESS CLIENT\nheadlessClients[]    = { \"127.0.0.1\" };    // list of IP addresses allowed to connect using headless clients; example: { \"127.0.0.1\", \"192.168.1.100\" };\nlocalClient[]        = { \"127.0.0.1\" };    // list of IP addresses to which are granted unlimited bandwidth; example: { \"127.0.0.1\", \"192.168.1.100\" };\n```\n\n##### server.Arma3Profile\n\nSee server.armaprofile.\n\n##### Arma3.cfg\n\n> [!NOTE]\n> See basic.cfg for more information.\n\n```cpp\nlanguage=\"English\";\nadapter=-1;\nMinBandwidth=800000;\nMaxBandwidth=25000000;\nMaxMsgSend=384;\nMaxSizeGuaranteed=512;\nMaxSizeNonguaranteed=256;\nMinErrorToSend=0.003;\nMaxCustomFileSize=100000;\nWindowed=0;\nserverLongitude=0;\nserverLatitude=52;\nserverLongitudeAuto=0;\nserverLatitudeAuto=52;\n```\n\n### Support & Troubleshooting\n\n#### Known Issues\n\n1. My server has 2500ms ping in server browser (This is caused by running the steam client as Non Administrator) see http://feedback.arma3.com/view.php?id=9374\n1. MaxMsgSend default is 128, higher values can create Desync problems if the server's available processing and/or bandwidth can not support the higher value\n1. if you run Arma 3 Dedicated server data package on system where is also installed client there is possibility the server will load the full client data instead server data package, this is caused by precedence check in registry.\n   The solution/workaround to this issue is to use arma3server.exe `-mod=` (where empty modline ensure it loads data from where server is placed)\n1. upnp=1; // in server.cfg may result into server not starting for 600 seconds on server with active firewalls / anti-ddos measures ,\n   it's not recommended setting for dedicated-servers where server process related ports are open/forwarded by default\n1. using multiple server instances with too narrow ranges in between each (e.g. first 2302, second 2314) may cause problems with query where second server reports at first range, use of minimum +100 ports for next instance next to 2302 thus 2402 then 2502 etc. for utmost safety use +200 or +1000\n1. engine has legacy automated port increment system for occupied sockets (used for client-listen servers, upnp) where first is tried 2302, then +12 up to 15 times (so 2314, 2326 ... 2482)\n\n#### Live Help\n\nFor live assistance, join the official **[Arma Discord server](https://discord.gg/arma)!**\nEspecially these channels:\n\n- `#server_admins`\n- `#server_linux`\n- `#server_windows`\n- `#server_tools`\n\n#### F.A.Q\n\n### See Also\n\n- Server Options\n- Battleye's RCON\n- Arma 3: Headless Client\n- Multiplayer Server Commands\n- Armed Assault Server Configuration","sections":[{"heading":null,"level":1,"markdown":"|  |  |\n|---|---|\n| > [!NOTE]<br>> **Arma 2:** For Arma 2/Arma 2:OA, see Arma 2: Dedicated Server. | > [!NOTE]<br>> For other titles, see Dedicated Server. |\n\nThis page contains useful information on how to install and configure an Arma 3 server and includes step by step guides of the install process. Also information on how to configure and run a server.\nThe majority of directories and paths are customisable, however those defined are all consistent with the tutorial instructions.\n\nMuch of the tutorial here was created using [this forum guide](https://forums.bohemia.net/forums/topic/139003-tutorial-installation-configuration-of-arma3-dedicated-server/).\n\n> [!NOTE]\n> About steamCMD utility: if you are using it on a dedicated host to install and update Arma 3 dedicated server, it is a good practice to create a separate steam account for that.\n> Arma 3 Dedicated server package is available for free (does not require regular Arma 3 to be purchased)."},{"heading":"Simple Setup (Arma 3 v1.24)","level":3,"markdown":"The introduction of the Arma 3 Launcher with Arma 3 v1.24 made it easier to use the game's exe as a server with a simplified server mods configuration.\n\n- Start the Arma 3 Launcher from Steam\n- Go to the **PARAMETERS > All Parameters > Host** section and tick **Server**\n- In the **MODS** tab, select the server's wanted mods\n- Press \"Play\"\n\nThis starts a dedicated server with the selected mods. This is adapted for a small casual dedicated server."},{"heading":"Installation","level":3,"markdown":""},{"heading":"Requirements","level":4,"markdown":"1. Steam Account\n1. Supported Operating System:\n   - Windows Server 2008 or later\n   - A modern Linux distribution\n1. Minimum Hardware:\n\n**[source](https://www.servermania.com/kb/articles/what-are-the-requirements-for-an-arma-3-server/)**\n\n| Part | Minimum | Recommended |\n|---|---|---|\n| CPU | 2.4 GHz Dual-Core | 3.5 GHz Quad-Core |\n| RAM | 2GB | 4GB |\n| Storage | 32 GB HDD | 32 GB SSD |\n\n> [!WARNING]\n> Arma 3 server does **not** support [IPv6](https://en.wikipedia.org/wiki/IPv6) or [DSlite IPv4 via IPv6 tunnel](https://en.wikipedia.org/wiki/IPv6_transition_mechanism#Dual-Stack_Lite_.28DS-Lite.29).\n> You **must** have a **real [IPv4](https://en.wikipedia.org/wiki/IPv4) connection**.\n> If you are in doubt, contact your Internet Service Provider."},{"heading":"Instructions (Windows o/s)","level":4,"markdown":"The following instructions will guide you through setting up one Arma 3 server on 1 box, however they will also set the foundations for installing multiple servers on that same box:\n\n1. Install the latest version of [DirectX](http://support.microsoft.com/kb/179113)\n1. Create the following empty directories\n   - D:\\Apps\\Steam\n   - D:\\Games\\Arma3\\A3Master\n   - D:\\Games\\Arma3\\A3Files\n1. Download [steamcmd.exe](https://developer.valvesoftware.com/wiki/SteamCMD) and save it to your targetted Steam install directory (E.g `D:\\Apps\\Steam`)\n1. Run the steamcmd.exe. (This will download and install the required steam files to your custom steam directory)\n1. Create an Arma3server_steamcmd_example.cmd file and save it to D:\\Games\\Arma3\\A3Files\n1. Run the Arma3server_steamcmd_example.cmd file\n1. Just after logging into Steam, the console window will hang and ask for a validation key\n   - Steam will have automatically sent you an email with this validation code, which you then need to input at the command prompt\n   - The Update console window should then continue to run and install Arma 3 ((DEV or STABLE) version to the target directory as defined in the .cmd file) eg (D:\\Games\\Arma3\\A3Master)\n1. Create a shortcut for the Arma3Server.exe on the server desktop\n1. Add the following parameters to the Target Line in the shortcut tab of the newly created desktop shortcut\n   - -port=2302 (Required if running multiple server instances including any previous Arma 2 instances)\n   - \"-profiles=D:\\Games\\Arma3\\A3Master\"\n   - -config=CONFIG_server.cfg\n   - -world=empty\n     - so it looks something similar to the following\n     - \"D:\\Games\\Arma3\\A3Master\\arma3server.exe\" **\"-profiles=D:\\Games\\Arma3\\A3Master\" -port=2302 -config=CONFIG_server.cfg -world=empty**\n1. Setup the Port Forwarding in your firewall and/or router accordingly, also doesn't seems like implemented in some routers Port Trigger feature works with Arma 3 Server (tested with ASUS RT-N66U)\n1. Make sure you have:\n   - Network Discovery enabled for your network type (the setting can be found in [Control Panel\\Network and Internet\\Network and Sharing Center\\Advanced sharing settings]. If you have problem with its state reset on the interface reopen, check if all of the required for this feature services are running: DNS Client, Function Discovery Resource Publication, SSDP Discovery, UPnP Device Host; this makes the server accessible from internet\n   - Windows Media Player Network Sharing Service enabled (makes server joinable) ;\n\nIf you cannot connect to server through server browser try to use \"direct connect\":\nthis is a client side issue (doesn't mean other clients will have it too), reason for the issue for now unknown,\nI can say it is not related to: Windows services, Windows network settings, network routers, firewalls...\n\nDevice Host:\n(note: Changes to the above 2 settings require Arma relaunch to be applied, as for server same for client machines;)\nCreate a simple Notepad document called \"CONFIG_server.cfg\" and save it to the root folder of your Arma 3 install on the server `D:\\Games\\Arma3\\A3Master`\n\n1. Start up your shortcut, check the server runs. (You will see a console pop up in your desktop after a few seconds)\n1. Close the console window down, then you will need to edit the following files which will have been automatically created\n   - D:\\Games\\Arma3\\A3Master\\Users\\Adminstrator\\Administrator.Arma3Profile\n   - D:\\Games\\Arma3\\A3Master\\Users\\Administrator\\Arma3.cfg\n1. Restart the server\n1. Start up your client Arma3.exe (Running the same branch as the server, (eg Stable or DEV) and you should then be able to see your server in the server browser (Filters are available to reduce the server list)\n1. Login to your server using the password you defined in CONFIG_server.cfg by pressing <kbd>/</kbd> to open the chat window and then type `#login ADMINPASSWORD` followed by <kbd>Return ↵</kbd>.\n\n   > [!WARNING]\n   > Make sure to never forget the '#' in front of any server command!\n1. Once logged in you will be presented with a mission list, select one of the missions to start the game\n1. Prove the stability of your server by running BI missions initially before you start adding user made content"},{"heading":"Instructions (Linux o/s)","level":4,"markdown":""},{"heading":"Installation","level":5,"markdown":"As a security best practice, create a user to run steam instead of running as root or an administrator.\nThis way, if your Arma 3 server is compromised the attacker will find it more difficult to access the rest of the operating system.\n\n```\nuseradd -m -s /bin/bash steam\n```\n\nSwitch to the newly created steam user.\n\n```\nsudo -i -u steam\n```\n\nCreate a new directory for SteamCMD to avoid cluttering the home directory.\n\n```\nmkdir ~/steamcmd && cd ~/steamcmd\n```\n\nDownload the [SteamCMD for Linux](https://developer.valvesoftware.com/wiki/SteamCMD#Linux) tarball from the link at the Valve Developer Community page.\nUse a command line download tool such as `wget` or `curl`.\n\nExtract the tarball.\n\n```\ntar xf steamcmd_linux.tar.gz\n```\n\nExecute steamcmd.sh. It will install the rest of the Steam client and start the Steam client shell.\nIf this step fails on a 64-bit OS, you likely need to [install 32-bit libraries](https://developer.valvesoftware.com/wiki/SteamCMD#32-bit_libraries_on_64-bit_Linux_systems).\n\n```\n./steamcmd.sh\n```\n\nChange the directory SteamCMD will install the server in.\n\n```\nforce_install_dir ./arma3/\n```\n\nAt the Steam client shell, login with a valid Steam username and password.\nThe Valve Developer Community Wiki [recommends that you create a new Steam account for this](https://developer.valvesoftware.com/wiki/SteamCMD#SteamCMD_Login).\nSteamCMD will cache the login credentials and anyone who gains access to your server will be able to log into the account used here.\nIn addition, you cannot log into a single Steam account from two places at once. You do not need to have Arma 3 purchased on the Steam account used here to download the server.\nTherefore, you should create a new Steam account with no purchases only for use on this server.\n\n```\nlogin myusername\n```\n\nInstall the Arma 3 Linux dedicated server. The validate option will check for corruption.\n\n```\napp_update 233780 validate\n```\n\nExit SteamCMD.\n\n```\nexit\n```\n\nCreate the directories used to store the profile files and Arma3.cfg file.\n\n```\nmkdir -p ~/\".local/share/Arma 3\" && mkdir -p ~/\".local/share/Arma 3 - Other Profiles\"\n```"},{"heading":"Updating","level":5,"markdown":"You will have to update the server whenever a patch is released on Steam.\n\nIf the server is running, stop it by pressing Ctrl+C in the terminal (or screen/tmux instance) that the server is attached to. Otherwise, switch to the steam user.\n\n```\nsudo -u steam -i\n```\n\nLaunch steamcmd.\n\n```\ncd /home/steam/steamcmd\n./steamcmd.sh\n```\n\nSet the Arma 3 installation directory to the same directory used above.\n\n```\nforce_install_dir ./arma3/\n```\n\nLogin to the Steam account used in the installation section above.\n\n```\nlogin myusername\n```\n\nUpdate the Arma 3 Linux dedicated server. The validate option will check for corruption.\n\n```\napp_update 233780 validate\n```\n\nExit SteamCMD.\n\n```\nexit\n```"},{"heading":"Configuration","level":5,"markdown":"You will most likely want to customise your server's name, password, security settings, and so on with a server.cfg file. Change to the arma3 directory and create and edit your server.cfg file.\n\n```\ncd ~/steamcmd/arma3\nvim server.cfg\n```\n\nIf you don't know how to use vim, use nano instead.\n\n```\nnano server.cfg\n```\n\nSee server config for documentation and examples.\n\nThe first time you run the server it will auto-create a profile file at `~/.local/share/Arma 3 - Other Profiles/server/server.Arma3Profile`.\nEdit this file to customise difficulty settings.\n\n> [!IMPORTANT]\n> The `-profiles=` parameter is broken on Linux - you **must** place your profiles in this directory."},{"heading":"Launching","level":5,"markdown":"A Linux executable is provided to launch the server. Make sure that you are running it under the steam user and not root or another administrator!\n\n```\ncd /home/steam/steamcmd/arma3\n./arma3server_x64 -name=server -config=server.cfg\n```\n\nNB: If you are using the `-mod=` parameter, you must specify relative paths *within or below* the Arma 3 directory. Symlinks will work.\n\nThe arma3server_x64 process will attach to the current terminal.\nIf you are connected to the server over SSH, the server will stop when you disconnect.\nYou can keep the server running using a terminal multiplexeer like [GNU Screen](https://www.gnu.org/software/screen/) or [tmux](http://tmux.sourceforge.net/).\nThere are many tutorials online on how to use these programs to detach and reattach processes from and to a terminal.\n\nYou can safely stop the server by pressing Ctrl+C in the terminal (or screen/tmux instance) that the server is attached to.\n\nFor older 32-bit executable use ./arma3server instead of ./arma3server_x64."},{"heading":"Case sensitivity & Mods","level":5,"markdown":"Some mods such as CUP Terrains and @ALiVE will not function if there are capital letters in any of their file names. If you do not update your mods on a regular basis, you can just use the command\n\n```\nfind . -depth -exec rename 's/(.*)\\/([^\\/]*)/$1\\/\\L$2/' {} \\;\n```\n\nin the directory where your mods are located. This will recursively search the directory tree and make all the filenames lowercase.\n\nIf you regularly update your mods using, e.g. Arma3Sync, you will find that this will redownload any files/folders that have changed case every time you run it.\nThe solution to this is to use a package called \"ciopfs\" - Case Insensitive On Purpose Filesystem. You should first run the \"find . -depth...\" command mentioned above on your mod folder.\nThen, make an empty directory outside of the mods directory, e.g. mods_caseinsensitive. You then mount the directory with:\n\n```\nciopfs mods mods_caseinsensitive\n```\n\nand tell Arma3Sync to synchronise in the mods_caseinsensitive directory. Once it has finished, you can unmount the directory with:\n\n```\nfusermount -u mods_caseinsensitive\n```\n\nYou should find that all of the files in the original mods directory are lowercase."},{"heading":"Additional Info","level":3,"markdown":""},{"heading":"Useful Links","level":4,"markdown":""},{"heading":"Further Reading","level":5,"markdown":"- [Steam Cmd Tutorial](https://developer.valvesoftware.com/wiki/SteamCMD)\n- [Dedicated Server Status (Linux info)](https://forums.bohemia.net/forums/topic/139605-dedicated-server-status/)\n- [Kelly's Heroes Dedicated server guide](http://www.kellys-heroes.eu/files/tutorials/dedicated/arma3dedicated.php#one)\n- In Game server commands\n- In Game admin commands\n- Command line params\n- Basic.cfg\n- Steam Difficulty settings\n- Server Configuration\n- [Sim-link GUI](https://code.google.com/p/symlinker/)"},{"heading":"File Locations","level":4,"markdown":"Some files are automatically created when you use certain commandline parameters\nSome files have to be created manually.\nIf you have followed the instructions accurately, you will now have the following files and directories in addition to the clean install\n\n- D:\\Games\\Arma3\\A3Master\\Users\\Administrator\\**Administrator.Arma3Profile** *(Difficulty settings)*\n- D:\\Games\\Arma3\\A3Master\\Users\\Administrator\\**Administrator.vars.Arma3Profile** *(Some binarised content which you cannot edit)*\n- D:\\Games\\Arma3\\A3Master\\Users\\Administrator\\**Arma3.cfg** *(Bandwidth settings)*\n- D:\\Games\\Arma3\\A3Master\\**MPMissions\\** *(This is where custom made mission.pbo's need to be placed)*\n- D:\\Games\\Arma3\\A3Master\\**arma3.rpt** *(Debug Log, automatically created every time the arma3server.exe is started)*\n- D:\\Games\\Arma3\\A3Master\\**CONFIG_server.cfg** *(Manually created)*\n- D:\\Games\\Arma3\\A3Files\\**Arma3server_steamcmd_example.cmd** *(Manually created)*\n- D:\\Apps\\Steam\\"},{"heading":"Port Forwarding","level":4,"markdown":"Arma 3 uses the same default ports as Arma 2 with the addition of several ports. So if you intend running Arma 2 and Arma 3 servers on the same machine, you need to edit the ports used.\n**Default ports are all UDP** and as follows:\n\n**Incoming**\n\n- 2302 (default Arma 3 Game port) + (VON is now part of main gameport due to NAT issues)\n- 2303 (STEAM query, +1)\n- 2304 (Steam port, +2)\n- 2305 (VON port, +3 - not used atm. but allocated)\n- 2306 (BattlEye traffic, +4)\n\n**Outgoing**\n\n| DST Port | Protocol | Destination | Comment |\n|---|---|---|---|\n| 2344 | TCP + UDP | 81.0.236.111 | BattlEye - arma31.battleye.com |\n| 2345 | TCP | 81.0.236.111 | BattlEye - arma31.battleye.com |\n| 2302-2306 | UDP | any | Arma Server to Client Traffic |\n| 2303 | UDP | any | Arma Server STEAM query port |\n| 2304 | UDP | any | Arma Server to STEAM master traffic |\n\nTo define the Arma 3 Game port used,\nstate -port= **** in your command line arguments (Where **** is the new initial Arma 3 Game, e.g 2302)\n\nand to define your Steam ports\nadd the following lines to your CONFIG_server.cfg (editing the actual port numbers as required)\n\n> [!NOTE]\n> Steam ports are now linked to game-port as +1 for query and +2 to-master.\n\nIf you are running multiple servers, i would suggest the following format\n\n**SERVER 1**\n\n2302 UDP (gameport + VON)\n\n2303 UDP (STEAM query port)\n\n2304 UDP (STEAM master port)\n\n2305 UDP (VON reserved port but not used atm.)\n\n2306 UDP (BattlEye traffic port)\n\nso open ports 2302-2306\n\n... and leave at least **100** ports between the next 2nd server set\n\n**SERVER 2**\n\n2402 UDP (gameport + VON)\n\n2403 UDP (STEAM query port)\n\n2404 UDP (STEAM master port)\n\n2405 UDP (VON reserved port but not used atm.)\n\n2406 UDP (BattlEye traffic port)\n\nso open ports 2402-2406\n\nand leave at least **100** ports between the next 3rd server set, etc."},{"heading":"NAT traversal","level":5,"markdown":"UPnP allows you to automatically create port forwarding on your router to bypass NAT (UPnP enabled routers are required).\nThe functionality can be easily enabled in server config as described in the server.cfg page."},{"heading":"Configuring for stable or Dev branch","level":4,"markdown":"Edit the `Arma3server_steamcmd_example.cmd` as defined below then run it\n\n- To select Development version\n\n```\nSET A3BRANCH=107410 -beta development\n```\n\n- To select stable build (Dedicated server package)\n\n```\nSET A3BRANCH=233780 -beta\n```\n\n- To select stable build (Full client\\server package)\n\n```\nSET A3BRANCH=107410\n```\n\n**Important Feature**\n\nSince **12th March 2013** the development branch and the stable branch versions are no longer compatible. This means:\n\n- Only DEV clients can connect to a DEV server\n- Only Stable clients can connect to stable servers"},{"heading":"Advanced Configuration","level":4,"markdown":""},{"heading":"Bandwidth Optimisation","level":4,"markdown":""},{"heading":"Multiple Server configuration","level":4,"markdown":"There are various methods available to run multiple Dedicated Arma 3 servers on the same box.\nEach server instance requires:\n\n- Its own unique set of ports\n- Its own profile\n- Its own config\n\n[This post](https://forums.bohemia.net/forums/topic/139003-tutorial-installation-configuration-of-arma3-dedicated-server/?page=10&tab=comments#comment-2344472) explains it more in depth.\n\nEach method has some pro's and cons\nTo select the preferred methodology that suits your requirements you need to have considered the following\n\n- The useage of the \"Keys\" folder\n- The useage of the \"MpMissions\" folder\n- Available Hard drive space\n- Update management"},{"heading":"Method 1","level":5,"markdown":"see [THIS POST](https://forums.bohemia.net/forums/topic/139003-tutorial-installation-configuration-of-arma3-dedicated-server/?page=9&tab=comments#comment-2343865) for more detailed information\nThis is copy of the master install into a different directory\nAs may times as you have space for\n\n**Pros**\n\n- Most robust\n- Unique MpMissions folder\n- Unique \"keys\" folder\n- Allows ability to run separate instances of different branches of the game, (E.g Dev or Stable)\n\n**Cons**\n\n- Uses more drive space\n- Requires more effort to create and automate the updating process"},{"heading":"Method 2","level":5,"markdown":"This uses 1 master install folder and has renamed arma3server.exe's in sub folders of the master\nsee THIS POST for more detailed information\n\n**Pros** (Compared to Method 1)\n\n- Uses less space than Method 1\n- Updating will be easier\n\n**Cons** (Compared to Method 1)\n\n- Not very robust\n- Shares MPMissions folders with all the other exe's (Will create a very cluttered MpMissions folder and allows admins to select addon required missions for a mod this server instance isn't running\n- Shares \"keys\" folder with all other exe's (This can cause an issue when running various differing -mod servers)\n- Will not allow you to run separate instances of different branches of the game"},{"heading":"Method 3","level":5,"markdown":"This is a hybrid of method 1, in that it is essentially a \"Virtual\" copy of the master install in a different directory\nthe difference being that many folders are [symlinked](https://en.wikipedia.org/wiki/Symbolic_link) to the initial Master directory\nsymlink GUI:\n\n**Pros** (Compared to Method 1)\n\n- Uses less drive space (As you wont have multiple copies of the addons folder)\n- Allows for unique MpMissions folder if desired\n- Allows for unique \"keys\" folder if desired\n- Updating will be easier\n\n**Cons** (Compared to Method 1)\n\n- Requires more effort to initially create the symlinks and directories\n- Will not allow you to run separate instances of different branches of the game at the same time, (E.g Dev or Stable)\n\nFor example, on Linux, if you initially have the following folder layout:\n\n```batch\n ~/game_servers/\n    arma3server/\n    ...\n    mods # folder where you keep your mods\n    arma3server\n    ...\n```\n\nInstead of copying the folders as directed in (Compared to Method 1), run the following commands:\n\n```batch\ncd ~/game_servers/\nmkdir arma3server_2/\nln -sr arma3server/* arma3server_2\ncd arma3server_2\nrm keys mpmissions mods\nmkdir keys\nmkdir mpmissions\nmkdir mods\n```\n\nThen proceed with the rest of the instructions in METHOD 1."},{"heading":"Method 4","level":5,"markdown":"You can of course mix and match all 3 previous methods to suit your specific requirements."},{"heading":"Method 5 (Arma 3 v2.22)","level":5,"markdown":"You can combine the -port, -profiles, -mpmissions and -keysFolder startup parameters to run multiple servers from the same Arma 3 installation directory while using different ports and separate directories for profiles, missions, and keys.\n\nThis approach allows you to host multiple servers without using symbolic links or duplicating the entire server installation.\n\nExample batch script for running multiple servers:\n\n```batch\n@echo off\n\nrem Starting TvT server\nstart arma3server_x64.exe -port=2302^\n -name=TvT^\n -profiles=Profiles\\TvT^\n -mpmissions=Profiles\\TvT\\MPMissions^\n -keysFolder=Profiles\\TvT\\Keys^\n -cfg=Profiles\\TvT\\Configs\\Basic.cfg^\n -config=Profiles\\TvT\\Configs\\Server.cfg^\n -mod=\"@CBA_A3;@ace\"\n\nrem Starting PvE server\nstart arma3server_x64.exe -port=2402^\n -name=PvE^\n -profiles=Profiles\\PvE^\n -mpmissions=Profiles\\PvE\\MPMissions^\n -config=Profiles\\PvE\\Configs\\Server.cfg\n```\n\nBefore running the script, create the following directory structure:\n\n```\nArma 3 installation/\n├── Profiles/\n│   ├── TvT/\n│   │   ├── MPMissions/\n│   │   ├── Keys/\n│   │   └── Configs/\n│   │       ├── Basic.cfg\n│   │       └── Server.cfg\n│   │\n│   └── PvE/\n│       ├── MPMissions/\n│       ├── Keys/\n│       └── Configs/\n│           └── Server.cfg\n│\n└── arma3server_x64.exe\n```"},{"heading":"Dedicated Server & Client configuration","level":4,"markdown":"> [!NOTE]\n> In order for the Arma 3 server to be able to connect to the Steam servers, the Arma 3 server has to be ping-able (ICMP 8 - Echo Reply) as well as opened TCP/UDP ports.\n\nThe only known issue, is to make sure you start the server up before you start the steam client\nFailing to do this causes steam port issues and your client will not be able to connect to the server"},{"heading":"Headless Client","level":4,"markdown":"> [!NOTE]\n> See Arma 3: Headless Client for changes in headless clients.\n\nA Headless Client can be used by missions to offload AI processing to a dedicated client, freeing up the dedicated server process from most AI processing.\nThus more AI units can be spawned and the server process will be able to dedicate most of it is processing towards communication with the clients.\nFor a Headless Client/Dedicated Server to function together efficiently, they both need to be connected to each other via extremely low latency and high bandwidth.\nEffectively, they need to be on the same LAN at least, but preferably running on the same computer."},{"heading":"Setup and Execution","level":5,"markdown":"- Headless Client for Arma 3 requires a **valid active Steam account logged in** to function (see [Dwarden's post](https://forums.bohemia.net/forums/topic/140621-arma-3-headless-client/?page=5&tab=comments#comment-2481581))\n- A Headless Client is simply Arma3.exe run from the command line with parameters, for example:\n\n```cpp\narma3.exe -connect=localhost -port=2444 -client -nosound -password=some_server_password -name=HC -profile=HC -mod=@CBA_A3;@blah;@blah;@blah\n```\n\nIn the example above, the headless client is running on the same host as the dedicated server.\nIt uses a profile called **HC** and connects to the server with a password as required by the server (the password is for password protected servers, optional).\nThe server in this example is running on port 2444, alter this to the port of your server.\n\n- The Headless Client profile needs to be created like any other profile in Arma 3 (Note: It is best if you name this profile **HC**)\n\nNo configuration of the profile is necessary, but after creation, edit **HC.Arma3Profile** located in **C:\\Users\\yourusername\\Documents\\Arma 3 - Other Profiles\\HC** and add this line:\n\n```cpp\nbattleyeLicense=1;\n```\n\nAlternatively, you can use the full Arma 3 client to connect to any multiplayer server with BattlEye enabled and accept the BattlEye License Agreement,\nwhich will do the same thing as manually editing **HC.Arma3Profile**.\n\nOnce the profile is ready, copy the profile directory to **C:\\Users\\yourusername\\Documents\\Arma 3 - Other Profiles** on the server (if the profile was not created on the server).\nIf the profile was created on the server or is not going to run on the server and is already on the computer it is going to run on, then it is ready to go.\n\n- If the Headless Client is on the server, the server's cfg must have the local loopback address as seen below (e.g. A3Server.cfg):\n\n```cpp\nlocalClient[]={ \"127.0.0.1\" };\nheadlessClients[]={ \"127.0.0.1\" };\nbattleyeLicense=1;\n```\n\nDwarden suggests that **battleyeLicense=1;** be in the server's config, but it is unclear whether this is actually necessary.\n([Dwarden's post](https://forums.bohemia.net/forums/topic/150815-headless-client-battleye/?tab=comments#comment-2413319)).\n\n- If the Headless Client is running in the same network or the same computer, the server's config has to have the address in **localClient[]=x.x.x.x**.\n\nThis will allow the server to communicate with the Headless Client using unrestricted bandwidth. It is also required to add the adress to **headlessClients[]={ \"x.x.x.x\" };**.\nMultiple headless clients at different addresses can be added:\n\n```cpp\nlocalClient[]={ \"127.0.0.1\", \"192.168.1.10\", \"192.168.1.210\" };\nheadlessClients[]={ \"127.0.0.1\", \"192.168.1.10\", \"192.168.1.210\" };\nbattleyeLicense=1;\n```"},{"heading":"Headless Client on a Dedicated Server Notes","level":5,"markdown":"If the Arma 3: Headless Client and a Dedicated Server are running on the same Windows computer (VM or physical),\nit *may* be beneficial to set processor affinity to prevent execution intensive threads from being scheduled across the same (v)CPUs.\n\n> [!WARNING]\n> Do **not** use this if you do not know what you are doing, as performance may be strongly impacted.\n\nThe operating system will generally schedule threads efficiently, but manual CPU allocation is possible.\nThis can be achieved by right-clicking on the process (e.g. Arma3Server.exe(*32)) in the **processes tab** of the Windows Task Manager and selecting **Set Affinity...**.\nBe aware that on a physical intel CPU, the odd numbered CPUs are Hyper-thread cores.\n\n> [!NOTE]\n> You can use automated solution for affinity assign via batch file with commandline `CMD /AFFINITY HEXvalue` e.g. `CMD /C START /AFFINITY 0xF3 arma3server.exe`.\n\nIt has been observed that although the Arma server and client processes will kick off multiple threads, the bulk of processing is used up by only one or two threads.\nFor example, spawning 50 AI units does not generate 50 threads.\nThere is one thread in the process that handles all of the AI units, irrespective of how many have been spawned.\nIn this way, the ARMA server and client processes do not make maximal use of the processing capability found in modern processors and so AI counts do not scale easily.\nAs such, faster CPU core speed is king and offloading the AI to multiple headless clients on the same computer will probably produce the best possible results for complex missions involving many AI units (albeit an expensive way to get the results).\n\n> [!NOTE]\n> Read the complete and detailed HOW-TO guide on Headless Client: Arma 3: Headless Client.\n\n-"},{"heading":"Example Files","level":4,"markdown":""},{"heading":"Arma3server_steamcmd_example.cmd","level":5,"markdown":"- Standalone Server Package (no need for game ownership on STEAM account)\n- Note: you might be asked to authorise your STEAM account due to STEAMguard (check email)\n- Note: it needs to be ran two or three times (1st authorise, 2nd STEAMcmd update itself, (when done, quit), 3rd update the Arma 3 Server data package)\n- Note: STEAMcmd needs to be in separate folder from STEAMclient (so always use unique folder like \"STEAMcmd\") to avoid file conflicts\n- Note: Arma 3 server data package needs to be in separate folder from Arma 3 client (so always use unique folder like \"A3server\" or \"Arma3server\") to avoid file conflicts\n- Code:\n\n  ```batch\n  @echo off\n  rem http://media.steampowered.com/installer/steamcmd.zip\n  SETLOCAL ENABLEDELAYEDEXPANSION\n\n      :: DEFINE the following variables where applicable to your install\n\n      SET STEAMLOGIN=mylogin mypassword\n      SET A3serverBRANCH=233780 -beta public\n          :: For stable use 233780 -beta public\n          :: For Dev use 233780 -beta development\n                  :: Note: quotation marks need to be wrapped around the entire \"+app_data......\"\n                  :: There is no DEV branch data yet for Arma 3 Dedicated Server package!\n\n      SET A3serverPath=D:\\Games\\Arma3\\A3Master\n          SET STEAMPATH=D:\\Apps\\Steam\n\n  ::\n\n  echo.\n  echo You are about to update Arma 3 server\n  echo     Dir: %A3serverPath%\n  echo     Branch: %A3serverBRANCH%\n  echo.\n  echo Key \"ENTER\" to proceed\n  pause\n  %STEAMPATH%\\steamcmd.exe +force_install_dir %A3serverPath% +login %STEAMLOGIN% +\"app_update %A3serverBRANCH%\" validate +quit\n  echo.\n  echo Your Arma 3 server is now up to date\n  echo Press \"ENTER\" to exit\n  pause\n  ```"},{"heading":"CONFIG_server.cfg","level":5,"markdown":"```cpp\n//\n// server.cfg\n//\n\n// NOTE: More parameters and details are available at http://community.bistudio.com/wiki/server.cfg\n\n// STEAM PORTS (not needed anymore, it is +1 +2 to gameport)\n// steamPort        = 8766;        // default 8766, needs to be unique if multiple servers are on the same box\n// steamQueryPort    = 27016;    // default 27016, needs to be unique if multiple servers are on the same box\n\n// GENERAL SETTINGS\nhostname        = \"My Arma 3 Server\";    // Name of the server displayed in the public server list\n//password        = \"ServerPassword\";        // Password required to join the server (remove // at start of line to enable)\npasswordAdmin    = \"AdminPassword\";        // Password to login as admin. Open the chat and type: #login password\nmaxPlayers        = 40;    // Maximum amount of players, including headless clients. Anybody who joins the server is considered a player, regardless of their role or team.\npersistent        = 1;    // If set to 1, missions will continue to run after all players have disconnected; required if you want to use the -autoInit startup parameter\n\n// VOICE CHAT\ndisableVoN        = 0;    // If set to 1, voice chat will be disabled\nvonCodecQuality    = 10;    // Supports range 1-30, the higher the better sound quality, the more bandwidth consumption:\n                        // 1-10 is 8kHz (narrowband)\n                        // 11-20 is 16kHz (wideband)\n                        // 21-30 is 32kHz (ultrawideband)\n\n// VOTING\nvoteMissionPlayers    = 1;        // Minimum number of players required before displaying the mission selection screen, if you have not already selected a mission in this config\nvoteThreshold        = 0.33;        // Percentage (0.00 to 1.00) of players needed to vote something into effect, for example an admin or a new mission. Set to 9999 to disable voting.\nallowedVoteCmds[] =                // Voting commands allowed to players\n{\n    // { command, preinit, postinit, threshold } - specifying a threshold value will override \"voteThreshold\" for that command\n    { \"admin\", false, false},        // vote admin\n    { \"kick\", false, true, 0.51},    // vote kick\n    { \"missions\", false, false},        // mission change\n    { \"mission\", false, false},        // mission selection\n    { \"restart\", false, false},        // mission restart\n    { \"reassign\", false, false}        // mission restart with roles unassigned\n};\n\n// WELCOME MESSAGE (\"message of the day\")\n// It can be several lines, separated by comma\n// Empty messages \"\" will not be displayed, but can be used to increase the delay before other messages\nmotd[] =\n{\n    \"Welcome to My Arma 3 Server\",\n    \"Discord: discord.somewhere.com\",\n    \"TeamSpeak: ts.somewhere.com\",\n    \"Website: www.example.com\"\n};\nmotdInterval = 5;    // Number of seconds between each message\n\n// MISSIONS CYCLE\nclass Missions\n{\n    class Mission1\n    {\n        template    = \"MyMission.Altis\";    // Filename of pbo in MPMissions folder\n        difficulty    = \"Regular\";            // \"Recruit\", \"Regular\", \"Veteran\", \"Custom\"\n    };\n};\n\n// LOGGING\ntimeStampFormat    = \"short\";                // Timestamp format used in the server RPT logs. Possible values are \"none\" (default), \"short\", \"full\"\nlogFile            = \"server_console.log\";    // Server console output filename\n\n// SECURITY\nBattlEye                = 1;    // If set to 1, BattlEye Anti-Cheat will be enabled on the server (default: 1, recommended: 1)\nverifySignatures        = 2;    // If set to 2, players with unknown or unsigned mods won't be allowed join (default: 0, recommended: 2)\nkickDuplicate            = 1;    // If set to 1, players with an ID that is identical to another player will be kicked (recommended: 1)\nallowedFilePatching        = 1;    // Prevents clients with filePatching enabled from joining the server\n                                // (0 = block filePatching, 1 = allow headless clients, 2 = allow all) (default: 0, recommended: 1)\n\n// FILE EXTENSIONS\n\n// only allow files with those extensions to be loaded via loadFile command (since Arma 3 v1.20)\nallowedLoadFileExtensions[] =        { \"hpp\", \"sqs\", \"sqf\", \"fsm\", \"cpp\", \"paa\", \"txt\", \"xml\", \"inc\", \"ext\", \"sqm\", \"ods\", \"fxy\", \"lip\", \"csv\", \"kb\", \"bik\", \"bikb\", \"html\", \"htm\", \"biedi\" };\n\n// only allow files with those extensions to be loaded via preprocessFile / preprocessFileLineNumbers commands (since Arma 3 v1.20)\nallowedPreprocessFileExtensions[] =    { \"hpp\", \"sqs\", \"sqf\", \"fsm\", \"cpp\", \"paa\", \"txt\", \"xml\", \"inc\", \"ext\", \"sqm\", \"ods\", \"fxy\", \"lip\", \"csv\", \"kb\", \"bik\", \"bikb\", \"html\", \"htm\", \"biedi\" };\n\n// only allow files and URLs with those extensions to be loaded via htmlLoad command (since Arma 3 v1.28)\nallowedHTMLLoadExtensions[] =        { \"htm\", \"html\", \"php\", \"xml\", \"txt\" };\n\n// EVENT SCRIPTS - see http://community.bistudio.com/wiki/Arma_3:_Server_Side_Scripting\nonUserConnected        = \"\";    // command to run when a player connects\nonUserDisconnected    = \"\";    // command to run when a player disconnects\ndoubleIdDetected    = \"\";    // command to run if a player has the same ID as another player in the server\nonUnsignedData        = \"kick (_this select 0)\";    // command to run if a player has unsigned files\nonHackedData        = \"kick (_this select 0)\";    // command to run if a player has tampered files\n\n// HEADLESS CLIENT\nheadlessClients[]    = { \"127.0.0.1\" };    // list of IP addresses allowed to connect using headless clients; example: { \"127.0.0.1\", \"192.168.1.100\" };\nlocalClient[]        = { \"127.0.0.1\" };    // list of IP addresses to which are granted unlimited bandwidth; example: { \"127.0.0.1\", \"192.168.1.100\" };\n```"},{"heading":"server.Arma3Profile","level":5,"markdown":"See server.armaprofile."},{"heading":"Arma3.cfg","level":5,"markdown":"> [!NOTE]\n> See basic.cfg for more information.\n\n```cpp\nlanguage=\"English\";\nadapter=-1;\nMinBandwidth=800000;\nMaxBandwidth=25000000;\nMaxMsgSend=384;\nMaxSizeGuaranteed=512;\nMaxSizeNonguaranteed=256;\nMinErrorToSend=0.003;\nMaxCustomFileSize=100000;\nWindowed=0;\nserverLongitude=0;\nserverLatitude=52;\nserverLongitudeAuto=0;\nserverLatitudeAuto=52;\n```"},{"heading":"Support & Troubleshooting","level":3,"markdown":""},{"heading":"Known Issues","level":4,"markdown":"1. My server has 2500ms ping in server browser (This is caused by running the steam client as Non Administrator) see http://feedback.arma3.com/view.php?id=9374\n1. MaxMsgSend default is 128, higher values can create Desync problems if the server's available processing and/or bandwidth can not support the higher value\n1. if you run Arma 3 Dedicated server data package on system where is also installed client there is possibility the server will load the full client data instead server data package, this is caused by precedence check in registry.\n   The solution/workaround to this issue is to use arma3server.exe `-mod=` (where empty modline ensure it loads data from where server is placed)\n1. upnp=1; // in server.cfg may result into server not starting for 600 seconds on server with active firewalls / anti-ddos measures ,\n   it's not recommended setting for dedicated-servers where server process related ports are open/forwarded by default\n1. using multiple server instances with too narrow ranges in between each (e.g. first 2302, second 2314) may cause problems with query where second server reports at first range, use of minimum +100 ports for next instance next to 2302 thus 2402 then 2502 etc. for utmost safety use +200 or +1000\n1. engine has legacy automated port increment system for occupied sockets (used for client-listen servers, upnp) where first is tried 2302, then +12 up to 15 times (so 2314, 2326 ... 2482)"},{"heading":"Live Help","level":4,"markdown":"For live assistance, join the official **[Arma Discord server](https://discord.gg/arma)!**\nEspecially these channels:\n\n- `#server_admins`\n- `#server_linux`\n- `#server_windows`\n- `#server_tools`"},{"heading":"F.A.Q","level":4,"markdown":""},{"heading":"See Also","level":3,"markdown":"- Server Options\n- Battleye's RCON\n- Arma 3: Headless Client\n- Multiplayer Server Commands\n- Armed Assault Server Configuration"}],"categories":["Arma 3: Multiplayer","Arma 3: Tutorials","Stubs"],"groups":["Multiplayer and Server"]}