Describe what the plugin should do the way you would explain it to a developer. Codella writes the Java, compiles it against your server’s API version, and hands back a .jar you drop into /plugins. No JDK, no IDE, no build tools — and the source is yours.
[13:42:01 INFO]: Starting minecraft server version 1.21.4[13:42:04 INFO]: Loading plugins...[13:42:05 INFO]: [KitsPlus] Loading KitsPlus v1.0.0[13:42:06 INFO]: [KitsPlus] Registered command /kit (4 kits)[13:42:06 INFO]: [KitsPlus] Cooldowns loaded from config.yml[13:42:07 INFO]: [KitsPlus] Enabled successfully[13:42:07 INFO]: Done (6.104s)! For help, type "help"> The hard part of a plugin was never the semicolons — it was knowing that a cooldown belongs in a map keyed by UUID, that inventory clicks need to be cancelled before they mutate, and that PlayerJoinEvent fires before the player is fully loaded. You describe the rules; the API knowledge is applied for you.
No JDK version to match, no Gradle wrapper, no shading a library into your jar and finding out at runtime that it clashed. The build runs in the cloud against the API version you picked and either produces a .jar or tells you exactly what failed.
The output is a multi-file plugin with a plugin.yml, listeners, commands, a config.yml and message files — the same layout a developer would hand you. You can read it, learn from it, edit it by hand, or hand it to someone who codes.
Changing a permission node, adding a second GUI page, or making a reward configurable is one more instruction. Nothing needs to be recompiled locally, and every version is kept so a change that made things worse is one click to undo.
A /kit command with four rank kits, a 12-hour cooldown per kit, a permission node for each one, and an admin command to reload the kits without restarting.
Everything the plugin needs to declare — commands, aliases, permission defaults, the API version to build against — is inferred from that sentence and written into the manifest. You do not have to know that this file exists, but it is there, and you can edit it.
name: KitsPlusversion: 1.0.0main: ai.codella.kitsplus.KitsPlusapi-version: 1.21commands: kit: description: Claim your rank kit permission: kitsplus.usepermissions: kitsplus.admin: default: opYes. A plugin is a compiled Java program, but you no longer have to be the one who writes it. You describe the behaviour you want in plain English, Codella writes the Java against the Spigot or Paper API, compiles it in the cloud, and returns the finished .jar. You never open an IDE, install a JDK, or configure a build tool.
No. Compilation happens on Codella's servers, so the only thing you need locally is a browser and somewhere to put the .jar file. Your Minecraft server itself still needs Java to run, exactly as it already does for every other plugin.
Yes. You get the full Java source alongside the compiled .jar, and you can download, modify, redistribute or sell it. Nothing is locked to the platform and there is no runtime dependency on Codella — the .jar runs on your server whether or not you ever open Codella again.
You describe the change and it gets rebuilt. Most plugins take a few rounds of refinement — adding a permission node, changing a cooldown, fixing a message — and each round is another plain-English instruction rather than a code edit. Version history keeps every build, so you can always roll back to one that worked.
It is ordinary Java either way — the output is a normal plugin built against the normal API, not an interpreted script or a wrapper. What a developer still brings is judgement on unusual architecture and deep performance work. For the commands, GUIs, economy hooks and minigames that make up most server plugins, the generated result is the same kind of code a developer would write.
Generally yes. Generated plugins use the same Bukkit event system and the same integration points as everything else in your plugins folder, including Vault for economy and PlaceholderAPI for placeholders. Tell Codella which plugins it needs to work alongside and it will target those APIs.
If you would rather understand what is happening under the hood, the guide walks through the same process by hand. If you want to see the range of what people generate, the community feed is public.