Configuration
Every file uxmBedrock reads, what each holds, and when a change takes effect.
All files are HOCON. /uxmbedrock reload reads them again and swaps the new settings in whole; a file that cannot be
read keeps the last good settings and says why in the console.
| File | Holds | Takes effect |
|---|---|---|
| config.conf | Language, server name, storage, network, modules, player choices, preview page | Reload; storage, network and preview need a restart |
| text.conf | Exact colours and the glyph pages | Reload, then the next build |
| menus.conf | Which menus of other plugins open as forms | Reload, at once |
| pack.conf | How the Bedrock pack is built | Reload, then the next build |
| gui.conf | Menu pictures and the changes to Bedrock's screens | Reload, then the next build |
| items.conf | The vanilla item under an item model | Reload, then the next build |
| commands.conf | Command names, aliases and switches | Restart |
| messages/ | One file per language | Reload |
| theme.conf | The colours every UXM plugin shares | Reload |
| Geyser extension | Where the extension finds the build | Geyser restart |
| Velocity | The proxy plugin | Proxy restart |
When a release adds a key to config.conf, the next start adds it with its comment and never changes a value you
wrote; the file as it was goes to backups/, the last five copies. The other files are written once and never
changed by an update.
Was this page helpful?