Troubleshooting
Plugin does not enable
- Confirm Java 17+ is being used.
- Confirm Vault is installed and a Vault-compatible economy provider is available.
- Check the console for dependency, YAML or database errors.
Configuration problems
- Run
/job doctorfor a detailed configuration audit. - Run
/job admin configcheckfor the standard config validator. - Use
/job doctor fixonly for supported safe automatic repairs; backups are created before safe fixes. - Check material/entity names and make sure feature sections are nested under the correct YAML keys.
Economy / bank does not match Vault
Check configs/economy.yml. Use bank.mode: vault-mirror when the JobSystem bank should directly follow Vault. Administrators can also use /jobadmin bank sync <player> or /jobadmin bank reset <player> for the legacy internal balance.
Rewards do not trigger
- Verify the player has joined the relevant job and has not reached configured limits.
- Check disabled worlds, action cooldowns and anti-exploit settings.
- For Chef rewards, the player must actually extract a configured cooked result from a furnace/smoker; automated hopper extraction is intentionally not rewarded.
- Check protection plugins/claims if rewards are being blocked in protected areas.
Database / persistence
- Do not manually edit database rows while the server is actively writing them.
- Back up the database before switching SQLite/MySQL or upgrading production servers.
- If an achievement was already claimed, v1.1.3 stores a persistent claim ledger to prevent repeated payouts.
Update checker
/job version shows the cached Modrinth status. Administrators can run /jobadmin updatecheck for an immediate asynchronous check. The checker can be disabled in configs/integrations.yml.
Support information
When reporting a problem, include the JobSystem version, server software/version, Java version, economy provider, relevant configuration and the complete console stack trace.