Editors

/jobsadmin opens the admin hub: Editor, Economy, Work orders, Players, Migration and Settings. Admin screens are written again from the jar on every start.

Jobs editor (in game)

Jobs list, then a hub per job with General, Actions, Milestone rewards, Anti-exploit and Perks, and Delete.

• General: name, icon, description, max level, level curve, income bonus, xp bonus, price share and enabled.
• Actions: add a rule by picking the action, then the target from the block you look at, your held item, a mob, a biome or a typed id; edit money and experience; remove one (confirmed).
• Milestone rewards: add, edit or remove a level's rewards.
• Anti-exploit: the five per-job switches.
• Perks: pick a perk, then edit it in ExyliaLib's ability editor.

Every save goes through the real job loader first. It is refused only for what the loader would drop (a problem the file already had does not block you), written atomically and followed by a reload, so the catalogue, screens and features see it at once. Deleting a job removes its file; players keep their levels in case it returns.

Web editor

Every job file is registered with ExyliaLib's web editor (/exylialib editor) as job-<id>, with the same loader check and a reload on apply. The settings records (config.yml, economy.yml, perks.yml, orders.yml, integrations.yml) are editable there too.

Settings

The hub's Settings opens ExyliaLib's config menus for every setting record; the language, budget, caps, report and others have no separate screen.

Players admin

Players lists online players and searches anybody who ever played. A player's screen lets you set a level, set experience, take them out of a job, reset them with ExyliaLib's player reset, and (with the economy guard) pause their pay. Online players are edited in memory on their own thread; others are written to the table.

All admin screens need exyliajobs.admin.