Review Jobs Reborn level-up commands before awarding a rank
Level-up rewards can run privileged commands. Test the exact target and execution context so a reward grants the intended rank without exposing administrative command access to players.
Before you start
Jobs Reborn tracks job membership, experience and rewards as well as money payments. Use a test player with a recorded level and balance. Some actions depend on optional integrations, so identify the job file and event before editing rewards.
Work through the check
- Copy the active job reward section and identify the level threshold, command text and documented player placeholder for your release.
- Check which console or player context executes the reward, and restrict the command to the specific rank operation needed by the permissions plugin.
- Use an isolated test account with no administrative rights and advance it through one reward threshold using documented test controls.
- Inspect the resulting permission group, any economy charge and logs, then test relogging and a nearby level to check whether the reward repeats unexpectedly.
Confirm the result
Only the intended account should receive the documented reward at the intended threshold. The player should not gain permission to execute the administrative command directly.
If the result differs
An unresolved placeholder can target a literal name or fail silently. Confirm the generated command in a private test log and redact identifiers before sharing a support report.
Recover safely
Restore the saved reward configuration and remove only the test account’s unintended rank if needed. Do not grant wildcard command permissions or replay all level rewards against existing players.
Documentation and related help
Check the Jobs Reborn maintainer documentation and Jobs Reborn maintainer reference against your installed release before applying changes.