Day[Z] Titan Launcher
DayZ knowledge topic

DayZ RCON and BattlEye

A focused RCON and BattlEye view of the current DayZ owner knowledge base.

matches36 sourceserver
36 current knowledge base matches These cards are selected from the existing knowledge base data, with no new technical content added.
Admin workflow / Profiles

Workflow: whitelist, ban and admin control

General admin workflow for controlling who can join and who has admin/RCon access, depending on server setup and mods.

ban.txt whitelist.txt admins.txt profiles
Existing editable values
  • ban.txt banned player identifiers when supported by the server/admin tool.
  • whitelist.txt allowed players when whitelist logic is enabled by server/mod.
  • admins.txt admin identifiers for admin tools or mission scripts when used.
  • BEServer*.cfg RConPassword remote admin password.
Admin workflow / Mission root

Backup before editing mission files

Recommended backup targets before editing configs, economy files, scripts or persistence.

mpmissions\dayzOffline.* config\serverDZ.cfg profiles storage_1
Existing editable values
  • mission folder backup protects XML, JSON and script edits.
  • config\serverDZ.cfg backup protects ports, passwords, template and server identity.
  • storage backup protects players, bases, vehicles and loot state.
  • profiles backup preserves logs and BattlEye/RCon config.
Runtime files / Profiles

profiles folder

Runtime output and admin files: logs, crash clues, BattlEye configuration and server profile data.

profiles *.RPT *.ADM *.log
Existing editable values
  • BEServer*.cfg RCon password and port; the launcher-created default is under instance root `battleye`.
  • *.RPT server runtime log for errors and mod load issues.
  • *.ADM admin log when enabled.
Runtime files / Profiles

profiles folder important files

Describes the most important files and folders inside the server profile directory.

profiles\*.RPT profiles\script_*.log profiles\crash_*.log profiles\*.ADM
Existing editable values
  • *.RPT main DayZ server log. Use for startup, mod, classname and economy errors.
  • script_*.log Enforce script errors and stack traces.
  • crash_*.log crash diagnostic output.
  • *.ADM admin/player activity log when admin logging is enabled.
Troubleshooting / Profiles

Workflow: debug BattlEye kicks

Steps for diagnosing script restriction, remoteexec or createvehicle kicks after installing mods or editing mission scripts.

battleye\*.log profiles\BattlEye\*.log scripts.txt remoteexec.txt
Existing editable values
  • BattlEye log read the exact restriction number and line context.
  • filter file open the matching filter, for example `scripts.txt`.
  • line number restriction usually maps to a filter line.
  • exception add a specific exception for the trusted mod/action.
Admin workflow / Server config

Workflow: ports, firewall and visibility

Connects game port, query behavior and RCon/BattlEye access so players and admin tools can reach the server.

config\serverDZ.cfg battleye\BEServer*.cfg launch arguments Windows Firewall
Existing editable values
  • server port game UDP port from launch/config.
  • steam query port server browser/query visibility depending on launch setup.
  • RConPort BattlEye RCon UDP port.
  • firewall rule allow required UDP ports.
Launcher workflow / Players

Launcher Players and RCon

Use the Players view for live server administration where RCon is configured.

BEServer*.cfg profiles\*.ADM RCon
Existing editable values
  • RCon test verify BattlEye RCon connection.
  • Admin message send a message to players through RCon.
  • Player list inspect connected player data when available.
  • Kick/ban style actions available when backed by RCon/admin support.
RCon and BattlEye / Profiles

BattlEye filters

BattlEye filter files control script, remote execution and object/action restrictions. Launcher-created instances normally use root `battleye` through `-BEpath`; existing servers may use `profiles\BattlEye`.

battleye\scripts.txt profiles\BattlEye\scripts.txt remoteexec.txt createvehicle.txt
Existing editable values
  • scripts.txt filters script commands and script detections.
  • remoteexec.txt filters remote execution calls.
  • createvehicle.txt filters object creation.
  • setpos.txt filters position changes.
RCon and BattlEye / Profiles

BEServer*.cfg

BattlEye server configuration. The launcher-created instance uses root `battleye` through `-BEpath`, while existing servers may keep BattlEye config under `profiles\BattlEye`.

battleye\BEServer_x64.cfg battleye\BEServer.cfg profiles\BattlEye\BEServer*.cfg
Existing editable values
  • RConPassword password used by RCon clients.
  • RConPort UDP port for RCon.
  • RestrictRCon controls RCon access restrictions when supported.
  • MaxPing optional ping limit depending on BattlEye support.
RCon and BattlEye / Instance root

Instance root battleye folder

BattlEye/RCon config may live under instance root `battleye` as well as under `profiles\BattlEye` depending on setup.

battleye battleye\BEServer_x64.cfg battleye\BEServer.cfg
Existing editable values
  • BEServer_x64.cfg preferred 64-bit BattlEye server config.
  • BEServer.cfg fallback BattlEye server config.
  • RConPassword password used by launcher RCon tools.
  • RConPort UDP port for RCon.
Runtime files / Profiles

script, crash and admin logs

Secondary logs for script runtime errors, crashes and admin activity.

profiles\script_*.log profiles\crash_*.log profiles\*.ADM
Existing editable values
  • script_*.log Enforce script errors and stack traces.
  • crash_*.log crash details useful when the server exits unexpectedly.
  • *.ADM admin/player action log when admin logging is enabled.
  • server_console.log console output when captured by a wrapper or launcher.
Persistence / Profiles

Mod saves inside profiles

Explains why a wipe may need profile cleanup too: many mods store their own databases or state outside `storage_1`.

profiles\* profiles\*.db profiles\*.json profiles\*.xml
Existing editable values
  • mod database trader, garage, banking, groups, territories or AI mission mods can save `.db`, `.json`, `.xml`, `.bin` or `.txt` files.
  • config-like files files that define settings should usually be kept during wipe.
  • state-like files files that store players, vehicles, bases, money, garages, territories or cooldowns may need wiping.
  • logs can usually be archived or cleared but are useful for debugging.
Persistence / Mission storage and profiles

Wipe: what to keep and what to delete

Separates config files from state files so a wipe resets gameplay without destroying server setup.

profiles storage_1 config\serverDZ.cfg DayZ server install\keys
Existing editable values
  • Usually keep `serverDZ.cfg`, mod folders, keys, BattlEye RCon config, launcher settings and intentional mod config files.
  • Usually delete for world wipe `storage_1/data`, vehicle/object economy persistence and map object persistence.
  • Usually delete for player wipe `players.db` or equivalent player persistence.
  • Inspect profiles mod banks, garages, territories, groups and traders may have separate state files.
Runtime files / Profiles

profiles crash dump files

Crash dump and crash log files created when the DayZ server process crashes.

profiles\*.mdmp profiles\crash_*.log
Existing editable values
  • *.mdmp binary crash dump for deeper crash analysis.
  • crash_*.log text crash information when generated.
  • RPT near crash time usually contains the lead-up to the crash.
  • mod update correlation compare crash time with recent mod/config changes.
Runtime files / Profiles

RPT startup log

Main DayZ server runtime log. Use it to diagnose failed startup, missing mods, bad classnames, script errors and economy load problems.

profiles\*.RPT
Existing editable values
  • Cannot open file missing PBO, wrong path or bad mod load order.
  • Addon requires addon missing dependency in `-mod` or `-serverMod`.
  • Unknown entity classname does not exist or mod is not loaded.
  • Script error broken mission script or mod script.
Persistence / Mission storage and profiles

Complete wipe checklist

Clear checklist for performing a real wipe, including DayZ storage and mod-created profile state.

storage_1 storage_* profiles config\serverDZ.cfg
Existing editable values
  • Stop server never wipe while the process is running.
  • Backup back up mission folder, storage and profiles first.
  • storage_1/storage_* delete or archive DayZ world/player/economy persistence according to wipe type.
  • profiles mod state inspect and remove mod-created save files that are not pure config.
Launcher workflow / Files

Launcher Files tab

Use this tab to quickly find and open important server paths without browsing the filesystem manually.

server root mpmissions profiles keys
Existing editable values
  • Server root open the selected server instance directory.
  • MPMissions open mission folder area.
  • Profiles open logs, RPT files and BattlEye/RCon config.
  • Keys open server `.bikey` folder.
Launcher workflow / Maintenance

Launcher Maintenance tab

Use maintenance actions for update and cleanup work that admins often do manually.

DayZ server install @mods keys profiles\logs
Existing editable values
  • Update server update the DayZ Dedicated Server install.
  • Update mods update installed Workshop mods.
  • Repair keys resync `.bikey` files from mods into the DayZ server install `keys` folder.
  • Clear logs clean/archive old logs.
Server config / Instance root

serverDZ.cfg

Main server configuration. Controls public identity, slots, passwords, mission template, time, persistence and several gameplay toggles.

config\serverDZ.cfg serverDZ.cfg
Existing editable values
  • hostname server name in browser.
  • password, passwordAdmin player and admin passwords.
  • maxPlayers player slot limit.
  • template selected mission, for example `dayzOffline.chernarusplus`, `dayzOffline.enoch`, or `dayzOffline.sakhal`.
Runtime files / DayZ server install

DayZ runtime addons folder

The vanilla DayZ Dedicated Server runtime PBO folder. This is different from mod `@ModName\addons` folders.

addons addons\*.pbo
Existing editable values
  • addons/*.pbo core server runtime data.
  • SteamCMD update normally repairs or replaces these files.
  • preflight missing_runtime_addons launcher blocks start if runtime addons are missing.
  • do not mix with mods Workshop mods belong in `@ModName\addons`, not this folder.
Runtime files / DayZ server install

DayZ runtime dta folder

Core DayZ runtime data required by the dedicated server executable.

dta dta\*.pbo
Existing editable values
  • dta/*.pbo required runtime data files.
  • preflight missing_runtime_dta launcher blocks start if these files are missing.
  • SteamCMD validate/update correct way to repair missing or damaged dta files.
Troubleshooting / Mission db

Event not spawning checklist

Diagnostics for vehicles, wrecks, animals, infected or custom objects configured as central economy events.

events.xml cfgeventspawns.xml cfgeventgroups.xml cfgspawnabletypes.xml
Existing editable values
  • active=1 event must be enabled.
  • nominal/min/max event population must allow at least one active event.
  • child type spawned classname must exist.
  • position placement mode must match the available spawn data.
Troubleshooting / Mission db

Loot not spawning checklist

Step-by-step knowledge for diagnosing why an item configured in `types.xml` does not appear in-game.

types.xml mapgroupproto.xml cfglimitsdefinition.xml storage_1
Existing editable values
  • type name must match a real classname from vanilla or loaded mods.
  • nominal > 0 item needs a target population above zero.
  • lifetime > 0 item must live long enough to be found.
  • category/usage/value must match valid names and supported map groups.
Troubleshooting / Mission custom files

Object spawner troubleshooting

Common reasons custom placed objects do not appear after adding object spawner JSON files.

cfggameplay.json objectSpawnersArr *.json
Existing editable values
  • objectSpawnersArr file path must be listed in `cfggameplay.json`.
  • JSON filename must match the path exactly.
  • name object classname must exist on server and client.
  • pos coordinate must be inside the playable map.
Troubleshooting / Profiles

Workflow: fix unknown classname errors

Debugs errors where the server cannot find a classname used by loot, events, starter gear or object spawners.

*.RPT types.xml events.xml cfgspawnabletypes.xml
Existing editable values
  • RPT unknown entity identifies the missing classname.
  • -mod verify the mod defining the class is loaded.
  • load order dependencies must load before dependent mods.
  • spelling classname is case-sensitive in practice for config lookup.
Troubleshooting / Mission files

Workflow: fix XML parse errors

Debugs broken XML that prevents mission/economy files from loading.

*.xml *.RPT
Existing editable values
  • line/column use RPT or validator location.
  • unclosed tag every opening tag needs a matching closing tag.
  • bad attribute quotes XML attributes need quoted values.
  • nested comments XML comments cannot be nested.
Mods / Launch arguments

Client mod vs server-side mod

Explains what decides whether a mod must be loaded by players or only by the server.

-mod= -serverMod= @ModName\addons
Existing editable values
  • Client mod anything that adds visible assets, items, vehicles, weapons, clothing, sounds, UI or client scripts. Put in `-mod`.
  • Server-side mod admin tools, logging, economy helpers or server-only logic that clients do not need. Put in `-serverMod` when supported.
  • Shared scripts/assets if clients interact with or see the content, it is usually a client mod.
  • Classnames in loot/events if the classname comes from a modded item/vehicle visible to players, clients need that mod.
Launcher workflow / Configuration

Launcher Configuration tab

Use this tab for normal server identity and launch configuration without manually editing `serverDZ.cfg`.

config\serverDZ.cfg server profile state
Existing editable values
  • hostname server name shown to players.
  • map/template selected mission map and `serverDZ.cfg` mission template.
  • maxPlayers player slot count.
  • password, adminPassword access/admin password fields.
Mission script / Mission scripts

mission script files

Mission script files can define custom player setup, server events, object spawning, admin logic and mod integrations.

init.c *.c
Existing editable values
  • main() startup entry point used by the mission.
  • CreateCustomMission() returns custom mission class when present.
  • MissionServer server mission class for gameplay hooks.
  • StartingEquipSetup starter gear logic.
Launcher workflow / Titan Launcher

Titan Launcher: what it can manage

High-level map of current launcher capabilities so admins know whether a task can be done through the UI or requires manual file work.

Overview Configuration Mods Editor
Existing editable values
  • New Instance create a local DayZ server instance and prepare the mission/config workspace.
  • Start/Stop/Restart/Kill control the selected server process.
  • Configuration edit common `serverDZ.cfg` values and related server settings.
  • Mods search, add, update, purge and sync keys for Steam Workshop mods.
Gameplay / Mission folder

cfggameplay.json

Gameplay feature switches and server-side rules. Commonly used for stamina, base building restrictions, map/navigation settings and player behavior.

mpmissions\dayzOffline.*\cfggameplay.json
Existing editable values
  • WorldsData map and player spawn related world settings.
  • PlayerData stamina, shock, drowning and player stat behavior.
  • BaseBuildingData construction and placement restrictions.
  • UIData player-visible UI feature toggles.
Loot economy / Mission root

cfgrandompresets.xml

Reusable random selection pools. Other economy files can reference presets so one logical group can randomly choose from many items.

mpmissions\dayzOffline.*\cfgrandompresets.xml
Existing editable values
  • cargo preset reusable cargo set for containers, infected or event rewards.
  • attachments preset reusable attachment set for weapons and clothing.
  • chance probability that a preset or child item is selected.
  • name preset identifier referenced by `cfgspawnabletypes.xml` or event children.
AI territories / Mission root

cfgterritories.xml

Animal and infected territory definitions. Territory files decide where AI families can spawn and patrol.

mpmissions\dayzOffline.*\env\*.xml mpmissions\dayzOffline.*\cfgterritories.xml
Existing editable values
  • territory color editor/debug grouping color.
  • zone name logical spawn zone name.
  • smin, smax minimum and maximum AI count in the zone.
  • dmin, dmax despawn or distance behavior depending on territory type.
Launcher instance files / Instance config

config/server-settings.json

Structured launcher-side settings for the selected server instance. It complements generated DayZ config and UI state.

config\server-settings.json
Existing editable values
  • ports game/query/RCon values tracked by the launcher.
  • profile paths selected config and profiles paths.
  • runtime options launcher-specific start and maintenance settings.
  • map/profile state selected map and related normalized values.
Launcher workflow / Configuration

How to change map with the launcher

Launcher-oriented map change workflow that connects UI actions to the underlying DayZ files.

Configuration tab config\serverDZ.cfg mpmissions Mods tab
Existing editable values
  • Mods tab install and enable required custom terrain/map mods first.
  • Configuration tab Map select the target map/template where supported.
  • serverDZ.cfg template verify the saved mission template.
  • Files tab confirm the matching `mpmissions` folder exists.
AI territories / Mission environment

Infected and animal territory XML

Defines where infected and animals can spawn, how many can occupy zones, and which AI families appear there.

env\zombie_territories.xml env\animal_territories.xml
Existing editable values
  • zone name territory identifier.
  • smin, smax minimum and maximum spawned AI count.
  • dmin, dmax distance behavior used by spawn/despawn logic.
  • x, z map position.
Open full knowledge base DayZ server launcher