CoreProtect Staff Reference
Public-safe technical notes for staff who configure or support CoreProtect on 1MoreBlock.
Verify destructive, economy-changing, permission-changing, and player-data commands against the installed build and an approved support case before running them.
Commands
Section titled “Commands”| Command | Permission | Purpose |
|---|---|---|
/co inspect | coreprotect.inspect | Toggles interactive inspection. |
/co lookup <parameters> | coreprotect.lookup | Queries logged actions. |
/co rollback <parameters> | coreprotect.rollback | Rolls back matching actions. |
/co restore <parameters> | coreprotect.restore | Restores a prior rollback. |
/co status | coreprotect.status | Shows CoreProtect status. |
Permissions
Section titled “Permissions”| Permission | Purpose | Suggested access |
|---|---|---|
coreprotect.inspect | Interactive inspection. | Moderation staff |
coreprotect.lookup | Log search. | Moderation staff |
coreprotect.rollback | World-changing rollback. | Senior staff only |
coreprotect.restore | World-changing restore. | Senior staff only |
Placeholders
Section titled “Placeholders”No plugin-owned placeholders were verified. PlaceholderAPI may still expose values through a separate expansion or an integrating plugin.
Configuration and integrations
Section titled “Configuration and integrations”- 1MB-AntiXRay and 1MB-XRayHunter use CoreProtect records for mining review.
- Use preview mode and narrow user/time/radius/action filters before rollback.
- Database retention and excluded actions affect what can be recovered.
Examples
Section titled “Examples”/co inspect/co lookup <parameters>/co rollback <parameters>Troubleshooting
Section titled “Troubleshooting”- Verify the world, radius, time expression, action, and user filters.
- Run a lookup or preview before rollback and record the command used.
- If data appears absent, check logging coverage and retention rather than broadening a rollback blindly.