Neu: Spare 20 % im ersten Monat — Code BRUCE20
Bereit zum Spielen?
Wähle dein Spiel, such dir einen Plan aus und spiele in unter 60 Sekunden los. Kein Lag, keine Ausreden.
Wuff! Los geht's!

Adding plugins is how a plain Minecraft server turns into a real one, with homes, an economy, land protection, minigames, or whatever else you want. The good news: installing a plugin takes about two minutes once you know the steps. The catch that trips almost everyone up is the server type. If your server runs the wrong software, no plugin will ever load, no matter how many times you upload it.
Here is exactly how to install plugins on a Minecraft server, what to check first, and how to fix the usual reasons one refuses to work.
.jar files. Download from Modrinth, Hangar, or SpigotMC, upload to the plugins folder, restart.plugins/<PluginName>/config.yml.This is the number one reason a plugin "doesn't work." Plugins only run on a Bukkit-based server:
They do not run on vanilla, Fabric, or Forge. Those either take no add-ons at all, or they use mods, which are a different thing (covered below).
Most panels show your server type in the settings or the startup line. If it says Vanilla, Fabric, or Forge, switch it to Paper before you do anything else. Paper is faster than Spigot, fixes dozens of bugs, and runs every Spigot and Bukkit plugin, so it is the safe default. Our Paper vs Purpur vs Pufferfish vs Leaves breakdown has the details if you want them.
Every plugin is a single .jar file. Get them from one of the three trusted libraries:
Not sure what to actually install? Search by the thing you want to add, "economy," "anti-grief," "minigame," and browse the top results. A few that almost every server ends up running:
/tpa, and a simple economyStart with those, then add whatever your server actually needs.
Check the Minecraft version before you download. A plugin listed for 1.20 can crash on 1.21. Most pages let you pick or filter the version. And never pull plugins from random "leak" sites, that is the quickest way to end up with a compromised server.
Two ways, both simple:
File manager (easiest): open your panel's file manager, go into the plugins folder, and upload the .jar straight in.
SFTP (best for several at once): connect with an SFTP client using your panel's SFTP details, then drop the .jar files into plugins.
That is the entire "install." The file just needs to sit in plugins.
Plugins load when the server boots, so a full restart is required, not a reload. A /reload can appear to work but often leaves plugins half-loaded and unstable, so restart properly instead.
When the server comes back, type /plugins (or /pl) in the console or in game as an operator. Your new plugin should appear in green. Red means it failed to load, almost always a version mismatch or a missing dependency.
The first time a plugin runs, it creates its settings at plugins/<PluginName>/config.yml. Open that file in the file manager, change what you want (permissions, messages, prices, whatever the plugin offers), save, and restart once more to apply. Some plugins accept /<plugin> reload, but a restart is always safe.
People search "install plugins" when they mean mods, and the reverse. The difference is real:
Rule of thumb: if a download page says "Fabric" or "Forge," it is a mod and will not work as a plugin. If it says "Paper," "Spigot," or "Bukkit," it is a plugin.
Work through these in order:
.zip or a source file instead of the compiled .jar.The server console tells you the truth here. When a plugin fails, it prints the exact reason on startup, so read the first red line.
Installing a Minecraft plugin comes down to three things: run Paper, drop the .jar into plugins, restart. Around ninety percent of "it won't install" problems are just the wrong server type or a version mismatch, and both take seconds to fix once you know to look.
If you would rather skip the setup, our Minecraft plans run Paper out of the box with a one-click file manager, so installing a plugin really is upload and restart.
Related posts on BruceNode: