GuidesOnly show guides for your app
GuidesGuidesWhen one plugin out of twenty is crashing your server, don't test them one at a time. Binary-search by halves with the File Manager and find the culprit in a few restarts instead of twenty.
Your server ran fine, you added a few plugins, and now it crashes on start or misbehaves — and you have no idea which plugin did it. Testing them one at a time is slow and demoralising. There's a much faster way borrowed from programming: binary search. Split the plugins in half, test, and each round throws away half the suspects. Twenty plugins take about five restarts instead of twenty.
| At a glance | |
|---|---|
| You need | The File Manager and the Console |
| Plan | Any |
| Time | Fifteen minutes for most servers |
Before the search, check whether the answer is already on screen. When a plugin crashes the server, the Minecraft console's plugin helper points at the likely file, and the Errors tab of the console filters the log down to just the failures. A stack trace usually names the offending plugin's package — a line like at com.someplugin.Main... is naming someplugin. If the console already tells you which plugin, skip straight to the fix. The binary search below is for the harder cases where nothing obvious is named — a silent misbehaviour, or two plugins that only clash together.
The idea: with the problem reproducing, remove half the plugins. If the problem goes away, the culprit is in the half you removed. If it stays, it's in the half that's left. Either way you've halved the suspects. Repeat until one plugin is left holding the blame.
Set up once:
/plugins to park disabled jars — call it plugins-off in your server's root. (Minecraft only loads what's inside /plugins, so anything here is switched off but safe.)Then loop:
.jar files from /plugins into plugins-off. Select them (multi-select), use Cut, open plugins-off, and Paste — or use the Move action..jar. That's your culprit.| Round | Plugins loaded | Problem? | Next |
|---|---|---|---|
| Start | 16 | Yes | Move out 8 |
| 1 | 8 | No | Culprit in the 8 you removed — bring back, remove half |
| 2 | 12 (removed 4 of them) | Yes | It's in these 4 — remove 2 |
| 3 | 14 (removed 2) | Yes | One of these 2 — remove 1 |
| 4 | 15 | No | The last one you removed is it |
Four restarts to find one plugin among sixteen.
Some plugins need another plugin to run. Vault, an economy plugin, a permissions plugin, or an API library like PlaceholderAPI are common dependencies. If you move out a dependency but leave the plugins that rely on it, those will now error too — and you'll chase a fake culprit.
Two habits avoid this:
depends on Vault, move Vault with it.Unknown/missing dependency: Vault) is telling you what you removed, not what's broken. Put it back.🎯 Good to know: Not every "conflict" is a bug in one plugin. Two plugins that do the same job — two economy plugins, two chat formatters, two that claim
/home— will fight. If your search lands on a plugin that's clearly duplicating another, the fix is to pick one.
Once one .jar is confirmed as the cause:
⚠️ Heads up: When you're done, move every innocent
.jarback fromplugins-offinto/pluginsand restart. It's easy to fix the problem and forget half your plugins are still switched off.
The reason this happens is adding plugins in a batch. Going forward, add one plugin at a time — install, restart, confirm it loaded cleanly, test it — so a new problem always points at the plugin you just added. See Install plugins.
With the culprit removed (or updated), the server starts cleanly and the misbehaviour is gone. Run /plugins and confirm the rest of your set is green — and that everything you parked in plugins-off is back in /plugins.
/plugins empty — then it isn't a plugin. Look at the world, the server software version, or a crash report.