Set up Jobs Reborn and check that job payments work

Jobs Reborn rewards configured actions with income, experience or points. Adding a job does not automatically create a functioning money economy. Verify the economy bridge and provider first, then test one profession with small payouts before enabling a wide range of actions.

Preserve existing professions and progress

Check the Jobs release and its declared dependencies against your exact server version. Use the official project links for Jobs and any required libraries. Stop the server and back up job definitions, general configuration and player storage. If Jobs uses MySQL, keep a consistent export alongside the matching files.

Follow plugin installation and inspect the first startup log. Resolve dependency or database errors before joining a job. Check Vault and the economy provider separately: Vault provides an integration interface, while the economy plugin owns balances. An installed bridge without a provider does not establish that deposits can succeed.

Test one profession

1. Use a private test account and record its starting balance and Jobs progress.
2. Run /jobs browse in Minecraft chat and inspect the jobs the installed configuration actually offers.
3. Read the chosen job's information with the installed help, then use /jobs join with its exact job name.
4. Perform one of that profession's configured actions in an ordinary survival test area.
5. Check the recorded payment, balance and job progress. Repeat a small controlled sample rather than running a farm before you know what is paid.

Do not assume a job named Miner pays for every mined block. Action types, material entries, equations, worlds and limits determine the outcome. Use the generated example configuration for your version and change one value at a time.

Review limits and repeatable actions

Set a deliberate policy for jobs per player, income limits and worlds where payments should apply. Inspect place-and-break loops, spawner farms, automated production and interactions with custom blocks or mobs. A profitable repeated action may be working exactly as configured, so test the intended economy rather than treating every large payment as a plugin error.

Keep sensitive administrator commands separate from ordinary browse, join and information permissions. Do not grant the full Jobs command wildcard to let a player select a profession. Check the exact permission and configured job-access rule when only one player cannot join.

Investigate missing or excessive payments

If experience changes but money does not, inspect economy and payout errors. If neither changes, check membership, the action, material, world and applicable limits. Verify whether another plugin cancelled the event. Run compatibility tests on a copy rather than disabling protections across a live market or protected spawn.

Leaving and rejoining can alter progress according to configuration; do not use it as a harmless refresh on an established player. Before changing payment equations, record the previous settings and test expected results at several levels. Send support the job name, action, location, balance before and after, versions and log time. Further reading: Jobs features, declared commands and permissions and example job configuration.

Looking for another plugin? Browse the Minecraft plugin guide directory.