Skip to content
DZconfig

DayZ Expansion support

Expansion settings, edited visually.

DZconfig turns Expansion's dense JSON into dedicated GUI screens for markets, AI, safe zones, missions, vehicles, and territories — then generates the exact files your server reads.

31 editable Expansion settings files
6 guided GUI categories
0 raw JSON you touch by hand

Market, AI, safe zones, airdrops — every Expansion module, edited visually.

Every surface keeps the GUI close to the generated server output, so you can understand what changed before you upload it.

MARKET

Market and traders

Edit currencies, categories, traders, stock behavior, and pricing through controls built for the Expansion economy.

ZONES

Territories and safe zones

Tune flags, radii, map colors, and protection settings with controls that keep coordinates visible the whole time.

AI

AI, patrols, and loadouts

Work through AI settings, patrol routes, crash patrols, and loadout structures with nested controls that match the file shape.

MISSIONS

Missions and events

Configure airdrops, contaminated areas, and missions, then generate the exact files your server expects.

VEHICLES

Garage and vehicles

Adjust parking, retrieval pricing, distance checks, and vehicle behavior from the same instance workspace.

GUIDED

Guided setting groups

Move through dozens of Expansion sections with purpose-built editors, validation, and generated outputs handled behind the scenes.

GUI polish with export confidence.

Expansion settings are too important for pretty controls that don't map back to the server. Every editor generates deterministic JSON in the structure your mod expects.

file covers output type
GeneralSettings.json Core toggles + behavior GUI editor JSON
MarketSettings.json Economy + trader rules GUI editor JSON
AirdropSettings.json Airdrop spawns + loot GUI editor JSON
SafeZoneSettings.json Protected zone geometry GUI editor JSON
RaidSettings.json Base raid configuration GUI editor JSON
Trader_*.json Per-trader item lists GUI editor JSON

Import, edit, generate.

Guided editors, import actions, generated files, and delivery all live in the same instance context — no juggling raw JSON in a text editor.

1

Import

Bring in Expansion defaults or upload the configuration already running on your server.

2

Edit

Use GUI controls for the messy settings: switches, ranges, map zones, grouped panels, and save-ready forms.

3

Generate

Create clean Expansion files and deliver them through download, FTP, or SFTP.

Build Expansion configs that match how admins think.

GUI editors for the messy files, generated straight into server-ready JSON.

Start configuring