skills.rest
kangarko
kangarkoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

rules-scanning

Diagnose Protect plugin rule-scanning failures by verifying unique rule names and item casing.

Updated Feb 15, 2026
Search Tags:#debugging#plugin#diagnose#minecraft#rule-scanning#confiscation
One-click install
npx skills add https://github.com/kangarko/ai-support --skill rules-scanning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rules-scanning
Source: https://github.com/kangarko/ai-support/tree/main/projects/protect/skills/rules-scanning
Command: npx skills add https://github.com/kangarko/ai-support --skill rules-scanning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Troubleshooting rule matching, scanning triggers, and item confiscation issues in the Protect plugin. This Skill guides operators to diagnose why a rule does not trigger or why items are confiscated incorrectly, helping shorten incident resolution time.

Core Features & Use Cases

  • Diagnostic Flow: follow a structured troubleshooting sequence to verify unique rule names, correct item naming (CASE-SENSITIVE UPPER_CASE Bukkit names), and ignore settings.
  • Consistency checks: ensures global uniqueness of rule names across all .rs files and checks for common pitfalls with confiscation thresholds.
  • Practical use: applies during QA or live support when rule-scanning misfires, enabling targeted debugging of plugin rule logic.

Quick Start

Enable Debug: [scan, operator] and verify each of the following: rule names are globally unique across ALL .rs files, material names match exactly using UPPER_CASE, and Ignore settings are not suppressing the scan.

Frequently Asked Questions about rules-scanning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why are rule scanning triggers failing to confiscate items in my Protect plugin?▼

Rule scanning triggers fail when material names do not match Bukkit's UPPER_CASE identifiers or ignore configurations suppress the scan. Enable Debug scan mode to troubleshoot the diagnostic flow and verify exact material name casing.

How do I debug incorrect item confiscation in Minecraft Protect plugin rules?▼

Debug incorrect item confiscation by enabling Debug operator mode to inspect the diagnostic flow. Check that rule names are globally unique across all .rs files and confirm ignore settings are not blocking the trigger.

What is the correct format for material names in Protect plugin rule definitions?▼

The correct format for material names in Protect plugin rule definitions is Bukkit's UPPER_CASE identifiers. Material name casing is case-sensitive and must match exactly to ensure rule scanning triggers match items correctly.

Do I need unique rule names across all .rs files for rule scanning to work?▼

Yes, you need globally unique rule names across all .rs files for rule scanning to work correctly. Duplicate rule names cause conflicts in the diagnostic flow and can prevent triggers from firing or confiscating items accurately.

Rule scanning not working after checking material names, what else should I verify?▼

If rule scanning is not working, verify that ignore configurations are not suppressing the scan. Additionally, ensure Debug scan and operator modes are enabled to output diagnostic flow data and check confiscation thresholds.

Related Skills

Explore More Software Engineering Skills→
the-perfect-developerthe-perfect-developer
11

rules-creation

Generate AGENTS.md and opencode.json configurations for OpenCode rules.

Community
Intermediate
blueman82blueman82
1

convergence-debugger

Diagnose deliberation convergence failures and output actionable remediation reports.

Community
Advanced
oaknationaloaknational
31

code-style

Enforce TypeScript coding conventions and project structure for Oak AI applications.

Official
Intermediate
sorodriguezzsorodriguezz

Developing Business Rules

Create and manage business rules and rule sets for dynamic logic execution.

Community
Advanced