How to install DayZ Editor Loader and add map edits

By Niko Catarino

Updated 7 October 2026

To add a DayZ Editor build to a Steam PC server, install DayZ Editor Loader and its requirements, then place the saved .dze file in EditorFiles/ inside the active mission. Test one small edit before deploying a compound, trader area or replacement town. Buildings that should spawn loot need a separate economy check.

Use DayZ Editor Loader, Workshop item 2276010135, published by dab. The DayZ Editor is the offline authoring tool. Loader is the package that reads its builds on your server. These PC Workshop packages cannot be installed on Xbox or PlayStation servers.

Keep authoring and server loading separate

Component	Where it belongs
DayZ Editor	The creator’s offline editing session, with its required CF and Dabs Framework packages.
DayZ Editor Loader	The server that loads the .dze builds; clients also need it when the build removes baked terrain objects.
Dabs Framework	Loader’s listed dependency; retain the scope needed by the complete mod set.
Custom object packages	Server and clients when their assets are used in the build, following each author’s requirements.

Scroll to see all columns →

The Editor’s author states it is offline only. Do not install the full authoring tool on the community server as a substitute for Loader. BuilderItems and other prop packs are content choices: add the packages your build uses, rather than copying an unrelated creator’s entire mod list.

BuilderItems’ author says its definitions are included in Expansion and links the split DayZ-Expansion-Map-Assets package. Check your installed module set before adding the standalone pack. Keep one provider for those definitions; the BuilderItems procedure covers this choice.

Record the terrain, game branch and package versions used to make the edit. A build containing deletions or custom objects needs those same terrain objects and classnames to exist on the target server.

Prepare the active mission and a recovery copy

Check the running server’s template setting to find its active mission directory. For a Chernarus mission named dayzOffline.chernarusplus, you would upload the build to a path such as:

mpmissions/dayzOffline.chernarusplus/EditorFiles/my-test-build.dze

Use your actual mission name, including its case on Linux. The server’s profiles directory is not the destination for these .dze files.

Take a stopped backup of the mission, saved world, profiles, current launch arguments and existing map edits. Save an independent copy of mapgrouppos.xml and mapgroupproto.xml before any loot export. Do not rely on a mod-generated .backup file as your only recovery copy.

Use a separate saved world for the test. If your chosen dependencies introduce CF into an existing world, CF’s author requires a wipe before first installation. Plan that change before touching the live save.

Install Loader with the correct scope

In VXPanel:

1. Stop the test service and open Mods.
2. Install Dabs Framework, item 2545327648, then the original Loader item. Compare the installed requirements with both authors’ current lists and the other mods in your build.
3. Start with Loader and its required framework client-required, so players also load the packages. This supports edits that remove objects built into the terrain.
4. Install any custom object packages used in the .dze. Keep their required frameworks before the dependent packages.
5. Check the accepted keys in the server’s keys/ directory. The inspected Loader package supplies dab.bikey; use the current files supplied by your installed releases.
6. Start once, read the new startup logs and confirm the service creates EditorFiles/ under its active mission. Stop before uploading the edit.

On a self-managed host, follow the manual package and key procedure. For folders named @Dabs Framework and @DayZ Editor Loader, the relevant client-required argument is:

"-mod=@Dabs Framework;@DayZ Editor Loader"

Keep the rest of your mod list and current launch command. Add CF before the mods that require it. Quote the complete argument where folder names contain spaces.

The author’s export reference permits server-only Loader for builds with no baked map deletions. Check every edit and its dependencies before choosing server-only loading. If an edit removes a building placed by the terrain creator, use client-required Loader and matching client packages. The panel’s server-side button doesn’t check your build for these deletions.

Save and upload a small .dze build

On the creator’s PC, load the target terrain in DayZ Editor with its required frameworks and every custom asset package used by the build. Start with one visible object in a clear test area. Keep it as an exported server object, rather than an Editor-only helper.

Save the build in the Editor’s .dze format. The default client save location is under Documents/DayZ/Editor/; if you set a custom client profiles location, use its Editor/ directory. Keep the source save and record the chosen test position.

Upload the .dze to the server’s active mission EditorFiles/ directory using Files and SFTP. Keep one copy of the edit. Remove an older version from that loading directory before adding a renamed replacement.

Load the placement through one system. If you also paste the same export into init.c, a VPP object file or another loader, it can produce duplicate objects. Renaming a .json, text export or compressed archive won’t turn it into a valid .dze save.

Start the server and inspect its fresh logs. The inspected Loader reads both supported binary and JSON-form .dze saves, reports failed reads and processes the loaded objects during mission startup. Do not hand-convert the file format to work around an unsupported export; resave through a compatible Editor release.

Add TerrainIslands pieces to an edit

Gormirn’s TerrainIslands, item 2393499239, adds placeable terrain pieces for building over land or water. Load it in the Editor session that creates the build, and install it for the server and joining clients. The author explicitly requires client loading; server-only Loader doesn’t make the custom assets available to players.

In the Editor, search tisl_ for the package’s objects or island for its islands. Choose the surface you need: _NG variants have no grass, while _CC variants cut clutter. Namalsk variants require Namalsk for their clutter to display correctly. Use the variant supported by your target terrain instead of choosing it by appearance in a different editing session.

Save a small .dze and upload it to the active mission’s EditorFiles/ directory using the steps above. The author recommends this Editor/Loader workflow and hasn’t tested other placement methods, including init.c. Keep one placement source so the same piece isn’t loaded twice.

Visit the test position with a matching client. Check the edges, height, collision and grass, then place a test item and walk across the surface. Repeat after a restart before adding buildings or player storage. If an older build shifts, compare the package versions: the October 2021 changes rebuilt terrain pieces and corrected mirrored sizes. Keep the previous export and compatible packages for recovery.

This section used AI-assisted research and drafting on 6 October 2026. We read the original description and all eight change entries. Current package contents, placement, collision and restart behavior haven’t been tested here.

Add roads with VanillaRoadPartsPack

Gormirn’s VanillaRoadPartsPack, item 2353800408, supplies road models for Editor builds. Install it in the offline Editor session and on both the server and joining clients. Use the package and signing-key procedure; the author requested a replacement key with the 12 November 2024 update, so copy the key from your installed release.

Search rbldr_road in the Editor for roads, or rbldr for the wider set, including paths and runways. Check the classname of each piece already in your build. The author warns that placing the game’s original road models, including bldr or vbldr versions, can affect matching roads baked into the terrain. An object that looks like the right road may still use a different model.

These pieces follow the map’s ground surface. Raising one over a pier or a TerrainIslands object won’t make it a flat road deck; Gormirn explains that limitation in the author comments. The same comments distinguish this package from roads for Terrain Builder. For the city crosswalk decal, the October 2021 change note says to place it on top of another road.

Save one short road section as a .dze and load it through the steps above. Keep the previous build separately. The author recommends Editor/Loader and hasn’t validated other placement methods, including init.c, for these models.

On the target terrain, walk and drive across the new section, inspect its edges and revisit nearby original roads. Repeat after a restart with a matching client. Later users report flickering or missing roads after DayZ 1.27; those reports haven’t been reproduced here. If roads disappear or overlap, compare the exported classnames and loaded packages before expanding the build. Restore the previous .dze set if the check fails.

Keep the package’s attribution and ADPL-SA license, including its noncommercial, Arma/DayZ-only and share-alike conditions. Availability on Workshop does not establish permission for every planned use.

This section used AI-assisted research and drafting on 7 October 2026. We read the description, all seventeen change entries, ten displayed comments and ten author replies, plus the linked license. Current package contents and in-game road behavior remain untested.

Add BuildingsMegaModPack buildings

Starlv’s BuildingsMegaModPack, item 2307297070, combines the author’s BuildingsModPack parts 1–4. Use the combined package without those four standalone packs: the author’s September 2021 clarification warns that loading both causes errors. The description links parts 5, 6 and 7 and IndustrialModPack separately; those links aren’t a claim that the extra packs are included.

Load BuildingsMegaModPack in your offline Editor session and install matching files on the server and joining clients. Follow the package and signing-key setup, then use the names and object images supplied inside the author’s package to choose a building. The Editor’s installation reference lists this pack as an additional building source.

Place one configured building class, save the .dze and upload it through the Loader steps above. Keep that placement in one loading system. Replacing the mission’s complete init.c with an example can remove your existing mission logic; it isn’t required for this .dze workflow.

Check the building with an ordinary client: doors, stairs, floors, collision and visibility from outside. Repeat after restarting. For natural loot, continue with the prototype and position checks below. A visible building and a successful loot-position export don’t establish that its class has suitable loot definitions.

The latest listed change, 23 January 2025, fixes textures. This section used AI-assisted research and drafting on 7 October 2026: the description, all three change entries, selected author replies and Editor installation reference were read. Current packaged classnames, client behavior and building loot haven’t been tested here. Keep the original distribution; the author prohibits repacking.

Add BuildingsModPack7 objects

Starlv’s BuildingsModPack7, item 2762521201, supplies another set of buildings and structures. It is separate from BuildingsMegaModPack, which combines parts 1–4. The part 7 description links the author’s other packs; choose packages for the objects your build actually uses.

Keep the original distribution and load it alongside the offline Editor. Install matching assets on the server and joining clients through the package and signing-key procedure. Choose a configured object from the installed Editor’s list and record its exact classname. The description doesn’t provide a classname list, so don’t use a screenshot’s label as an object name.

Place one object, save a small .dze and upload it using the steps above. Check doors, stairs, floors and collision from a matching client, including interactions with infected and projectiles where relevant. Repeat after restarting. For loot, follow the prototype and position checks below; placing the model alone won’t establish working loot spawns.

Starlv prohibits repacking and requires permission to open, modify or reuse individual parts. Keep the previous export for recovery and remove a failed placement from your test build instead of changing the package.

We read the original description, ten displayed comments and all six change entries for this AI-assisted section on 7 October 2026. The last entry is 16 March 2022, and all six entries have no explanatory text. Current classnames, package contents and building behavior remain untested.

Add ZStuff objects to an edit

Starlv’s ZStuff, item 2384407442, supplies towers, walls, fences, shelters and other objects, plus scenes for map creators. Load the original package alongside the Editor when making the build, then install matching assets for the server and joining clients through the mod installation procedure.

Use the package’s Objects.txt to find the object names. The author identifies that list in the December 2021 change notes. Confirm that your installed release still supplies it and that the chosen class appears in the Editor. A screenshot or a scene’s title isn’t a classname.

Place one object and save a small .dze using the steps above. Check it on the test server before assembling a complete base: enter and leave buildings, climb ladders, open gates from both sides and drive through the open entrance. Check collision with players, infected and projectiles where the structure is meant to block them, then repeat the placement check after a restart. The author’s 27 March 2024 update addresses vehicles being blocked by open gates; it doesn’t establish how every object behaves in the current game.

Keep the original distribution. Starlv prohibits repacking and requires permission for opening, modifying or reusing individual parts. If an object fails the checks, remove its placement from the test build and retain the working export rather than modifying its PBO.

This section used AI-assisted research and drafting on 7 October 2026. We read the original description and all eight change entries. The current object list, package contents, collision and game behavior haven’t been tested here.

Verify placement and terrain deletions

Join with the required client packages and travel to the recorded test position. Check visibility, position, rotation, collision and access from a normal player’s perspective. If the build uses custom assets, confirm another joining client can see them too.

If the edit removes an object built into the terrain, check that it is gone on both the server and a matching client. Walk through its former position to check for invisible collision, and inspect nearby terrain features before removing more objects. A server screenshot won’t show whether the object is gone on the client.

Stop and start the same test world, then return to the location. Loader recreates placements from the .dze at startup. These decorative map edits do not use the same persistence as player-built bases: the inspected creation flags include ECE_NOPERSISTENCY_WORLD. Don’t rely on this placement workflow to preserve vehicles, containers or loot inventories. Use the relevant vehicle or economy procedure for those jobs.

Export loot positions for added buildings

Placing a building does not give it working loot by itself. The economy needs both a prototype definition for that building class and the positions where that class exists. Choose the configured building classname for an interactive building. A raw .p3d placement can look similar while lacking the building’s configured doors or loot behavior.

In the reviewed Loader release, the author-supported configuration is this field in the active server configuration, such as the serverDZ.cfg selected by -config=:

enableAutoMapGroupPosExport = 1;

Use it on the test instance after saving independent copies of the mission’s existing map files:

1. Check that mapgroupproto.xml contains the required building prototype and retain the terrain’s existing definitions. Merge supported custom definitions without replacing the whole file with a fragment.
2. Stop the service, add the field to the active server configuration and validate the edited file.
3. Start with the complete set of intended .dze builds loaded. Read the fresh RPT for the export message and any failed object or file operations.
4. Stop the service and inspect the resulting mission-root mapgrouppos.xml. Validate its XML and check the added test position, existing terrain buildings and intended deletions.
5. To keep the checked position file without exporting it again at startup, set the export field to 0 and start again. If you keep export enabled for future edits, preserve independent backups and inspect its output after each build change.
6. Check natural loot from a normal client. Existing item population, locations and lifetime can delay the visible result. Follow loot troubleshooting before assuming the placement failed.

In the inspected release, the export includes only world objects whose classes appear in the mission’s mapgroupproto.xml, and skips suppressed objects. It writes the mission’s mapgrouppos.xml, replacing any position list you’ve maintained by hand. Keep your independent backup and compare it with the export before accepting the new file. A custom building without a prototype will not gain loot positions through this export.

Older wiki examples use EditorLoaderModule.ExportLootData and ExportLootExperimental in init.c. Those names are absent from the inspected current Loader script. Use the release’s supported server configuration above; copying an old example can cause a script compile failure.

Fix missing builds and loot

Symptom	Check
EditorFiles/ never appears	Active mission, successful Loader compilation, framework order and service write access.
File present but nothing loads	Actual .dze extension, supported save format, read errors and selected mission.
Some objects missing	Exact classnames, required custom packages and whether the objects were marked Editor-only.
Objects duplicated	Multiple .dze copies, old versions and another placement mechanism such as init.c.
Deleted building remains or has collision	Client-required Loader for baked deletions, matching client package and matching terrain.
Building has no natural loot	Prototype definition, exported position, valid mission map files and economy restrictions.
Existing loot positions disappear	Restore the independent map-file copy and reconcile the complete export before restarting.
Server fails after adding a wiki snippet	Check release support; the reviewed script uses enableAutoMapGroupPosExport, not the older export fields.

Scroll to see all columns →

Roll back or update the edit

Stop the service and move the new .dze out of EditorFiles/ into your recovery directory. Restore the previous build set, server export setting and mission map files together, then start and revisit the location. Removing the .dze does not erase unrelated saved bases or inventories that players created nearby.

Before updating Editor, Loader or object packages, retain the original source save and the tested export. Review the change notes, load the source in the matching authoring environment and repeat the placement, deletion and loot checks. Keep the original distributions; the authors prohibit unauthorized repacks.

Related documentation: Author’s server-export reference.

Return to the DayZ tutorial directory or continue with changing the map.