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

# Configuration files

Where Server Bot keeps settings, when to use the hosted editor, and how to make safe file changes.

For most changes, use **Configuration** at [bots.mantic.dev](https://bots.mantic.dev) or `/settings` in Discord. These editors label fields, provide list/map controls, message and embed previews, and show changes before saving. Use **Edit YAML** or the Files page when you need direct access and your account has the required permission.

Configuration files are created under `bot/` at first startup. Each feature's configuration is generally stored beneath `bot/features/<Feature>/`. The hosted editor may show optional defaults that are not written into a file until changed. Keep the setting names and YAML indentation intact.

## Main files

| Path                                | Purpose                                                                                                                                                                   |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `bot/config.yml`                    | Licence, bot token, main Discord server ID and general bot preferences. The `SERVERBOT_TOKEN` environment variable, if set, takes precedence over the token in this file. |
| `bot/commands.yml`                  | Slash-command availability and command settings.                                                                                                                          |
| `bot/messages.yml`                  | Shared embed colours and common message text.                                                                                                                             |
| `bot/panel.yml`                     | Hosted Control Panel access and session settings.                                                                                                                         |
| `bot/technical_settings.yml`        | Advanced runtime options. Change only when the setting is understood.                                                                                                     |
| `bot/features/<Feature>/config.yml` | Feature-specific settings and messages.                                                                                                                                   |
| `bot/modules/`                      | Optional module JAR files, not configuration.                                                                                                                             |

The feature page in Configuration is the best guide to each setting. Generated setup guidance and field explanations are updated with the current bot version. The old reference snippets in some linked file pages may not match a newer release; do not replace your generated files with a sample from a different version.

## Safe direct edits

1. Stop the bot before editing configuration directly on the host.
2. Make a private backup of the file.
3. Change only the required values; preserve IDs as full digit strings and keep YAML indentation.
4. Save the file and restart the bot if the feature requires it.

For edits from the hosted Files page, save the file through the editor. A previous file version is saved automatically and can be restored from **Backups** beside the file. Configuration edits through the builder show a Before/After review and apply when saved.

Ticket, application, Auto Voice Channels and Minecraft module settings from older JSON versions may be converted to YAML when the feature loads. The original JSON is kept as `.json.migrated-backup`. If a YAML file already exists, it is used instead of converting JSON. Stored records and caches may remain JSON even when settings use YAML.

For data-folder preservation and restore precautions, see [Backups and data](https://docs.mantic.dev/server-bot/backups-and-data.md).
