Turn off CoreProtect inspection without granting rollback access
Inspection mode changes what happens when staff click blocks, so leaving it enabled can confuse routine building. Teach inspectors the toggle while keeping world-changing recovery permissions separate.
Follow the procedure
- Check the installed CoreProtect permissions reference and identify the inspector capability. Do not grant rollback, restore, purge or administrative access simply to let a helper inspect a block.
- Use a non-operator helper account with the intended role. Run
/co inspector the documented/co ialias and click a disposable test block. - Confirm the expected inspection output appears. Check whether the helper’s ordinary block action is replaced by inspection so they understand why clicking behaves differently.
- Run the same inspection toggle again to disable it. Click another test block and verify the account has returned to its normal allowed building behaviour.
- Test reconnect behaviour on your installed release and record whether inspectors must toggle the mode again. Avoid assuming state persists or resets identically across plugin versions.
- Confirm the helper cannot invoke recovery or purge operations. Keep the staff guide clear that a block-history result is evidence for review, not permission to alter another player’s build.
Check the result
The helper can enter inspection, read the expected block history and leave inspection cleanly, while recovery commands remain denied. A successful read demonstrates the inspector role; normal block interaction after the second toggle demonstrates that the apparent building problem is resolved.
If the result is wrong
If clicking still does not behave normally, check region protection, game mode and other inspection plugins before changing CoreProtect permissions. If history is unavailable, verify logging and retention. Do not grant operator status or reset player data to clear an inspection-mode misunderstanding.