> 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/manticrods/configuration-files.md).

# Configuration files

ManticRods configuration file guide

ManticRods creates these files under `plugins/ManticRods/` on startup. Generated YAML files include comments for their settings. The files available depend on your ManticRods version; use your server's generated files as the current reference.

## Main files

| File                                                                          | Purpose                                                              |
| ----------------------------------------------------------------------------- | -------------------------------------------------------------------- |
| [config.yml](/manticrods/configuration-files/config.yml.md)                   | General behavior, currencies, fishing, captcha, and first-join rods. |
| [commands.yml](/manticrods/configuration-files/commands.yml.md)               | Command names and aliases. Changes require a restart.                |
| messages.yml                                                                  | Player-facing messages and command help text.                        |
| rods.yml                                                                      | Rod types and rod settings.                                          |
| enchants.json                                                                 | Enchantment definitions and behavior.                                |
| drops.json                                                                    | Fishing drops, weights, and drop commands.                           |
| fishing-event.yml                                                             | Fishing event settings and rewards.                                  |
| prestige.yml                                                                  | Rod prestige requirements and progression.                           |
| [override-prices.yml](/manticrods/configuration-files/override-prices.yml.md) | Price overrides and shop price redirects.                            |

## Menu files

See [Menus](/manticrods/configuration-files/menus.md) for the menu files: `main.yml`, `settings.yml`, `upgrades.yml`, `prestige.yml`, `shard-shop.yml`, `fish-prices.yml`, and `leaderboard.yml`.

## Edit and reload

Use `/manticrod editor` to edit the settings supported by the in-game editor. It requires `manticrods.editor`, operator-only by default. Changes made in the editor are saved and reload plugin settings. Other menu files can be edited directly; run `/manticrod reload` after manual edits if you have `manticrods.reload`. Restart the server after changing command names or aliases.


---

# 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/manticrods/configuration-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.