> 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/manticswords/config-files.md).

# Config Files

Where ManticSwords stores its settings and how to edit them.

ManticSwords creates these files under `plugins/ManticSwords/` on startup. YAML keys use lowercase words separated by hyphens. Back up the folder before major edits.

| File                                                                       | What it controls                                                                           |
| -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| [config.yml](/manticswords/config-files/config.yml.md)                     | General behavior, economy providers, captchas, payouts, and player controls.               |
| [commands.yml](/manticswords/config-files/commands.yml.md)                 | Command names and aliases; changes require a full restart.                                 |
| [messages.yml](/manticswords/config-files/messages.yml.md)                 | Player-facing messages and command help.                                                   |
| [enchants.json](/manticswords/config-files/enchants-json.md)               | Enchant chances, levels, rewards, and messages.                                            |
| `drops.yml`                                                                | Extra drops by mob type.                                                                   |
| [mob-swords.yml](/manticswords/config-files/mob-swords.yml.md)             | Sword types, appearance, mob and world restrictions, and enchant settings.                 |
| [override-prices.yml](/manticswords/config-files/override-prices.yml.md)   | Item sale-price overrides and ShopGUIPlus redirects.                                       |
| [prestige.yml](/manticswords/config-files/prestige.yml.md)                 | Prestige requirements, restrictions, and rewards.                                          |
| [mobslaying-event.yml](/manticswords/config-files/mobslaying-event.yml.md) | Event timing, eligibility, schedules, and rewards.                                         |
| [Menu files](/manticswords/config-files/menus.md)                          | Main, upgrade, crystal shop, leaderboard, mob prices, prestige, and player settings menus. |

Use `/manticsword editor` for general settings, commands, messages, enchantments, drops, swords, upgrades, prestige, the event, price overrides, and the crystal shop. The editor saves and reloads each change. Other menu files can be edited directly.

For manual edits, run `/manticsword reload`. Restart the server after changing command names or aliases. `enchant-list.txt` is generated for reference and should not be edited.


---

# 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/manticswords/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.