mcMMO tasks
Task guides and troubleshooting for mcMMO. Check the installed release before changing configuration or data.

Find which mcMMO XP multiplier changes a player reward
Unexpected skill XP can come from several multipliers rather than the block or action value alone. Compare a single controlled activity before changing the whole progression curve.
Check the installed content
mcMMO progress belongs to player data, while its configuration controls future skill behaviour. Preserve both before changing progression rules. Match the installed release when checking permissions and configuration; current configuration references identify changes that require a full server restart.
Work through the change
Record the skill, activity and displayed XP gain for one ordinary account. Save experience.yml and the permission assignments that may apply player or group multipliers.
Read the matching experience reference and list the relevant global, skill and player modifiers. Keep the base action reward distinct from the effective amount the player receives.
On staging, remove one optional modifier from a test account and repeat the same activity with equivalent tools and conditions. Use a normal full restart for configuration changes as directed by the maintainer docs.
Restore each modifier individually and record the result. Include a second account without the special group so you can separate server-wide settings from inherited permissions.
Verify the result
The recorded difference should be attributable to a particular modifier or combination. An ordinary account should receive the planned baseline without needing to reset any skill levels.
If the result differs
If the results vary between attempts, inspect bonuses, party sharing and activity eligibility before adjusting the base XP. A different block source or player state can invalidate an otherwise useful comparison.
Keep a recovery path
Restore the saved experience settings and temporary permission changes if the result is unclear. Keep existing player progress intact; changing future XP rates is separate from correcting or removing stored levels.
References and related help
Check the maintainer reference: mcMMO documentation, mcMMO documentation.
Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.

Test mcMMO party XP sharing at the edge of its range
Party members standing apart may receive different XP even when they belong to the same party. Test sharing eligibility and distance before changing skill rewards.
Check the installed content
mcMMO progress belongs to player data, while its configuration controls future skill behaviour. Preserve both before changing progression rules. Match the installed release when checking permissions and configuration; current configuration references identify changes that require a full server restart.
Work through the change
Record the installed mcMMO version, party state and intended sharing rules. Consult the current party reference for unlock requirements and the configuration governing the sharing range.
Create a small staging party with two ordinary test accounts that meet the documented prerequisites. Keep their relevant skill and bonus conditions comparable.
Perform one repeatable XP activity with both players close together, then repeat near and beyond the configured sharing boundary. Record the gain on each account rather than only the party message.
Compare the same activity outside the party to establish the baseline. Apply any range change through the supported configuration workflow and repeat after a normal restart.
Verify the result
Sharing should follow the configured eligibility and range, and a player beyond the boundary should behave as documented. The baseline should explain whether the total gain changed or was redistributed.
If the result differs
If nobody shares, inspect party unlocks and the selected sharing mode before increasing the range. If only one account differs, compare permission bonuses and activity eligibility rather than editing both player profiles.
Keep a recovery path
Restore the original range and test-party settings when the trial ends. Do not remove production party records or reset levels to fix sharing; preserve the party and player storage before any later migration.
References and related help
Check the maintainer reference: mcMMO documentation, mcMMO documentation.
Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.

Check an mcMMO ability permission without granting every skill command
A player may have access to a skill but lack its active ability or related command. Test the exact permission path rather than granting a broad mcMMO wildcard.
Check the installed content
mcMMO progress belongs to player data, while its configuration controls future skill behaviour. Preserve both before changing progression rules. Match the installed release when checking permissions and configuration; current configuration references identify changes that require a full server restart.
Work through the change
Identify the skill action that fails and whether it is an ability, a command or ordinary passive progression. Open the permission reference for the installed release and record the relevant nodes.
Compare the ordinary player group with a working test group, including inherited permissions and explicit denials. Keep operator status out of both test accounts.
Grant only the documented node required for the failed action on staging. Test activation using the intended tool, prerequisites and cooldown, then test an unrelated administrative command that should remain denied.
Remove the temporary grant and repeat the original failure. This confirms that the permission changed the result rather than a coincidental cooldown or equipment change.
Verify the result
The permitted gameplay action should work while administrative skill-editing or issuance commands remain unavailable. The denied test should fail predictably without affecting the player existing levels.
If the result differs
If the grant has no effect, inspect cooldown, skill requirements and region restrictions before adding more permissions. If an unwanted command works, trace inherited groups and operator privileges.
Keep a recovery path
Restore the previous permission assignments and remove the temporary group if access becomes too broad. Preserve player data and document the final narrow nodes so later rank changes do not undo the intended boundary.
References and related help
Check the maintainer reference: mcMMO documentation.
Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.

Explain why a player-placed block gives no mcMMO XP
Blocks placed by players may be treated differently from naturally generated blocks. Check the anti-exploit rules before increasing rewards or disabling protection across the server.
Check the installed content
mcMMO progress belongs to player data, while its configuration controls future skill behaviour. Preserve both before changing progression rules. Match the installed release when checking permissions and configuration; current configuration references identify changes that require a full server restart.
Work through the change
Record the skill, block type and how the affected block was created. Keep a naturally generated comparison area separate from the player-placed test area.
Read the experience reference and installed configuration for source eligibility and exploit prevention. Do not assume a visually identical block has the same reward history.
Mine one permitted natural block and one deliberately player-placed block with equivalent tools and account permissions. Record XP, drop behaviour and relevant plugin messages.
Repeat with an unrelated supported block source and check any world or region restrictions. Change only the specific staging rule if your gameplay design deliberately allows that source.
Verify the result
The observed XP should match the documented source policy, with the natural control confirming that the skill itself works. A blocked repeat-placement loop should remain blocked unless you intentionally redesign the economy.
If the result differs
If neither source awards XP, inspect the skill permission and world rules first. If rewards occur inconsistently, check other plugins replacing blocks or handling breaks before weakening anti-exploit settings.
Keep a recovery path
Restore the original source policy if the trial permits a repeatable XP farm. Remove only expendable test blocks and keep player levels intact; a source-eligibility issue does not require deleting skill data.
References and related help
Check the maintainer reference: mcMMO documentation, mcMMO documentation.
Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.

Compare mcMMO diminished returns with a genuine XP failure
A reduced reward after repetitive play may be an intentional progression rule. Measure the pattern before treating it as lost player data or changing every skill multiplier.
Check the installed content
mcMMO progress belongs to player data, while its configuration controls future skill behaviour. Preserve both before changing progression rules. Match the installed release when checking permissions and configuration; current configuration references identify changes that require a full server restart.
Work through the change
Record the affected skill, repeated activity and when its XP changed. Save the experience configuration and note the account bonuses and party state during the report.
Check whether your installed release enables diminished returns or another activity limit for that situation. Use its documented thresholds and timing rather than assuming values from another server.
Reproduce a small controlled sequence on staging with a fresh test state and a normal account. Record the reward over the sequence and compare a different eligible activity.
Apply one documented staging adjustment only if the rule conflicts with your intended progression. Restart normally where the configuration reference requires it, then repeat the same sequence.
Verify the result
The change in reward should follow an identifiable configured rule or expose a separate fault. The comparison activity should help show whether the whole skill is unavailable or only repetitive gains are reduced.
If the result differs
If rewards stop immediately for every activity, inspect permissions and loading errors instead of the return curve. If the pattern depends on a special account, compare its inherited multiplier settings.
Keep a recovery path
Restore the previous rule if the adjustment creates an easy repeatable XP loop. Retain the measurements and preserve player progress; do not compensate or reset levels until the cause and affected period are established.
References and related help
Check the maintainer reference: mcMMO documentation.
Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.

Reduce mcMMO notification noise without changing skill progress
Skill notifications can overwhelm chat even when progression works normally. Identify the message source before disabling skill features or changing rewards to quiet the display.
Check the installed content
mcMMO progress belongs to player data, while its configuration controls future skill behaviour. Preserve both before changing progression rules. Match the installed release when checking permissions and configuration; current configuration references identify changes that require a full server restart.
Work through the change
Capture the exact message and activity that produces it. Record whether it appears in chat, an action bar or another display and whether all players see it.
Consult the installed configuration reference for the relevant display or notification setting. Keep experience values and player levels outside this presentation change.
Change one display setting on staging and repeat the triggering activity with an ordinary account. Compare the actual skill XP before and after so a quieter interface is not mistaken for disabled progression.
Check important ability or cooldown feedback still reaches the player. Test alongside your other action-bar or scoreboard plugin to identify competing display updates.
Verify the result
The intended notification should be quieter or hidden while the skill still gains XP normally. Players should retain the information required to understand active ability availability.
If the result differs
If messages remain, identify which plugin sends the captured wording before changing more mcMMO settings. If another display flickers, compare plugins individually on staging rather than disabling progression.
Keep a recovery path
Restore the original display settings if usability worsens, then restart normally where required by the installed configuration reference. Keep the player database unchanged because this task concerns presentation rather than progression data.
References and related help
Check the maintainer reference: mcMMO documentation.
Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.

Tune one mcMMO activity reward without resetting existing levels
A single activity can reward too much or too little XP while the rest of the skill feels right. Change its future reward independently of existing player progression.
Check the installed content
mcMMO progress belongs to player data, while its configuration controls future skill behaviour. Preserve both before changing progression rules. Match the installed release when checking permissions and configuration; current configuration references identify changes that require a full server restart.
Work through the change
Choose the exact skill source and write down the intended new reward. Save experience.yml and a completed player-data backup before editing progression configuration.
Locate the source entry in the reference for the installed release. Distinguish the activity reward from a global multiplier so the change stays limited to the intended behaviour.
Apply a small staging adjustment and perform a normal restart as required by the documentation. Compare the same activity with equivalent tools and account bonuses before and after.
Test another activity within the same skill and one unrelated skill. Confirm their baseline rewards remain unchanged and inspect a test player existing level after the restart.
Verify the result
The selected activity should award the intended new amount while other sources and stored levels remain intact. Record the measured difference so players can understand the balance change.
If the result differs
If all activities change, inspect the multiplier or enclosing section edited. If nothing changes, confirm the server loaded the intended file and source rather than repeatedly raising the configured value.
Keep a recovery path
Restore the saved configuration if the balance is unsuitable. Do not roll back the player database for a reward-rate change unless a separate reviewed recovery requires it; configuration and earned progression have different recovery implications.
References and related help
Check the maintainer reference: mcMMO documentation.
Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.

Test mcMMO party invitations before changing membership limits
A rejected party invitation can come from party state, permissions or a configured limit. Reproduce the rejection before removing members or recreating a production party.
Check the installed content
mcMMO progress belongs to player data, while its configuration controls future skill behaviour. Preserve both before changing progression rules. Match the installed release when checking permissions and configuration; current configuration references identify changes that require a full server restart.
Work through the change
Record the invitation message, party membership and the inviter role. Consult the installed party and permission references for leadership and membership requirements.
Create a disposable staging party with ordinary accounts. Confirm the leader can invite one eligible player and that an unauthorised member cannot perform restricted management actions.
Compare the failing production condition with the test, including membership limits, another party membership and any documented invitation restrictions. Change only the relevant staging setting.
Test acceptance, a deliberately ineligible invitation and departure from the disposable party. Check that membership counts and shared features update after a normal restart if configuration changed.
Verify the result
Eligible invitations should work within the intended limit, while rejected cases should have an explainable rule. Existing production membership and player skill levels should remain untouched.
If the result differs
If the test works but the reported invitation fails, compare account permissions and current party state. If every invite fails, inspect configuration load errors and leadership permissions before increasing limits.
Keep a recovery path
Restore the original membership setting and remove the disposable test party through supported commands when finished. Keep production party storage backed up and avoid deleting a real party as a diagnostic shortcut.
References and related help
Check the maintainer reference: mcMMO documentation, mcMMO documentation.
Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.