DayZ admin commands and RCON setup
Use BattlEye RCON to inspect connected players, broadcast messages and moderate your DayZ server. Configure its password and UDP port in the BattlEye file loaded by the running instance, then check access with a compatible client. For a Workshop admin menu, follow that mod’s installation and permission procedure.
Choose the administration channel
Section titled “Choose the administration channel”| Task | Use |
|---|---|
| Moderate players through a remote connection | Configure BattlEye RCON using the steps below. |
| Control the game process | Use your supervisor or VXPanel Console power controls to start, stop or restart. |
| Open a menu, teleport or spawn an object | Install VPP, COT or a mod that documents the required feature. |
| Control who can join | Configure a join password or whitelist. |
Keep the native game setting passwordAdmin, BattlEye’s RConPassword, join controls and mod administrator files separate. They control different kinds of access. Check command support in DayZ before using a table copied from Arma.
Find the active BattlEye configuration
Section titled “Find the active BattlEye configuration”Save your launch settings and configuration, and record the game, query and RCON endpoints. If the server is managed, use the RCON endpoint assigned to your service and its supported password control. Choosing an arbitrary port can conflict with another instance.
Locate -BEpath in the launch arguments or current startup log and confirm which BattlEye directory the instance uses. Edit that configuration after saving it. The path override is described in the DayZ server configuration reference; a directory named battleye elsewhere may belong to another instance.
On Windows x64, the documented filename is BEServer_x64.cfg in BattlEye’s working directory. BattlEye can rename a loaded configuration, so inspect the active instance’s file and suffix. Linux uses lowercase filenames. Confirm the installed server’s directory and naming before transferring a Windows example. See BattlEye’s configuration reference.
Set the password and port
Section titled “Set the password and port”Use the supported stop control and wait until the game process exits. In the saved working copy, keep one assignment for each field:
RConPassword REPLACE_WITH_A_UNIQUE_SECRETRConPort REPLACE_WITH_ASSIGNED_UDP_PORTReplace both placeholders before uploading. Enter a numeric RCON port allocated to this instance, with no conflict with its game ports. Set a strong secret and exclude it from screenshots, shared launch examples and support logs. Use your supported firewall controls to allow inbound UDP from the required management addresses.
Upload the checked file, start the instance and read the new startup output. Test RCON access in the next step even if players can join the game. BEC supplies optional third-party administration and scheduling; you can configure BattlEye RCON without installing it.
Prove the connection with a harmless command
Section titled “Prove the connection with a harmless command”Enter the server address, assigned RCON UDP port and RCON password in a compatible client. Request commands and players. Compare the player list with your instance before sending a command that changes access.
VXPanel exposes a Console RCON field and Send control where the service policy permits it. On your private test server, send this broadcast:
say -1 RCON test: this is an announcement only.Have a connected tester check the text in chat. Save the build, endpoint and result in your test record, excluding the password. Arrange the restart through scheduled maintenance or native server messages; a chat announcement itself leaves the process running.
Identify players before moderation
Section titled “Identify players before moderation”Check the argument order against BattlEye’s command reference:
| Command | Purpose |
|---|---|
players |
Inspect session numbers and GUIDs. |
kick [player #] [reason] |
Disconnect the selected session. |
ban [player #] [minutes] [reason] |
Restrict access for that player; a duration of 0 is permanent. |
bans |
Obtain the ban list and entry numbers. |
removeBan [ban #] |
Delete the matching ban entry. |
Replace the bracketed arguments with values from the current list. Run players again before acting because session numbers can change after reconnects. Match the player to the incident evidence and retain the reason. Practice with a consenting test account and a short ban duration, then check ban removal and the account’s ability to rejoin.
Label stored identities by system: BattlEye GUID, DayZ identity or Steam64 ID. Use the identifier required by each mod permission or whitelist format instead of substituting one for another. Include the active ban data in your backup.
Diagnose a failed connection
Section titled “Diagnose a failed connection”| Result | Check next |
|---|---|
| Timeout | Confirm the loaded directory, startup result, RCON port and UDP firewall policy. Testing a TCP connection does not test this UDP service. |
| Authentication rejected | Compare the client profile with the current RCON secret. Neither a join password nor passwordAdmin authenticates this connection. |
| Read-only command works, announcement fails | Read the reply, inspect the command and panel policy, and ask a player to check chat. |
| Mod menu remains unavailable | Check the mod’s permissions and load order through its own procedure. |
For rollback, stop the instance and restore the saved configuration and launch settings. Revoke temporary management access; replace any secret exposed during troubleshooting.
Source and verification scope
Section titled “Source and verification scope”This guide used AI-assisted research and drafting. On 3 October 2026, the linked DayZ and BattlEye references were used to check configuration and command syntax. Verification did not include a live RCON login, kick or ban. Complete the connection and test-account checks on your instance before giving staff access.