DayZ Admin Commands: What Actually Works on a Server
DayZ admin commands depend on the tool: learn what Bohemia documents for RCon and server files, plus safe options for managing a PC server.
You will need
- DayZ for PC on Steam
- Owner or administrator access to a community server
- Access to the server panel or configuration files
DayZ admin commands on PC depend on which tool is connected to your community server: BattlEye RCon, server access files, a hosting panel, or an admin mod. Bohemia’s current DayZ server configuration guide documents the admin password and BattlEye setup, but it does not publish a general in-game chat-command list. This guide maps routine jobs to the tools that support them and leaves disputed # commands out. It covers the Steam PC build; it does not apply to Xbox, PlayStation, or Microsoft Store/Game Pass PC servers.
Match the admin job to the right tool#
Start with the job, not a copied list of commands. DayZ server administration is split across server configuration, BattlEye Remote Console (RCon), host-panel controls, and optional mods. They do different things, and a command that belongs to Arma or another game is not automatically a DayZ command.
| Admin job | Where to start | What to verify |
|---|---|---|
| See who is connected | Host panel or a supported BattlEye RCon tool | The server is running and the list has refreshed |
| Remove or ban a player | Host panel or a verified RCon workflow | The player identifier and ban list afterward |
| Restrict who can join | The server’s whitelist and access settings | The correct SteamID64 is listed |
| Send a server message | Host panel or a verified RCon workflow | The message reached the intended players |
| Teleport, spawn items, or use in-game tools | A compatible admin mod | The mod and dependencies match the server build |
A server owner password, the password players use to join, and an RCon password are separate credentials. Giving someone one does not necessarily grant the tools they need, and sharing an owner secret just to let them kick a player gives them more access than the task requires. If you are still deciding where to run the community, compare what to check in a DayZ host before choosing a panel.
Use the Players tab for everyday moderation#
For a group that wants routine moderation in one place, we recommend Game Hosting for DayZ PC/Steam. Its current DayZ panel can show the live player list, kick a player, add or remove bans, review the combined ban list, manage the permitted-player list, and send an announcement. That covers common housekeeping without making every moderator connect an external RCon client.
The Players page is useful only while the server is running and answering. If the list is empty or stale, check the server status and refresh before acting; do not mistake a missing response for proof that nobody is online. For a DayZ permitted-list entry, the panel asks for the player’s 17-digit SteamID64 from their Steam profile; the online table can show a separate BattlEye ID. A display name can change, so confirm which identifier the action needs. See the DayZ whitelist setup and ID guide before enabling the restriction.
The panel’s permitted list is an access-control list, not a game-wide friends list. Before enabling it, confirm that every intended player is included and that one trusted owner can still reach the server to correct mistakes. Keep bans and permitted players separate: a whitelist says who may enter, while a ban records who must not.
This product serves the DayZ PC build on Steam. It does not host Xbox, PlayStation, or the Microsoft Store/Game Pass PC build, so it cannot bridge an incompatible platform. For a step-by-step overview of configuration fields, see DayZ server settings by goal.
Use BattlEye RCon for remote server actions#
BattlEye RCon is a way to administer a BattlEye-enabled server from an RCon client or an integrated host panel. Bohemia’s DayZ guide places BEServer_x64.cfg beside BEServer_x64.dll; the folder can be changed with the -bePath and -profiles startup parameters. The guide documents RConPassword and RestrictRCon, but it does not publish a universal numeric RCon port or default.
Do not copy a port number from a guide for another game or provider. Use the endpoint assigned to your server by its host, and ask that host if the panel does not show it. If you manage your own machine, check the actual BattlEye configuration and firewall before connecting. Exposing a remote administration port to the whole internet makes a password mistake much more expensive.
The general BattlEye documentation describes RCon operations such as listing players, kicking a player, and sending a message. That reference spans multiple BattlEye games; confirm the exact command and syntax supported by your DayZ server and RCon client. Game Hosting’s DayZ console suggests players, kick, bans, and say -1 message actions, but a panel suggestion is not proof that every third-party setup accepts the same syntax.
Treat a failed RCon connection as a configuration problem to inspect, not a reason to guess another port or weaken restrictions. Check that the server is running, the configured RCon password matches, the host has exposed the assigned endpoint, and the chosen tool speaks BattlEye RCon.
Keep passwords and access lists separate#
The server configuration file and access lists handle different kinds of access. In serverDZ.cfg, password is for players joining, while passwordAdmin is the server-administrator password. Bohemia’s guide also documents enableWhitelist and the related player-list files. Read the current guide before changing a setting, because the file—not a generic panel screenshot—defines what the server is configured to use.
| Setting or file | Purpose |
|---|---|
password |
Optional password for joining the server |
passwordAdmin |
Server-administrator password |
enableWhitelist |
Turns the configured whitelist behavior on or off |
whitelist.txt |
Player IDs allowed by the whitelist |
ban.txt |
DayZ player IDs recorded as banned |
priority.txt |
Priority-queue IDs where the server setup supports that feature |
If you edit a file directly, first confirm which server and map folder you opened, save a copy of the original, and stop or restart the server only as its host documentation directs. Keep credentials out of screenshots, chat, and shared notes. After saving, check the file itself and then verify the access behavior with a test account before telling the whole group the rule changed.
The panel and file can show different views while the server is stopped or before its next read. If the visible player or ban state does not match the file, inspect the active server’s path and refresh its status instead of editing a second copy. The detailed server-settings guide explains how to identify the active config and mission files.
Add a compatible admin mod only for extra powers#
RCon and access lists handle routine moderation, but they do not provide every in-game tool a community may want. Teleporting, spawning items, and changing a player’s state usually require an admin mod. A mod is a third-party project with its own author, dependencies, update schedule, and compatibility status; it is not a built-in DayZ feature.
For example, the Community Online Tools Workshop page identifies its authors and lists Community Framework as a requirement. Its current page also displays a compatibility warning, so a recent update date alone is not enough to call it compatible with the stable DayZ build. Check the Workshop page and the mod author’s current instructions before you put it on a server your group depends on.
When you do choose a mod, install its required dependencies in the order the author documents, keep the server and players on matching versions, and make a recoverable backup before changing the mod list. Do not remove a mod that has saved items or objects from a live world without first checking what data it owns. Our DayZ server mods installation guide covers the general server-side workflow; it does not promise that a particular mod works with every game build.
Choose a starter setup for your group#
A small private group often needs less than a public community. Start with the least powerful setup that covers the jobs someone will actually perform, then add tools only when there is a reason.
| Server situation | Practical starting point |
|---|---|
| Friends who need occasional moderation | A trusted owner, a join password or whitelist, and the host’s player controls |
| A group with rotating moderators | Named panel permissions or a restricted RCon account; keep billing and file access with the owner |
| Public PvE or roleplay community | A written rule set, a consistent ban/appeal process, and a compatible admin mod only for powers the team needs |
| Admins who are rarely online together | A documented handoff: who can change access, where bans are recorded, and how to contact the owner |
Before granting access, decide who may kick, ban, edit files, restart the server, and install mods. Those are separate jobs. An assistant who only handles player conduct may not need file access or permission to change the map. Keep a short record of bans and their reasons so the next moderator can tell a current decision from an old dispute.
Do not promise a particular mod, player limit, or response outcome until you have checked the current server and plan.
Treat undocumented chat commands as unverified#
Search results often repeat #login, #kick, #lock, or #shutdown as if they were one universal DayZ command set. Bohemia’s current DayZ server guide does not provide that list. A 2016 Bohemia Feedback Tracker item says the #exec commands were intentionally disabled and points administrators toward RCon for player actions. That old report is limited to #exec; it does not establish what every other chat command does on every current setup.
So this guide does not tell you to type a disputed command into chat. If your provider or admin mod documents a specific command for your exact build, test it on a disposable server with a second account before relying on it for moderation. Keep an owner-controlled way back into the server, and never test a lock or ban on the only account you can use to administer it.
The safest answer to “what are all the DayZ admin commands?” is to name the layer first. Use the host’s verified controls for routine jobs, BattlEye RCon for the functions your server and tool document, configuration files for access rules, and a compatible mod for powers beyond those tools. If none of those sources documents a command, do not borrow it from an Arma guide and hope the chat window agrees.
Quick answers
What are all the admin commands in DayZ?
There is no current Bohemia list of general in-game chat commands in its DayZ server guide. Use documented BattlEye RCon, your host panel, server access files, or a compatible admin mod for the job.
How do I access admin tools in DayZ on PC?
Use the tools your community server supports: BattlEye RCon, its host panel, access-control files, or a compatible admin mod. These instructions cover PC and Steam.
Can I use
Bohemia’s current DayZ configuration guide documents the passwordAdmin setting but does not give a #login procedure. Do not rely on an untested command list.
How do I ban someone from my DayZ server?
Use a ban control provided by the server panel or your verified BattlEye RCon setup, then check the server’s ban list before the next session.