How genesix Works
How a plugin gets built and checked, what Plugin Inspector and Server Dock do, and answers to the detailed questions.
Deep Minecraft Knowledge
Paper API, Events, Persistence, Architecture
A general-purpose coding agent doesn't know these Minecraft-specific failure modes until they surface in production. This agent is purpose-built for Paper: async database operations that keep your TPS stable, proper event lifecycle management, thread-safe player caching, atomic economy transactions, and clean resource cleanup on shutdown — baked in, not discovered the hard way. Your plugin is also started on a real server in a sandbox and played by a test player, then reviewed, before you get the JAR.
From Prompt to Plugin
Describe Your Plugin
Tell the agent what you want in plain language. Custom commands, game mechanics, admin tools, minigames - anything you can imagine for your server.
Get Your Plugin
The agent designs the architecture, writes the Java, and wires in the integrations your idea needs - Citizens, PlaceholderAPI, Vault, ProtocolLib, or any API you name. Before you see it, every build passes Minecraft-specific code checks and a final review, and most plugins also run through a live test on a real server in a disposable sandbox. You get a plugin that has already run on a server, not just code that compiles. Your players never meet the bugs we caught first.
Install It on Your Server
Three ways to get the JAR onto your server. Download it to your computer and place it in your plugins folder yourself. Install it remotely with genesix Runtime from Server Dock, in one click, with the previous version backed up automatically. Or upload it over SFTP straight to your server. Remote installs take effect at the next restart, which genesix can run for you.
Test & Iterate
Try it on your server, then come back to chat. Add features, fix behavior, tweak configs - each iteration builds on the last until it's exactly right.
Want to see how a conversation with the agent works? Time Travel takes a chat back to an earlier message, and Remix turns a finished plugin into the starting point for a new variant. Read the full chat guide →
Built for Production Servers
Every plugin is planned, coded, sandbox-tested on a real server (for most plugins), and reviewed against Paper API best practices. The agent is guided to follow these patterns (among others).
TPS-Safe by Default
Database reads and writes run asynchronously off the main thread. Your server tick rate stays stable even under heavy plugin load.
Thread-Safe State
Player caches use concurrent data structures with proper join/quit lifecycle. Economy operations are atomic — no double-spend, no race conditions.
Clean Shutdown
Plugins shut down cleanly on server stop or restart — tasks are cancelled, database connections are closed, and cached data is persisted so nothing is lost.
Clean Resource Lifecycle
NPCs, display entities, packet listeners, and scheduled tasks are tracked and cleaned up on disable. No orphaned entities after a restart.
Reviewed Before Delivery
Three stages before you get the JAR. First, static checks catch threading issues, null safety problems, and resource leaks at build time. Second, a sandbox live test starts your plugin on a real Paper server in an isolated, disposable cloud sandbox, separate from your own server and data, matched to your Minecraft version (1.20.x, 1.21.x and 26.x); a test player joins, runs its commands as a regular player and as an operator, tries subcommands, opens and clicks its menus, then leaves, and the server is shut down cleanly. If the plugin crashes, freezes the server, or fails to start or stop, the agent gets the exact error and fixes it before delivery. Third, a review step checks it against a checklist covering persistence, event handling, and API correctness. For 26.x the sandbox test currently covers startup, background tasks and shutdown, without a test player. Plugins that require another plugin to be installed and a few edge cases are not sandbox-tested, and the test confirms your plugin runs without errors, not that it does exactly what you asked; the review and your own testing cover that.
Third-Party Integrations
Tested with Citizens, PlaceholderAPI, LuckPerms, Vault, and ProtocolLib — but the agent can wire up any third-party API you ask for. Soft-dependency patterns so your plugin loads even if the dependency is missing.
Self-Healing Iterations
Build fails? The agent reads the compiler output and fixes it. Runtime error? Paste the stack trace in chat. The agent diagnoses the issue and delivers a fixed JAR in the next cycle.
A Minecraft-Specific Validation Catalog
Ask a generic coding agent to build this and you'll spend as much time debugging Paper-specific gotchas as you spent writing the prompt. Each genesix plugin goes through an extensive analysis review before it reaches you — not a generic Java linter with Minecraft branding, or generic LLM code review — every check targets real Paper-plugin pitfalls that only show up once a plugin is running a real server with real players on it.
A few examples, out of dozens in the catalog:
Main-thread database or network calls — flagged before they can freeze your server with 40 players online, not just when you're testing alone.
GUI click/drag duplication exploits.
Economy transactions that don't roll back cleanly on failure — no silently duplicated or vanished balances once real trades are happening.
Scheduled tasks and connections that aren't released on disable — leaked threads and open database handles pile up on servers that stay up for months; a weekend server never notices.
Permission nodes that don't match the commands they gate — matters the moment you have a staff hierarchy, not just op and non-op.
Removed or renamed Paper/Bukkit APIs — code that compiled fine last version and breaks silently the day you update.
Plugin Inspector
Know what a Minecraft plugin actually does before you install it.
Upload any Paper plugin JAR. genesix analyzes its security, network behavior, Minecraft API usage, threading, lifecycle, dependencies, and runtime risks — then generates a plain-language inspection report. No source code required.
- Analyzes the exact artifact you're about to install
- Detailed report explaining how findings will affect your server
Server Dock (beta)
Know what needs fixing before your players notice.
Add one small plugin to each Paper server and it links to genesix over a secure, outbound-only connection. No open ports, no panel passwords. genesix then checks each server's setup, watches how it runs, and tells you in plain language what needs you and how to fix it.
- Setup check: 24 checks on Java, memory, config files, plugins and crashes, based on Paper's own guides, each with the current value, the recommended one and how to change it
- Lag, memory and disk watched every minute, with what to do when something goes wrong
- A history of every plugin, config setting, server build and Java change, next to every crash and restart
- One-click install and updates of your plugins, with an automatic backup and one-click restore
- Remote restart with a countdown for players
Included with Iron (3 servers) and Diamond (8 servers).
Coming next
- AI root-cause analysis for crashes and lag, with fixes you approve
- Fleet-wide rollouts and config drift across your network
More Questions
Is my plugin tested in a sandbox on a real server?
Yes, for most plugins. After it compiles and passes static checks, it is started on a real Paper server matching your Minecraft version, in an isolated, disposable sandbox that never touches your own server or data, and a test player plays it before you get it. Plugins that require another plugin to be installed and a few edge cases are not sandbox-tested, and the test checks that the plugin runs without errors, not that it does exactly what you asked.
Can I edit the plugin after?
Keep chatting to add features, change behavior, or tweak config. Each message builds on the previous version of your plugin.
Will it conflict with my other plugins?
Plugins use soft-dependency patterns for third-party integrations — they load cleanly even if a dependency like Citizens or Vault is missing. The agent can integrate with any plugin API you specify, not just the ones listed on this page. If you hit a conflict, describe it in chat and the agent will fix it.
Can genesix install plugins on my server for me?
Yes. Add genesix Runtime to your Paper server once and it appears under Server Dock. From there, click Install plugin and pick any plugin you built: a new plugin goes into plugins/, an update into plugins/update, and both take effect at the next restart, which you can start from genesix with a countdown for your players. Every update backs up the previous version first, so you can restore it in one click. Server Dock is included with the Iron (up to 3 servers) and Diamond (up to 8 servers) plans.
Is it safe to connect my server to genesix?
genesix Runtime only makes an outbound, encrypted connection with its own certificate, so you open no ports and share no passwords. It sends server details: versions, the plugin list, selected settings from your config files, performance readings (lag, memory, disk, entity counts) and the player count. Never chat, player names or world files. You stay in control: /genesix disconnect or removing the JAR cuts it off, remote installs and restarts can each be turned off in its config, and removing the server in genesix revokes its identity.
Can it build a full network core or replicate an entire server setup?
Production networks use multiple specialized plugins working together — not one monolithic system. genesix Blocks builds focused, single-purpose plugins that do one thing well. For core infrastructure (permissions, economy, punishments), use established community plugins. Use genesix Blocks for the custom gameplay and features that make your server unique.
Still unsure? Check the full documentation, the best practices guide, or contact support.
Describe the plugin your server is missing.
genesix builds it, checks it, and installs it. No Java required.
Build Your First Plugin