Serverdatei-Wissensbasis

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

Keep the mission template aligned with the active map folder under mpmissions.

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

JSON syntax must stay valid. Use the Validator before saving large edits.

Defines loot classes and central economy values: how many items can exist, where they spawn, and how they respawn.

Very high nominal values can hurt performance and flood the map.

Controls attachments and cargo that can spawn inside or on complex items, weapons, clothing and containers.

Class names must exist in game/mod config or they will not spawn correctly.

Defines dynamic event behavior such as vehicle spawns, infected groups, animals, wrecks and other event-driven objects.

Event names must match matching spawn files such as cfgeventspawns.xml.

Coordinates for dynamic events. This is where many event spawn points are placed on the map.

Bad coordinates can place events under terrain, in water, or outside the playable area.

Fresh spawn and player spawn point definitions for the mission.

Test spawn changes in-game; invalid placement can trap new players.

Underground trigger zones used by bunker or underground areas to change environment behavior.

Only useful on maps or custom areas that support underground trigger behavior.

Static toxic or effect zones. Used for contaminated areas and custom hazard placement.

Large effect zones can make areas unplayable and may affect client performance.

Global central economy constants. Controls high-level behavior for cleanup, spawn limits and economy timing.

Small changes can have server-wide effects; document values before experimenting.

Turns central economy systems on or off, including dynamic and static economy behavior.

Disabling core economy sections can make loot, infected or vehicles disappear.

Registers economy XML files and mod economy folders so the mission can load additional loot definitions.

If a mod loot file is not registered here, its types may not be loaded by the economy.

Mission startup script. Commonly customized for starter gear, player initialization and mission-specific behavior.

This is script code. A syntax error can stop the mission from starting.

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

Do not delete current logs while diagnosing startup or mod loading failures.

Server-side public keys for signed mods. Clients need matching mod signatures to join.

Missing keys usually cause client join/signature errors.

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

Preset names are references. Renaming one preset without updating every caller can silently break random spawning.

Weather controller for clouds, fog, rain, wind, overcast transitions and storm behavior.

Extreme fog, rain or wind values can heavily change gameplay visibility and travel difficulty.

Automated server messages shown to players, often used for restart warnings, rules and Discord reminders.

Do not rely only on messages for restarts; pair them with the launcher's restart countdown or RCon workflow.

Defines the valid names for categories, usages, values and tags used by types.xml and economy placement.

Adding a category here does not spawn items by itself; types.xml and map group data must also use it.

Loot proxy definitions for buildings and map objects. It tells the economy what categories and loot points a building can contain.

This file is sensitive. Bad local positions or category changes can make loot float, clip or stop spawning in buildings.

World placement of loot groups/buildings. It links building classnames to concrete map coordinates.

Normally generated from the map. Manual edits are risky unless you know the exact world coordinates and object classnames.

List of objects ignored by central economy cleanup or persistence processing.

Putting too many persistent objects on ignore can leave junk on the server and increase storage size.

Environment configuration used by some missions for ambient behavior, environment effects and world tuning.

Availability and supported keys can vary by map and mission template.

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

Large counts or overlapping high-density territories can affect server FPS.

Runtime persistence database for placed items, bases, vehicles, players and economy state.

Do not hand-edit binary persistence files. Back them up before wipes, restores or map changes.

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

Keep RCon password private and open only the needed firewall port.

Mod metadata and class definitions. These files explain what classnames, weapons, items, vehicles or scripts a mod adds.

Do not edit packed Workshop mod PBOs directly unless you are maintaining your own server-side override mod.

Defines grouped spawn compositions for dynamic events. Used when one event should spawn several objects together as a layout.

Group offsets are relative to the event center. A valid group can still spawn badly if the center point is on a slope or inside geometry.

Vehicle spawning is split across multiple files. events.xml controls population, cfgeventspawns.xml controls coordinates, and cfgspawnabletypes.xml controls parts/cargo.

Raising vehicle counts without enough valid spawn points can cause repeated failed spawn attempts or uneven distribution.

Explains how loot classification works. category describes item type, usage describes allowed places, and value often represents loot tier.

If an item has a usage/value combination that no map group supports, it may appear to be configured correctly but never spawn.

Count flags decide what existing items are counted toward nominal/min limits. These flags strongly affect rare loot availability.

For rare weapons, enabling player/cargo/hoarder counting can make new spawns much rarer after players stash items.

A wipe resets stored world state. Used after major economy changes, map changes, broken vehicle state or corrupted persistence.

Always stop the server and make a backup before deleting persistence. Editing economy XML alone does not guarantee existing persisted items are removed.

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

Read the newest RPT after a clean restart. Old RPT files often describe already-fixed errors.

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

Script stack traces usually point to the mod or mission script file that failed; do not fix them by randomly changing XML values.

Controls which mods the server loads and whether clients must load them too.

Putting a server-only admin mod in -mod can force every client to download it. Putting a client-required content mod in -serverMod can make classnames missing for players.

Signature files prove that client PBOs match server-accepted keys. Public modded servers usually depend on this.

If verifySignatures is enabled and a key is missing, players can see signature mismatch or kicked from server errors.

The mission template in the configured serverDZ.cfg selects which mission folder the server loads.

If the template points to a missing or wrong mission folder, the server can start incorrectly or fail mission initialization.

Optional JSON object spawner files can place custom map objects, bases, trader props or event objects through cfggameplay.json.

Classnames must exist on both server and client when they are visible objects from mods.

Spawn bubbles define areas where new players can spawn, often grouped by coastal, inland or custom spawn logic.

A large radius can place players in unsafe terrain. A tiny radius can cause repeated spawn validation failures.

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

High smax values across many nearby zones are a common source of poor server FPS.

A quick map of how central economy files depend on each other.

When a change does not appear in-game, check whether persistence is still holding old state before assuming the XML is ignored.

Many DayZ XML files use comments to keep disabled examples or temporarily remove entries from loading.

Broken comment nesting can invalidate the whole XML file. XML comments cannot be nested.

Common JSON rules that matter when editing DayZ mission configuration.

One trailing comma can stop the entire JSON file from loading. Validate before restart.

Classnames used in economy files must exist in vanilla game data or loaded mods.

A typo in a classname usually fails silently in the economy or appears as an unknown entity in logs.

AI agent configuration for animals and infected. It defines AI families, spawn groups and behavior references used by territory files.

AI classnames must exist in the loaded game or mod config. Invalid agent entries can reduce or break AI spawns.

Explains how cfgspawnabletypes.xml uses preset names from cfgrandompresets.xml to avoid repeating large cargo or attachment lists.

Preset names are plain strings. A spelling mismatch does not auto-correct and can leave items spawning empty.

Prototype data for loot clusters when a map uses clustered economy placement. It groups local loot points into reusable cluster definitions.

Not every map uses this file. If present, treat it like mapgroupproto.xml: bad local points can break loot placement.

World positions for cluster prototypes. It places reusable loot clusters at concrete map coordinates.

This is usually generated with map tooling. Manual edits need accurate world coordinates.

Custom override or extension file for building loot group prototypes when a mission/map supports user economy additions.

Use this for additions when supported instead of editing generated base map files, but keep structure identical to expected map group XML.

Custom world placement file for additional loot groups or custom buildings when supported by the mission.

The referenced group must exist in mapgroupproto.xml or mapgroupproto_user.xml.

Temporary server startup workflow for generating a fresh mapgrouppos file from placed proxy data. Add the export command to mission init, start the server, wait for generation, then remove the command before normal play.

While the export command remains in init.c, normal loot spawning is blocked. Do not leave it enabled on a live server.

Workflow for custom mapped areas made in DayZ Editor and loaded on a server through DayZ Editor Loader. DayZ Editor is used offline to build and export edits; Editor Loader reads the exported edit files on server start.

Keep DayZ Editor as an offline authoring tool. For live servers, load Editor Loader server-side and place the exported .dze files under the active mission's EditorFiles folder.

Optional custom economy files used to keep modded or server-specific loot separate from vanilla types.xml.

A custom types file must be registered or included by the economy system. Otherwise the XML can be valid but unused.

Optional custom dynamic event definitions for server-added vehicles, objects, AI groups or map events.

Event names should be unique. Duplicate names across files make troubleshooting difficult.

Optional override-style global economy constants when a server keeps custom values outside vanilla globals.xml.

If both vanilla and custom global files define the same variable, confirm which one the mission actually loads last.

Main infected territory placement file. Defines where infected can appear and how dense each zone is.

Dense infected zones near player hubs can create CPU load and heavy combat pressure.

Animal territory placement. Controls where wildlife can spawn and which animal families are used.

Predator territories with high counts can make routes much harder and can affect performance.

Wolf-specific territory file on missions that separate predator zones from generic animal territories.

Wolves are expensive and dangerous compared with passive animals. Avoid overlapping many wolf zones.

Bear-specific territory file on missions that split bear zones from general animal territories.

Small radius with high bear count can create unfair spawn pressure and server load.

Detailed explanation of ce folder registration. This controls which extra economy folders and XML files are loaded.

If mod loot exists but never spawns, check this file before changing types.xml values.

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

Script errors can prevent mission startup. Keep backups before editing .c files.

Stores player character persistence for the selected mission instance.

Never edit this database by hand. Stop the server before backup, restore or deletion.

Stores persisted world objects, bases, containers and economy state chunks.

Deleting only part of storage can create inconsistent state. Prefer launcher backups before manual wipes.

Backup strategy for mission persistence before edits, wipes, map migration or economy experiments.

Backups taken while the server is running can miss recent writes or capture inconsistent persistence.

Core central economy folder. Contains most files that control loot, events, globals, messages and economy switches.

Most db changes require a server restart. Some population changes may also need persistence cleanup to become obvious.

Environment and territory folder. Usually contains AI territory XML for infected and animals.

Territory changes are gameplay and performance changes. Test with server FPS monitoring.

Many servers and mods add custom folders under the mission for extra economy files, trader files, object spawners or mod configs.

A file being inside mpmissions does not guarantee it is loaded. Find the reference that includes it.

High-level order of how mission files become active: server config selects the mission, scripts initialize it, and economy files load registered data.

When debugging, confirm the selected mission folder first. Editing the wrong mission folder is a common mistake.

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

Do not fix loot by only raising nominal. First confirm classname, usage/value, map group support and persistence state.

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

If the event has no valid spawn positions, increasing nominal will not help.

How to make modded items actually spawn: load the mod, register or merge its economy files, and ensure clients can join.

Copying a mod types.xml into the mission is not enough if the mod itself is not loaded.

Explains when a normal restart is enough and when persistence cleanup is needed for economy changes to be visible.

A wipe is destructive. Use launcher backup before deleting any storage_* content.

Practical meaning of common weather values for admins tuning atmosphere and visibility.

Weather values can be valid XML but still create bad gameplay if fog/rain stays near maximum for too long.

Knowledge for building automated restart warnings and recurring server messages.

Mission messages are not the same as an actual restart scheduler. They only notify players.

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

If a modded object is visible to clients, the client must load the mod too.

Explains coordinate fields used by mission placement files.

Some JSON formats use [x, y, z], while some tools show [x, z, y]. Always confirm with the target file format.

Controls how spawn areas avoid invalid terrain, water, steep slopes or blocked positions.

If spawn bubbles are too restrictive, players may repeatedly fail to spawn or appear in unintended fallback areas.

Practical meaning of static effect area settings for toxic zones and custom hazards.

Large vertical or horizontal radii can affect players inside buildings or underground areas unexpectedly.

How underground trigger settings affect bunkers, caves or custom underground spaces.

Only tune this for maps that actually use underground systems. Unsupported fields may be ignored.

How cleanup-related values decide when bodies, ruined items, dropped loot and event objects disappear.

Very long cleanup values can leave too many objects in the world and reduce performance.

Controls how complete or broken vehicles are when they spawn.

If essential parts have very low chance, vehicles may spawn but be unusable most of the time.

Explains spacing controls that prevent events from spawning too close to players, other events or unsafe positions.

Huge spacing values can make an event almost never find a valid location.

How server-managed mod economy folders are loaded without merging every mod entry into vanilla XML.

Folder organization is useful, but every referenced file still needs valid XML and valid classnames.

Path and filename rules that prevent hard-to-see mission load mistakes.

Windows is forgiving about case, but tools, logs and server scripts may still expose path/name mismatches.

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

The fastest rollback is a clean backup made while the server is stopped.

Complete multi-file workflow for adding or tuning car spawns through the central economy.

Cars are not controlled by one file. If the event exists but has no matching spawn points or the child classname is wrong, no car will appear.

Adds modded vehicles correctly, including mod loading, keys, economy event setup, spawn positions and parts.

A modded car can fail for three different reasons: mod not loaded, classname wrong, or economy/spawn files incomplete.

Controls whether spawned vehicles are nearly complete, damaged, missing parts, or stocked with cargo.

Low essential-part chance makes vehicles spawn but feel broken. Tune battery, radiator, spark plug and wheels deliberately.

Multi-file workflow for changing where infected spawn, how many appear, and which infected families are used.

Raising territory counts and global caps together can quickly hurt server performance.

Explains how to change loot carried by infected or spawned on infected-related objects, depending on mission/mod support.

Zombie loot support can vary by classname and mod. If cargo is ignored, verify the infected classname supports spawnable cargo.

General workflow for creating any new dynamic event: wreck, custom object, AI group, vehicle, crate, animal or contaminated event.

Event name consistency is critical. events.xml and cfgeventspawns.xml must refer to the same event name.

Adds a new tier, usage or category and connects it to items and map locations.

Adding Tier5 to items does nothing unless map groups also allow Tier5 or the matching value/usage.

Complete path for making a modded item spawn naturally in the world.

If the classname is valid but usage/value has no map support, the item can still fail to appear.

Creates a dynamic loot crate, supply box or custom container event with configured cargo.

A crate event can spawn an empty container if cfgspawnabletypes.xml is missing or cargo chances are too low.

Changes animal placement, predator pressure and broad animal population limits.

Predators with high smax and small radii can make an area unfair and expensive for the server.

Creates or tunes a static contaminated area and connects it to gameplay rewards if needed.

Static toxic zones need gameplay testing. Radius and height can affect buildings or underground areas unexpectedly.

Places custom map objects, decorations, trader props, bases or event props through object spawner JSON.

Objects can be valid but invisible to players if the required client mod is missing.

Changes what new players spawn with and explains how script, classnames and mods interact.

Starter gear can use classnames that are not in types.xml, but they still must exist in loaded game/mod config.

General debugging flow after changing mission XML, JSON, scripts, economy or object spawners.

Always debug from the first error in the newest RPT; later errors may be caused by the first failure.

Complete workflow for switching the active mission map, including template, mission folder, required map mods and persistence.

Do not reuse Chernarus persistence on a different terrain unless you intentionally know how that map handles storage.

Configures start time, day speed and night speed for the server.

Very high acceleration can make lighting and survival feel unstable. Test the full day/night loop after changes.

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

Exact file names can vary by admin mod. Search the active mod documentation or mission scripts before assuming one format.

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.

Overly broad BattlEye exceptions weaken security. Back up filters before changing them.

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

Never fix BattlEye kicks by disabling large groups of filters without understanding the logged restriction.

Generic workflow for trader, market or economy mods whose config files live inside the mission folder.

Trader file formats are mod-specific. The launcher knowledge base explains the workflow, but exact keys depend on the installed trader mod.

Generic workflow for mods that add AI patrols, missions, airdrops or custom encounters.

Some AI/mission mods do not use vanilla events.xml; do not force central economy workflow onto a mod with its own scheduler.

Places visible objects for traders, safezones or custom hubs and connects them with mod-specific safezone/trader config.

Visual objects and safezone logic are often separate files. Seeing the trader desk does not mean the safezone/trader logic is active.

Tunes base building rules, required materials and persistence cleanup balance.

Base balance is economy plus gameplay. Changing material spawns without cleanup/lifetime review can cause hoarding or scarcity.

Balances raiding by changing availability of explosives, ammo, tools and base damage rules.

Raid balance changes may take time to show because existing stashes remain in persistence.

Tunes survival difficulty through food loot, animal spawns and cleanup/population settings.

Reducing food loot and animals at the same time can make early survival much harder than intended.

Balances military weapons, ammo and equipment across tiers and military areas.