Hey everyone,
I built something I want to share with this community — it's called genesix Blocks, and it's an AI agent that generates Paper plugins from plain language descriptions.
You describe what you want in a chat interface. The agent designs the plugin, writes the Java, compiles it with Gradle, and hands you a JAR. You drop it in /plugins and reload.
The agent produces plugin with production quality: proper async threading, atomic economy transactions, concurrent player caches, clean resource lifecycle, all compiled and reviewed.
Link: https://blocks.genesix.app
The problem it solves
If you run a server, you've been here: you need a specific mechanic — a bounty system, a spleef arena, a custom join message — and it doesn't exist on SpigotMC or Modrinth. You can commission a developer, but that takes time and money. Or you can try to learn Java, but that's a whole journey when you just need one plugin by Saturday.
If you're a developer, you've been on the other side: you know exactly how to build it, but you're tired of wiring up the same boilerplate — the SQLite connection, the command executor, the config loader, the event listeners. You want to focus on the interesting parts, not the scaffolding.
Blocks tries to help both sides.
For server owners
You don't need to know Java. Describe what you want like you'd explain it to a developer you hired:
"Create a Bounty Hunter plugin. Players place bounties on each other, track kills and earnings, show a GUI with player heads sorted by reward amount."
The agent builds the full plugin — commands, permissions, config.yml, SQLite persistence, GUI — and compiles it. You get a JAR.
If something doesn't work right, paste the error or describe what went wrong in the same chat. The agent reads it and delivers a fixed version. You can keep iterating until it's right.
For developers
The agent understands Paper API patterns — async database operations, thread-safe caching, proper event lifecycle, soft-dependency wiring, Adventure text components. You can be specific:
"Create a quest system using Citizens NPCs. The Lumberjack NPC wears leather armor, holds an iron axe, and gives a quest to chop 20 oak logs. Track progress in SQLite. Citizens is a soft dependency — if not installed, disable NPC features but still load the plugin."
It handles the boilerplate. You focus on the architecture decisions. Currently JAR-only output — source code export is something we're working on, and would like to hear from you how would you like to have it (downloadable source code, GitHub integration, etc).
What it actually produces
Compiled JAR targeting Paper 1.21.1 through 1.21.11 (you pick the version)
plugin.yml with commands, permissions, and descriptions
config.yml with defaults and customizable messages
SQLite persistence where needed
Soft-dependency patterns for Citizens, PlaceholderAPI, Vault, LuckPerms, ProtocolLib, and others
Every plugin goes through a review step before you get the JAR — static analysis catches threading issues and null safety problems at compile time, then a dedicated reviewer checks persistence, event handling, and API correctness.
What people are building
A few real examples from the plugin ideas library:
Bounty Hunter — economy, GUI with player heads, SQLite, kill tracking, configurable messages. One prompt. (source on GitHub)
Spleef Arena — lobby, BossBar countdown, spectator mode, inventory save/restore, floor reset
NPC Quest System — Citizens integration, progress tracking, item turn-in, action bar updates
Staff Disguise Tool — ProtocolLib packet-level mob disguises, per-player rendering
Boss Fight Event — display entities for floating health bars, animated damage numbers, phase transitions
There's a full plugin ideas gallery with prompts you can copy and paste.
Pricing
Free tier to start, no credit card. Paid plans for more messages and higher-quality AI models. Details on the site.
Honest caveats
No one is perfect. Complex plugins sometimes need a couple of iterations to get right. The agent is good at self-correcting when you give it feedback.
Source code export isn't available yet. You get the JAR. If that's a dealbreaker for you, fair enough — we're working on it, and would love to hear from you on preferred way to access the plugin source code.
It targets Paper post-hard-fork with Mojang mappings. Spigot and CraftBukkit aren't supported.
No raw NMS access. The agent builds on the Paper API and uses ProtocolLib for packet-level features (fake entities, disguises, per-player scoreboards). If your plugin idea requires direct net.minecraft.server internals — custom network protocols, deep world-format manipulation, or bypassing the Paper API — this isn't the right tool for that yet. That said, NMS support is something we can add to the agent's capabilities if there's demand. If that's something you'd use, let us know — it helps us prioritize.
If you try it, I'd genuinely appreciate feedback — what worked, what didn't, what you wish it could do. You can reach us on our Discord or at [email protected].
Thanks for reading.
I built something I want to share with this community — it's called genesix Blocks, and it's an AI agent that generates Paper plugins from plain language descriptions.
You describe what you want in a chat interface. The agent designs the plugin, writes the Java, compiles it with Gradle, and hands you a JAR. You drop it in /plugins and reload.
The agent produces plugin with production quality: proper async threading, atomic economy transactions, concurrent player caches, clean resource lifecycle, all compiled and reviewed.
Link: https://blocks.genesix.app
The problem it solves
If you run a server, you've been here: you need a specific mechanic — a bounty system, a spleef arena, a custom join message — and it doesn't exist on SpigotMC or Modrinth. You can commission a developer, but that takes time and money. Or you can try to learn Java, but that's a whole journey when you just need one plugin by Saturday.
If you're a developer, you've been on the other side: you know exactly how to build it, but you're tired of wiring up the same boilerplate — the SQLite connection, the command executor, the config loader, the event listeners. You want to focus on the interesting parts, not the scaffolding.
Blocks tries to help both sides.
For server owners
You don't need to know Java. Describe what you want like you'd explain it to a developer you hired:
"Create a Bounty Hunter plugin. Players place bounties on each other, track kills and earnings, show a GUI with player heads sorted by reward amount."
The agent builds the full plugin — commands, permissions, config.yml, SQLite persistence, GUI — and compiles it. You get a JAR.
If something doesn't work right, paste the error or describe what went wrong in the same chat. The agent reads it and delivers a fixed version. You can keep iterating until it's right.
For developers
The agent understands Paper API patterns — async database operations, thread-safe caching, proper event lifecycle, soft-dependency wiring, Adventure text components. You can be specific:
"Create a quest system using Citizens NPCs. The Lumberjack NPC wears leather armor, holds an iron axe, and gives a quest to chop 20 oak logs. Track progress in SQLite. Citizens is a soft dependency — if not installed, disable NPC features but still load the plugin."
It handles the boilerplate. You focus on the architecture decisions. Currently JAR-only output — source code export is something we're working on, and would like to hear from you how would you like to have it (downloadable source code, GitHub integration, etc).
What it actually produces
Compiled JAR targeting Paper 1.21.1 through 1.21.11 (you pick the version)
plugin.yml with commands, permissions, and descriptions
config.yml with defaults and customizable messages
SQLite persistence where needed
Soft-dependency patterns for Citizens, PlaceholderAPI, Vault, LuckPerms, ProtocolLib, and others
Every plugin goes through a review step before you get the JAR — static analysis catches threading issues and null safety problems at compile time, then a dedicated reviewer checks persistence, event handling, and API correctness.
What people are building
A few real examples from the plugin ideas library:
Bounty Hunter — economy, GUI with player heads, SQLite, kill tracking, configurable messages. One prompt. (source on GitHub)
Spleef Arena — lobby, BossBar countdown, spectator mode, inventory save/restore, floor reset
NPC Quest System — Citizens integration, progress tracking, item turn-in, action bar updates
Staff Disguise Tool — ProtocolLib packet-level mob disguises, per-player rendering
Boss Fight Event — display entities for floating health bars, animated damage numbers, phase transitions
There's a full plugin ideas gallery with prompts you can copy and paste.
Pricing
Free tier to start, no credit card. Paid plans for more messages and higher-quality AI models. Details on the site.
Honest caveats
No one is perfect. Complex plugins sometimes need a couple of iterations to get right. The agent is good at self-correcting when you give it feedback.
Source code export isn't available yet. You get the JAR. If that's a dealbreaker for you, fair enough — we're working on it, and would love to hear from you on preferred way to access the plugin source code.
It targets Paper post-hard-fork with Mojang mappings. Spigot and CraftBukkit aren't supported.
No raw NMS access. The agent builds on the Paper API and uses ProtocolLib for packet-level features (fake entities, disguises, per-player scoreboards). If your plugin idea requires direct net.minecraft.server internals — custom network protocols, deep world-format manipulation, or bypassing the Paper API — this isn't the right tool for that yet. That said, NMS support is something we can add to the agent's capabilities if there's demand. If that's something you'd use, let us know — it helps us prioritize.
If you try it, I'd genuinely appreciate feedback — what worked, what didn't, what you wish it could do. You can reach us on our Discord or at [email protected].
Thanks for reading.
- Type
- Offering
- Provided by
- Team
