Everything Voxen can do

01 — Getting started

From zero to a project

Voxen turns a plain-English description into a working Minecraft plugin: it writes the Java, wires the plugin.yml, and compiles a.jar you can drop straight into your server. No Java toolchain, no IDE, nothing to install.

1. Create an account

Sign up with an email and password from the landing page. Your projects are saved to the cloud and tied to your account — you can pick them up from any device.

2. Create a project

Every project targets one server platform and one Minecraft version:

• Name — what you'll see on your dashboard. It also seeds the plugin ID.
• Software — Paper (recommended), Spigot, or Purpur.
• Version — from 1.8.8 up to 1.21.x. Pick the version your server actually runs.

Voxen scaffolds the project for you: a main class extending JavaPlugin, a plugin.yml, and a pom.xml already configured with the right dependencies for your target.

02 — Generating with AI

Describe it. Voxen writes it.

Simple mode

Every project opens in Simple mode: one prompt box. Describe the plugin and hit generate — Voxen writes the classes, registers the commands, and updates the plugin.yml.

What makes a good prompt

• Name the commands you want (/home, /sethome) and what each one does.
• Spell out the rules: cooldowns, permissions, costs, limits per player.
• Describe the edge cases you care about: what happens on death, on world change, for ops.

Prompt Architect

Only have half an idea? The wand button next to the prompt box opens the Prompt Architect: give it "something with kits" and it produces a full technical spec — commands, permissions, edge cases — that you can review and send to the generator.

03 — The editor

A real IDE in the browser

Switch to Code view from the toolbar to open the full workspace: file tree on the left, the Monaco editor (the same engine as VS Code) in the middle, AI chat on the right.

• File tree — create, rename, and delete files and folders. Java package folders collapse into dotted paths, like a real IDE.
• Tabs & search — open multiple files, search inside the active file with match navigation.
• Format — one click re-indents the active Java file.
• Auto-save — every change is saved to the cloud about two seconds after you stop typing. The save indicator in the toolbar tells you where you stand.
• Download .zip — export the full source tree at any time; the code is yours.

04 — AI tools

Four AI tools, one workspace

AI chat

The assistant in Code view edits the project with you: ask for a new feature, a change, or a refactor in plain English and it updates the relevant files. It keeps the last few messages as context, so you can iterate — "now make the cooldown configurable" just works.

Quick actions

With a file open, three one-click actions appear above the chat input:

• Explain — a plain-English walkthrough of what the open file does.
• Optimize — rewrites the file for cleaner, faster code without changing behavior.
• Fix Bug — hunts for defects in the file and applies a minimal, targeted fix.

AI Code Audit

Analyze Code in the editor toolbar scans the open file and reports findings by severity — CRITICAL, WARNING, INFO. Every finding has a Quick Fix button that patches just the lines involved.

05 — Building the .jar

From source to .jar

Build .jar runs a real Maven build on Voxen's servers, compiling your project against the actual Spigot or Paper API for your chosen version. The build terminal streams the log; on BUILD SUCCESS you download the .jar directly.

Installing on your server

When the build fails

A compilation error shows the exact Maven output in red. Hit Quick Fix with AI and the error log is sent back to the model, which patches the code and lets you rebuild.

06 — Plugin Porter

Update a plugin you already have

The Plugin Porter takes an existing plugin — even one you only have as a compiled .jar — and moves it to another Minecraft version. It's made for the classic situation: you update your server and a plugin you rely on stops loading.

How it works

• Import — hit Import plugin on your dashboard and upload a .jar (Voxen decompiles it back to readable Java) or a .zip with the source. Pick the target platform and version.
• Port — the AI rewrites the code for the target API: renamed events, removed methods, material names across the 1.13 flattening, api-version, dependencies. You get a report of every change. A port costs 1 generation.
• Rebuild — the result is a normal Voxen project. Build it, download the new .jar, and keep editing it with the AI like any other project.

What to expect

• Obfuscated jars are declined. Many premium plugins are obfuscated on purpose; decompiling them yields nothing useful, so Voxen detects and rejects them upfront.
• NMS plugins port partially. Plugins that reach into Minecraft internals (net.minecraft) are version-locked by design — Voxen warns you and does what it can, but expect manual follow-up in the editor.
• Decompiled code looks different. Comments and variable names are lost in compilation; the recovered code is functionally equivalent but less pretty than the original source.

07 — Project settings

plugin.yml without the YAML

The Settings view is a GUI over your plugin's metadata. Everything you set here is written into plugin.yml automatically and stays in sync:

• General — plugin ID, version, author, API version, and the main class path.
• Commands — register /commands with a description and permission node each, without touching YAML syntax.
• Danger zone — delete the project permanently. There is no undo.

08 — Compatibility

Version-aware by design

Minecraft's plugin API has changed a lot over the years. Voxen doesn't generate one-size-fits-all code — it targets the exact platform and version you picked:

• Materials — before 1.13 ("the Flattening") it uses legacy names like Material.WATCH; on 1.13+ it uses modern ones like Material.CLOCK and the BlockData API.
• Chat & colors — legacy ChatColor below 1.16, BungeeCord hex colors on Spigot 1.16+, and the native Adventure API with MiniMessage on modern Paper and Purpur.
• Dependencies — the pom.xml pins the right API artifact and Java toolchain for your target.

Supported today: Spigot, Paper, and Purpur, from Minecraft 1.8.8 to 1.21.x.

09 — Limits & ownership

Plans, limits & your code

Plans & generations

The free plan includes 5 full generations and 1 project — enough to build and ship a real plugin. Starter (€7.99/month) includes 150 generations per month; Pro (€14.99/month) includes 500, both running on a premium AI model with automatic fixing of build errors. Only full plugin generations consume your allowance: edits, explanations, code audits, and builds are unlimited on every plan. Your allowance resets on each billing cycle, and you can cancel anytime from Plans & Billing.

BYOK — bring your own key

BYOK (€3.99/month) is our cheapest plan: generations are unlimited and run on your own OpenRouter, NVIDIA, or Google AI Studio API key, so the model usage is billed by your provider at their rates, not by us. Before checkout you connect your key in a short wizard that validates it live against the provider; it's then stored encrypted server-side and never sent back to your browser. If your key stops working (revoked or out of provider credit), generations fall back to the free model until you replace it from Plans & Billing.

Ownership

Everything Voxen generates for you — source code and compiled .jar — is yours. Use it, modify it, ship it on any server, commercial or not. Export the source as a .zip whenever you want.

Found a bug? Want a feature?

Use the Feedback button in the app header. It goes straight to the person building this.