Overview

1. Create Your Account

Click Get Started on the home page. After agreeing to the Terms of Service, sign up with Google or your email address. You'll land directly in the chat, ready to build your first plugin.

2. Build Your First Plugin

Start a chat and describe what you want. The agent builds, tests, and reviews your plugin. Download the JAR when it's ready.

A free account lets you scan plugins with Plugin Inspector. To build plugins in chat, subscribe to Iron or Diamond from the Usage page in your profile menu.

3. Subscribe When You're Ready

Open your profile menu, choose Usage, and pick a plan. Iron gives you 400 monthly AI credits with an advanced assistant. Diamond gives you 800 monthly AI credits with a premium assistant and longer JAR retention.

Both plans include private plugins, Server Dock, Plugin Inspector, and as many chats as you like. Payments are processed by Paddle.com Market Limited. Cancel any time from the same Usage page.

Describe Your Plugin

Start a chat and tell the agent what you want. Custom commands, game mechanics, admin tools, minigames — describe it in plain language and the agent handles the rest.

Example: “Create a plugin that gives players a speed boost when they eat golden apples, with a configurable duration and cooldown.”

Download the JAR

The agent writes the code, compiles it, and delivers a JAR file complete with plugin.yml, config files, permissions, and commands. Download it from the chat's three-dot menu in the sidebar.

Install It on Your Server

With genesix Runtime connected, click Install plugin on the server's page and restart it from genesix. Or copy the JAR to your server's /plugins folder yourself and restart. Your plugin is live as soon as the server is back up.

Iterate Through Chat

Keep chatting to refine your plugin. Add features, tweak behavior, adjust configs — each iteration builds on the last until it's exactly what you need.

1. Static checks

After the plugin compiles, automated checks look for Paper-specific problems such as slow work on the main thread, duplication exploits, and leftover tasks after disable.

2. Sandbox live test

Your plugin is started on a real Paper server in an isolated, disposable cloud sandbox that never touches your own server or data, matched to your Minecraft version (Paper 1.20.x, 1.21.x and 26.x). A test player joins and plays it: runs its commands as a regular player and as an operator, tries subcommands with sensible arguments, opens and clicks its menus, and joins and leaves. Then the server is shut down cleanly.

If the plugin crashes, freezes the server, or fails to start or stop, the agent receives the exact error and fixes it before delivery. The test runs automatically after a successful build, usually in well under a minute; there is nothing to set up.

What it does not cover: it checks that the plugin runs without errors, not that it behaves exactly as you described. Plugins that require another plugin to be installed (hard dependencies) and a few edge cases are not sandbox-tested. For 26.x the sandbox test currently covers startup, background tasks and shutdown, without a test player yet.

3. Review

A dedicated review step checks the plugin against your request and a checklist covering persistence, event handling, and API correctness. Testing it on your own server and telling the agent what to change remains the final check.