> For the complete documentation index, see [llms.txt](https://docs.mantic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mantic.dev/manticdarkzone/config-files.md).

# Config Files

ManticDarkzone configuration files and safe editing guide.

ManticDarkzone creates these files inside `plugins/ManticDarkzone/` the first time the server starts. Stop the server before making manual edits, and keep a backup of each file.

| File                      | Purpose                                                                                                       |
| ------------------------- | ------------------------------------------------------------------------------------------------------------- |
| `config.yml`              | World restrictions, command rules, permissions, portals, shop toggle, and ignored regions.                    |
| `commands.yml`            | Alternative names for the main commands.                                                                      |
| `messages.yml`            | Player-facing messages and supported placeholders.                                                            |
| `darkzone-mobs.yml`       | Global spawning, mob targeting, damage, and reward selection.                                                 |
| `zones.yml`               | Spawn-zone bounds, mob mixes, limits, and per-zone overrides. Create or edit zones in game with `/mdz zones`. |
| `portals.yml`             | Portal entrances and destinations. See the **portals.yml** page in this section.                              |
| `mobs/<mob>.yml`          | Default settings for one mob type, such as `mobs/zombie.yml`.                                                 |
| `menus/leaderboard.yml`   | Kill leaderboard appearance.                                                                                  |
| `menus/darkzoneshop.json` | Shop layout, trade items, and purchase commands.                                                              |

## YAML and JSON naming

All generated YAML keys use lowercase kebab-case: `spawn-frequency-seconds`, `max-drops`, and `mob-settings`. Keep underscores in enum values such as `ZOMBIE`, where the value is an entity name rather than a setting key.

The shop is JSON and uses the exact camelCase field names its serializer expects, such as `shopItems` and `dropAmountToTrade`. Do not convert those JSON fields to kebab-case.

Use spaces for YAML indentation, not tabs. Quote values beginning with `&` or `#`. Use `[]` for an empty list and `{}` for an empty map. JSON does not support comments.

Do not publish a full config file if it contains private licensing values or server credentials. Keep those values in your server's local copy.

## Reload or restart

`/mdz reload` reloads `config.yml`, `messages.yml`, `darkzone-mobs.yml`, the shop, and portals. It also recalculates spawn areas and removes active Darkzone mobs.

Restart the server after manual edits to `zones.yml`, mob profile files, leaderboard settings, command aliases, or registered command permissions. Saving a zone in the in-game editor applies it immediately.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mantic.dev/manticdarkzone/config-files.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.