36 current knowledge base matches
These cards are selected from the existing knowledge base data, with no new technical content added.
Admin workflow / Mission root
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.
Persistence / Mission storage and profiles
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.
Persistence / Mission storage and profiles
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
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.
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.
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.
RCon and BattlEye / Profiles
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
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
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.
Launcher instance files / Instance diagnostics
Launcher-side operational logs and diagnostic storage. Separate from DayZ game logs in `profiles`.
logs
log_storage
diagnostics
backup-restore.log
Existing editable values
logs launcher operation logs for backup, maintenance and runtime actions.
log_storage archived or stored launcher logs.
diagnostics generated diagnostic artifacts when available.
backup-restore.log backup and restore operation details.
Launcher workflow / Titan Launcher
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.
Launcher instance files / Instance config
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
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.
Launcher workflow / Configuration
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.
Launcher workflow / Maintenance
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.
Launcher workflow / Metrics / Events
Use metrics and events to understand whether a config or mod change affected runtime health.
runtime process
event log
profiles\*.RPT
Existing editable values
Metrics CPU, memory, disk and server FPS history for the selected instance.
Measured interval change sampling interval for runtime monitoring.
Events launcher operation log and failures.
RPT link through Files inspect game-side errors when launcher events point to startup issues.
Launcher workflow / Players
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.
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.
Server config / Instance root
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`.
Server config / Server config
Explains the exact chain that decides which map/mission the server starts.
config\serverDZ.cfg
mpmissions
-mod=
storage_*
Existing editable values
serverDZ.cfg template main value that selects the mission folder; launcher instances pass it via `-config=...\config\serverDZ.cfg`.
mpmissions folder name must match the template, for example `dayzOffline.chernarusplus`.
terrain mod custom maps require the terrain mod in `-mod`.
mission files selected folder supplies `init.c`, db XML, env XML and map placement files.
Admin workflow / Profiles
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.
Launcher instance files / Backups
Launcher backup metadata files that list available backups and storage backup archives.
backups\backup-index.json
backup_storage\storage-backup-index.json
storage_backup_*.zip
Existing editable values
backup-index.json index for manual restore-capable backups.
storage-backup-index.json index for periodic or storage-specific backups.
storage_backup_*.zip storage backup archive files.
createdAt/status/path metadata used by the Backups tab.
Launcher instance files / Launch profiles
Stores or records the instance launch profile used by the launcher when building server start arguments.
launch\launch-profile.json
Existing editable values
executable DayZ server executable path when recorded.
arguments generated or stored launch arguments.
profile/config paths paths passed to the DayZ process.
mod arguments generated `-mod` and `-serverMod` sections.
Launcher workflow / Backups
Use backups before high-risk mission edits, wipes, map changes, mod overhauls or economy experiments.
storage_*
server config
mission files
Existing editable values
Create backup capture configured backup sources for the selected server.
Preview restore inspect what a backup would restore.
Restore restore selected backup data.
destination folder configure where backups are written.
Launcher instance files / Instance config
The launcher's per-instance configuration folder. It stores DayZ config plus launcher-managed state for mods and keys.
config
config\serverDZ.cfg
config\server-settings.json
config\modlist.json
Existing editable values
serverDZ.cfg DayZ server config used by the selected instance.
server-settings.json launcher-managed structured settings that complement `serverDZ.cfg`.
modlist.json launcher mod list, order, enabled state and client/server assignment.
key-index.json tracks keys synced by the launcher.
Use this tab to manage Workshop mods and their server-side key workflow.
@WorkshopMod
keys\*.bikey
mod list
Existing editable values
Search Workshop find mods by name or Workshop ID.
Add mod stage/download a mod into the server instance.
client/server toggle choose whether the mod belongs in client-required `-mod` or server-side logic.
move up/down change mod load order.
Persistence / Mission storage
Explains when a normal restart is enough and when persistence cleanup is needed for economy changes to be visible.
db\*.xml
storage_1
Existing editable values
restart reloads XML and scripts.
storage cleanup removes persisted world state that may still hold old items.
full wipe resets players, bases, vehicles and world economy.
world wipe resets world objects while preserving players if handled carefully.
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.
Launcher instance files / SteamCMD
SteamCMD is used by the launcher to install/update DayZ Dedicated Server and Workshop content.
steamcmd.exe
SteamCMD path
Existing editable values
SteamCMD path configured in launcher settings.
anonymous login used for DayZ Dedicated Server where supported.
saved Steam credentials used for Workshop operations that require a Steam account.
update server Maintenance action that uses SteamCMD.
Persistence / Mission storage
Stores persisted world objects, bases, containers and economy state chunks.
storage_1\data
storage_*\data
Existing editable values
data/*.bin persisted object chunks.
delete data folder world/object wipe while players may remain if `players.db` is kept.
restore data folder brings back bases and placed objects from backup.
Persistence / Mission storage
Stores player character persistence for the selected mission instance.
storage_1\players.db
storage_*\players.db
Existing editable values
players.db player position, inventory and character state.
delete players.db player wipe while other world state may remain.
backup players.db preserve characters before world wipe.
Troubleshooting / Profiles
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
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.
Complex workflow / Server config
Complete workflow for switching the active mission map, including template, mission folder, required map mods and persistence.
config\serverDZ.cfg
mpmissions\dayzOffline.*
storage_*
-mod=
Existing editable values
serverDZ.cfg template set the mission folder name that should load; launcher-created instances store it under `config\serverDZ.cfg`.
mpmissions folder ensure the matching mission folder exists.
-mod load required terrain/map mods for custom maps.
storage_* old map persistence should usually not be reused across different maps.
Launcher instance files / Instance config
Tracks `.bikey` files copied by the launcher during key sync so mod signature keys can be managed predictably.
config\key-index.json
keys\*.bikey
DayZ server install\keys\*.bikey
Existing editable values
source mod which mod provided the key.
source key path original `.bikey` location under a mod `keys` folder.
target key path copied key under the `keys` folder next to the DayZ server executable.
sync time when launcher last wrote the key index.
Launcher instance files / Instance config
The launcher's source of truth for installed/enabled mods, mod order and whether each mod is client-required or server-side.
config\modlist.json
Existing editable values
id/workshopId identifies the mod.
name/folder display name and local folder path.
enabled whether the mod is included in launch arguments.
type client/server assignment used to build `-mod` or `-serverMod`.
![Day[Z] Titan Launcher logo](/assets/img/logo2.png?v=1777231699){kind=logo}
