Menu
Troubleshooting Protect commands, permissions, and common permission confusion
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Troubleshooting format display, hover/click events, gradients, images in formats, and color permissions
Troubleshooting rule matching, replace vs rewrite, groups, and rule processing order
Troubleshooting channel system: messaging, range, modes, proxy, and Discord linking issues
Troubleshooting /tell, /reply, /ignore, PM formatting, social spy, and mail delivery
Troubleshooting command spy, transaction logging, and database log browsing
Troubleshooting Boss commands, PAPI placeholders, and permission issues
| name | commands |
| description | Troubleshooting Protect commands, permissions, and common permission confusion |
protect.bypass.scan is explicitly FALSE for OPs — unlike most permissions, OP status does NOT grant this. Must be granted via a permissions plugin. Alternatively set Ignore.Ops: true in settings.yml/protect edititem amount ≥384 triggers warning — because the default over-64 rule will confiscate items with 65+ stacks, and unnatural-stack catches anything over the natural maxprotect.group.{group} is for WorldEdit limits, NOT rule groups — two unrelated "group" concepts exist. WorldEdit groups use protect.group.{name} permission mapped to WorldEdit.Total_Limit config. Rule groups use ignore perm operators for bypass. Major confusion sourcespigot.yml stats.disable-saving: false — if stats saving is disabled, playtime tracking is unavailable and require/ignore playtime operators will throw an error