I will be updating this thread regularly with more information regarding tools, scripts, instructions, etc. Make sure to bookmark it!
One of the biggest gripes I had when I first started administering a DayZ server was the utter lack of documentation for the process. This is my attempt to consolidate some of the information in this forum and to help new and veteran server administrators get their bearings. I will give credit to authors of other threads where I can. I'd like to see that this gets used as a central repository for server knowledge as there seems to be a real lack of information out there for new server administrators.
What you should know before purchasing a server
- Hosting a server will get you no in-game reward or advantage. You're just another sucker like the rest of us. People are going to think that you have all of these wonder scripts that you can do to restore gear, stop hackers, etc. NOPE.
- You will get a lot of flak from the community, whether you're deserving of it or not. (OMG SERVER ADMIN ABUSE)
- Hackers are rampant, and there's not much that you can do about it other than following or slightly bending the DayZ staff rules
- You are at the mercy of the ARMA platform. Servers are buggy. They can crash a lot
- If you're not getting server donations, you're paying for this out of your own pocket
- You can only use the default Chenarus map. You CANNOT use any new map on official servers.
ARMAOA Beta - The ARMA 2 Operation Arrowhead beta. This is different from any of the DayZ Source code. These updates are usually pushed out by 3rd party launchers such as Six Launcher and DayZ Commander
DayZ Mission Files - These are the files that go in the @dayz directory, and contain the information you need to run a server.
IMPORTANT: There are RULES that you need to follow as a server administrator. They are as follows:
- The server MAY NOT be passworded
- You MAY NOT run any other mods, or keys.
- You CANNOT kick other players for your friends and clanmates
- You CANNOT lock the server for ANY reason at ANY time
- You CANNOT edit the DayZ Mod mission files
- Battleye MUST be installed and running at ALL TIMES
- Minimum slot count of 40 (30 for countries where bandwidth is expensive i.e. developing countries)
- You may only ban players for two reasons: Malicious talk, and racism.
- You may only kick for disruptive behavior (such as continued VOIP over side channel).
Where do I start?
There are two options that face you if you'd like to purchase a DayZ Server. Here's the scoop:
A bare bones Windows Server that will require you to go through the set-up process from start to finish. This involves you installing ARMA and DayZ yourself and requires you to do all of the server management yourself. You can either set up your own server or you can rent a dedicated server from a server host.
Guidelines for setting up your own hardware.
This information and much more can be found in this thread.
- Quad Core CPU @ 2.5GHz (amended - Feedback suggests that as long as you're running a faster CPU, you should be fine)
- 2GB+ RAM (RAM isn't a big issue in an ArmA server, so don't be overly concerned with having copious amounts [16GB+] of it as it won't be required)
- 50GB+ HDD (Preferably SATA3 or SSD) (Installation alone is ~20GB. Also, keep log files in mind! These get HUGE if not pruned)
- Bandwidth at least 2TB a month. Hive and Player client communication accounts for A LOT of bandwidth.
- Easy access to configuration files, DayZ files, and anything else that you might want to tinker with
- Much more freedom with your administration style
- You can make the server scalable. Need to increase slots? No problem!
- Much more expensive. Either pay for your own hardware / Internet or get a hosting company
- Setup and administration learning curve
- Whitelisting Process can be delayed
- Total lack of support should you not know what you're doing
Hosted servers are ran by hosting companies. These companies will either charge per slot (player slot) or per month. Management of these server is limited to a web interface, and permissions and features are generally dependent on the host that you pick. All updates are generally done by the hosting company, requiring little maintenance on your part.
- Servers are generally set up within a certain amount of time (usually 12-24 hours depending on the host)
- Straight forward administration via Web Interface (again, depending on the host)
- Most hosts have a support team in place with SLAs (service level agreements [they're obligated to respond in X amount of time])
- Cost is usually based on Slot (player count) and is fairly competitive and cheap
- Occasional service interruptions (whether it be caused by network outage, tool updates, etc)
- Potential for lack of support
- Very restricted administration capabilities
Look around the forums at the various promotional threads and make a conscious decision!
XelaServers (For 15% off, enter promo code 15%DayZ )
TrinityGames (30% off included in the price!)
Apex Servers (For 15% off, enter promo code PREPAY)
TotalSimplicity (Canadian Host)
And many more! (if you're a hosting company please let me know and I will add you to the list)
Okay now I understand the server options, what's next?
Once you've made your decision on which way to go, you can base your next steps on that
Firstly, purchase and configure your DayZ server. Here's a few threads with information on how to configure your dedicated DayZ server:
- Install ARMA 2 & Operation Arrowhead on the server via steam, you can move the server anywhere you please afterwards. Bohemia has a Wiki set up for this.
- Sign your server up for DayZ via the Web Request Form
- Wait for further instructions from the DayZ staff.
- (Please note, some threads indicate that the setup instructions included may not be accurate - can be build this out?)
Optimizing your server (EXCELLENT POST)
Helpful Tools: (I did not develop any of these tools, and do not accept responsibility for anything they may do to harm your server or system, nor can I provide any insight as to how they operate)
- DayZ Server Suite (log parser, etc)
- Paronity's Log Parser
- DayZ Log Parser
- Battleye Extended Controls (RCON command-line tool)
- Ryahn's Server Tool Sigma (Heartbeat, anti-crash, log pruner, etc)
- More to come - just ran out of time
- Once you've purchased your server from your server host, you'll need to wait for them to send you the details for your server, as well as the links for TCAdmin. (or whatever back-end administration platform they use
- Login to the back-end and configure your server based on the information below
- Depending on your access, configure the difficulty of your server, along with Server Name, etc. Make sure you're running the latest patch!
- Familiarize yourself with what you do and do not have access to. Find out where to go for logs, how to do updates, etc.
Q: How long does it take my server to be set up?
A: It takes about a few minutes to setup your account but your server will take 1 - 3 hours to install. The time to install changes due to traffic on box being installed on. There are circumstances in which your server can take up to 24 hours to be ready, such as peak order times, etc.
Q: What are the admin commands / How do I use Battleye RCON?
A: You can check this wiki for RCON commands.
You can also check this wiki for admin commands.
Q: Why can I not log in with RCON? It kicks me out!
A: Make sure you have a BEServer.cfg or BEServer_active_XXX.cfg with RCONPassword and MaxPing configured. If you do not have one, we can upload a default one for you edit.
Q: How do I adjust my difficulty settings or what do they mean?
A: You can check this wiki out on how to adjust it and it explains how things work
Q: Why can't I see my server in Six Launcher/DayZ Commander/Ingame?
A: If you cannot see it in either, please try using your IP and Port and connecting remotely in-game to the IP. If it still does not sign up, please submit a ticket.
Configuring your DayZ Server
What you should know
- You cannot deviate from the official server naming convention
- Most variables in the configuration file cannot/should not be changed
- Changing something that shouldn't be changed can result in unpredictable behaviour - YOU are responsible for this, not your server host.
Instance IDs identify your server. For example, my server is US355. This is my Instance ID. This will be provided either by your Managed Server host (if they do whitelisting) or the DayZ staff after you've registered your server at the link above under "Dedicated Servers". You must include this, as it is a part of the official server naming convention linked above.
DayZ difficulty comes in three flavors with settings enabled/disabled based on what you choose. These variables are configurable. In this section I will attempt to describe what each variable in the configuration file means.
- Regular (Pretty much everything is enabled)
- Veteran (Map waypoints are disabled, name tags are disabled)
- Expert (HUD, Crosshairs, Waypoints, Nametags are disabled)
Here's an example of the Configuration file (cfgdayz.ArmA2OAProfile) for a server set at the "Regular" difficulty. Below, I will give descriptions as to what each variable does.
For reference, a 0 = off, and 1 = on.
3rdPersonView=1; -- (0,1) Disables or Enables 3rd Person View for your server
armor=0; -- ALWAYS DISABLED - Gives you improved body armor, tank armor etc
autoAim=0; -- ALWAYS DISABLED - Enables auto aim when you're not looking through your weapon's scope. Also works with crosshair off
autoGuideAT=0; -- ALWAYS DISABLED - AT missiles will be automatically guided to their target. If 0, player has to lock onto the target.
autoSpot=0; -- ALWAYS DISABLED - If you're close enough to an enemy, you'll report it without right-clicking
cameraShake=1; -- ALWAYS ENABLED - Used for camera shake for shock, injuries, etc.
clockIndicator=0; -- ALWAYS DISABLED - Displays the clock indicator on the left of your screen when giving/receiving orders like "At 11 o'clock, eemy man at 200 meters"
deathMessages=1; -- (0,1) Displays "XXX was killed by YYY" messages in multiplayer
enemyTag=0; -- ALWAYS DISABLED - Displays information on enemy units
friendlyTag=0; -- ALWAYS DISABLED - Displays information on friendly units. ONLY WORKS WITH 'Weaponcursor=0', eg crosshair on.
hud=0; -- ALWAYS DISABLED - Shows you leaders location and your position in formation
hudGroupInfo=0; -- ALWAYS DISABLED - Shows your group information in the HUD
hudPerm=1; -- (0,1) Permanently show or disable the HUD
hudWp=0; -- ALWAYS DISABLED - hows Waypoints right after they're ordered to you
hudWpPerm=0 ; -- ALWAYS DISABLED - Shows Waypoints permanently
map=0; -- (0,1) Enable or Disable Waypoints on the map
netStats=1; -- Enables the scoreboard functionality
tracers=0; -- ALWAYS DISABLED - Displays tracers even of small arms that in real life would not have tracers
ultraAI=0; -- ALWAYS DISABLED - Enables some kind of super AI that hears and sses more and has better tactics. This is for both friendly and enemy sides.
unlimitedSaves=0; -- ALWAYS DISABLED - Enables saing permanently. For single player missions. But you then can only load the last save state.
vonID=1; -- When using VoN (Voice over Network), display the name of the player speaking.
weaponCursor=1; -- Shows the crosshair for your weapon
skillFriendly=0; -- Friendly tactics skill (For AI Only)
precisionFriendly=0; -- Friendly shooting precision (For AI Only)
skillEnemy=0; -- Enemy tactics skill (For AI Only)
precisionEnemy=0; -- Enemy shooting precision (For AI Only)
More information about the configuration file can be found here.
There are multiple threads in the Server General forum like this one that will help you further with your configuration files.
Configuring your Server's startup and running parameters
A lot of great information can be found here.
Below are variables that you can directly configure for your server:
passwordAdmin = "xyzxyz";
Password for Administrator Access via in-game chat menu / Admin Menu
Servername visible in the game browser. Please make sure you follow the official server naming convention
maxPlayers = 40;
The Max player slots for your server. Please ensure you are following the slot rules found here.
disableVoN = 1;
Enables or disables the Voice over Net. Default = 0.
Enables or Disables BattlEye. By default, this is set to 0 (off). Please enable it!
Set to prevent obsolete versions of the ARMAOA client from joining. Example: requiredBuild=95417; will restrict anyone who's running an older ARMAOA beta version of 95417 from connecting.
Configuring BattlEye on your Dedicated Server
In order to enable BattlEye for your server, you'll need to edit your server.cfg file. source
Enables or disables the BattlEye anti-cheat engine. Default 0. - since 1.09 beta. Note that this requires specific dlls to be installed on the server and all clients joining the game. They can be found here
These steps are for managed server hosts who use ACP/TCAdmin.
To get to the configuration files
DO NOT EDIT THESE FILES WHILE THE SERVER IS RUNNING
The Configuration Files menu
What you find find in these files:
Generally, this file is only going to be modified if you're running a dedicated server More information can be found here.
Where BattlEye records Player Names and GUIDs for users who are hackers. More information can be found here
You can set your Max Ping and RCON passwords here. You'll need to set your ARMA RCON password here if you want to log in via the in-game chat menu.
Most of the settings in here are straight forward. Reply to this thread if you have specific questions. The parameters you are editing are 0 and 1 flags in the server.cfg file.
Where the magic happens. This holds all of the different server configuration settings such as crosshair, map, and others as seen in the section above. 0 = off, 1 = on. More information can be found here
Edited by smasht_AU, 03 February 2013 - 02:39 AM.