iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Prefer not to run the server on your own PC? Godlike.Host offers hosted DayZ servers with free DDoS protection and up to three free backups a day.
The essential DayZ administration stack has three parts: BattlEye RCon for live moderation, configuration and access files for persistent server rules, and an optional server-side admin mod for in-game powers. Vanilla DayZ does not provide chat-based administrator commands, so an administrator who wants teleport, item spawning or freecam must add a compatible mod.
Use RCon for immediate actions such as listing players, kicking, banning and broadcasting. Use serverDZ.cfg, types.xml, whitelist.txt and ban.txt for settings that should survive a restart. Add Community Online Tools (COT) or VPPAdminTools only when you need an in-game control panel. The exact directives and command syntax can vary by server build and management software, so test on a private instance before changing a public server.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →
The three tool categories every DayZ administrator should understand
| Tool or file | Primary job | When you use it | Main dependency or risk |
|---|---|---|---|
| BattlEye RCon | Remote, live moderation | Inspecting online players, kicking, banning and sending messages | Requires a separate RCon port, a strong password and a compatible RCon client or panel |
serverDZ.cfg |
Core server rules and network settings | Changing the name, password, player limit, time and related settings | Most changes require a restart; a malformed file can prevent startup |
types.xml |
Loot economy | Changing item quantities, rarity and spawn locations | Syntax errors or extreme quantities can destabilize the economy |
whitelist.txt and ban.txt |
Access control | Allowing selected Steam accounts or blocking accounts and GUIDs | IDs must be copied exactly and files are normally re-read at restart |
| Community Online Tools or VPPAdminTools | In-game administrator powers | Teleport, spawning, freecam, ESP, god mode, spectating and weather control | Third-party version compatibility, permissions and the risk of excessive power |
These tools have different scopes. RCon does not replace configuration files, and a configuration file cannot provide an in-game teleport menu. Keeping those roles separate makes troubleshooting much easier.
Set up BattlEye RCon safely
RCon settings belong in the BattlEye configuration file, not in serverDZ.cfg. On Windows the file is commonly named BEServer_x64.cfg; on Linux, installations often use the lowercase form beserver_x64.cfg. The file normally contains an RCon password, an RCon port and a restriction directive.
#1 Best Overall
- Use any means necessary to survive a hostile open world for as long as possible.
- explore the authentic open world of chernarus, featuring 230 square kilometres of hand-crafted terrain based on real-life locations.
- become immersed in a tense, emotional experience driven by the emergent interactions of 60 players on a single server, each one fighting for survival.
- experience a wide variety of complex survival mechanics, from hunting and crafting, through to sophisticated injury simulation and transferable diseases.
- survive against environmental dangers, including the infected, dynamic weather, and animal predators
Configure the file
- Stop the DayZ server before editing files. This prevents the process from overwriting your changes.
- Open the BattlEye folder selected by your host or startup script and locate the 64-bit server configuration file.
- Set a long, random RCon password. Do not reuse the game password, operating-system password or a password used by another administrator.
- Choose an RCon port that is not used by the game, Steam query or voice traffic. A commonly suggested pattern is game port plus three—for example, game port
2302and RCon port2305—but verify the actual allocation with your host. - Save the file, start the server and connect with your RCon client using the server address, RCon port and RCon password.
- Run a harmless command such as
playersto confirm that authentication works before testing moderation actions.
If you place the file in a custom location, the launch option -BEpath= can point the server to that BattlEye directory. The -config=serverDZ.cfg launch option selects the main DayZ configuration file; it does not move the RCon configuration by itself.
Understand the restriction setting
Community administrator guidance describes RestrictRCon as a safety switch. One widely circulated interpretation says that a value of 1 blocks actions such as kick, ban and shutdown over RCon, and that the default when the directive is absent is 1. Because this behavior is not consistently documented in the same way across guides and server versions, verify the directive against the documentation for your current DayZ and BattlEye build. If moderation commands authenticate but are refused, inspect this setting before changing passwords or ports.
DayZ RCon commands for everyday moderation
The following commands are the commonly cited BattlEye RCon forms. Some panels add a leading # to commands, while others accept the form shown here. Confirm the syntax in your client and test each command privately.
| Command | Purpose and example |
|---|---|
players |
Lists connected players and the slot or player numbers used by other commands. |
kick <number> [reason] |
Kicks the player in the specified slot. Example: kick 7 Please reconnect after the restart. |
ban <number|guid> <minutes> [reason] |
Bans a player by slot number or BattlEye GUID. A duration of 0 is commonly used for a permanent ban. Example: ban 7 60 Repeated combat logging. |
bans |
Displays the current ban list and the ban numbers associated with entries. |
removeBan <ban#> |
Removes the ban entry identified by its list number. |
loadBans |
Reloads the ban file without a full server restart, when supported by the running BattlEye version. |
say -1 <message> |
Broadcasts a message to everyone. Example: say -1 Restart in five minutes. |
say <number> <message> |
Sends a private message to the specified player number. |
Do not assume that an RCon command called #restart will work. One administration guide lists hash-prefixed commands including #kick, #ban and #restart, while other guidance says RCon has no dependable clean-restart command and recommends a scheduler or BattlEye Extended Controls (BEC) for scheduled restarts. Treat restart syntax as implementation-dependent and test it away from live players.
Use server configuration files for persistent rules
serverDZ.cfg: identity, limits and timing
serverDZ.cfg holds the server name, password, player count, time settings and network-related options. Use it for the rules players see every session rather than trying to repeat those settings through RCon. The launch option -config=serverDZ.cfg tells the server which file to load.
Make one change at a time and keep a dated backup. If the server stops launching after an edit, restore the last known-good file, then reapply changes individually. A restart is normally required for edits to this file to take effect.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #3
- 🎮 Collector's Item: Allows for CO/VS functionality for co-op action (cable included). CO/VS multiplayer technology allows two Pocket Players to be linked together for cooperative gameplay using the included CO/VS cable
- 🎁 Konami Licensed Collectible: Includes arcade version of Contra and Super Contra
- High Resolution: This pocket-sized game features a high-resolution 2.8-inch full-color vertical display.
- Powered by either 4 AA batteries or by any micro USB cable (not included)
- 🎵 Built-in front facing speaker, volume control, and 3.5 mm headphone jack.
types.xml: the loot economy
types.xml controls spawnable items, including their quantities, rarity and permitted locations. It is the correct place to tune the loot economy; RCon cannot permanently alter those definitions. Keep a backup before editing, validate the XML structure, and avoid setting every item to extreme abundance because that changes progression and can increase server load. Changes generally require a restart or the server’s normal economy reload procedure.
Whitelist and bans
To restrict access, set enableWhitelist = 1 in serverDZ.cfg and place one Steam64 ID per line in profiles/whitelist.txt. A whitelist is an allow-list: an account absent from the file will not be admitted while the setting is enabled.
ban.txt can contain a BattlEye GUID or Steam64 ID, with an optional duration and reason. Keep reasons factual and useful to other administrators. Both files are normally read again when the server restarts, so plan a restart after editing unless your management layer explicitly supports a live reload. RCon’s loadBans command can reload bans on versions that implement it, but it does not make whitelist changes live.
Rank #4
- Award winning innovative design that bridges the gap between roleplaying and boardgaming in space by integrating ship to ship and boarding action.
- You and your friends play characters as the crew of a ship laid out in modular format. Your ship is on a hex map. The enemy controls whatever challenges you face. Your continuing characters rise in power as you face tougher and more exciting challenges.
- Age 12+ / 1-6 players / 60-240 minutes playing time
- Second edition, advanced rule book sold seperately
Do not confuse passwordAdmin with RCon
passwordAdmin is documented briefly as the password used to become a server administrator, but community guides disagree about exactly what it unlocks and whether it grants any RCon capability. Keep it separate from the BattlEye RCon password and do not assume that setting one configures the other. Test the behavior on your specific server build before giving the credential to staff.
Some guides also state that verifySignatures = 2 is the only supported value and that it requires mod keys. That claim is not independently confirmed across current documentation, so check the setting against the version and mod-signing requirements of your installation instead of copying it blindly.
Open and document the right ports
DayZ installations commonly use the range 2302–2306 for game, Steam query and voice or Steam traffic, but the exact allocation depends on the host and launch parameters. Open only the ports your server actually uses, and record each purpose in your firewall and hosting panel.
Best Value
- Dress in style on Nasdara, Sakhal, Chernarus or Livonia with our design. Built to survive in the badlands of dayz in any zombie wasteland so take a day off and dress to impress with our low insulation but high cool Z inspired design.
- Compatible with all PC gamers or console players. Game in comfort for dayz. Also a great gift idea for any discerning online survival gamers.
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
- Set the game port explicitly.
- Set the Steam query port explicitly rather than relying on an assumed default.
- Set an RCon port outside the game-port range.
- Allow the RCon port through the host firewall only from trusted administrator addresses when your environment supports source restrictions.
- Never publish the RCon password in a public Discord channel, startup command visible to ordinary users or shared screenshot.
If RCon cannot connect, check the address, port, firewall rule, BattlEye path and password in that order. A server can be fully reachable for players while its RCon port remains closed.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Add in-game administration with a server-side mod
Vanilla DayZ has no built-in in-game chat command system for administrators. Community Online Tools (COT) and VPPAdminTools are commonly used server-side options. Feature sets cited for these tools include teleport, item spawning, freecam, ESP, god mode, spectating and weather control.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Typical launch arrangement
A commonly shown arrangement is:
-mod=@CF;@VPPAdminTools -servermod=@ServerSideOnlyThe exact mod list, order, key files and server/client installation requirements depend on the mod release and hosting environment. Read the selected mod’s current documentation, install matching versions, and test with a non-owner account before exposing the menu to staff. Keep powerful functions permission-gated: teleport and spectate are moderation tools, while god mode and item spawning can compromise the survival economy if granted broadly.
When a mod is worth the dependency
- Choose RCon alone for a lightly moderated server where kicking, banning and announcements are sufficient.
- Add an admin mod when moderators need visual investigation, player teleportation, live weather control or controlled item operations without leaving the game.
- Prefer configuration files for rules that should remain stable even if a mod is removed or updated.
Mod updates can change menus and permissions. Keep a rollback copy of the previous release and remove obsolete client or server files rather than stacking versions.
Practical administration workflows
Handling a disruptive player
- Run
playersand identify the correct slot number; do not rely on a display name alone. - Send a private warning with
say <number> <message>when a warning is appropriate. - Use
kickfor a temporary removal, including a concise reason. - Use
banonly when the evidence and server policy justify it; choose a duration and record the reason. - Check
bansafterward so another administrator can identify the entry and reverse it withremoveBanif necessary.
Preparing a scheduled restart
- Announce the time with
say -1. - Confirm that the scheduler or BEC installation, rather than an untested RCon restart command, owns the restart process.
- Save pending whitelist, ban and configuration edits before the restart.
- After startup, verify that the expected player limit, access rules and RCon connection are active.
Troubleshooting checklist
- Authentication fails: verify that you edited the BattlEye file actually selected by
-BEpath=, used the correct filename capitalization for the operating system and restarted after saving. - RCon connects but kick or ban is refused: inspect
RestrictRConand confirm the command syntax accepted by your client. - Players cannot join after enabling a whitelist: check that each Steam64 ID is on its own line in
profiles/whitelist.txt, then restart. - A ban appears ineffective: confirm that the GUID or Steam64 ID was copied accurately, reload bans if supported, and restart if not.
- The server fails after a configuration edit: restore the last backup, validate punctuation and XML structure, then reapply one change at a time.
- Admin mod features are missing: check matching client/server versions, load order, required keys and whether the account has been assigned the mod’s permission group.
- Scheduled restarts do not run: check the scheduler or BEC logs instead of assuming that an RCon
#restartcommand is portable.
Choosing a reliable DayZ admin stack
For most servers, start with RCon, a backed-up serverDZ.cfg, documented access files and a restart schedule. Add an in-game mod only after you can explain why RCon and configuration files are insufficient. This minimizes third-party dependencies while still giving moderators immediate control.
Documentation quality is uneven: community guides differ on hash-prefixed commands, restart support, RestrictRCon defaults and the behavior of passwordAdmin. Treat those items as version-sensitive. Before opening a public server, reproduce every command and permission on a private instance, record the working syntax, and give each administrator the smallest set of credentials and mod permissions needed for the job.
Recommended Free Tools
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
