[EN] Install AdminCore on an Arma 3 server

1. Gather your server information

Collect the information required to create the licence.

Sign in to AdminCore with the subscription owner's account. Have the server name, public IP address, game port and serverCommandPassword value from server.cfg ready. The server command password is not the regular administrator password.

server.cfg

serverCommandPassword = "YOUR_LONG_UNIQUE_PASSWORD";

Core includes one server licence, AdminCore RCON and the anti-cheat. Pro supports up to three licences and also includes the in-game administration panel and developer console.

2. Prepare the ban.txt file

AdminCore synchronises bans with the server's local file.

The path must point to the ban.txt file used by the Arma 3 profile. The path below is commonly used on OxygenServ. If the file does not exist, create an empty one before generating the package.

OxygenServ / Linux

mkdir -p /home/container/serverprofile/home/Player
touch /home/container/serverprofile/home/Player/ban.txt

For another Linux host, locate the profile directory configured in the startup parameters and adjust the path. On Windows, enter the absolute path, for example C:\arma3server\profiles\ban.txt.

3. Create the licence in AdminCore

The package is generated specifically for this server instance.

In the AdminCore panel, open “My servers”, then “Create a licence”. Enter the server name, public IP, game port, absolute ban.txt path and server command password. Select “Create and compile package”.

Wait for the Docker compilation to finish, then select “Download ZIP”. Do not share this archive: its extensions are bound to the licence key, IP address and port. Never reuse a package generated for a different server.

4. Install the @admincore directory

The ZIP contains the Windows and Linux binaries and all required PBO files.

Extract the archive. Upload the complete @admincore directory to the Arma 3 server root, next to arma3server_x64.exe on Windows or arma3server_x64 on Linux. Keep the DLL and SO files in the root of @admincore and the PBO files inside @admincore/addons.

Expected directory structure

@admincore/
├── admincore_rcon.dll
├── admincore_rcon_x64.dll
├── admincore_rcon.so
├── admincore_rcon_x64.so
├── admincore_anticheat.dll
├── admincore_anticheat_x64.dll
├── admincore_anticheat.so
├── admincore_anticheat_x64.so
└── addons/
    ├── admincore_rcon.pbo
    ├── admincore_anticheat.pbo
    └── admincore_ingame.pbo  (Pro plan)

Linux file and directory names are case-sensitive. Keep their exact spelling and letter case.

5. Add AdminCore to the startup parameters

AdminCore must be loaded as a server-side mod.

Add @admincore to your host's -serverMod option or startup script. If other server mods are already configured, separate them with a semicolon and keep the existing entries.

Startup parameter

-serverMod=@admincore

With other server mods

-serverMod=@extension;@admincore

6. Integrate the in-game panel (Pro plan)

This step only applies to the Pro package.

The Pro ZIP contains an AdminCore_InGame_MISSION directory before @admincore. Copy AdminCore_AdminMenu.hpp into your mission directory, then add the following include to description.ext.

description.ext

#include "AdminCore_AdminMenu.hpp"

Open the supplied CfgRemoteExec.hpp and merge its classes into CfgRemoteExec > class Functions in your mission. If either section already exists, do not create a duplicate: only add the AdminCore class declarations inside the existing class Functions section.

CfgRemoteExec.hpp

class admincore_ingame_acfn_adminRequest { allowedTargets = 2; };
class admincore_ingame_acfn_initClient { allowedTargets = 1; jip = 1; };
class admincore_ingame_acfn_open { allowedTargets = 1; };
class admincore_ingame_acfn_notify { allowedTargets = 1; };
class admincore_ingame_acfn_clientAction { allowedTargets = 1; };
class admincore_ingame_acfn_revive { allowedTargets = 1; };
class admincore_ingame_acfn_giveVItem { allowedTargets = 1; };
class admincore_ingame_acfn_giveGear { allowedTargets = 1; };
class admincore_ingame_acfn_displayInventory { allowedTargets = 1; };
class admincore_ingame_acfn_collectInventory { allowedTargets = 1; };

Do not add a functions directory or an execVM call. The PBO preInit registers the functions automatically. F2 opens the in-game administration panel, while F3 opens the developer console for authorised administrators.

7. Start the server and verify the connection

Check the logs before using the administration features.

Fully restart the Arma 3 server. Search the RPT log for the [ADMINCORE RCON] and [ADMINCORE ANTICHEAT] prefixes. RCON should report that its server loop has been initialised.

Expected RPT result

[ADMINCORE RCON] Boucle serveur initialisée

Return to AdminCore. The licence should display “Agent connected” or “Server active”. Open the overview and select “Refresh” in the Players section to confirm that the server responds.

8. Troubleshoot common issues

Connection errors usually come from the licence or server configuration.

If the agent remains offline, make sure -serverMod contains @admincore, the DLL or SO files are in the mod root, the PBO files are in addons, and the public IP and port exactly match the licence.

If the RPT shows “CONNEXION REFUSÉE”, verify the IP, port and subscription. If ban commands fail, verify serverCommandPassword and the absolute ban.txt path. If package generation fails, also review “Docker logs” under My servers.

After changing the IP, port, ban.txt path or server command password, use “Regenerate DLL / SO”, download the new ZIP, replace the entire @admincore directory and restart the server. The previous package remains active until the new compilation succeeds.