The Case Against AI Plugins Is Mostly Right

The Spigot community has been arguing about low effort AI plugins, and the criticism is better than the people making it are usually given credit for. It is also aimed at something specific, and it is worth understanding exactly what, because it is probably not what you are doing.

Kodari TeamUpdated Sep 20, 2026 · 9 min read
On this pageThe actual objectionWhat defenders defendThe key distinctionThe maintenance objectionOn disclosureWhere this leaves youFAQ
the actual objection
// The complaint, as stated on SpigotMC

"I would much rather see a beginner upload a
simple plugin they actually wrote and understand
than somebody upload a huge plugin generated for
them that they cannot properly maintain."

// Note the verb. It is "upload", not "generate".
From a thread titled "Spigot has a serious problem with low effort AI generated plugins". The distinction in that sentence is the whole argument.

We make a tool that generates Minecraft plugins, so there is an obvious version of this article where we defend the category and tell you the critics do not understand the technology. That article would be wrong, and anyone who has actually read the threads would know it was wrong. The criticism is largely correct. It is also narrower than it first appears.

The argument on Spigot is not really about whether a model can write working Java. It has mostly moved past that. It is about what happens after, and specifically about what gets published to a public marketplace by people who cannot support it.

What People Are Actually Objecting To

Read the threads carefully and the same complaint appears repeatedly, with the same shape. The original post in the most recent one describes the pattern in submissions: "The descriptions all sound the same. The feature lists are full of pointless filler." And on what happens when something goes wrong, the author "either has no idea how to fix it or comes back with another AI generated answer."

That second half is the real grievance. Not that a machine wrote the code. That the person who published it cannot answer a question about it, cannot fix a bug in it, and when asked, returns with another generated response that may or may not address the problem. From the point of view of everyone downstream, that resource is abandoned the moment it is uploaded.

The third complaint is about fairness, and it is worth quoting because it is the emotional core of the thing. Handmade plugins end up "mixed in with resources made by people who have spent years learning Java, Bukkit, Spigot, Paper, databases, concurrency, performance, backwards compatibility." If you have put in those years, watching the listing fill with output that took ninety seconds is genuinely galling, independent of whether that output works.

The objection is not to generated code. It is to generated code being presented as a maintained product by someone who cannot maintain it.

The Defenders Are Not Defending What You Think

What is striking about these threads is that the pushback does not come from people saying the critics are wrong about quality. It comes from people drawing a line in a different place. One reply puts it directly: "If it actually works and the author knows how to maintain it a minimum, then who cares whether they used AI or not?"

Another, from someone describing themselves as using AI heavily: "I use AI heavily myself, but I see it more as a development tool than something that completely designs everything."

Both of those are conditional defences, and both conditions are about the human. Can you maintain it. Do you understand it. Nobody in these threads is arguing that a plugin is good because a model wrote it. The disagreement is about whether the origin matters once those conditions are met, and reasonable people land differently on that.

The Distinction That Resolves Most Of This

There are two completely different activities being discussed as though they are one, and separating them dissolves most of the argument.

Generating a plugin for your own server. You need a custom crate, a join reward, a shop tweak that no public plugin does the way you want. You describe it, you get it, you run it. There is no marketplace listing, no support obligation to strangers, no claim of craftsmanship. If it breaks, it breaks for you, on your server, and you fix it or regenerate it. Almost nobody in these threads objects to this. It barely comes up, because it does not affect them.

Publishing a generated plugin as a product. You upload it, other servers depend on it, and you take on an implicit promise to answer questions and fix bugs. This is the thing people are angry about, and they are right to be, because the promise is often one the uploader cannot keep.

The overwhelming majority of what server owners want from plugin generation is the first category. If that is you, the Spigot argument is not about you, and you should not absorb guilt that was aimed somewhere else.

Taking The Maintenance Objection Seriously

That said, the maintenance complaint deserves a real answer rather than a jurisdictional one, because a weaker version of it applies even on your own server. If a plugin breaks in six months and you do not understand a line of it, you have a problem regardless of whether anyone else was depending on it.

Some of that answer is structural. A plugin you can read is fundamentally different from a jar someone handed you. This is a real argument for getting source code rather than compiled output, whoever or whatever produced it, and it is the same argument for negotiating source delivery when you commission a plugin from a person. Handing over a jar and nothing else is how you end up stuck, and that predates AI by about fifteen years.

Some of it is about whether the thing actually compiles and runs before it reaches you. A generated plugin that has never been built is a guess. One that has been compiled, had its errors read, and been corrected until it builds is a meaningfully different artifact. That does not make it good, but it removes the entire category of failure where the plugin was never valid Java in the first place, which is a large share of what people are complaining about.

And some of it is honesty about scope. A generated plugin is a reasonable answer to a contained request. It is not a reasonable answer to a network core that five hundred players depend on during peak hours. Anyone telling you otherwise is selling something.

On Disclosure

The community is currently discussing whether resources should carry a flag marking them as AI generated. Whatever is decided, the underlying instinct is correct and worth adopting voluntarily: if you publish something you did not write, say so.

This costs you very little and it prevents the specific failure that generates the most resentment, which is someone discovering the origin of a plugin after they have already built a dependency on it and asked a question the author cannot answer. Presenting generated work as hand written is the part that reads as deceptive. Saying plainly what it is removes that entirely, and the people who would refuse it on those grounds were never going to be happy users of it anyway.

Where This Leaves You

If you run a server and you want a custom feature, generate it. Read what comes out, even if you only half understand it. Keep the source somewhere you can find it again. Test it somewhere that is not your live server on a Friday night. That is the entire ethical burden, and it is the same burden as installing any plugin from a stranger.

If you are thinking about uploading generated plugins to a marketplace, the community has told you clearly what it expects, and it is not unreasonable: be able to support what you publish. If you cannot fix a bug in it without regenerating the whole thing, you are not in a position to maintain a resource other people depend on.

And if you have spent years learning this properly and find the whole development irritating, that is fair. The useful version of the complaint, the one about maintenance and disclosure rather than about origin, is one the tooling should be judged against. We would rather be measured by it than argue with it.

Frequently Asked Questions

Is it wrong to use an AI generated plugin on my server?

No, and this is not really what the community argument is about. The objection in those threads is to publishing generated plugins as maintained products, not to running one on your own server. Running it affects only you, and you carry the same responsibility you would for any third party plugin.

Should I tell people my plugin was AI generated?

If you publish it, yes. Disclosure is being actively discussed in the community, and volunteering it costs nothing while preventing the main source of bad feeling, which is people discovering the origin only after they hit a bug you cannot fix.

What is the real risk with generated plugins?

Not usually that the code is wrong on day one, since anything that compiles and runs has cleared the most common failure. The risk is that nobody understands it when it needs to change. Keeping the source, and keeping the scope contained, is what mitigates that.

Can AI generated plugins perform as well as handwritten ones?

For contained features, often yes. For anything where performance under load matters, an experienced developer brings judgement about concurrency, caching, and server tick budget that you should not assume is present. Scope is the honest dividing line, not quality in the abstract.

Why would a plugin generator publish an article agreeing with its critics?

Because the criticism is specific and mostly correct, and pretending otherwise would be obvious to anyone who has read the threads. The parts that are about maintenance and disclosure are standards worth being held to rather than argued with.

EditorialMinecraftAIPlugin DevelopmentCommunitySpigot
Generate it, read it, and keep the source
Try Kodari free