Menu
Troubleshooting WorldEdit limits, global ignore settings, and after-scan hooks
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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 | worldedit-config |
| description | Troubleshooting WorldEdit limits, global ignore settings, and after-scan hooks |
protect.group.{group} confusion with rule groups — two unrelated "group" concepts. WorldEdit groups = permission-based block limits. Rule groups = reusable operator sets in group.rs. Major user confusion sourceIgnore.Worlds validates world names on load — if a listed world isn't loaded when Protect starts, you get errors. Ensure Protect loads AFTER world management plugins (Multiverse, etc.)After_Scan only fires for confiscate/clone actions — not for then command. Users report "After_Scan commands not running" for rules that only use then command — those run directly from the rule, not via After_ScanProtectCheck tracks already-sent notify messages per scan to prevent duplicates. If seeing duplicates, multiple scans may be triggering simultaneously (e.g. join + inventory open)