Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesiTechGuides 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.
Download the vanilla mission files from Bohemia Interactive’s official DayZ-Central-Economy repository. Select the folder that matches your map—dayzOffline.chernarusplus for Chernarus, dayzOffline.enoch for Livonia, or dayzOffline.sakhal for Sakhal/Frostline—then download the complete folder or only the XML file you need. Back up the live mission folder, compare files that contain custom changes, upload the replacement through your host’s web file manager or FTP, restart the server, and inspect the startup/RPT log.
What “default XML files” means in DayZ
DayZ server economy and mission behavior are defined by XML files inside the active mission folder. “Default” means the unmodified files shipped for a particular map, rather than a file copied from another map or a configuration edited for a modded server.
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 →
The official Bohemia Interactive DayZ-Central-Economy repository is the authoritative place to obtain those vanilla files. The repository is organized by map, so the first decision is not which individual XML to download but which mission directory your server actually runs.
Replacing one file can repair a specific system while preserving the rest of a customized server. Downloading the complete map folder gives you a clean vanilla baseline, but copying it over a live mission can remove custom loot tables, event edits, mod registrations, and messages. Choose the smallest replacement that solves the problem.
#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
Choose the correct map directory
| In-game map | Repository directory | Use this directory when |
|---|---|---|
| Chernarus | dayzOffline.chernarusplus |
Your mission is the standard Chernarus offline mission. |
| Livonia | dayzOffline.enoch |
Your server runs Livonia, also known as Enoch. |
| Sakhal/Frostline | dayzOffline.sakhal |
Your server runs the Sakhal map from the Frostline content. |
Do not substitute one map’s XML files for another’s simply because the filenames look identical. Event coordinates, spawn points, category definitions, and available mission files can differ by map. Sakhal also currently lacks its own messages.xml in the repository, so an apparently missing file there is not necessarily an incomplete download.
Where the files live in a DayZ mission
The files belong in the mission directory used by the server, not in the game’s installation directory and not in a mod’s own folder. A Chernarus mission normally contains a db/ directory plus root-level configuration files such as cfgeconomycore.xml, cfgeventgroups.xml, cfgeventspawns.xml, and related files.
On a managed host, the mission directory may be exposed under a provider-specific path. Use the folder that already contains your server’s live db directory and files such as types.xml and globals.xml. If you see more than one mission folder, match the name to the map selected in the server’s configuration panel.
What each default XML file controls
Use the following reference to identify the narrowest file to restore. The path is relative to the mission folder unless stated otherwise.
| File | Primary control | Typical reason to restore it |
|---|---|---|
db/types.xml |
Ordinary item and loot spawning: nominal counts, lifetimes, categories, usage areas, and tier values. | Loot no longer spawns as expected, or a hand-edited item entry is malformed. |
db/globals.xml |
Global Central Economy limits, timers, and population-related settings. | Economy-wide limits or timing values need to return to vanilla. |
db/events.xml |
Dynamic event definitions, including helicopter crashes, vehicles, animals, and other events. | A dynamic event is missing, repeatedly errors, or has an invalid definition. |
db/economy.xml |
Central Economy subsystem switches. | An economy subsystem was disabled or changed unintentionally. |
cfgspawnabletypes.xml |
Attachments, cargo, and spawn-damage rules for entities that appear with contents or attachments. | Vehicles, weapons, containers, or other entities spawn with incorrect contents or damage. |
cfgrandompresets.xml |
Reusable cargo and attachment pools referenced by spawnable entities. | A preset used by spawnable types is missing or invalid. |
cfgeconomycore.xml |
Economy root classes, defaults, logging settings, and custom economy-file registration. | Custom economy files are not registered, or mission-file diagnostics need checking. |
cfglimitsdefinition.xml |
Valid category, usage, value, and tag names consumed by types.xml. |
A types.xml entry uses an invalid label or category. |
cfgeventspawns.xml |
Exact world coordinates used by event definitions. | Events use incorrect locations or their spawn coordinates were edited. |
cfgplayerspawnpoints.xml |
Fresh-player spawn locations and related constraints. | New characters spawn in the wrong areas or no valid points remain. |
messages.xml |
Scheduled in-game messages, including restart warnings. | Server notices are missing or contain invalid schedules. Sakhal currently has no separate repository copy of this file. |
types.xml and ordinary loot
types.xml is the file most administrators mean when they ask for the “default loot XML.” It defines item entries and values such as nominal quantity, minimum quantity, lifetime, category, usage, and tier. Restoring it changes ordinary item spawning; it does not restore dynamic crash sites, vehicle events, or player spawn points.
events.xml and event coordinates
events.xml describes what dynamic events can occur. The coordinates at which those events may appear are held separately in cfgeventspawns.xml. If an event definition is vanilla but its locations were changed, restoring only events.xml will not restore the original positions.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteGlobal economy files
globals.xml contains broad limits and timers, while economy.xml controls Central Economy subsystem switches. A clean types.xml cannot compensate for a disabled or incorrectly limited economy subsystem.
Download the vanilla files
Download a complete map folder
Use the repository’s ZIP download when you want a complete baseline for one map or when several related files may have been edited. After downloading, extract only the map directory you need. Keep its directory structure intact: files under db/ must remain under db/, while root-level files must stay at the mission root.
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.
Download one or a few files
Open the matching map directory and save the individual XML files needed for the repair. This is appropriate when, for example, a custom server has a carefully tuned types.xml but its events.xml is damaged. Preserve the downloaded filename and capitalization; hosts and file tools may treat similarly named files as different objects.
Check that the download matches the server
- Confirm the map directory name before extracting or uploading.
- Check that a file intended for
db/is not accidentally placed at the mission root. - For a full-folder download, verify that the expected root files and
db/directory are present. - Do not assume every map contains identical files; Sakhal’s missing repository
messages.xmlis an example.
Restore the files safely: an exact workflow
- Identify the active mission. In the host’s server settings, note the selected map and the mission folder currently being used. Confirm it by locating the live
db/types.xmlanddb/globals.xml. - Back up the live mission folder. Download or copy the entire folder, including its
db/directory and root XML files, before changing anything. Give the backup a date-based name so you can identify it if a rollback is required. - Decide on the replacement scope. Select one file for a targeted repair, a related group such as the economy files, or the complete map folder for a full vanilla reset. Do not choose a full reset merely because one XML has an error.
- Compare the vanilla copy with the live copy. Review differences in a text editor or comparison tool. Mark mod-specific entries, custom loot, custom events, and registered economy files that must remain. A direct overwrite can remove all of those changes.
- Stop or schedule the server for maintenance. Uploading while the server is writing mission data can leave an incomplete file. Follow the host’s normal stop and start controls, and tell players when the maintenance will occur.
- Upload to the matching mission path. Through the host’s web file manager or FTP, open the active mission folder. Place
types.xml,globals.xml,events.xml, andeconomy.xmlinsidedb/; place files such ascfgspawnabletypes.xml,cfgeconomycore.xml, andmessages.xmlat the mission root. Replace only the files selected in the previous step. - Keep the backup until validation is complete. Do not delete the old files immediately. If the server fails to start or a customization disappears, the backup is your quickest rollback.
- Start the server and inspect its logs. Check the normal startup or RPT log for XML parsing errors, missing-file warnings, and mission-file warnings. The official
cfgeconomycore.xmldefaults includelog_missionfilewarningandsave_types_startup, which provide useful context when diagnosing economy-file problems. - Test the affected system. Check the specific result: loot for
types.xml, event behavior forevents.xml, economy timing or limits forglobals.xml, and new-player locations forcfgplayerspawnpoints.xml. A successful boot alone does not prove that a targeted change produced the intended behavior.
Choose selective replacement or a complete reset
| Replacement scope | What it changes | When it is appropriate | Main risk |
|---|---|---|---|
| One XML file | One configuration area, such as ordinary loot or event definitions. | A known file is corrupt or a single system must return to vanilla. | Related files may still contain incompatible custom edits. |
| A related group of files | Several parts of one system, such as event definitions plus event coordinates. | The problem crosses file boundaries or the files were edited together. | Custom changes in that group are removed unless merged back. |
| Complete map folder | The full vanilla mission baseline for the selected map. | You intentionally want to remove all mission-level customizations and have a verified backup. | Loot, event, spawn, message, and economy customizations can all disappear. |
| Server reinstall | A provider-level reset beyond individual XML files. | A total reset is intended and every other server change can be recreated. | Reinstallation wipes other changes along with the reset. |
A hosting guide summarizes the trade-off plainly: “The fastest way to restore your server to default values would be a reinstallation, but reinstalling wipes every other change you’ve made right along with it.” Treat that as a last resort, not as the normal way to repair types.xml or another single file.
Free tools Windows power users keep installed
One-click scans. No signup required.
Targeted recovery examples
Restore the original loot table
- Download
db/types.xmlfrom the map directory that matches the server. - Compare it with the live file and copy back any intentional mod or custom-item entries you still need.
- Replace only the live
db/types.xml. - Restart and inspect the log for parsing warnings, then allow the economy time to repopulate before judging ordinary loot behavior.
If the log reports an invalid category, usage, value, or tag, inspect cfglimitsdefinition.xml as well. That file defines the names that types.xml is allowed to consume; restoring one without the other may leave a naming mismatch.
Restore dynamic events
Replace db/events.xml for the event definitions. If the event still appears at incorrect locations, compare and restore cfgeventspawns.xml too. Vehicle, animal, and helicopter-crash behavior can involve both the definition and its allowed coordinates.
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
Restore attachments and cargo
Use cfgspawnabletypes.xml for entity attachment, cargo, and spawn-damage rules. Check cfgrandompresets.xml when the file references reusable cargo or attachment pools. Replacing only the preset file will not repair an invalid rule in cfgspawnabletypes.xml, and the reverse is also true.
Recommended Free Tools
Restore player spawn points
Replace cfgplayerspawnpoints.xml when fresh characters spawn incorrectly. This affects new-player entry locations and constraints, not the ordinary item economy.
Validate and troubleshoot after replacement
The server will not start
- Check that the XML is in the correct directory, especially the distinction between mission root and
db/. - Review the startup/RPT log for the first XML parsing error; later warnings may be consequences of that first failure.
- Confirm that the file was fully uploaded rather than truncated by the web file manager or FTP session.
- Restore the backed-up file if the error began immediately after replacement, then compare the downloaded copy again.
The server starts but the system is unchanged
- Verify that you edited the mission selected by the server, not an unused map directory.
- Confirm that the file name and case match the live file exactly.
- Check whether a related file controls the behavior:
cfgeventspawns.xmlfor event locations,cfgrandompresets.xmlfor referenced pools, orcfglimitsdefinition.xmlfor labels used bytypes.xml. - Allow the Central Economy to process the change; a restart does not instantly repopulate every item or event.
Custom content disappeared
This normally indicates that a whole vanilla file replaced a customized one. Restore the backup, then merge the needed custom entries into the vanilla baseline rather than overwriting the file blindly. Keep a change log for each XML so future repairs can distinguish stock content from deliberate edits.
A file is absent from the downloaded map
Check the map name first. The Sakhal directory’s lack of a separate messages.xml is documented, so do not create a copied Chernarus or Livonia file solely to make the folder look identical. Use the files supplied for the selected map and preserve any working live file unless the server documentation specifically requires a replacement.
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
When a reinstall is justified
Use a full reinstall only when the goal is to erase the server’s mission-level changes and you have a complete backup plus a plan to recreate mods, registrations, gameplay settings, custom spawn tables, and messages. If the objective is to repair one economy or event file, selective replacement is safer and preserves unrelated work.
Before choosing a reinstall, list every customization that must survive. If you cannot identify and back up those settings, do not proceed with a destructive reset. A clean vanilla folder is useful as a reference even when you ultimately merge only a few files into the live mission.
Final restoration checklist
- Map confirmed: Chernarus, Livonia, or Sakhal.
- Correct repository directory selected.
- Live mission folder backed up and retained.
- Replacement scope chosen deliberately.
- Vanilla and live files compared for custom entries.
- Files placed in the correct root or
db/directory. - Server restarted through the host’s normal controls.
- Startup/RPT log checked for XML and mission-file warnings.
- Affected loot, event, economy, attachment, or spawn behavior tested.
- Backup kept until the server has remained stable.
The Bottom Line
For a safe default restoration, use the Bohemia Interactive map folder that matches your server, replace only the XMLs involved in the problem, and keep a complete backup before uploading. A full reinstall is appropriate only for an intentional, documented reset.
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.
