How to install MMG Base Storage and fix despawning in DayZ

By Niko Catarino

Updated 3 October 2026

Install the original MMG package on the server and clients, then register its supplied economy definitions in the active mission. Place a container, add cargo and check both after a stop/start. An item showing in an admin menu proves neither economy registration nor cargo recovery.

Use MMG Base Storage, Workshop item 3210162677, by Mighty Moitzbert. This guide covers Steam PC setup, persistence and storage conflicts. Xbox and PlayStation hosting cannot load the package.

Choose the current main package

The main and NoCodeLock versions were merged, according to the author’s 10 April 2026 change notes. Install the original main item and disregard older instructions to load both variants. Check the intended release before choosing a similarly named before-1.29 listing. Author’s change notes

Use the change history when investigating cargo dropped after restarts, supply-crate upgrades or clothing stacking. Subsequent entries cover Armored Cabinet raiding and old-table/craftable-gunrack errors. Confirm your subscribed release, then reproduce the affected action on your test world; a recorded fix needs validation with your mod set.

With the service stopped, back up the mission, world save, profiles, packages, keys and launch settings. List the storage, clothing, lock and placement mods you intend to combine. Start on a restricted instance using that set, retaining a smaller test set for conflict diagnosis.

Install the package for server and clients

Open Mods in VXPanel while the service is stopped. Search 3210162677, confirm its Steam link and author, and select Install. Review the current required-item list and retain the server-and-client scope. Follow VXPanel mod controls for dependency handling and package updates.

For a manual server, create a mod folder from the subscribed package and place its supplied .bikey files in keys. Retain signature verification. Add the folder to your existing argument, matching the name you used:

"-mod=@MMG Base Storage"

Preserve all other required packages in that list. Connecting players must load the matching MMG client release for its models and scripts. Resolve admission errors with missing-PBO checks before investigating storage persistence.

Register the supplied economy definitions

Get the types and trader files from the installed package’s files directory, as directed by the author. The installation notes warn that missing types can lead to despawning. Retain the supplied class names, lifetimes and flags for the first test. Author’s installation notes

Register an MMG file alongside the vanilla definitions:

1. Stop the service and confirm which mission serverDZ.cfg selects.
2. Open the MMG types document in the package’s files directory. Check that you selected economy types rather than a trader configuration.
3. Create the active mission’s mmg_ce/mmg_types.xml from that types document. Retain the package original and create the directory if needed.
4. Inspect the copied XML for a single <types> root containing the <type> entries. Wrap an entry fragment in that root if the supplied file has no wrapper.
5. Insert the following registration within the existing <economycore> element of that mission’s cfgeconomycore.xml:

<ce folder="mmg_ce">
    <file name="mmg_types.xml" type="types" />
</ce>

This procedure chooses the directory mmg_ce and filename mmg_types.xml; create them yourself. Match filename case on Linux and retain the other economy registrations. Check db/types.xml and the registered custom files for previous MMG imports, reconciling any existing definitions before adding this one. Additional economy files and mod registration

Inspect definitions for deployed storage classes and the kits used to create them. The kit and container need their respective checks. Finding the kit in natural loot does not validate the container’s lifetime, and a zero natural-loot target does not settle placed-object persistence. Test the supplied definitions before tuning their values.

Validate the XML and upload it using Files and SFTP. On startup, inspect the fresh RPT/script logs for parse errors, missing registered files and unknown classes. The DayZ economy editor provides supported XML checks; run the in-game cargo and script checks as separate tests.

Check XML and duplicates on a Windows host

From the Windows server directory, use this read-only PowerShell check to parse the copied XML and list repeated names within that document. Change the mission path when running another map:

$mmgTypesFile = '.\mpmissions\dayzOffline.chernarusplus\mmg_ce\mmg_types.xml'
$mmgTypesDocument = New-Object System.Xml.XmlDocument
$mmgTypesDocument.XmlResolver = $null
$mmgTypesDocument.Load((Resolve-Path -LiteralPath $mmgTypesFile).Path)
if ($mmgTypesDocument.DocumentElement.Name -ne 'types') {
    throw 'Expected one types root in the copied MMG document.'
}
$mmgTypesDocument.SelectNodes('/types/type') |
    Group-Object { $_.GetAttribute('name') } |
    Where-Object Count -gt 1 |
    Select-Object Name, Count

Repair parse errors before startup. An empty result means no class names repeat in this document. Check names against other registered types files too and retain one intended definition per class. This command’s scope is XML parsing and duplicates in one file; registration and loaded-class validity require their own checks.

Inspect the generated storage configuration

After the first clean startup, stop and open MMG_Storage under your active -profiles directory. Save a copy of the generated configuration. The Workshop description names this directory and describes an option to disable CodeLock ability on the items.

Read the installed file’s comments to identify that release’s filename and supported lock field. Apply your lock policy to the existing setting, restart and check a lockable item as an ordinary player. When disabling lock ability across the items, test the resulting access behavior with the main package.

If Code Lock is part of your mod set, identify which configuration belongs to MMG and which belongs to Code Lock. Check the combined releases for owner access, denied access and the intended raiding policy. A switch in one package may not govern the other’s locks.

Test storage, attachments and cargo after restart

Select a few items that exercise different storage actions, taking their exact classes from the installed files. Record positions and cargo before stopping the server. Use admin spawning to inspect item behavior, then check natural loot through a separate test if your server uses it.

Test item or action	Observe before and after stop/start
A deployed crate	Compare its position and cargo, including quantities and condition
A lockable locker or cabinet	Try owner and denied access; compare the saved lock state and cargo
Clothing/loadout attachments	Transfer items through their slots and check retained attachments
A supply-crate upgrade	Check materials consumed and the resulting object with its cargo
Disassembly	Verify the tool/action and remove cargo before dismantling

Scroll to see all columns →

Transfer clothing and weapons between player inventory and storage, checking each intended attachment slot. For a failed slot, repeat the action on the smaller test mod set: the author reports conflicts with other storage mods. Identify the conflicting combination before introducing a slot-expansion package.

Choose a disposable test item and empty it before disassembly. The author’s listed tool is a screwdriver; check the installed release for that item’s action and returned materials. An upgrade may replace the original object, so inspect the resulting class and its economy definition as well as cargo.

Complete the normal save/shutdown and restart the same mission and world save for the persistence check. Rejoin and inspect every recorded container and its contents. Confirm the launch settings if storage appears missing: a fresh save or different mission can cause that observation. Retain the logs and original backup during diagnosis.

Diagnose disappearing items and recover

Symptom	Investigation
Storage disappears during a run	Check the active economy import, class definitions and lifetime; look for duplicate imports
Container remains but cargo drops on restart	Compare package revision, save/shutdown evidence, script errors and other storage mods
Clothing or weapon slots reject items	Identify the item and attachment; compare client releases and storage/clothing combinations
Kit spawns but deployed storage goes missing	Inspect both class definitions and evidence that the deployed object was saved
Lock behavior breaks your server rules	Check the active MMG configuration and the other lock packages
Upgrade or old-table actions error	Match the package revision to the author’s relevant change entry
Storage goes missing after a map change	Compare the selected mission, profiles and world save in the launch settings

Scroll to see all columns →

Register missing definitions before running another test. That edit does not restore deleted items, so use a suitable world backup if the community needs recovery. Compare the last working run with the first failure in server logs.

For an economy or configuration rollback, stop and restore the saved files. Keep package, profile and world versions matched when rolling back a release. Move or export the community’s cargo before removing MMG, then follow mod removal when changing the live mod list.