allaymc-plugin-dev
Build AllayMC Plugins
AllayMC plugin setup can be hard to align across Gradle, metadata, lifecycle APIs, and server behavior. This skill guides Claude, Codex, and Claude Code through template-based plugin development and troubleshooting.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "allaymc-plugin-dev". Create a new plugin called WelcomePlus for AllayMC.
Expected outcome:
- A concise setup plan for the Java template.
- Recommended package, group, plugin entrance, author, and version values.
- A list of project files to update and local build commands to run.
Using "allaymc-plugin-dev". Add a command and listener to my existing plugin.
Expected outcome:
- A targeted change list for command registration and event listener wiring.
- References to the relevant bundled Allay tutorials.
- Validation steps for build, server startup, and runtime behavior.
Using "allaymc-plugin-dev". My plugin jar builds but does not load on the server.
Expected outcome:
- A troubleshooting checklist for plugin entrance, API version, jar location, and package names.
- Likely causes ranked by evidence from the provided files or logs.
- Next commands and file checks to confirm the fix.
Security Audit
Low RiskStatic analysis reported many high-risk patterns, but manual review found they come from LGPL license prose, Markdown code formatting, and legitimate git or Gradle workflow examples. No prompt injection, credential access, data exfiltration, obfuscated code, or malicious network behavior was found in LICENSE, README.md, or SKILL.md. The skill is low risk because it can guide users or agents to run standard development commands and read local reference paths.
Low Risk Issues (4)
Risk Factors
⚙️ External commands (4)
📁 Filesystem access (3)
Quality Score
What You Can Build
Start a New Plugin
Create a plugin skeleton that keeps the main class, package name, Gradle group, and plugin metadata consistent.
Add Server Features
Add commands, events, scheduled tasks, configuration, permissions, forms, or persistent data using the bundled Allay tutorials.
Update an Existing Plugin
Compare an existing plugin with the template, update API versions, and troubleshoot loading or class resolution failures.
Try These Prompts
Use allaymc-plugin-dev to create a new AllayMC Java plugin named <name>. Set the group, package, author, version, and plugin entrance consistently.
Use allaymc-plugin-dev to add a command and an event listener to my existing plugin. Follow the bundled Allay tutorials and explain each file change.
Use allaymc-plugin-dev to migrate this plugin to Allay API version <version>. Check Gradle metadata, plugin entrance, imports, and lifecycle usage.
Use allaymc-plugin-dev to diagnose why this plugin fails to load. Review my Gradle file, plugin metadata, main class name, jar output, and server log excerpt.
Best Practices
- Keep the Gradle group, package name, plugin entrance, and compiled main class aligned.
- Use the bundled template and tutorials before inventing custom project structure.
- Build locally and test on an Allay server after every metadata or lifecycle change.
Avoid
- Do not change the API version without checking imports, metadata, and lifecycle compatibility.
- Do not copy jars manually without confirming the shaded output path and plugin directory.
- Do not assume nullable behavior unless the Allay Javadoc explicitly permits null values.