VyroAI

Loading...

Cloud Build

Compile your Minecraft plugins and mods to a .jar file without installing anything.

How it works

When you click Build, VyroAI sends your project to a dedicated build server that runs Gradle or Maven and compiles it to a .jar file. You never need Java, Gradle, or Maven installed on your machine.

How to build

  1. Open your plugin or mod project in the IDE
  2. Click “Build & Export” in the toolbar
  3. The build log streams live in the chat — green means success
  4. Download the .jar from the build output panel

The hammer icon in the Code Studio toolbar. This is the button step 2 means.

Build fails?

If compilation fails, the error is shown inline. Click Auto-Fix to let the AI read the build log and repair it. It fixes every root cause in that build, not one file at a time — so seeing several files change in one round is the tool working, not misbehaving.

In Chat mode that Auto-Fix button reads Plan Fix instead: it works out the fix and talks it through without touching your files. Switch the mode above the message box to Build if you want it applied.

The build check after a generation

You do not always have to press Build to find out whether new code compiles. After a generation that writes files in a plugin or mod project, VyroAI compiles the project by itself — the same build the Build & Export button runs — before it hands the project back. The reply always carries one line about it:

When the first compile fails, VyroAI can spend up to two repair rounds on it: the AI fixes the files the errors point at, and the project is compiled again after each round. If the repair leaves things worse than they started, every file is put back exactly as it was. A run you stop with Stop gets no build check.

Once the project compiles — on the first try or after repair — there can be one more round. If the post-build checks find something that would stop part of it working on a server (a config key the code reads but never defines, a listener or command that is never registered, a requirement that was not built, a security hole), the AI fixes it and the project is compiled again. A second line then follows the build check: Checks: fixed N problems the post-build checks found ✓ — and your project still compiles. If that round breaks the build or fixes nothing, the files are put back and it is not charged; if its changes are kept, it is billed like a repair round.

Repair rounds are billed, and your switches do not stop them

A repair round whose changes are kept is billed onto the same run, like the rest of the generation, so the credit total under that reply includes it. A round that changed nothing, or whose work was put back, is not charged.

The two switches under the Build & Export arrow do not control this check. Stop on error (no auto-fix) only stops the Auto-Fix your browser would start by itself after an automatic build. It does not stop the repair rounds on the server, and there is no switch for them on your side.

When the fix is a library we do not have yet

Some build failures are not something any rewrite can repair: the library your code needs is simply not there to download. When VyroAI reads that in the log, the failed-build card grows a Request library button and puts it first, ahead of Auto-Fix — because asking for the library is the fix, and a code rewrite is the fallback.

Pressing it opens Request a library with the coordinate from the error already filled in. Add a sentence about what you need it for, and a repository link if you have one, and send it: it goes into the same review queue a VyroAI developer works through. You have to be signed in — it says "Please sign in first" if you are not — and asking for something already requested answers "That library has already been requested." A sent one answers "Request sent — an admin will review it."

The button is deliberately not offered for four failures that look identical in the log:

In all four cases requesting a library would be a dead end, so the card leaves Auto-Fix in the primary spot instead.

The version card — when "cannot find symbol" is really a wrong version

The compiler never says wrong version. When a library is pinned to a version that does not exist, or to one that does not have the class your code uses, javac says cannot find symbol — which reads exactly like the AI wrote broken code.

Cloud Build reads the failure for that case and, when it finds it, the failed-build card gains an amber version card above the folded details, one per library:

Two things sit under it. Fix version swaps that one version string in your build file — a literal text edit, no AI run and no credits — and then tells you set to … Build again. Open dependency page opens the library's own page in a new tab, where every published version is listed, for when the suggestion is not the one you want.

The button is only drawn when there is a patch to apply; if the file has changed since the build, pressing it says the file no longer contains that version — edit it by hand.

"This project compiles against Spigot, but…" — the platform notice

A build can stop and tell you your plugin has outgrown the server API it declares: you picked Spigot, but the code uses something only Paper provides. VyroAI does not switch the platform for you, on purpose — swapping the API behind your back can change how your plugin behaves at runtime without producing a single error, so the build says so and leaves the decision to you.

You have two ways forward, and the message names both:

If you declared nothing at all, nothing is blocked — the build picks the API your code needs and tells you which one the jar ends up requiring.

What else is under the button

Build & Export is a split button: the wide half always compiles, and the small arrow beside it opens the menu. Clicking the label or the hammer never opens a menu by accident.

In the menu:

Neither switch touches the build check on the server described above.

Compiling it yourself instead

You never have to use the cloud build. Download with Build Scripts gives you a zip that compiles on your own machine with the standard tools:

The same download offers a step-by-step dialog with these commands ready to copy. You need Java and the build tool installed locally, which is exactly what the cloud build exists to spare you — but for an air-gapped server or a CI pipeline, this is the way.

Never paste Gradle or Maven terminal commands into the chat and ask the AI to run them — it cannot execute shell commands. Use the Build button instead.

Try it now: Describe your plugin and see the plan, free and with no account. Open the plugin generator

Where to next

Also linked from this page: Build History — every past build with its result, and the ones worth starring

13 of 22 in Minecraft Studio · Last checked 12 September 2026 · Previous: Folia Plugins on Paper