VyroAI

Loading...

Which Servers Your Plugin Runs On

Nine platforms you can tick, why ticking several is normal, and when you end up with two jars.

One question, as many answers as you like

In Project Settings → Build there is a question called What does this target?. It only appears once you switch off Use global build settings at the top of that tab, which is on by default, so switch that off first. It is not a dropdown where you pick one thing — you tick every platform your plugin is meant for, and ticking several is the normal case rather than the clever one.

VyroAI writes the plugin against what you ticked, and the AI is told the same list, so it stops guessing your platform from message to message.

The nine you can tick

PlatformWhat it is
**Bukkit**The original plugin API. Old, and still what some servers run
**Spigot**Bukkit plus Spigot's extras — the widest audience, because a Spigot plugin also runs on Paper
**Paper**Spigot plus the Paper API: action bars, titles, richer chat. A Paper plugin does **not** run on plain Spigot
**Purpur**A Paper fork — Paper plugins run on it as they are
**Pufferfish**Another Paper fork — same story
**Folia**Regionised threading. Needs scheduling written for it, so tick it deliberately rather than "just in case"
**Velocity**A modern proxy, sitting in front of your servers. Its own plugin API entirely
**BungeeCord**The classic proxy. Also its own API
**Waterfall**A BungeeCord fork

Why the jar count changes

Under the chips is a line saying what you are about to get, and it is worth reading, because the answer is not "one jar per tick":

That is why there is no "two-jar project" switch anywhere: the answer is worked out from what you ticked instead of being asked for.

Nothing is picked for you

Leave every box unticked and the line reads "Nothing selected yet — VyroAI will ask before it builds." That is on purpose. Guessing Paper for a Folia project is exactly the kind of quiet wrong answer that costs an afternoon, so the app asks rather than assumes.

The new-project wizard asks a shorter version of the same question

The nine tick boxes above are the Project Settings → Build answer. The wizard that makes a new plugin asks first, and it asks differently: one dropdown called Server Platform with seven choices in two groups — Bukkit-based: Paper, Paper + Folia, Folia, Spigot, Bukkit; Proxy: Velocity, BungeeCord. The Default settings dialog on the Projects page offers exactly the same seven.

Two differences are worth knowing. Purpur, Pufferfish and Waterfall exist only in the Build tab, so in the wizard pick the fork's parent — Paper for Purpur or Pufferfish, BungeeCord for Waterfall — and tick the fork itself afterwards. And Paper + Folia is a wizard-only entry: the Build tab has no combined box, because there you tick Paper and Folia as two boxes, which is the same answer written its way.

So after the wizard, open Project Settings → Build once and check the ticks say what you meant.

And which Minecraft version

Platform and version sit on the same Project Settings → Build tab (both appear only once Use global build settings is switched off), but the version setting does not go into the jar by itself. It is handed to the AI, which writes that version into your build file (pom.xml or build.gradle) when it writes the project, and Cloud Build compiles whatever the build file says. Since 11 September 2026 a version named in your newest request — "make it for Paper 1.21.4" — also wins over this setting, for plugin and mod projects.

The version list runs from 1.16.5 up to 26.2, and every entry in between is there to pick:

Pick the version your server actually runs before the AI writes the project. To change it afterwards, ask the AI in a message — "make it for Paper 1.21.11" — so it rewrites the build file, then build again; changing the setting and pressing Build gives you the same jar. A mismatch is a crash on startup or the first time somebody uses the plugin — see When the Server Console Shows an Error.

Why 26.2 comes after 1.21.11

It is not a typo, and nothing skipped a hundred versions. Mojang changed how Minecraft is numbered in December 2025: releases are now year.drop.hotfix, so 26.1 was the first of them and 1.21.11 was the last of the old 1.x line. There is no 26.0.

So a "26" version is newer than any "1." version, and the list is in order even though it does not look it.

Changing your mind later

You can retick at any time, and the AI follows the new list from the next message. What it cannot do is rewrite history for free: code already written against Paper does not become Spigot code because you unticked Paper.

If a build stops with "This project compiles against Spigot, but…", that is this setting and your code disagreeing. Cloud Build explains the message and the two ways out of it.

If you are not sure, tick Spigot alone. It runs on Spigot and Paper — the widest reach — and you can always add Paper later when you actually want something only Paper offers.

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

Where to next

11 of 22 in Minecraft Studio · Last checked 17 September 2026 · Previous: An Existing Mod or Jar