How to Install Plugins on Your Minecraft Server

Step 1: Make Sure You Are Running the Right Server Software

A plugin needs the Bukkit API underneath it, and that is a property of the server software rather than of Minecraft. Paper, Purpur, Spigot have it. Fabric, Forge, NeoForge, Vanilla do not, and a plugin jar dropped on one of those does nothing at all. If you are not sure which one you are on, the startup tab in the panel names the jar. Paper is what we install by default: it is Spigot with a long list of performance fixes on top and it takes the same plugins.

Steps 2 to 6: Find It, Upload It, Restart, Verify

1. Find Your Plugin

   SpigotMC is the oldest and largest repository, Modrinth is the newer one and leans open source, and Hangar is Paper's own. Those three and the developer's own GitHub releases are the list. A jar from a chat server or a file locker can hand somebody operator rights on your server, wipe the world, or use the machine to attack other people, and it will look exactly like the real plugin while it does it.

2. Download the .jar File

   Plugin pages list the versions they support. A plugin built for a different major version usually refuses to enable, and sometimes enables and then breaks halfway through. If a plugin arrives as a zip with several jars in it, its page says which of them belongs on the server.

3. Upload to the /plugins Folder

   In the file manager the server root holds world, logs and plugins. The jar goes in plugins, loose, not in a folder of its own. Drag and drop into the browser window works too.

   /plugins/YourPlugin.jar

4. Restart Your Server, and Never /reload

   It is tempting because nobody gets kicked, but a reload leaves the old classes in memory and the old event listeners registered, and the bugs that come out of that are close to undebuggable. Stop the server properly and let the panel bring it back.

   stop

5. Verify and Configure

   A plugin that loaded says so by name. Red text with a stack trace under it usually names a missing dependency or a version mismatch in its first two lines. After the first successful start the plugin writes its own config, and changes to that file need another restart or the plugin's own reload command.

   /plugins/YourPlugin/config.yml

Common Issues and How to Fix Them

Two things go wrong more often than everything else combined. The first is Java. An UnsupportedClassVersionError in the console always means the same thing: the jar was compiled for a newer Java than the one the server is starting with. Of the 16 Minecraft versions we offer, 9 want Java 21 and 7 want something older, and the startup tab is where you set it.

The second is a missing dependency. Plugins lean on each other: most economy plugins want Vault as the bridge to your permissions plugin, and anything that touches packets wants ProtocolLib. The plugin page lists what it needs, and the console names it on the line above the stack trace.

Recommended Starter Plugins

Five is a working server. Add two or three at a time and restart in between: twenty jars at once tells you nothing about which one broke the boot.

Questions people ask while installing