DayZ RCon Commands

BattlEye RCon commands are short and literal. You send them over the RCon session. The server applies them or it does not. CFTools Cloud wraps the ones you use nightly in buttons and keeps a log. The underlying words are still these. Knowing them matters when a button is the wrong button and you need to say what you meant.

players lists who BattlEye sees, with ids. kick removes a player from this session. ban is the stick that is supposed to survive the reconnect. Bans have a reason and a duration if you use the form that includes them. Write the reason as if a stranger will read it later, because a stranger on your staff will. say sends a global message. Use it before a restart. A restart with no say is how you teach regulars to distrust you. The restart guide is the schedule. The command is the announcement.

There are load and lock commands for the mission that differ by build and by how brave you are. Do not paste a block of unverified commands from a 2019 forum into a live Saturday slot. Run the one you need on a test server, or read the effect in Cloud's log after a single action. A command that reloads the mission is a wipe of the current session even when it is not a wipe of persistence. Say so.

These commands do not edit loot. They do not change the map. They do not install a Workshop mod. Admins who want RCon to be a config editor are thinking of a different job. Loot is types.xml. Mods are the startup line and the host, which is CFTools Architect if that is where the files live. RCon can restart the process after those files change. It cannot apply the files.

Whitelist and reserved slots are adjacent and easy to confuse with bans. A ban says this identity should not play. A whitelist says only these identities should play. A reserved slot says these identities can still connect when the server is full. Cloud is where those lists should live if you do not want three text files and no audit. The ban and whitelist guide separates them. The priority queue page is the reserved-slot half.

If RestrictRCon is 1, kicks and bans from an outside IP will not work and the command will look like it was sent. Check the cfg before you blame the tool. The BattlEye page is that check. If the command works in the local BattlEye window and not from Cloud, the route or the password is wrong. If it works from nowhere, the server is not running the cfg you edited.

Keep a short personal list of the commands you trust. Add to it when you have used one on purpose. A moderator with the whole internet's command dump and no judgment is a liability Cloud's permissions can limit. Give people the buttons they need. Do not give every friend the raw password because the button list felt slow to set up.

A short set you will actually use

Keep the live vocabulary smaller than the internet's list. players before you act, so the id is from this session and not from a screenshot in a ticket. kick with a reason you would repeat in an appeal. ban with a duration that matches a written rule, not a mood. say with a minute count before any restart. Those four, logged, run a community. Everything else is a tool you test on a quiet experimental instance or on a passworded side server before it touches the population on the main roster.

Load and shutdown commands deserve a rehearsal because they kick every player. Run one in the afternoon with a say that names the minute. Confirm the process comes back, the map token is unchanged, and the modded or vanilla flag still matches the hostname. A command that "reloads the mission" can look like a tidy admin button and behave like a wipe of the current life even when persistence files remain. If you did not mean to empty hands, do not discover the distinction at peak. Write the effect next to the command in your own notes. Cloud's button labels are only as good as the last time you watched them.

Do not invent syntax. BattlEye is picky, and a mistyped ban is worse than no ban because you think the player is gone. Copy the form from a command you already watched succeed. When a moderator asks for "the command that deletes a base," tell them the truth: bases are persistence files, not an RCon verb. Send them to the host, or to yourself, on purpose, with the server stopped if the edit is dangerous. RCon can restart afterward. It should not be the editor.

Global say is also a tone problem. A wall of warnings every ten minutes trains people to ignore the one that precedes a restart. Use it for restarts, for a wipe that is about to happen, and for a rare emergency. Put the rules in the hostname and in Discord. The community servers that stay full are not the ones spamming the console. They are the ones whose bans stick and whose restart clock is boring. Boring is the goal. If you need a new command every week, you are managing a crisis, not a server, and the open list will show the population leaving even if you never read it.