Which plugin is causing my issue, or which are outdated for my version?

When something breaks and you're running a stack of plugins, the trick is to let the Console tell you as much as it can, then narrow the field with a quick divide-and-conquer test. Here's how to pin down the offender.

Read the Console first

Every plugin logs whether it enabled at startup, and outdated ones print warnings or errors as they load. Open the Console, restart the server, and read the startup lines carefully — an outdated or broken plugin usually names itself right there, often with a note that it's built for a different Minecraft version.

Isolate a bad plugin

1. Stop the server.
2. In Files, temporarily move half of your plugins out of the plugins folder (into a spare folder).
3. Start the server and test whether the problem is gone.
4. Depending on the result, narrow to the half that still misbehaves and repeat, halving each time until one plugin remains.
5. Once identified, update or replace that plugin.

Tip: After a Minecraft version update, re-check every plugin against the new version and update any that print warnings — outdated plugins are the most common source of post-update issues.

Frequently asked questions

How do I know a plugin is outdated? The Console will typically warn that it was built for an older Minecraft version, or it will fail to enable. That's your signal to grab the newer build.

Do I have to test one plugin at a time? No — halving is faster. Move out half, test, and keep splitting the problem set. You'll usually find the culprit in just a few restarts.

A plugin has no update for my version — what now? You may need to find a maintained alternative, or hold off on updating your server until the plugin catches up. Our team can suggest options via a ticket if you're stuck.