Configuration
Every file the plugin writes, reloading, and what an update does to your files.
| Page | What it holds |
|---|---|
| config.conf | Language, storage, item data, limit, routes, drag and drop, anvil, grindstone, worlds, books, display, charges, cooldowns, the treaty, effect materials, claims, editor, menu sounds |
| Enchantment files | enchantments/<id>.conf, one per enchantment |
| rarities.conf | The chance on each route and the table level |
| types.conf | The format, the per item limit, the grindstone rule |
| targets.conf | Extra enchantable items, named sets, targets and slots |
| vanilla.conf | Vanilla enchantments in your own words |
| commands.conf | The name, aliases and switch of every command |
| Menu files | The six windows |
| Messages | messages/messages_<language>.conf |
| Languages | The seven languages and how a player's language is chosen |
| theme.conf | The colours, glyphs and small capitals every UXM plugin shares |
Every file is HOCON: key = value, blocks in braces, # comments.
Reloading
/uxmenchants reload reads config.conf, every content file, the messages, the theme and the three player windows
again, and redraws every player's items. The content is validated whole first; a wrong file refuses the reload and
names the file, the key and the line. storage, editor.enabled and commands.conf need a restart.
What an update does
When a release adds a key, the next start adds it to your config.conf with the comment that explains it, and it never
changes a value you wrote. Your file as it was is kept in backups/; the last five copies are kept. Alignment inside a
block may move, and a key you deleted comes back. The other files are written only when missing.
Related: config.conf
Was this page helpful?