Arma 3 dedicated server windows

ⓘ

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.
Arma 3 Dedicated server package is available for free (does not require regular Arma 3 to be purchased).

⚠

The -profiles= parameter is broken on Linux — you must place your profiles in this directory.

ⓘ

STEAM ports are now linked to game-port as +1 for query and +2 to-master.

cd ~/game_servers/
mkdir arma3server_2/
ln -sr arma3server/* arma3server_2
cd arma3server_2
rm keys mpmissions mods
mkdir keys
mkdir mpmissions
mkdir mods

ⓘ

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.

arma3.exe -connect=localhost -port=2444 -client -nosound -password=some_server_password -name=HC -profile=HC -mod=@CBA_A3;@blah;@blah;@blah

localClient[]={"127.0.0.1"};
headlessClients[]={"127.0.0.1"};
battleyeLicense=1;

localClient[]={"127.0.0.1", "192.168.1.10", "192.168.1.210"};
headlessClients[]={"127.0.0.1","192.168.1.10","192.168.1.210"};
battleyeLicense=1;

@echo off
@rem http://media.steampowered.com/installer/steamcmd.zip
SETLOCAL ENABLEDELAYEDEXPANSION

	:: DEFINE the following variables where applicable to your install

	SET STEAMLOGIN=mylogin mypassword
	SET A3serverBRANCH=233780 -beta
		:: For stable use 233780 -beta
		:: For Dev use 233780 -beta development
				:: Note, the missing qoutation marks, these need to be wrapped around the entire "+app_data......"
				:: There is no DEV branch data yet for Arma 3 Dedicated Server package !!!

	SET A3serverPath=D:\Games\ArmA3\A3Master
		SET STEAMPATH=D:\Apps\Steam

:: 

echo.
echo You are about to update Arma 3 server
echo 	Dir: %A3serverPath%
echo 	Branch: %A3serverBRANCH%
echo.
echo Key "ENTER" to proceed
pause
%STEAMPATH%\steamcmd.exe +force_install_dir %A3serverPath% +login %STEAMLOGIN% +"app_update %A3serverBRANCH%" validate +quit
echo.
echo Your Arma 3 server is now up to date
echo Press "ENTER" to exit
pause

//
// server.cfg
//
// comments are written with "//" in front of them.

// NOTE: More parameters and details are available at http://community.bistudio.com/wiki/server.cfg

// STEAM PORTS (not needed anymore, it is +1 +2 to gameport)
// steamPort		= 8766;		// default 8766, needs to be unique if multiple servers are on the same box
// steamQueryPort	= 27016;	// default 27016, needs to be unique if multiple servers are on the same box

// GENERAL SETTINGS
hostname		= "My Arma 3 Server";	// Name of the server displayed in the public server list
//password		= "ServerPassword";		// Password required to join the server (remove // at start of line to enable)
passwordAdmin	= "AdminPassword";		// Password to login as admin. Open the chat and type: #login password
maxPlayers		= 40;	// Maximum amount of players, including headless clients. Anybody who joins the server is considered a player, regardless of their role or team.
persistent		= 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

// VOICE CHAT
disableVoN		= 0;	// If set to 1, voice chat will be disabled
vonCodecQuality	= 10;	// Supports range 1-30, the higher the better sound quality, the more bandwidth consumption:
						// 1-10 is 8kHz (narrowband)
						// 11-20 is 16kHz (wideband)
						// 21-30 is 32kHz (ultrawideband)

// VOTING
voteMissionPlayers	= 1;		// Minimum number of players required before displaying the mission selection screen, if you have not already selected a mission in this config
voteThreshold		= 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.
allowedVoteCmds[] =				// Voting commands allowed to players
{
	// {command, preinit, postinit, threshold} - specifying a threshold value will override "voteThreshold" for that command
	{"admin", false, false},		// vote admin
	{"kick", false, true, 0.51},	// vote kick
	{"missions", false, false},		// mission change
	{"mission", false, false},		// mission selection
	{"restart", false, false},		// mission restart
	{"reassign", false, false}		// mission restart with roles unassigned
};

// WELCOME MESSAGE ("message of the day")
// It can be several lines, separated by comma
// Empty messages "" will not be displayed, but can be used to increase the delay before other messages
motd[] =
{
	"Welcome to My Arma 3 Server",
	"Discord: discord.somewhere.com",
	"TeamSpeak: ts.somewhere.com",
	"Website: www.example.com"
};
motdInterval = 5;	// Number of seconds between each message

// MISSIONS CYCLE
class Missions
{
	class Mission1
	{
		template	= "MyMission.Altis";	// Filename of pbo in MPMissions folder
		difficulty	= "Regular";			// "Recruit", "Regular", "Veteran", "Custom"
	};
};

// LOGGING
timeStampFormat	= "short";				// Timestamp format used in the server RPT logs. Possible values are "none" (default), "short", "full"
logFile			= "server_console.log";	// Server console output filename

// SECURITY
BattlEye				= 1;	// If set to 1, BattlEye Anti-Cheat will be enabled on the server (default: 1, recommended: 1)
verifySignatures		= 2;	// If set to 2, players with unknown or unsigned mods won't be allowed join (default: 0, recommended: 2)
kickDuplicate			= 1;	// If set to 1, players with an ID that is identical to another player will be kicked (recommended: 1)
allowedFilePatching		= 1;	// Prevents clients with filePatching enabled from joining the server
								// (0 = block filePatching, 1 = allow headless clients, 2 = allow all) (default: 0, recommended: 1)

// FILE EXTENSIONS

// only allow files with those extensions to be loaded via loadFile command (since Arma 3 v1.20)
allowedLoadFileExtensions[] =		{"hpp","sqs","sqf","fsm","cpp","paa","txt","xml","inc","ext","sqm","ods","fxy","lip","csv","kb","bik","bikb","html","htm","biedi"};

// only allow files with those extensions to be loaded via preprocessFile / preprocessFileLineNumbers commands (since Arma 3 v1.20)
allowedPreprocessFileExtensions[] =	{"hpp","sqs","sqf","fsm","cpp","paa","txt","xml","inc","ext","sqm","ods","fxy","lip","csv","kb","bik","bikb","html","htm","biedi"};

// only allow files and URLs with those extensions to be loaded via htmlLoad command (since Arma 3 v1.28)
allowedHTMLLoadExtensions[] =		{"htm","html","php","xml","txt"};

// EVENT SCRIPTS - see http://community.bistudio.com/wiki/ArmA:_Server_Side_Scripting
onUserConnected		= "";	// command to run when a player connects
onUserDisconnected	= "";	// command to run when a player disconnects
doubleIdDetected	= "";	// command to run if a player has the same ID as another player in the server
onUnsignedData		= "kick (_this select 0)";	// command to run if a player has unsigned files
onHackedData		= "kick (_this select 0)";	// command to run if a player has tampered files

// HEADLESS CLIENT
headlessClients[]	= {"127.0.0.1"};	// list of IP addresses allowed to connect using headless clients; example: {"127.0.0.1", "192.168.1.100"};
localClient[]		= {"127.0.0.1"};	// list of IP addresses to which are granted unlimited bandwidth; example: {"127.0.0.1", "192.168.1.100"};

language="English";
adapter=-1;
MinBandwidth=800000;
MaxBandwidth=25000000;
MaxMsgSend=384;
MaxSizeGuaranteed=512;
MaxSizeNonguaranteed=256;
MinErrorToSend=0.003;
MaxCustomFileSize=100000;
Windowed=0;
serverLongitude=0;
serverLatitude=52;
serverLongitudeAuto=0;
serverLatitudeAuto=52;

1) Update your firewall rules to include the 64 bit binary

2) BattleEye changes

• 64 bit binary runs the beserver_x64.dll
• It also needs a BEServer_x64.cfg (Which is simply a renamed copy of your BEServer.cfg

If you run an addon server and are having issues, then try running the 32 bit arma3server.exe until the addon makers have fixed their content

This is how you do it.

Take note.
There are additions within these instructions that you may not need, if you only intend running 1 instance of an Arma3 server on your machine
However, adding these superfluous commands and content will not be detrimental to single instance servers
Directory paths are all customisable but for the sake of this tutorial, all file examples and command lines used will be consistent with the tutorial instructions

INFORMATION

SteamCmd Tutorial
Dedicated Server status & Changelog
kellys-heroes Dedicated Server Guide
In Game Server commands
In Game Admin commands
ArmA2 Dedicated server
Commandline Parameters
Basic.cfg
Difficulty settings
Server Configuration
simlink GUI:
Firedaemon Tutorial for ArmA3

DeathTec’s Video Tutorial

TOOLS
 

Arma-Server-Monitor
Firedeamon
Arma 3 Restarter.exe server monitor
***

A U-tube video tutorial by Kirkwood364 which uses Tophe’s Arma 2 Dedicated Server Tool to administer and run an A3 server
(Links for all the files required are available in the 1st comment of his Utube video)

USEFUL ADDONS

• Your teamspeak details
• Your web address
• Server rules

Edit the ArmA3_Steam_Updater.cmd and run it

To select Development version

• SET A3BRANCH=107410 -beta development

To roll back to stable build

• SET A3BRANCH=107410

To use the Dedicated server package (Stable branch only)
This has a smaller diskspace footprint than the full client installs

• SET A3BRANCH=233780 -beta
  In your root install, make sure your steamappid.txt file entry is 107410 (Do not use 233780)

Important Feature
since 12th March 2013
the development branch and the stable branch versions are no longer compatible. this means:

• Only DEV clients can connect to a DEV server
• Only Stable clients can connect to stable servers

Important Feature
since ? 2014
A dedicated server package is now available which has a smaller disk space footprint than the full client install
Most if not all client only required files have been removed. Graphics, sounds etc
This package is only available on the stable branch.
Use SET A3BRANCH=233780 -beta
Leave the steamappid.txt file entry as 107410

ArmA3 uses the same default ports as ArmA2 with the addition of 2 steam ports. So if you intend running A2 and A3 servers on the same machine, you need to edit the ports used
Default ports are all UDP and as follows

• 2302 (Arma3 Game port & VON)
• 2303 (Steam query port)
• 2305 (Steam Port)
• 2306 (BattleEye RCON port)
• 8766 (Steam port) obsolete since 1.22 hotfix patch. This is now hardcoded to use Gameport + 3 (eg 2305)
• 27016 (Steam query port) obsolete since 1.22 hotfix patch. This is now hardcoded to use Gameport + 1 (eg 2303)

• 2302 UDP (used for game & VON)
• 2303 UDP (Steam query port)
• 2304 UDP (? no information available for this port useage)
• 2305 UDP (used for Steam Port)
• 2306 UDP (BattleEye RCON port)

• 2322 UDP (used for game & VON)
• 2323 UDP (Steam query port)
• 2324 UDP (? no information available for this port useage)
• 2325 UDP (used for Steam Port)
• 2326 UDP (BattleEye RCON port)

so open ports 2322-2326
leave at least 10 ports then repeat the process for No3 server etc

Update for the armaserver_x64.exe

I also found I needed to add a firewall rule for the 64 bit server executable for it to be broadcast on the WAN (Still don’t know why it wouldn’t work without doing that as all the ports were opened)

(End of 64 bit binary only)

Battleye is the ArmA engine’s anti cheat application. It is automatically installed and updated.

It can be disabled in your CONFIG_Vanilla.cfg by defining  Battleye=0;

If you have followed these instruction to the letter, you will see a Battleye folder in your d:\Games\Arma3\A3Master»

You will need to manually create a file in this folder named BEServer.cfg using a text editor such as Notepad

with the following content (Edit as you see fit)

RConPassword ABC123XYZ
RConPort 2306
MaxPing 250

There is an additional command you can define which is RConIP. However this can cause issues and if you have used the instructions in this tutorial, you will not need to

Update for the armaserver_x64.exe

1) BattleEye changes

• 64 bit binary runs the beserver_x64.dll
• It also needs a BEServer_x64.cfg (Which is simply a renamed copy of your BEServer.cfg

logFile = «A3Master.log»;

reference: In Game Admin commands

(Known to work, (highlighted in Green))
Not working: (Highlighted in red)
Untested (Highlighted in black)

SERVER MANAGEMENT

• #login < password > : Admin login
  #logout : Admin logout
  #lock : Lock server (Auto unlocks at end of mission)
  #unlock : Unlocks server
  #missions : Stops mission, reloads mission list
  #reassign : Moves all players from their unit selection slots back into the lobby
  #restart : returns the mission to the unit selection screen, with all players in their slots and restarts the mission
  #shutdown: shuts the server down
  #Init : Reloads file defined by -config command line parameter

PLAYER MANAGEMENT

• #userlist : Displays the list of users on the server (use pgup to scroll up)
  #kick < Server Player ID > (First entry for a player using #userlist)
  #kick < nickName > (Second entry for a player using #userlist
  #kick < Player UID > (Third entry for a player using #userlist)

  #exec kick < Server Player ID > (First entry for a player using #userlist)
  #exec kick < nickName > (Second entry for a player using #userlist
  #exec kick < Player UID > (Third entry for a player using #userlist)

  #exec ban < Server Player ID > (First entry for a player using #userlist)
  #exec ban < nickName > (Second entry for a player using #userlist
  #exec ban < Player UID > (Third entry for a player using #userlist)

DEBUGGING

• #monitor 10 : Activates the server monitor which reports Bandwidth and memory useage Every * seconds via chat window)
  #monitor 0 : Deactivates the server monitor
  #debug off : Deactivates debugging
  #debug 30 : Debug reporting interval (Default is 10 seconds
  #debug von
  #debug console
  #debug checkFile expansion\Dta\ui.pbo
  #debug userSent <username>
  #debug userInfo <username>
  #debug userQueue <username>
  #debug JIPQueue <username>
  #debug totalSent 10

RUNNING DEDICATED SERVER & CLIENT ON SAME MACHINE
If you have followed these instructions, the only known issue, is to make sure you start the server up before you start the steam client
Failing to do this causes steam port issues and your client wont be able to connect to the server

RUNNING MULTIPLE SERVERS ON SAME MACHINE

This is possible and there are a few methods to accomplish this.
Each server instance requires

• Its own unique set of ports
• Its own profile
• Its own config

• The useage of the «Keys» folder
• The useage of the «MpMissions» folder
• Available Hard drive space
• Update management

• Most robust
• Unique MpMissions folder
• Unique «keys» folder
• Allows ability to run seperate instances of different branches of the game, (E.g Dev or Stable)

Cons

• Uses more drive space
• requires more effort to create and automate the updating process

• Uses less space than Method 1
• Updating will be easier

Cons Comparison to Method 1

• Not very Robust
• 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
• Shares «keys» folder with all other exe’s (This can cause an issue when running various differing -mod servers)
• Will not allow you to run seperate instances of different branches of the game

• Uses less drive space (As you wont have multiple copies of the addons folder)
• Allows for unique MpMissions folder if desired
• Allows for unique «keys» folder if desired
• Updating will be easier

Cons Comparison to Method 1

• Requires more effort to initially create the simlinks and directories
• Will not allow you to run seperate instances of different branches of the game at the same time, (E.g Dev or Stable)

To define a different location for your MpMissions, such as a drop box location, carry out the following steps.
 

• Either Move your MpMissions to its new location or just delete it. (Don’t leave a copy in the original location)
• run cmd tool on your server to create the link, use «» around the directories

  example
  mklink /J «D:\Games\Arma3\A3Master\mpmissions» «C:\Users\user\Desktop\Dropbox\mpmissions»

Credits to

• Banshee (His original post)
• Kinsman (His original post)

I created a Debugging tutorial guide for serverside issues which you can find in the sticky section of this forum

https://forums.bistudio.com/topic/172834-tutorial-debugging-server-issues-eg-not-loading-correctly/

Steps to take

First element to decide is:
Does the issue show itself from

• a) Clientside perspective (i.e a client trying to join the server, or maybe viewing the game browser etc)
  B) Serverside perspective (Issues that can only be seen from backend (RDP) access

Now that you have a better understanding of where the issue lies, be confident that this tutorial works, because it does. many admins have used it to set up there servers successfully. So it is likely you skipped over some steps or didn’t read the instructions carefully enough (Like we all do)
There may of course be errors somewhere. if they are please let me know so I can update this. Others are likely to have also suffered the same fate.
 

• For any initial query Read through this first post (It is updated with posted content as and when required)
• If your query is not answered here, then follow the «Updated to this post» link at the top of this post and read on from there
• If you still have no answer then post on the thread and we will try and get a solution

  You will need to provide us with the following information before we can help, without it we are just guessing

• Do Not try to run addons or custom missions until you have proven a Vanilla install
• Copy of the RPT file (Ideally on Pastebin)
• Copy of the Config_Vanilla.cfg (Ideally on Pastebin)
• copy of arma.cfg (Bandwisth settings)
• Command line used
• Your issue in detail
• Steps you have taken to resolve
• Type of setup, eg
  • O/S,
  • number of servers running on the same box
  • How you are connecting to it, eg LAN, remotely via the Internet or if on the same machine

Dwarden said:

all server hosters, we have Skype channel for collaborative work of server admins, add me on Skype and demand access, slap me on IRC, try hit me over email or so … thanks

Known Issues

• Error! app 107410 is 0x1: (This occurs when you have run out of drive space or possibly memory, and is first seen after an steam update of the game)
• 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

  Dwarden said:

  easily solveable, on server firewall set enabled for any ICMP V4 incoming
  (or specifically «»Destination Unreachable» , «»Echo request»», «»Time Exceeded»», «»Source Quench»», «»Redirect»»)
  also make sure you allow NAT traversal for this rule in the firewall

• Server keeps crashing (Admins report servers as being stable, so this is likely to be one of the following unless this is a widespread issue caused by a recent patch)
  • Recently uploaded mission has critical errors (Normally description.ext entry)
  • Use of 3rd party content, eg user made missions or addons
  • Server not capable of handling the resources required, badly configured or underpowered
• DirectX
  • Windows Web Server 2008 — Error message: arma3.exe — Entry Point Not Found.The procedure entry point CreateDXGIFactory1 could not be located in the dynamic link library dxgi.dll.
    Reporting Post
    Solution Post
    Bug Tracker Ticket
    • Windows 2008 server with this issue, the following may resolve it
    • Nobody has yet reported being able to run a -server with 2003

     

    noseek said:

    This problem has been solved

    Our server original operating system: Windows Server 2008 Enterprise (Simplified Chinese) SP1

    Run steam and ArmA 3 Alpha occur same error message: …CreateDXGIFactory1 could not be located in the dynamic link library dxgi.dll…

    First, download and install directx_11_redist,the problem persists

    Then upgrade Windows Server to SP2, still error… :cryy:

    Last, download and install Windows6.0-KB971512-x86,the problem is solved!

    For reference

• ArmA2 and ArmA3 servers conflict if they use the same ports. on the same machine.
  It can cause one of the servers to use a different port automatically which will not have been defined in your firewall outbound rules and therefore not visible to the outside world
  this is easily remedied by stating a different port number in your startup params, eg -port=2312 (Leave at least 10 ports between servers)
  So your target line would then look something like

  «D:\Games\ArmA3\A3Master\arma3server_x64.exe» -port = 2312 -config=CONFIG_Vanilla.cfg
  .

• ArmA3server package loading Arma3 client data when both are installed on the same machine
  if you run Arma 3 Dedicated server data package on a system where the client is also installed there is a possibility the server will load the full client data instead of the server package, this is caused by precedence check in the registry, the solution/workaroud to this issue is to use a -mod= parameter in the command line even if you aren’t using any mods (The -mod= ensures the server loads the game data from the server.exe root folder)
  Examples of allowed useage
  • -mod=
    -mod=@myMod1
    -mod=@myMod1;@MyMod2

@echo off

SETLOCAL ENABLEDELAYEDEXPANSION

:: DEFINE the following variables where applicable to your install

SET STEAMLOGIN=mylogin mypassword
SET A3BRANCH=233780 -beta
:: For stable use SET A3BRANCH=107410
:: For Dev use SET A3BRANCH=107410 -beta development
:: For Dedi server stable package use SET A3BRANCH=233780 -beta
:: Note, the missing qotation marks, these need to be wrapped around the entire "+app_update......"

SET A3Path=D:\Games\ArmA3\A3Master
SET STEAMPATH=D:\apps\Steam


:: _________________________________________________________

echo.
echo You are about to update ArmA3
echo Dir: %A3Path%
echo Branch: %A3BRANCH%
echo.
echo Key "ENTER" yo procede
pause
%STEAMPATH%\steamcmd.exe +login %STEAMLOGIN% +force_install_dir %A3Path% +"app_update %A3BRANCH%" validate +quit
echo .
echo Your ArmA3 is now up to date
echo key "ENTER" to exit
pause

//
// config_Vanilla.cfg
// comments are written with "//" in front of them or encapsulated with /* and */
// visit https://community.bistudio.com/wiki/server.cfg for more info
 
//     GLOBAL IDENTIFICATION     //
hostname = "My Server: My Teamspeak address"; // The name of the server that shall be displayed in the public server list
 
 
 
//     JOINING RULES     //
//password = "ServerAccessPassword";         // Password for joining, eg connecting to the server, leave commented out for initial testing
maxPlayers = 40;                             // Maximum amount of players. Civilians and watchers, beholder, bystanders and so on also count as player.
persistent = 1;                              // If 1, missions still run on even after the last player disconnected.
headlessClients[]={127.0.0.1};               // The server doesn't allow arbitrary connections from headless clients if you do not define the headless clients IPs.
                                             // Multiple Connections and Addresses are allowed in the case of more than one Headless Client.
localClient[]={127.0.0.1};                   // to indicate clients with unlimited bandwidth and nearly no latency (https://dev-heaven.net/issues/62500), Available since Arma 2:OA build 99184 , including Arma 3
onUserConnected = "";                        //
onUserDisconnected = "";                     //
// disconnectTimeout = 5;                    //  Server wait time before disconnecting client, default 90 seconds, range 5 to 90 seconds. (since Arma 3 update 1.56+)
// loopback = true;                          // While using the Dev version of Arma III, adding this option will force server into LAN mode. This will allow multiple local instances of the game to connect to the server for testing purposes. 
                                             // At the same time it will prevent all non-local instances from connecting.
//upnp = 1;                                  // Automatically creates port mapping on UPNP/IGD enabled router. 
                                             // This option allows you to create a server behind NAT (your router must have public IP and support UPNP/IGD protocol).
                                             // Warning: When enabled then this setting may delay server start-up by 600s 
                                             // (standard UDP timeout of 10 minutes) if blocked on firewall or bad routing etc. Thus in such case is recommended to disable it.
forceRotorLibSimulation = 0; // Enforces the Advanced Flight Model on the server. Default = 0 (up to the player). 1 - forced AFM, 2 - forced SFM.
  
 
 
//     LOGGING     //
logFile = "A3Master.log";
timeStampFormat = "short";                   // Possible values are "none" (default),"short","full".
// WELCOME MESSAGE ("message of the day")
// It can be several lines, separated by comma
// Empty messages "" will not be displayed at all but are only for increasing the interval
motd[]={
"",
"",
"",
"__________ SYSTEM MESSAGES __________",
"Welcome to My Server",
"IMPORTANT Verify Signatures is enabled",
"",
"TS3 Server: teamspeak.mydomain.com",
"Web: www.mywebsite.com",
"TS3 Server: teamspeak.zeus-community.net",
"__________ END OF MESSAGE __________"
};
motdInterval = 5;                            // Time interval (in seconds) between each message
 
 
 
//     VOTING     //
voteMissionPlayers = 1;                      // Tells the server how many people must connect so that it displays the mission selection screen.
voteThreshold = 0.33;                        // 33% or more players need to vote for something, for example an admin or a new map, to become effective
//voteMissionPlayers = 0;
 
 
 
//     VON     //
disableVoN = 0;                              // If set to 1, Voice over Net will not be available
voncodec = 1;                                // If set to 1 then it uses IETF standard OPUS codec, if to 0 then it uses SPEEX codec (since Arma 3 update 1.58+)
vonCodecQuality = 11;                        // since 1.62.95417 supports range 1-20 //since 1.63.x will supports range 1-30 //8kHz is 0-10, 16kHz is 11-20, 32kHz(48kHz) is 21-30
 
 
 
//     SECURITY     //
passwordAdmin = "AdminPassword";             // Password to become server admin. When you're in Arma MP and connected to the server, type '#login xyz'
serverCommandPassword =  "WhateverYouWant";  // "Password to use server commands via scripts"; 
Battleye = 1;                                // = 0 to disable battleye
verifySignatures = 2;                        // Turn on addon checking system, so that players cannot join with any addon, only those you allow and host in keys folder
kickDuplicate = 1;                           // Do not allow duplicate game IDs. Second player with an existing ID will be kicked automatically. 1 means active, 0 disabled.
requiredSecureId = 2;
allowedFilePatching = 0;                     // Allow or prevent client using -filePatching to join the server. 0, is disallow, 1 is allow HC, 2 is allow all clients (since Arma 3 1.49+)
allowedLoadFileExtensions[] = {"h","hpp","sqs","sqf","fsm","cpp","paa","txt","xml","inc","ext","sqm","ods","fxy","lip","csv","kb","bik","bikb","html","htm","biedi"};
allowedPreprocessFileExtensions[] = {"h","hpp","sqs","sqf","fsm","cpp","paa","txt","xml","inc","ext","sqm","ods","fxy","lip","csv","kb","bik","bikb","html","htm","biedi"};
allowedHTMLLoadExtensions[] = {"htm","html","xml","txt"};
//allowedHTMLLoadURIs = {};                  // Leave commented to let missions/campaigns/addons decide what URIs are supported. Uncomment to define server-level restrictions for URIs
onUnsignedData = "kick (_this select 0)";    // unsigned data detected
onHackedData = "kick (_this select 0)";      // "ban (_this select 0)"; // tampering of the signature detected
onDifferentData = "";                        // data with a valid signature, but different version than the one present on server detected
doubleIdDetected = "";                       //
 
 
 
 
//     MISSION MANAGAEMENT     //
missionWhitelist[] = {};                     //an empty whitelist means there is no restriction on what missions' available 
 
/////     LEAVE THE FOLLOWING MISSION CYCLE CLASS COMMENTED OUT UNTIL YOU HAVE PROVEN THE SERVER INSTALL     /////
/*
//     MISSIONS CYCLE (see below)     //
class Missions
{
     class Mission1
     {
          template="co_xx_mymission.stratis";
          difficulty="Regular";
     };
};
*/
 

             // Situational awareness
             groupIndicators = 0; // Group indicators (0 = never, 1 = limited distance, 2 = always)
             friendlyTags = 0; // Friendly name tags (0 = never, 1 = limited distance, 2 = always)
             enemyTags = 0; // Enemy name tags (0 = never, 1 = limited distance, 2 = always)
             detectedMines = 0; // Detected mines (0 = never, 1 = limited distance, 2 = always)
             commands = 0; // Commands (0 = never, 1 = fade out, 2 = always)
             waypoints = 1; // Waypoints (0 = never, 1 = fade out, 2 = always)

            // Personal awareness
             weaponInfo = 1; // Weapon info (0 = never, 1 = fade out, 2 = always)
             stanceIndicator = 1; // Stance indicator (0 = never, 1 = fade out, 2 = always)
             staminaBar = 1; // Stamina bar
             weaponCrosshair = 0; // Weapon crosshair
             visionAid = 0; // Vision aid

             // View
             thirdPersonView = 1; // 3rd person view
             cameraShake = 1; // Camera shake

             // Multiplayer
             scoreTable = 0; // Score table
             deathMessages = 0; // Killed by
             vonID = 1; // VON ID

             // Misc
             mapContent = 0; // Extended map content
             autoReport = 0; // Automatic reporting
              multipleSaves = 0; // Multiple saves
        };

        //aiLevelPreset is counted from 0 and can have following values: 0 (AI Level Low), 1 (AI Level Normal), 2 (AI Level High), 3 (AI Level Custom).
        //When 3 (AI Level Custom) is chosen, values of skill and precision are stored to the class CustomAILevel.
        aiLevelPreset=3;
    };
    class CustomAILevel
    {
        skillAI=0.85;
        precisionAI=0.5;
    };
};

language=»English»;
adapter=-1;
MinBandwidth=800000;
MaxBandwidth=25000000;
MaxMsgSend=384;
MaxSizeGuaranteed=512;
MaxSizeNonguaranteed=256;
MinErrorToSend=0.003;
MaxCustomFileSize=100000;
Windowed=0;
serverLongitude=0;
serverLatitude=52;
serverLongitudeAuto=0;
serverLatitudeAuto=52;

-Profiles switch is used to define the location of BE, saved files, configs etc
This would be used when you want to run additional ArmA3 installs on the same machine or want to define a custom folder for the files to be read from and written to.

 
Example -profiles command line entry
«-profiles=d:\Games\ArmA3\A3Master»

eRazeri  created an auto-restart batch file to restart the server if it crashed:
::Made by eRazeri

@echo off
:start
C:\Windows\System32\tasklist /FI "IMAGENAME eq arma3server.exe" 2>NUL | C:\Windows\System32\find /I /N "arma3server.exe">NUL
if "%ERRORLEVEL%"=="0" goto loop
echo Server monitored is not running, will be started now
start "" /wait "D:\Games\Arma3\A3Master\arma3server.exe" -config=CONFIG_Vanillar.cfg "-profiles=G:Games\ArmA3\A3Master" -world=empty
echo Server started succesfully
goto started
:loop
cls
echo Server is already running, running monitoring loop
:started
C:\Windows\System32\timeout /t 10
C:\Windows\System32\tasklist /FI "IMAGENAME eq arma3server.exe" 2>NUL | C:\Windows\System32\find /I /N "arma3server.exe">NUL
if "%ERRORLEVEL%"=="0" goto loop
C:\Windows\System32\taskkill /im arma3server.exe
goto start

mods are basically a collection of addons installed in folders
Addons are made by 3rd parties to add content or functionality to the game

 
Typical Structure of a Mod folder
A3 root folder
………. \ @XYZMod
………………..\ addons
………………………… \ xyz.pbo
………………………… \ xyz.pbo.tag.bisign

 
The root MOD folder can be called anything you want, there is however an unwritten unofficial protocol that is widely used and that is to precede the folder name with the «@» character
The addons folder contains 2 type of files
.pbo (This is the actual addon)
.bisign (This is the file that the server communicates with to verify the integrity of the corresponding.pbo file
Each .pbo is (or should be) paired with its own .bisign

 
When you download an addon, typically the addon maker packs it into his own «named» mod folder,
for example @CBA_A3
Apart from the Mod folder, there should also be a «Keys» folder in the download.
The .bikey that is contained in the keys folder is for serverside use only, clients don’t need or use it.
(Some .bikeys come in the addons folder, they dont belong there but cause no harm residing there)

Quick Explanation

If verifysignatures=2 has been declared in the server.config

1. The currently loaded mission defines the addons that are required by the client to play on the server for that mission
2. The *.Bikeys found in the servers «keys» folder define what addons you are allowed to connect to the server with (Whitelisting).
3. Apart from actual addons that are used in missions this should also contain all the Bikeys for any clientside addons that you allow such as Sound mods etc

Detailed Explanation

Every correctly configured and signed addons requires 3 different files to work within a server where addon signature verification is enabled

These are

1. Addon.pbo
2. Addon.MyBikey.bisign
3. MyBikey.Bikey

The Addon.pbo and Addon.MyBike.bisign are paired together and should be found in @Modfolder\addons

The MyBikey.Bikey are for servers only and are normally packaged with the addon and bisign files but stored in a seperate folder, normally called «Keys».

Point to note *.bisigns are not needed on the server itself but afaik will be needed on any headless clients that connect to the server

When a client connects to the server there is a 2 stage check carried out by the server on the addons the client has loaded

Check 1: It checks all the addons on the client and verifies that their paired *.bisign matches one of the keys found in the keys folder. (If there is a mismatch it wont allow the client to connect)

Check 2: Every mission has addon requirement entries listed in 2 sections within its mission.sqm file. If the client does not have these «required» addons the client will not be allowed to connect

There are 3 main categories of addons

1. Server-only addons
2. Client-only addons
3. Mission Dependancy addons

Server-only addons

These are addons that only the server is required to run and are loaded on the server using the command line parameter -servermod=

These tend to be addons that run scripts and do not create mission dependancy, so typically to stop them being accidentally loaded by clients do not come with any .bisigns or .bikeys and are coded in such a way that if the node they are being run on is not the server, their scripts exit

Client Only addons

also known as clientside addons. Typically this covers sound mods, any SFX mods, GUI mods such as the Shac Tac collection. They wont (or shouldnt) create any mission dependancies, nor effect other clients or the server 

Mission dependancy addons

These are addons that bring new content to the game such as vehicles, units, weapons, terrain etc. The likes of RHS, TFAR, Alive, ACE, CUP fall into this category. When classes from these addons are used in a mission they automatically add an entry into the mission.sqm which defines the actual addons you need to play that mission. Typically these addons need to be run on both the server and the client.

The addon creator first makes his own private key which he uses to sign all his addons.

The tools for this are available from the ArmA Tools collection

When he signs his addons with this tool, he creates a *.bisign for each addon and one *.Bikey that covers all the addons he just signed

Some creators make a new private key each time they resign their addons, this tends to be how they control their versioning.

You can if you wish resign any addons you host with your own keys, there are advantages and disadvantages to this

Advantages

     1)  Gives you 100% of control over exactly what version of addons you allow

          (Some addon creator continue to use the exact same private key to resign their addons with)

          (Some addon creator create a new key but with exactly the same syntax, making it problematic to debug some issues)

     2) Reduces instability issues

     3) For me massively reduces client support calls

Disadvantages

1. You have to fully manage your addon pack and offer it via your own repository

For me the advantages far outweigh the disadvantages

Our addon management is almost fully automated.

The addon admin manually updates the content in our repo

Then via 1 batch file it

1. automatically resigns all the addons with an automatically created date stamped private key (Example ZIslands_2017_03_14.bikey)
2. Updates all the servers with the updated addon pack
3. Uploads the updated pack to our file host server

Then the clients just need to  hit an update button on their arma 3 sync tool and voila every client and the server are running exactly the same content.

As you can imagine this saves having to keep a list of what addons we allow, , where to get them etc . It removes a lot of hassle from supporting clients and re explaining to them how to manually manage their addon packs

RESIGNING ISSUES

If your having issues resigning an addon, the following solution may help

Hardhast stated in a thread that was he;ping  guy who was having issues with his bikey and bisign not liking each other after resigning an addon in his mod pack

To use addons is basically the same format for both clients and servers, apart from the server «.bikey» and config file entries

 
Unpack and copy them into your arma3 folder
Initialise the addons by defining either

 
a) -mod=@CBA_A3;@ModB;@ModC in the command line for a desktop shortcut that is linked to your arma3.exe\arma3server.exe
B) -mod=@CBA_A3;@ModB;@ModC in the parameters field for a firedeamon service (recommended for servers) you can get a clan discount for this great tool
c) using a similar command line in a custom launcher tool (Some are good some are not so).
d) Using the ingame Mod launcher system (Clients only)
SERVER ONLY:
Define verifysignatures=2 on your server config file (The same file where you define the admin password)
Copy the .bikey in the mod’s «keys» folder to the server’s A3 root «Keys» folder
(The Keys folder white lists the allowed addons on your server. If someone tries to connect to the server with addons, you dont have a bikey installed for, they wont be able to connect.
You should allow some clientside addons such as JSRS Mod, shack tac hud etc, do this by adding their .bikey to your keys folder. These are clientside only addons, you dont need to run these addons on the server

In MOST cases, you don’t have to keep the addons in the mod folders that the addons came in, you can create your own and copy all the files needed into your own mod structure

http://www.armaholic.com/ is the best source for direct downloads
http://play.withsix.com/arma-3 is a download and management application (Steep learning curve but widely used across a lot of servers. You will need to learn this at some point)
ArmA3Sync is a serverside/clientside content management and launcher application, easier to use and set up. We personally use this, it gives better control and ease of use to our clients
 

Version 1.01

• Added info about defining a different port if running an A2 and an A3 server on the same machine
• Added «Known Issues about Windows 2003 server and Direct X (No solution as yet)
• Added links to WIKI for folks who were unable to find the obvious information

Version 1.02

• reformatted , reorganised initial post
• Added example files
• Added firedeamon section
• Added Port forwarding section
• Added Autorestart section
• Added Running Client and Server on same machine section

Version 1.03

• Updated «How To» instructions, added initial start up to be in online mode and run as Administrator
• Added additional commandline params
• Added to troubleshooting: Known issues

Version 1.04

• Added «How to run development version
• Updated troubleshooting: with fix for DirectX issue
• Updated troubleshooting: with «How best to use this thread»

Version 1.05
Date: 17th March 2013

• Added Section: «LOCATION OF FILES (When setting parameters)»
• Added Section: «RE-LOCATING MPMissions (For example to a dropbox)»
• Added «VerifySignatures = 2» into config.cfg (My bad, why I forgot to add this I will never know) IMPORTANT Please add to config

Version 1.06
Date: 23rd March 2013

• Added Section: «Server Admin Commands)»

Version 1.07
Date: 26th May 2013

• Major rewrite of tutorial modifying for useage of ArmA3server.exe and multiple server instances
• Added section for Multi Server set up on the same machine

Version 1.08
Date: 27th May 2013

• Syntax error in the ArmA3_Steam_Updater.cmd
• changed

SET A3BRANCH="233780 -beta"
:: For stable use SET A3BRANCH="107410"
:: For Dev use SET A3BRANCH="107410 -beta development"
:: For Dedi server stable package use SET A3BRANCH="233780 -beta"
+app_update %A3BRANCH%

to

SET A3BRANCH=233780 -beta
:: For stable use SET A3BRANCH=107410
:: For Dev use SET A3BRANCH=107410 -beta development
:: For Dedi server stable package use SET A3BRANCH=233780 -beta
:: Note, the missing quotation marks, these need to be wrapped around the entire "+app_update......" statement
"+app_update %A3BRANCH%"

Version 1.09
Date: 29th May 2013

• Win2003 can now be used
• Tidy up of initial thread, no consistency in Directory defintions

Version 1.10
Date: 25th June 2013

• Changed filenames ArmA3Alpha…… to ArmA3 to reflect beta release changes
• Added Server bandwidth optimisation section ( very good help link)
• Added «Running Server and client on same machine»

Version 1.11
Date: 25th August 2013

• Added known issues entry to explain the steam error Error! app 107410 is 0x1

 
Version 1.12
Date: Feb 2014

• Added information about the dedicated server package for the stable branch

Version 1.13
Date: 9th April 2014

• Added information to the troubleshooting section and the Known issues section
• Specifically information about running a client install and a server install on the same machine

Version 1.14
Date: 12th April 2014

• Clarified requirement to run ArmA3server.exe as administrator. (This is a requirement of Battleye)

Version 1.15
Date 12th June 2014

• Added Mods & Addons section

Version 1.16
Date 5th July 2014

• Updated port information to reflect changes in steam query port detailed in A3 patch 1.22 hotfix
• sections changed are
• PORT FORWARDING (ArmA3) (Firewalls)
• CONFIG_Vanilla.cfg

Version 1.17
Date 31st August 2014

• Updated port information, forgot to make some changes from the 1.22 hotfix patch
• sections changed are
• PORT FORWARDING (ArmA3) (Firewalls)
• CONFIG_Vanilla.cfg

Version 1.18
Date 25th October 2015
Updated the Config_Vanilla.cfg by commenting out and adding new entries to it.
sections changed are

• CONFIG_Vanilla.cfg
• serverCommandPassword
• allowedLoadFileExtensions
• allowedPreprocessFileExtensions
• allowedHTMLLoadExtensions
• // HEADLESS CLIENT
• headlessClients[]={127.0.0.1};
• localClient[]={127.0.0.1};

Version 1.19
Date 30th April 2016

• Edited the entire tutorial, decluttering it and creating expanding spoiler tags for each section to make it less of a «wall of text»
• Edited the config_vanilla.cfg to reflect changes up to and including patch 1.58
• Edited the *****.ArmA3Profile (Difficulty settings) to reflect changes in patch 1.58
• Added a Battleye configuration section

Version 1.20
Date 16th March 2017

• Massive update to the «Addons» section
• Updated some info for the armaserver_x64.exe (Still got to work through the entire doc to update everything for this)

Version 1.21
Date 21st March 2017

Worked through entire post updating to include arma3server_x64 changes

Important changes are

• Firewall rules
• Battleye configuration