Configuration
Every file the plugin writes, reloading, and what an update does to your files.
| Page | What it holds |
|---|---|
| config.conf | Language, storage, slots, permissions, employment, ledger, decay, income cap, milestones, tax, server account, claims, zones, leaderboard, signs, report, explore, placeholder actions, editor, menu sounds |
| protections.conf | Farm grades and what never pays |
| economy.conf | What costs are taken in |
| display.conf | What a player sees while working |
| Job files | jobs/<id>.conf |
| Contract files | contracts/<id>.conf |
| Zone files | zones/<id>.conf |
| boosters.conf | Permission boosters |
| schedule.conf | Calendar boosters |
| titles.conf | The title ladder |
| shop.conf | The job shop |
| commands.conf | The name, aliases and switch of every command |
| Menu files | The thirteen 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
/uxmjobs reload reads every file again and swaps the result in as one snapshot, so a reload is never half applied.
A file that is wrong refuses the reload and the server keeps the last good snapshot; the console names the file and the
key. 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 config.conf, protections.conf, economy.conf or
display.conf with its comment, and never changes a value you wrote. Your file as it was is kept in backups/; the
last five copies are kept. Alignment may move, and a key you deleted comes back.
Related: config.conf
Was this page helpful?