Best Practices
These tips will help you get better results from the agent and avoid common pitfalls. The key principle: one plugin, one job.
Think Single-Purpose
The best plugins do one thing well. Real Minecraft servers don't run on a single monolithic plugin — they combine focused tools that each handle a specific domain. LuckPerms handles permissions. LiteBans handles punishments. Vault handles economy. Your custom plugin should follow the same philosophy.
✅ Good scope
- "A bounty system where players place bounties on each other with a GUI leaderboard"
- "A crate and key system with animated opening and weighted rewards"
- "A custom enchantment plugin that adds 5 new enchants with visual effects"
- "A staff freeze command that prevents movement and logs the interaction"
⚠️ Too broad
- "A full network core with permissions, punishments, economy, essentials, and a web panel"
- "Replicate the entire EssentialsX plugin"
- "Build me a hub system with cross-server teleportation, queues, and a lobby selector"
These are multi-plugin systems that take teams months to build. Break them into focused pieces instead.
Describe What Players Actually Do
The more concrete your description, the better the first result. Describe the actual player experience — what commands they type, what they see, what happens when they click.
❌ Too vague
"Make a shop plugin"
The agent doesn't know what kind of shop, what currency, or how players interact with it.
✅ Clear and actionable
"A shop plugin with /shop that opens a category GUI (weapons, armor, food, blocks). Each category shows items with prices. Players click to buy using Vault economy. Items and prices are configurable in config.yml. Add /sell hand to sell the item you're holding."
Tell the Agent What's Already on Your Server
If your server already runs plugins that your new plugin should work with, mention them in your prompt. The agent will make sure they play nicely together — and your plugin will still load fine even if one of those plugins is removed later.
Example: "I use Vault for economy and PlaceholderAPI for scoreboards. My new bounty plugin should charge players through Vault and show their bounty count on the scoreboard."
Common plugins to mention: Vault (money), PlaceholderAPI (scoreboards/tab), Citizens (NPCs), LuckPerms (ranks/groups), WorldGuard (protected regions), MythicMobs (custom mobs).
Iterate Instead of Overloading
Start with the core mechanic. Once it works, add features in follow-up messages. This gives you a working plugin faster and lets you test each piece before adding complexity.
Recommended flow
- Message 1: Core mechanic — "A bounty plugin where players place bounties and collect them on kill"
- Message 2: Polish — "Add a GUI with player heads sorted by reward amount"
- Message 3: Config — "Make bounties expire after 24 hours, add a minimum amount config option"
Use Established Plugins for Infrastructure
For core server infrastructure — permissions, economy, punishments, essentials commands — use battle-tested community plugins. They have years of edge-case handling, security patches, and community support. Use genesix Blocks for the custom gameplay and features that make your server unique.
Recommended stack
Use existing plugins for:
- Permissions (LuckPerms)
- Economy (Vault + EssentialsX)
- Punishments (LiteBans)
- Essentials commands (EssentialsX)
- World management (Multiverse)
Use genesix Blocks for:
- Custom minigames
- Unique server mechanics
- Custom GUIs and shops
- Event plugins and seasonal content
- Glue plugins that tie your stack together
When Something Doesn't Work
"It doesn't work" is hard for the agent to act on. "I typed /bounty but it didn't take coins from my balance" gets you a fix in one message.
What to tell the agent
- What you typed or clicked
- What happened (or didn't happen)
- What you expected to happen instead
- Any red text from your server console — paste it or screenshot it
Tip: Use the Fix a Bug prompt template — it walks you through exactly what to include.