Test Jobs Reborn break-and-place rewards for a money loop

Applies to: Jobs Reborn; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

A positive break reward can become exploitable when players replace the same block repeatedly. Test the configured protection and reward policy on a small sample before opening a mining job publicly.

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 file and record the break and place entries for one inexpensive block, plus any relevant protection settings.
Prepare a controlled area where the test account can build, keeping naturally generated blocks separate from blocks placed during the trial.
Break one natural block and one player-placed block, recording money and job experience changes after each payout interval.
Repeat a short place-and-break cycle and compare its net return with your intended policy; inspect the current release’s block information tools if protection tracking is unclear.

Confirm the result

Natural gathering should pay as intended, while a repeat placement cycle should not produce an unintended profitable loop. Any placement penalty must be understood before players build valuable structures.

If the result differs

Older troubleshooting examples can use material names from obsolete Minecraft versions. Match the current generated job example and installed protection behavior rather than copying an old block identifier.

Recover safely

Restore the previous reward entry or temporarily make the affected action nonpaying through documented settings while reviewing the exploit. Keep player balances and historical records intact for a measured reconciliation.

Documentation and related help

Check the Jobs Reborn maintainer documentation and Jobs Reborn maintainer reference against your installed release before applying changes.

Give a LuckPerms permission an expiry without leaving permanent access

Make a LuckPerms event rank expire while preserving other ranks

Limit a LuckPerms command permission to one Minecraft world

Keep a LuckPerms permission local to one network backend

Move a player along a LuckPerms track without replacing unrelated groups

Fix a LuckPerms prefix priority without changing chat formatting

Remove a direct LuckPerms exception without weakening its parent rank

Apply a small LuckPerms web-editor session to the correct server

Export LuckPerms data before changing its storage configuration

Find an inheritance cycle before it complicates a rank change

Keep default-player permissions separate from staff inheritance

Diagnose LuckPerms edits that reach one backend but not another

Check a player UUID before changing LuckPerms account data

Remove a staff member from one LuckPerms track without clearing their account

Give an EssentialsX rank a fixed home limit

Restrict one EssentialsX warp to an approved player group

Test EssentialsX teleport delay and movement cancellation

Add an EssentialsX cooldown to one utility command

Resolve an EssentialsX command alias conflict without removing either plugin

Check EssentialsX AFK kick exemptions for a staff role

Limit EssentialsX nickname changes without granting formatting control

Give staff a read-only EssentialsX player-information role

Recover from an accidental EssentialsX ignore setting

Restrict EssentialsX repair commands to the intended tool policy

Review EssentialsX command-disabled entries after a plugin change

Test an EssentialsX jail location without trapping a real player

Change the EssentialsX starting balance for new players only

Set EssentialsX maximum and minimum money limits with a boundary test

Change the EssentialsX currency symbol without changing stored money

Test an EssentialsX pay dispute using two controlled accounts

Review EssentialsX worth prices before enabling item selling

Explain an EssentialsX balance leaderboard that looks out of date

Trace an unexpected EssentialsX command charge

Back up EssentialsX money before a player-data migration

Verify a LiteBans temporary ban expires at the intended time

Test whether a LiteBans mute covers a private-message command

Build a LiteBans appeal-review role without punishment access

Check a LiteBans moderator’s maximum punishment duration

Find which plugin handled a ban command on a mixed-plugin server

Verify the server scope of a LiteBans network punishment

Investigate a LiteBans database connection failure without losing history

Reverse one appealed LiteBans punishment while preserving the audit trail

Test an AdvancedBan time layout before staff use it

Check AdvancedBan warnings without accidentally escalating a real player

Give an AdvancedBan helper access to history without ban powers

Check AdvancedBan storage before changing from local files to MySQL

Lift one AdvancedBan restriction after an approved appeal

Locate AdvancedBan correctly on a proxy network

Test SuperVanish visibility with separate staff and player accounts

Check whether a vanished SuperVanish moderator can pick up items

Verify flight is safe when a SuperVanish moderator reappears

Check silent chest inspection without changing container contents

Find a SuperVanish join or player-list information leak

Remove vanish access from a staff role without leaving a hidden account

Check PremiumVanish layered visibility after changing staff ranks

Verify PremiumVanish network vanish across Velocity backends

Check vanished staff interactions before a live investigation

Recognize the PremiumVanish API jar before installing an integration

Give GrimAC alerts to one observer without granting exemptions

Remove a GrimAC exemption and verify when checks resume

Collect a GrimAC prediction log for a false-positive report