Updating your Egg? Please see How to Update Egg to avoid any issues!
 Red-Thirten 💻 🔨 |
 Aussie Server Hosts 💻 💡 |
 IAmSilK 💻 💡 |
 Daave 💻 ⭐ 💤 |
From Bohemia Interactive's Website:
Experience true combat gameplay in a massive military sandbox. Deploying a wide variety of single and multiplayer content, over 20 vehicles and 40 weapons, and limitless opportunities for content creation, this is the PC’s premier military game. Authentic, diverse, open - Arma 3 sends you to war.
- Configurable to run 32 or 64-bit versions of the server
- Max Players is configurable and able to be host enforced (*see Recommended Egg Modifications)
- Able to download server updates on startup
- Able to download, update, and load Steam Workshop mods on startup (*see Installation Requirements)
- Accepts uploaded HTML modlist files exported from the Arma 3 Launcher to define mods to load on the server.
- Also accepts manually listed mods, CDLCs, and server-side only mods.
- Checks for mod updates against their Steam Workshop page's last update for quick and efficient update checks.
- Automatically moves mod
.bikey's to the/keys/directory.
- Configurable to download Creator DLCs
- Configurable to run Beta/Performance binaries of the server (if desired; advanced users only)
- Additional Arma 3 startup parameters can be added to fine-tune performance
- Configurable to run up to 5 Headless Clients in parallel with the main server (may require additional performance overhead)
- WHMCS compatible (*see Recommended Egg Modifications)
- A valid, real Steam account, with Steam Guard turned off, is required to install the server (default "anonymous" login cannot be used). This account does not need to own Arma 3. For security reasons it is recommended by Valve that you create a new Steam account just for your dedicated servers.
- For automatic Steam Workshop mod downloading to work, the Steam account does need to own Arma 3. However, this is optional functionality, and mods can be manually uploaded to the server if desired. Hosts may feel free to change the "Disable Mod Downloads/Updates" variable to
1if they would not like to offer it's functionality to clients.
Default server ports are listed below, but the Main port can be any port. There are three more ports after the Main port that are relative to the Main port (For example: The BattlEye port is always 4 ports higher than the Main port). All four ports are required for normal server behavior. It is recommended that each server be 100 ports separate from each other.
| Port | Default (UDP) |
|---|---|
| Arma 3 Game & VON (Main) | 2302 |
| Steam Query (+1) | 2303 |
| Steam Port (+2) | 2304 |
| BattleEye (+4) | 2306 |
| Bare Minimum | Recommended | |
|---|---|---|
| Processor | Recent x86/64 (AMD/Intel) processor. No ARM support. | ARMA 3 is mainly CPU intensive. Contrary to popular belief, the server binary can run on multiple cores/threads. However, it's ability to manage asynchronous tasks and hyperthread is very limited, meaning additional cores/threads reach diminishing returns very quickly. In addition, it's ability to utilize all of the CPU allotted to it for AI processing seems to be limited as well. Therefore, a Headless Client and a properly written mission file are highly recommended if large amounts of AI units will be used. |
| RAM | 2048 MiB | 3072 MiB (If used, every Headless Client uses an additional 2048 MB of RAM as well) |
| Storage | 10 GB | 50+ GB (depends on how many mods are installed) |
| Network | 0.512 Mbit/s/player | 1-5 Mbit/s/player |
| Host OS | Most stable Linux OS branches should work | Using the latest kernel version for your installed OS can prevent some edge-case installation/boot issues. |
External/Compatible RCON clients can be used to connect to the server if the following requirements are met:
- An extra port is forwarded and assigned to the server in Pterodactyl. It is recommended to use the +5 port from the Main port (ie. if Main port is 2032, RCON port would be 2037). The +3 port cannot be used as it is reserved.
server.cfghasBattlEye = 1;. Unfortunately, RCON cannot be used with BattlEye off.- A
beserver_x64.cfgfile (orbeserver.cfgif using 32-bit) is added to/home/container/battleye/launchwith the following content:
RConPassword your_rcon_password
RConPort your_rcon_port
Server hosts may wish to save space and avoid download issues by mounting large and/or common mods. Unfortunately, Arma only allows mods to be loaded from directories down-stream of the server binary (ie. /home/container/*. Docker limitations disallow Pterodactyl from mounting mounts into /home/container/*. The only way around this that I can think of is to create a symlink with a destination that is outside of this location. If anyone knows a way around this, please open an Issue to let us know.
The following are highly recommended variable modifications you can make to the egg after importing it to your panel. While viewing this egg, simply go to the "Variables" tab of the egg editor to make these changes.
- To make deploying servers easy (or if you are using WHMCS), it is recommended to edit the default values of "Steam Username" and "Steam Password" to your Steam account dedicated for hosting. This will make all newly installed servers use these credentials. DO NOT make these fields visible to the end user so that they can use their own Steam accounts; the panel will save their Steam credentials in plain text, which is a BIG NO NO for security and privacy.
- If you would like to restrict the maximum number of players that can join your client's server, you can change the permissions of the "Max Players" variable so that clients can only view this value (and not edit it). It's default value can also be changed, or the value can be changed on a server-by-server basis as desired.
If you already have an Arma 3 egg installed on your panel, there are a couple things to consider before updating to this egg:
- The Startup Command has changed, but Pterodactyl currently does not update this across all your existing servers. Servers will still boot with their old Startup Command, but the new HTML Modlist feature will not work, and depreciated variables for config files will be used. Servers will have to be manually updated to the new Startup Command via the Startup tab.
- Startup Variables have been completely rehauled. While most important existing variables have retained their Environment Variable names, a lot of their titles and order have been adjusted. Simply updating your existing egg with this egg may lead to Startup Variables being terribly out of order and cluttered. Therefore, the following steps are recommended to avoid this:
- Change the name of your existing Arma 3 egg to "Arma 3 (Old)".
- Install this updated egg as a new egg in your nest.
- Make any egg modifications you would like. (*see Recommended Egg Modifications)
- Change all existing Arma 3 servers to the new egg via the Startup tab.
- Delete the old egg.