How to increase loot on a DayZ server
Want more food, tools or ammunition on your server? Start with one item in types.xml. This guide uses canned tuna to show how to raise its loot targets through VXPanel without deleting your saved world.
For other changes, jump to infected pockets or modded loot.
On 31 October 2026 we checked the installed mission files in VYKIX Architect. Chernarus set Canteen to nominal=20 and min=10. Nasdara used 55 and 45. Copying the Chernarus pair onto Nasdara would lower its target by 35. Read the starting values in your own mission before applying a “more loot” example. Compare the four map entries.
Find the file for the loot you want to change
Section titled “Find the file for the loot you want to change”- Stop DayZ on Dashboard. Open Configuration → Config, select Refresh and wait for Synced. Note the value of Mission → Template.
- Download the mission files you will edit. For a saved-world backup, check what your backup includes.
- In File Manager, open
mpmissions/<your-template>/db/types.xml. Common mission folders aredayzOffline.chernarusplusfor Chernarus,dayzOffline.enochfor Livonia anddayzOffline.sakhalfor Sakhal. Use the folder selected by your Template.
The example selects Chernarus. Edit your own mission folder.
Raise the item’s loot targets
Section titled “Raise the item’s loot targets”In the active mission’s db/types.xml, find <type name="TunaCan">. TunaCan_Opened is another item. Record the existing nominal and min before editing. For another item, use Bohemia’s vanilla types or the mod’s registered file for its exact class.
Architect, 2 November 2026. The Chernarus entry counts items on the map and allows shelf locations in Town or Office, in Tier 1 or Tier 2. Check those filters if you are looking for food in military buildings.
- Change
nominalfrom20to30andminfrom15to22as example balance choices, not a recommended preset. Keepminno higher thannominal. - Keep the existing location filters and counting flags. They determine where the item may appear and which items count toward the target. The target is not a quota for each building.
- Select XML, choose Validate XML content, then Save Content. Wait for confirmation before starting the server through Dashboard.
To undo the direct edit, stop the server and restore the two values you recorded for TunaCan. For our Chernarus example that was nominal=20 and min=15. Validate, save and restart. Leave world storage in place so players keep their gear and bases. The lower target applies as the economy replenishes.
Register a small override instead of changing stock XML
Increase one item through a types override
Section titled “Increase one item through a types override”An override keeps your changes in a small separate file. Use it instead of editing the same values in stock XML. Under Bohemia’s merge rules, an existing class keeps fields you omit from the override.
- While the server is stopped, open the active mission folder. Use Create Directory to add a folder named
customif it does not exist. - Inside
custom, select New File, name itloot-overrides.xmland enter:
<?xml version="1.0" encoding="UTF-8"?><types> <type name="TunaCan"> <nominal>30</nominal> <min>22</min> </type></types>Switch the loot override editor to XML. Run Validate XML content, then Save Content and wait for the saved-file confirmation.
- In
cfgeconomycore.xml, add inside existing<economycore>before its closing tag:
<ce folder="custom"> <file name="loot-overrides.xml" type="types" /></ce>If a <ce folder="custom"> block already exists, add only the <file> line inside it. Keep its other entries. If another file already overrides TunaCan, edit that definition rather than adding a competing override.
- Validate
cfgeconomycore.xmlas XML, save and wait for confirmation. Start the server.
To undo this separate-file version, stop the server and remove the <file> registration you added for loot-overrides.xml if it contains only this trial. If you added the tuna entry to an override used by other items, restore just that entry. Validate the edited file, save and restart.
This short override works because TunaCan already exists. A new mod item needs its complete definition. If you add usage, tag or value entries, that list replaces the earlier group; flags also need their complete set. Omit these groups when changing only loot targets.
To check downloaded copies locally, run these commands from the mission folder:
[xml](Get-Content -LiteralPath '.\custom\loot-overrides.xml' -Raw) | Out-Null[xml](Get-Content -LiteralPath '.\cfgeconomycore.xml' -Raw) | Out-Null
Diagnose loot that does not spawn
Section titled “Diagnose loot that does not spawn”Look for new loot in areas allowed by the item’s filters. Creating an item with an admin tool checks its classname, but bypasses economy placement. Keep a player connected during this check so the economy does not enter its configured idle mode.
| What you’re seeing | What to change or check |
|---|---|
| Your edit has no effect | Reopen the active file and check its saved values. Look for another registered override of the same class. |
| More loot was requested, but little is visible | Existing stock may still count toward the target. Check counting flags, eligible positions and restock before raising the numbers again. |
| Only mod items are missing | Confirm the mod loads and its complete types file is registered with the correct path and classnames. |
| Loot appears in the wrong places | Check category, usage, tier and tag names against the mission’s cfglimitsdefinition.xml and user definitions. |
| All loot, or both loot and infected, stop after an edit | Open the startup log and resolve its first XML or economy error. Restore the saved configuration if needed; don’t delete persistence. |
| Infected still have empty pockets | Check the class-to-preset link and chance values. Only newly spawned infected use the new cargo rules. |
Open Logs → RPT Log and use Filter to find the startup error. If initialization failed, follow the filename in that first error. Common sources are cfgeconomycore.xml, files under db/ and registered overrides. The loot diagnostics guide explains how to trace them.
The shown Init sequence search is an example. Search your own error or file.
Restock timing and idle-item lifetime
Change loot lifetime and restocking
Section titled “Change loot lifetime and restocking”Make loot replenish sooner
Section titled “Make loot replenish sooner”Raise min to trigger replenishment while more stock remains, or reduce restock to shorten the interval between replacements. Keep nominal unchanged if you want the same target population. For example, keep nominal=20, raise min from 10 to 15 and reduce restock from 600 to 60 seconds. That changes the replacement interval from ten minutes to one; it does not guarantee a free spawn position.
Restock timing applies when stock reaches the low-stock threshold and between individual replacements. If restock is already 0, check counted stock and eligible positions before changing other values.
Check longer lifetimes against balance and load
Section titled “Check longer lifetimes against balance and load”A lifetime of 3600 seconds means one hour. Increasing it lets idle items occupy positions and count toward their targets for longer; it does not raise nominal. Change individual items through an override first. Ruined-item cleanup and flag refresh use separate timers.
More saved objects can add memory/save work. Compare load under similar player activity before economy-wide lifetime increases. The number alone can’t predict cost.
Fill levels and pristine spawns
Separate spawn condition from durability
Section titled “Separate spawn condition from durability”For more magazines, change nominal. For fuller magazines, use supported quantmin and quantmax values; see percentages and the -1 default. For better condition, change damage. These settings affect new spawns. They do not repair saved items or prevent wear.
Make one item spawn pristine
Section titled “Make one item spawn pristine”Stock NVGoggles uses damage 0.0 to 0.32:
The source rule is unchanged. This override requests zero damage for new goggles.
- Stop the server, download the mission files and check for an existing
NVGogglesoverride. - In File Manager, create
custom/item-condition.xmlin the active mission with this content:
<?xml version="1.0" encoding="UTF-8"?><spawnabletypes> <type name="NVGoggles"> <damage min="0.0" max="0.0" /> </type></spawnabletypes>Validate and save the file as XML before opening cfgeconomycore.xml.
- Add this block inside the existing
<economycore>root. If thecustomblock already exists, add only the<file>line:
<ce folder="custom"> <file name="item-condition.xml" type="spawnabletypes" /></ce>- Validate and save
cfgeconomycore.xml, then start the server. Inspect newly spawned goggles before they take damage. Saved goggles retain their existing condition, and this rule does not charge batteries.
Because this override changes only damage, the existing attachments and cargo rules remain. Damage 0.0 means undamaged; 1.0 means zero health. Another override or a script can still change the item’s condition. Check downloaded files locally with:
[xml](Get-Content -LiteralPath './custom/item-condition.xml' -Raw) | Out-Null[xml](Get-Content -LiteralPath './cfgeconomycore.xml' -Raw) | Out-NullFor global condition, LootDamageMin and LootDamageMax in globals keep float type="1" under the supplied definition. Account for per-class rules first.
Change food and gear on infected
Section titled “Change food and gear on infected”Stop the server and download cfgspawnabletypes.xml and cfgrandompresets.xml from the active mission. Infected pockets use cargo presets rather than world-loot targets.
- Find
ZmbF_CitizenANormal_Beigeor your class in spawnabletypes. It points tofoodCity/toolsCity.
Food/tool presets and worn-equipment entries are separate.
- In
cfgrandompresets.xml, findfoodCity. Change its outerchance="0.16"tochance="0.2"to raise the roll from 16% to 20%. Keep the preset name, individual item entries and closing tag.
Edit the outer chance while keeping individual food choices.
- Run Validate XML content in the XML editor. Choose Save Content, wait for the confirmation and start DayZ. Only new infected use changed cargo. Old pockets aren’t refilled.
These Chernarus examples come from Bohemia’s spawnable types and cargo presets. Other infected classes may use different presets. Changing a shared preset affects every class that references it. To change only one class, copy the preset under a new name and point that class to the copy. Preserve its other cargo and attachments because an explicitly defined list replaces the earlier list.
Both the outer preset roll and individual item rolls can leave empty pockets. Remember that 0.5 is 50%, while 0.005 is 0.5%. To add more infected themselves, change infected territories.
Edit categories with the VYKIX economy editor
Section titled “Edit categories with the VYKIX economy editor”The economy editor prepares changes from a mission ZIP in your browser. It does not upload the ZIP or modify your original file.
- Import the mission ZIP. Choose Reset to 1× to clear blueprint overrides, then adjust Global loot base. Keep other populations and events at
1×if you want to change only loot. - Select Preview Changes and compare each file’s old and new values.
- Select Download Edited ZIP, inspect
VYKIX-CHANGES.jsonand apply your chosen files while the server is stopped.
The export contains the supported files that changed, not a complete replacement mission. Preserve your custom and mod registrations. The tool does not import a standalone types file or edit individual items; use the TunaCan example above for a single-item change.
Edit downloaded XML on Windows
Edit one item visually on Windows
Section titled “Edit one item visually on Windows”XML Notepad gives a field tree. Download through File Manager/SFTP and copy the original:
- File > Open the working file.
- Ctrl+F, Use XPath, search
/types/type[@name='TunaCan']under Find controls. - Change matching nominal/min. File > Save As, then View > Compare XML Files… per menu commands.
- While stopped, upload to the active original path and start.
Parse types.xml without uploading it
Section titled “Parse types.xml without uploading it”This read-only parser rejects DTDs/external resource resolution:
$xmlSettings = [System.Xml.XmlReaderSettings]::new()$xmlSettings.DtdProcessing = [System.Xml.DtdProcessing]::Prohibit$xmlSettings.XmlResolver = $null$xmlReader = [System.Xml.XmlReader]::Create( (Resolve-Path -LiteralPath '.\db\types.xml').Path, $xmlSettings)try { while ($xmlReader.Read()) {} }finally { $xmlReader.Dispose() }Silence means successful parse. It doesn’t validate classes or eligible positions.
Register modded loot
Section titled “Register modded loot”Installing a content mod does not necessarily add its items to natural loot. In cfgeconomycore.xml, register the mod’s complete item definitions as types and its attachment or cargo rules as spawnabletypes. Use files matching the installed release. The mod installation guide shows the registration structure. A trader list cannot replace an economy definition.
Mod-specific loot checks
Section titled “Mod-specific loot checks”MuchStuffPack requires MuchFramework. Before importing its loot XML, check that the server can start with the required mods. The author ended support with DayZ 1.26 and prohibits repacking. In our DayZ 1.30.164200.56 test, unpatched MuchFramework failed to compile at m_ElapsedSinceLastUpdate, before the economy could read the loot files. A separate community patch got the pair through startup. We did not test timed furniture behaviour or migrate saved items. Publisher’s notice · Community patch
After applying the corrections below to eight mission XML files, we started the same twelve-mod combination with fresh test storage. The new RPT completed economy initialization at 21:13:43 and contained none of those 204 mod-class rejections or the invalid tag/tier warnings. A fresh DZSA query found all twelve mods. Eight unrelated stock-mission class warnings remained, alongside animation warnings and script diagnostics; this is a verified economy correction, not a claim that every mod feature was exercised.
Mass'sManyItemOverhaul
Mass’sManyItemOverhaul: replace outdated economy definitions
Section titled “Mass’sManyItemOverhaul: replace outdated economy definitions”MMIO 1566911166 is now deprecated: its author has stopped updates and links the separate 1.30 fix, 3826131868. That fix corrects six script paths for food, clothing, weapons and chess items; it does not replace the base assets. Keep CF and the original pack, and load the fix after MMIO. Check this exact combination on a separate world before upgrading an established server.
3826131868, in Architect on 31 October 2026. See the loot-file limitation.
1566911166, in Architect on 31 October 2026. See the loot-file limitation.CF’s first-install wipe requirement still matters on an existing non-CF world. In the package installed on 31 October 2026, open File Manager → @1566911166 → Xmls. The relevant files are types(NOT A REPLACER).xml and cfgspawnabletypes(NOT A REPLACER).c; an old Ce/Old path does not describe this installed package.
The types file contains 426 <type> fragments with no enclosing <types> root. The panel rejects it as a standalone XML document. Either merge the complete type entries into your current types file, or wrap them once in <types>...</types> and save as mission custom/mmio-types.xml. The .c attachment file is XML text, not a script: remove its initial ///PLEASE... instruction line, wrap its five type entries in <spawnabletypes>...</spawnabletypes>, and save as custom/mmio-spawnabletypes.xml.
Register those two complete files inside the existing <economycore>:
<ce folder="custom"> <file name="mmio-types.xml" type="types" /> <file name="mmio-spawnabletypes.xml" type="spawnabletypes" /></ce>If a custom registration already exists, add only the two <file> lines to it. Validate both wrapped XML files and the core before saving. Both wrappers parsed successfully in our source check, with no duplicate names within the supplied types file. Check your existing mission for earlier MMIO definitions before importing them; installing the 1.30 script patch does not require registering the same loot twice.
The same file uses civilian, hunting and military as tags, which stock Chernarus does not define. Tags describe loot positions; building uses belong in <usage>. For this Chernarus example:
| Entries | Replace the invalid tags with |
|---|---|
Mass_GunMittens and its White, Black, Red, Blue, Brown and Grey variants |
<usage name="Village" /> and <usage name="Hunting" /> |
Mass_LunchBox |
<usage name="Village" /> |
Mass_PistolCase, Mass_THICCWeaponCase, Mass_WeaponCase, Mass_JunkBox |
<usage name="Military" /> |
Remove the empty <usage /> and <value /> placeholders in those entries. Keep their other fields. These distribution choices are our example, not new author defaults. Do not add fake tag names to silence the log: they also need matching loot positions to do anything.
The original author confirms that MMIO is deprecated and links the script fix. A comment on the fix page reports a client crash when wearing the cat-ear item; we have not reproduced that player action. Server startup does not establish that every wearable or weapon is safe to use.
MMG military gear
Register MMG gear and attachments
Section titled “Register MMG gear and attachments”MMG 2663169692 supplies 16 complete types files in @2663169692/files/types/ and files/spawnabletypes/mmg_cfgspawnabletypes.xml. Copy the types files into a mission folder such as custom/mmg, register each filename as type="types", then register the attachment file as type="spawnabletypes". Include the NBC/NVG, carbine and patch files as well as the camouflage sets you intend to use. Keep admin gear out of natural loot with both nominal and min at 0; the supplied admin helmet has nominal=0 but min=1, which should be reconciled.
2663169692, in Architect on 31 October 2026. See the loot-file limitation.The installed mmg_types_patches.xml contains two <type name="EXAMPLE"> blocks. Remove both complete placeholder blocks from your mission copy before registering it. Do not import ITEMS ADDED IN LAST UPDATE.xml a second time when its entries already appear in the complete files. Validate every edited file and cfgeconomycore.xml before starting.
Our 1.30 run also rejected three supplied names: MMG_tactical_shirt_dark_woodland, MMG_assault_pack_multicam_tropic and MMG_mmps_nag_multicamblack. Exclude those complete entries from the mission copy. Do not guess a corrected spelling: a similar name is not proof that the installed mod defines that item.
The JPC uses default PlateCarrier pouches, and pouch stacking was removed. Raising vest targets will not make an incompatible attachment fit. These changes are recorded in the package changelog.
Tactical Flava
Tactical Flava: check full files, updates and presets
Section titled “Tactical Flava: check full files, updates and presets”Flava 2646817942 supplies @2646817942/extra files/TacticalFlava_types.xml and TacticalFlava_spawnabletypes.xml. Both installed files are complete XML documents: copy them to your mission’s custom folder and register them as types and spawnabletypes respectively. Our 31 October package check found 329 types and 95 attachment entries, with no duplicate type names within either full file.
2646817942, in Architect on 31 October 2026. See the loot-file limitation.The new content/new_types.xml file contains 207 rootless entries already included in that full types file. Do not register it too. This installed full file does not have the repeated TF_AK74M found in some older external examples.
The bundled README labels cfgrandompresets.xml as a DayZ 1.19 file. Preserve your current mission’s presets. Compare the preset= references in Flava’s attachment file with your existing cfgrandompresets.xml; add only a genuinely missing named preset, inside the existing root. All references resolved against our current Chernarus mission without replacing any vanilla presets.
Recent Workshop comments also report AK and attachment problems. Those are player reports, not a gameplay test by VYKIX. Our evidence establishes the twelve CE rejections and successful server startup with the stated combination.
MunghardsItempack
MunghardsItempack: check the package and retired items
Section titled “MunghardsItempack: check the package and retired items”The original pack, 1734713776, and the Sakhal edition, 3349805878, are alternatives. Install only the edition you intend to use. The Sakhal author removed the simple backpack because it caused startup crashes on that terrain.
When migrating an older setup, update retired names in loot and trader files: Zippo_new became Zippo_mung, and zenitco_pt3_buttstock became zenitco_pt3_buttstock_mung. These changes are recorded in the original pack’s changelog.
1734713776, in Architect on 31 October 2026. See the loot-file limitation.For the original pack, @1734713776/types/types.xml is a complete <types> document containing 151 entries in our installed package. Copy it to mission custom/munghards-types.xml and register that file once as types. It supplements your existing economy; it is not a replacement for the mission’s full db/types.xml. Keep original and Sakhal-edition setup separate.
The original package still includes meleesling_colorbase_mung and meleesling_black_mung. Our 1.30 server rejected both as nonexistent. Remove their complete entries from your mission copy and any matching trader or attachment references.
Install the Sakhal edition
Section titled “Install the Sakhal edition”- Stop the server. In Steam Workshop, install
3349805878as a Client mod. The listing has no separate required Workshop dependencies. - In File Manager, copy
@3349805878/types/types.xmlinto your active Sakhal mission asmunghards-sakhal-types.xml. Preserve the package original and the mission’s vanilladb/types.xml. - Remove the seven complete
<type>...</type>entries listed below from your mission copy. Keep its single<types>...</types>root. - Add this registration inside the existing
<economycore>...</economycore>root in the mission’scfgeconomycore.xml:
<ce folder=""> <file name="munghards-sakhal-types.xml" type="types" /></ce>- Validate both XML files, save, start the server and inspect its fresh RPT. Check DZSA using the query port. Clients need the same Sakhal pack.
| Remove from the Sakhal mission copy | Reason observed on 1.30 |
|---|---|
meleesling_colorbase_mung, meleesling_black_mung |
Classes do not exist |
simplebackpack_blue_mung, simplebackpack_camoblack_mung, simplebackpack_green_mung, simplebackpack_redpink_mung, simplebackpack_redyellow_mung |
Removed backpack classes still appear in the supplied XML |
The supplied file had 151 active entries. After removing these seven, our fresh Sakhal economy initialized with 144 entries and no further Munghards class rejections. The separate jaakari_simple... backpack entries were not rejected; do not remove them just because their names contain “simple.”
Arma Weapon Pack
Arma Weapon Pack: add the weapon and its ammunition
Section titled “Arma Weapon Pack: add the weapon and its ammunition”Remastered Arma Weapon Pack 1793351435 needs separate entries for weapons, magazines and ammunition. The DMR uses A2M14_DMR with A2M14_DMRMAG; the MK17 and MK48 use .308 ammunition. Its optional support for CPB ammunition does not make CPBWeapons a required dependency.
1793351435, in Architect on 31 October 2026. See the loot-file limitation.Open @1793351435/XMLS/. Copy types (NOT A REPLACE).xml and a2_spawnabletypes.xml into the active mission’s custom folder, then register them as types and spawnabletypes. Both have their correct outer XML roots; the installed files contain 61 types and 30 attachment entries. Keep the weapon, magazine and ammunition entries together. Replacing all vanilla types with this small mod file would remove unrelated loot definitions.
On our 31 October DayZ 1.30.164200 test, the economy initialized and DZSA continued to find the server, but CE rejected A2M32 and M32_Magazine as nonexistent types. Remove those two entries from your imported copy and their associated attachment definitions; keep the original package files intact. This verifies startup, not firing or reloading every weapon.
Forward Operator Gear
Forward Operator Gear: update classnames and attachment rules
Section titled “Forward Operator Gear: update classnames and attachment rules”FOG 2931560672 supplies @2931560672/Extras/FOG_Types.xml, FOG_spawnabletypes.xml and ALL_CLASSNAMES.txt. Copy the two XML files into your mission’s custom folder and register them with their respective types and spawnabletypes roles after checking the following issues.
2931560672, in Architect on 31 October 2026. See the loot-file limitation.The installed types file has 1,789 entries and 19 repeated class names. Some repeats disagree: early entries classify clothing as weapons with a Unique filter, while later entries use clothes. For each repeat, retain one complete definition that matches the item and your terrain. Our test copy retains the final supplied definition; do not combine conflicting fields blindly. A zero nominal and min requests no natural loot, even when attachments are correctly registered. Choose a small target for the specific items you want, such as FOG_Bergen_Rucksack_M81, rather than enabling the entire pack indiscriminately.
FOG_Bag_F4Terminator_Black also uses Tier5, which our stock Chernarus limits did not define. For a Chernarus military example, change that entry’s value to <value name="Tier4" />; keep its supplied nominal and min at 0 unless you deliberately want it in natural loot. This fixes the terrain filter without enabling the item. A custom map may define different tiers, so check its active limits before using this example.
SQUAD MSF-C
SQUAD MSF-C: choose stable files and check retired classes
Section titled “SQUAD MSF-C: choose stable files and check retired classes”If you have the old Steam bookmark, item 2064801519 is the authors’ 2021 manual. They label it out of date. In Architect, search for the installable package 1583941197, then use the XML files from that installation and the corrections below. Archived Steam manual
SQUAD 1583941197 includes its setup files in @1583941197/Server Files/Types/. You do not need a Discord download to reach them. The folder contains 14 MSFC...xml types fragments, grouped by clothing, camouflage, patches, flags, weapons, magazines and weapon supports, plus SpawnableTypes.xml with 75 attachment entries.
1583941197, in Architect on 31 October 2026. See the loot-file limitation.- Combine the complete type entries you need inside a single
<types>...</types>root in missioncustom/squad-types.xml. Include magazines and weapon supports when enabling weapons. - Keep only one entry each for
MSFC_PlateCarrier_Vest_ATACFG_Logo,MSFC_OPS_Core_ATACS_FGandMSFC_Facemask_ATACS_FG. The supplied ATACSAU, ATACSFG and SURPAT files repeat these classes. - Wrap
SpawnableTypes.xmlin<spawnabletypes>...</spawnabletypes>and save ascustom/squad-spawnabletypes.xml. - Register the two files as
typesandspawnabletypes, validate and save. If merging directly instead, insert entries before the existing closing root tag, not after it.
Version 2.0 removed SURPAT Desert, so do not restore retired classes from an older list. The package’s classic Trader text is not Expansion Market JSON. Its README also prohibits use on monetized servers; check that restriction before choosing it for such a server.
Our DayZ 1.30.164200 startup reached CE, but the supplied definitions still produced specific failures. Omit MSFC_L96A1 and MSFC_ORSIS_T5000 from loot and traders pending a compatible weapon update: their generated instances logged Weapon.SaveCurrentFSMState: trying to save weapon without FSM. A nominal change cannot repair the weapon script.
CE also rejected these supplied names as nonexistent: MSFC_TacticalBelt_Desert, MSFC_PlateCarrier_Vest_ATACFG_Logo, MSFC_AK12_Punk, and the MSFC_Pouches_Magazine_ variants ATACSAU, ATACSFG, Multicam, Multicam_Black, Multicam_Snow, Multicam_Tropic and SURPAT. Remove those entries from your mission copy and references to them in attachment rules. Preserve the originals so an eventual mod update can be compared. DZSA visibility does not remove these item-level exceptions.
CPBWeapons
CPBWeapons: match ammunition to the weapon
Section titled “CPBWeapons: match ammunition to the weapon”CPBWeapons 1705066179 includes its economy definitions in the installed package. Keep each weapon’s compatible magazines and ammunition together. Armor-piercing or hollow-point ammunition requires support from that particular weapon and magazine; a similar cartridge label is not enough. The author’s ammunition chart is a compatibility reference, not a types file to import.
1705066179, in Architect on 31 October 2026. See the loot-file limitation.Open @1705066179/XML/. The types filename is CBPtypes.xml, with that spelling. It contains a complete <types> root and 195 entries. Copy it into the mission’s custom folder and register it as types. The separate cpb_spawnabletypes.xml contains 44 rootless attachment entries: wrap them in <spawnabletypes>...</spawnabletypes> before registering that file as spawnabletypes. Keep each weapon’s matching magazines and ammunition in the imported types; adding only rifles can leave players unable to reload them.
The 31 October 1.30.164200 startup accepted the group and completed CE, but rejected ten supplied types: CPB_Glock41_Black, CPB_Glock41_Magazine, CPB_MK16_Tan, CPB_Ammo_40mm_HE, CPB_Ammo_40mm_BHE, and CPB_Ammo_40mm_Color_White, _Red, _Yellow, _Green, _Purple (each color uses the full CPB_Ammo_40mm_Color_ prefix). Exclude those entries and matching attachment references from your mission copy. Do not substitute similarly named ammunition without verifying that the weapon supports it.
BulletStacksPlusPlus
BulletStacksPlusPlus: check stack capacity and ammunition supply
Section titled “BulletStacksPlusPlus: check stack capacity and ammunition supply”BulletStacksPlusPlus 1711179264 increases the capacity of supported ammunition stacks. It does not multiply the number of stacks requested by the economy.
Stop the server, install 1711179264 as a Client mod in Steam Workshop, then restart with the same mod available to players. Use only one stack mod at a time. Keep your existing economy files; there is no new loot file to register just to change stack capacity.
Positive quantmin and quantmax values are percentages of the new capacity. If a particular stack grows fourfold, changing 40–80% to 10–20% preserves roughly the same number of rounds. Leave -1 sentinels and population fields nominal/min unchanged for a fill-only adjustment. Later cartridges are not automatically covered by an older mod’s class list.
1711179264, in Architect on 31 October 2026. See the hosted startup result.Our separate Sakhal comparison with the original stack mod completed economy initialization without the colored-flare rejections caused by Redux below. DZSA found the two-mod setup with MunghardsItempack_Sakhal. This verifies server startup and that specific difference, not every ammunition type or client stacking action.
For the withdrawn Redux fork, see the three rejected flare classes.
GRW ER7 Gauss Rifle
GRW ER7 Gauss Rifle: match the economy to your terrain
Section titled “GRW ER7 Gauss Rifle: match the economy to your terrain”ER7 Gauss Rifle 2307022759 requires Dabs Framework. Its supplied economy uses Namalsk-oriented filters such as lore, Tier6, Tier45 and Tier345, which are not default Chernarus filters. Adapt those filters to your terrain while keeping the rifle, battery, scope, magazine and ammunition available together.
2307022759, in Architect on 31 October 2026. See the hosted startup result.For the installed package, open @2307022759/XML/ and copy er7_types.xml and er7_cfgspawnabletypes.xml into the mission’s custom folder. Both are complete XML documents. Register them as types and spawnabletypes. For a Chernarus military-loot example, replace the supplied usage, value, category and tag filters in each of the five type entries with:
| Class | Category | Usage | Value |
|---|---|---|---|
ER7_Gauss and ER7_Scope |
weapons |
Military |
Tier4 |
ER7_Gauss_Magazine |
magazines |
Military |
Tier4 |
Ammo_ER7RFW |
ammunition |
Military |
Tier4 |
ER7_Gauss_Battery |
tools |
Military |
Tier4 |
Keep the other numeric values and flags. Each entry has one <category name="..." />, <usage name="Military" /> and <value name="Tier4" />; this example removes the Namalsk-specific tag. These are example distribution choices, not new author defaults. This prepared Chernarus file reached economy initialization on 1.30.164200, and a fresh DZSA query found the running test server.
An attachment rule can produce a rifle without a battery or magazine, depending on its chances. ER7_Gauss_T5 appears only in the supplied attachment definitions, while Ammo_ER7RFW_Teleport is absent from the types file. Neither gains a natural-loot target merely by appearing elsewhere. Firing, charging and special ammunition behavior were not tested by this server-only check.
Cheytac M200
Cheytac M200: match the rifle, ammunition and optics
Section titled “Cheytac M200: match the rifle, ammunition and optics”Cheytac M200 1819921337 needs matching rifles, magazines, ammunition and accessories in your economy. Install it as a Client mod. The installed package has no separate types file, so use complete definitions based on your current mission’s vanilla counterparts.
| Item | Verified installed classnames | Vanilla economy entry to copy as a starting point |
|---|---|---|
| Rifle | ussr_m200, ussr_m200_black |
CZ527 |
| Seven-round magazine | Mag_ussrm200_7Rnd |
Mag_CZ527_5rnd |
| Loose ammunition | Ammo_408cheytac |
Ammo_308Win |
| Ammunition box | AmmoBox_408Cheytac_15Rnd |
AmmoBox_308Win_20Rnd |
| Fixed optic | M200Optic, M200Optic_Black |
HuntingOptic |
| Adjustable optic | M200ZeroOptic, M200ZeroOptic_Black |
HuntingOptic |
| Suppressor | M200Suppressor, M200Suppressor_black |
M4_Suppressor |
Copy the complete vanilla type entry, change the copy’s name to the chosen mod class and set its nominal and min targets. Keep the original vanilla entry. Put the new definitions inside a single <types>...</types> root in custom/cheytac-types.xml, then register it as type="types" under your existing custom economy block. Choose location filters appropriate to your server; a copied vanilla entry is a starting point, not the author’s balance preset.
The rifle accepts Mag_ussrm200_7Rnd; that magazine accepts Ammo_408cheytac. Its seven-round capacity and the loose ammunition’s 15-round capacity come from the installed configuration. Similar .408 names from other mods are not interchangeable automatically.
1819921337, in Architect on 31 October 2026. See the hosted startup result.Uncuepas Civilian Clothing
Uncuepas Civilian Clothing: update renamed loot classes
Section titled “Uncuepas Civilian Clothing: update renamed loot classes”Use the current classnames from Uncuepas Civilian Clothing 1762444175 consistently in loot, traders, cargo and starting equipment. Raising targets cannot restore an item that the mod renamed or removed.
1762444175, in Architect on 31 October 2026. See the hosted startup result.The installed root classes.xml is a classname list, despite its extension: it contains // headings and unclosed <type> lines, without economy fields. Do not register it as a types file. To add one item, copy the complete entry for its vanilla counterpart from your current mission, rename that copy and choose its targets. For example, copy the TaloonBag_Blue entry, change only its name to Uncuepa_TaloonBag_Black, then set nominal 5 and min 2 as an initial balance choice. Keep its lifetime, flags, category and location filters. Put the copied definition inside a complete <types> root in custom/uncuepa-types.xml, register it as types, validate and start. Leave the original vanilla entry in place.
SotaVanillaRetexture
SotaVanillaRetexture: keep the current mission economy
Section titled “SotaVanillaRetexture: keep the current mission economy”Sota 2760370513 supplies Chernarus additions at @2760370513/XMLs/Chernarus/1.23/sota/sota_xmls/. Copy sota_types.xml and sota_cfgspawnabletypes.xml to a mission folder named sota_xmls. Add their two file registrations to your existing cfgeconomycore.xml, using type="types" and type="spawnabletypes". The installed files contain 291 types and 65 attachment/cargo entries.
2760370513, in Architect on 31 October 2026. See the loot-file limitation.Do not replace the current mission core or random presets with the bundled 1.23 copies. All preset references in these Sota additions resolved against our current Chernarus presets. classnames.txt is at the mod root; sota_ and warm_ identify additions. Similar weapon labels can still have distinct classes. The separate Livonia folder needs the same release-age check before use.
Our 1.30 startup rejected sota_BallisticHelmet_Tttsko, sota_GorkaHelmet_Tttsko and sota_Mich2001Helmet_Tttsko as nonexistent. Remove these three complete entries from the imported types file. Do not rename them by guesswork or replace your current mission with the older example to try to make them work.
Mounts & Sights
Mounts & Sights: use the correct spawn classes
Section titled “Mounts & Sights: use the correct spawn classes”Mounts & Sights 3322252091 is the installable mod. ID 3310948480 is its Steam setup guide, so do not add that ID to a Workshop import list. The installed Types/Readme.txt links the author’s complete types and attachment examples.
3322252091, in Architect on 31 October 2026. See the hosted startup result.Save the types example as mission custom/mounts-types.xml and the attachment example as custom/mounts-spawnabletypes.xml; register them as types and spawnabletypes. The checked examples contain 99 types and 20 attachment entries and already have XML roots. Keep combined mount/sight classes registered at nominal 0 for persistence. Raise targets only for the separate loot items you want. When a supplied rule changes a vanilla rifle’s attachments, reconcile it with any existing rule for that rifle so the complete intended attachment list survives.
For administrative creation, use the mount class ending _NoAttachment, spawn the sight separately, then combine them. Disable an admin tool’s automatic attachment creation for these mounts. The economy’s Akol_AKMount_Exps/Akol_Exps special case is different from a bare mount with randomized optics.
To attach AWS sights to these mounts, load AWS 2143128974, Mounts & Sights 3322252091, then the compatibility addon 3322263460. Register its additional 100-entry types example alongside both base economies; it does not contain AWS’s own types. Remove natural-loot/trader entries for AD_MosinMount and AD_B13Mount. The author also recommends excluding AD_XPS34, AD_XPS34_HHS, AD_Pilad, AD_PVS4, AD_MRS and AD_OKP7 when using this combination. Akol_AD names identify combined M&S/AWS items; keep their supplied zero spawn targets.
3322263460, in Architect on 31 October 2026. See the hosted startup result.CJ187-MoreDrinks
CJ187-MoreDrinks: check food classes and nutrition
Section titled “CJ187-MoreDrinks: check food classes and nutrition”CJ187-MoreDrinks 1775478803 adds food and drink containers and changes some vanilla nutrition values. Consider both abundance and nutrition when balancing your loot. Closed and opened cans are separate classes: for example, BlackOlivesCan and BlackOlivesCan_Opened. Adding either to a trader does not register it for natural loot.
1775478803, in Architect on 31 October 2026. See the hosted startup result.The installed CLASSNAMES.txt contains only a “will be added later” placeholder, and this package has no supplied types file. For a complete initial definition, copy your current vanilla SodaCan_Cola type, rename the copy to the author’s Cola, and choose its nominal/min targets. Keep the original entry and all other fields in the copied definition. Wrap the new entry in <types>...</types>, save as mission custom/cj-drinks-types.xml, and register it as types. Repeat with the appropriate vanilla counterpart for each desired item, rather than pasting bare classnames into XML.
The author’s listed drink classes include Cola_Cherry, Cola_Light, Pepsi, Pepsi2, Pepsi_Light, Fanta, Sprite, MTN_Dew, MTN_Dew2 and MonsterEnergy1 through MonsterEnergy8. Bottles use Bottle_Milk, Bottle_Cola and Bottle_Pepsi. Add closed food cans to the natural economy; opened variants are separate objects. These names and the mod’s nutrition changes come from the linked Workshop description, not the empty packaged list.
CJ187-LootChest
Configure CJ187-LootChest spawns
Section titled “Configure CJ187-LootChest spawns”LootChest 2345073965 uses its own crate configuration, independent of ordinary world-loot targets. Install CF before LootChest as Client mods; heed CF’s first-install wipe requirement when adding it to an established non-CF world.
2345073965, in Architect on 31 October 2026. See the hosted startup result.- Start once, then stop. Under the active profiles folder, open
CJ_LootChests/. Our run generatedLootChests_V106.json,LootChestsTools_V106.jsonandLootChests_LOG.logthere. Download the JSON files before editing. - In
LootChests_V106.json, edit the existingLootChestsLocationsarray. Every location needs a distinctname. Setnumberno higher than the number of entries in itsposlist. - Write each position as a quoted
"X Y Z|yaw pitch roll"string, with spaces between numbers. Y is height. The pipe separates position from orientation; commas belong between JSON strings, not inside the coordinate triplets. Use positions for your terrain, not copied Chernarus coordinates on another map. - Set
chestto an array of supported crate classnames. Usekeyclass: ""for an unlocked crate. A named key such asCJ_Key1locks it;openable0means key only,1adds lockpicks, and2adds supported tools. Distribute that key through your economy, trader or another deliberate route. - List desired item classes in
loot.lootrandomizeis the chance to omit each entry:0.0keeps every requested entry,0.5omits roughly half, and1.0requests an empty chest. Large items still need enough container space.RandomQuantitycontrols item fill, whileMaxSpareMagslimits spare magazines for predefined weapons. - Validate JSON, save and restart. Read
LootChests_LOG.logfor rejected locations, missing classes and configuration errors before relying on the result.
The subsequent isolated run completed economy initialization and passed a fresh DZSA check on DayZ 1.30.164200. Its LootChests_LOG.log recorded the manager initializing, filling three crates and creating CJ_LootChest_Brown_Medium, CJ_LootChest_Olive_Medium and CJ_LootChest_Tan_Medium at the supplied Tisy positions. That verifies server-side creation with the default file; opening, keys and player looting were not exercised.
To make a location predictable while checking it, use one position, number: 1, one crate class, keyclass: "", lootrandomize: 0.0 and a short vanilla loot list such as NailBox and Rag. Keep all other required fields from the generated location. This tests the configuration without making a locked chest whose key is unavailable.
LC_Table_... names refer to LootCategories; each table reference selects one item from that table. Repeat a reference when you want several picks. Firearm table names start LC_Table_Weapons_. LC_predefined_... names refer to assembled weapon presets in LCPredefinedWeapons; keep the weapon, magazine, attachments and separate optic fields compatible. Ordinary item names do not need either prefix.
The second file controls supported keys/tools. Preserve its entries. The supplied manual supports SledgeHammer, Crowbar and Lockpick; time is seconds for tools, -1 disables that option, and dmg is percentage damage to the tool or key. Key names/descriptions use name|description. Do not assume adding an arbitrary tool classname gives it an unlock action.
The package also includes @2345073965/@Admins - PLEASE READ!/serverfiles/Lootchest_types.xml and Lootchest_cfgspawnabletypes.xml. Copy these complete files into a mission custom folder and register them as types and spawnabletypes. Their economy definitions serve a different purpose from the JSON crate locations. Preserve current vanilla presets instead of replacing them with the example mission file.
The current validation notes explain that invalid configuration is backed up as LootChests_V106.json_INVALID_YYYY-MM-DD_HH-MM-SS and reset. An unexpectedly regenerated default file is a reason to inspect that backup and log. Empty position/chest arrays skip entries. Filling happens at startup/restart, without continuous refilling of opened crates; custom containers need the mod’s supported base class.
Look up all fields, full item entries and filters in the economy reference.
Verify a new spawn or undo the change
Section titled “Verify a new spawn or undo the change”After startup, check the new RPT for the registered filename or a parse error. Run a fresh DZSA Server Check and compare the map and client mods. Then visit a location eligible for the item: a server listing does not prove the new loot target was applied.
To revert a separate override, stop DayZ and remove only its registration from cfgeconomycore.xml. If you edited a stock entry directly, restore that entry’s original values. Restart and inspect new spawns. Leave storage_* intact: existing items do not need to be erased to undo the rule.
For a world using Collectable Items or MosinScope, check the recorded issue before copying old loot tables.





