Configuration

DragonMineZ is configured through JSON files that server owners, singleplayer hosts and add-on authors can edit. Most of them live in the config/dragonminez folder of the game or server instance and are generated the first time DMZ boots; story, wish and NPC data lives inside each world save instead. The server sends its config files to every player who joins, so on a server everyone plays with the server's values.

This section of the wiki documents every config file, the gamerules and permission nodes DMZ adds, and how to apply and keep your changes safely.

General Server Config

Progression, TP, world generation, the story, racial skills, world bosses and storage.

General User Config

Personal client settings: HUD behavior, cameras, auras and tutorials.

Combat Config

Blocking, parrying, mitigation, Speed, Ki Surge, combat flight and ki weapons.

Skills Config

Skill costs, which master teaches what, and technique tuning.

Entities Config

Base stats of DMZ creatures and saga enemy transformations.

Gravity Config

Dimension gravity, the Gravity Device and weight training zones.

Dynamic Growth

Practice-based stat growth and its anti-farming rules.

Gamerules

Ki-griefing and building protection for terrain and arenas.

Permissions

Every command permission node and how checks resolve.

Notice to Server Owners

Backups, updates and multiplayer advice before you edit anything.

Reloading and Updating Changes

What /dmzreload covers and how DMZ updates upgrade your files.

Where config lives

See also: Locating Specific Folders

The config/dragonminez/ folder belongs to the instance, not to a world: every world played on that instance uses the same files. Except for the client-only files marked below, the server sends every file in this folder to joining clients.

File	What it holds	Documented on
`general-server.json`	Server-wide gameplay settings: progression, TP, world generation, the story, racial skills, Dynamic Growth, gravity, world bosses, storage.	General Server Config
`general-user.json`	Client-only. Personal client settings, never sent by the server.	General User Config
`hud_layout.json`	Client-only. HUD style and element layout, written by the HUD editor.	HUD
`radial_layout.json`	Client-side order of the entries in the radial menus, saved when you reorder them.
`combat.json`	Combat tuning values.	Combat Config
`skills.json`	Skill costs and eligibility, and which master offers which skill.	Skills Config
`techniques.json`	Ki attack, strike and evasion technique tuning.	Skills Config
`training.json`	Training minigame tuning.	Training Points and Mastery
`entities.json`	Base stats per entity and saga transformation defaults.	Entities Config
`races/<race>/character.json`	Race identity and appearance defaults.	Custom Races
`races/<race>/stats.json`	Race base stats and scaling per class.	Custom Races
`races/<race>/forms/*.json`	Forms that belong only to that race.	Custom Forms
`forms/*.json`	Shared stack forms layered on top of a race's own forms.	Custom Forms
`raids/*.json`	Raid definitions.	Raids
`tournaments/*.json`	Tournament definitions.	Tournaments
`oldBackup/`	Copies of config files DMZ upgraded or regenerated, in the same relative layout (for example `oldBackup/races/saiyan/stats.json`). DMZ never reads them back.	How to JSON

The default races generated in races/ are human, saiyan, namekian, frostdemon, bioandroid, majin and glind. Any other folder under races/ is loaded as a custom race.

Gameplay rules that aren't JSON files are covered on Gamerules (ki-griefing and arena building) and Permissions (who can run each command). The per-world folders (sagas, quests, side quests, wishes, dialogues, NPC placements and JSON player data) are listed on Locating Specific Folders.

How config reaches the clients

Main article: Reloading and Updating Changes

When a player joins, the server sends them every file under config/dragonminez except general-user.json and hud_layout.json. While connected, the client uses the server's values for everything those files control.
The server sends the files as they are on disk. After editing a file, always run /dmzreload config; until you do, the server keeps running the old values while players who join afterwards already receive the edited file.
/dmzreload config and /dmzconfig resend the files to everyone online.
On disconnect, the client drops the server's copy and goes back to its own local files.

Editing config safely

Keep the files valid JSON. A file with a syntax error is never overwritten: DMZ runs on that file's defaults for the session and reports the file, line and column in the log (and in chat on login).
Don't edit configVersion. DMZ uses it to upgrade the file after a mod update: the old file is moved to oldBackup/, new defaults are written, and the values you changed are merged back in.
Comments and notes inside the files are removed whenever DMZ rewrites them, so keep your notes elsewhere.
Take your own backup before bulk edits on a live server.