Plugins add commands, permissions, economies, protection and minigames to a Minecraft server without touching the game's code — and unlike mods, players don't have to install anything. This guide covers picking a plugin-capable server type, installing a plugin, configuring it, and the errors you'll hit along the way.
Plugins vs mods — check this first
Plugins only run on Paper, Spigot, Purpur or Bukkit servers. They do not load on Vanilla, Forge, Fabric or NeoForge — those run mods, which are a different thing and need a matching client install.
Check your server type in the Software tab of your dashboard. If it says Vanilla, switch to Paper (the fastest and most compatible choice today) — your world carries over, and Paper runs every Spigot/Bukkit plugin. Want mods and plugins on one server? That's what Purpur-with-plugins or a hybrid like Arclight is for, but keep it simple unless you need it.
Where to get plugins
Download only from sources that scan uploads:
- Hangar — Paper's own plugin site
- Modrinth — fast, well moderated
- SpigotMC — the largest catalogue
- Bukkit Dev — older plugins
Two things to check on every plugin page before you download:
- Supported versions must include your server version (shown in the Software tab). A plugin built for 1.20 will usually load on 1.21 but may throw errors on newer blocks or items.
- Dependencies. Many plugins need another plugin present — most commonly Vault (economy/permissions bridge), ProtocolLib (packet handling) or PlaceholderAPI. The plugin page lists them; install those first.
Install a plugin (three steps)
- Upload the
.jar. Open the Files tab in your dashboard, go into thepluginsfolder, and drag the.jarin. Or connect over SFTP (see SFTP connection guide) and drop it in/plugins/. Do not unzip it — plugins ship as a single.jar.
/plugins/
├── EssentialsX-2.21.0.jar
├── LuckPerms-Bukkit-5.4.jar
└── Vault-1.7.3.jar
-
Restart the server. Plugins load on startup — the
/reloadcommand exists but breaks more plugins than it helps, so use a proper restart from the dashboard. -
Check the console. On boot you'll see
[YourPlugin] Enabling YourPlugin vX.Y. Then run/pluginsin the console or in-game (as OP): plugins in green loaded, plugins in red failed — scroll up in the console for the error.
Configure it
Most plugins create a folder on first run:
/plugins/EssentialsX/
├── config.yml
└── ...
Edit config.yml in the Files tab (it has a built-in editor) and restart to apply. Two rules for YAML files: indent with spaces, never tabs, and keep the exact indentation of the line above — one misplaced space and the plugin refuses to load its config.
A sensible starter set
| Plugin | What it does | Needs |
|---|---|---|
| EssentialsX | /home, /tpa, /spawn, kits, warps, basic economy commands | Vault for the economy |
| LuckPerms | Permissions and ranks — who can use which commands | — |
| Vault | Lets economy and permission plugins talk to each other | — |
| WorldGuard + WorldEdit | Protect spawn, claim regions, build fast | — |
| CoreProtect | Log every block change and roll back griefing | — |
| Chunky | Pre-generate your world so new chunks don't lag players | — |
Install LuckPerms first if you're adding anything else — most plugins assume a permissions plugin is present, and without one every player either has every command or none.
Troubleshooting
Plugin shows red in /plugins. Scroll the console for Could not load 'plugins/X.jar'. The line after it says why — the three usual causes are below.
"Unsupported API version" / UnsupportedClassVersionError. Version mismatch. Either the plugin is newer than your server (update the server in the Software tab) or was built for a newer Java runtime than the server is using (rare — pick a plugin release that lists your server version).
"Could not load plugin: missing dependency". Install the dependency it names (Vault, ProtocolLib, PlaceholderAPI…) and restart.
Plugin loads but commands say "unknown command". A permissions problem, not an install problem. Give yourself OP from the Players tab, or grant the permission node in LuckPerms.
Server won't start after adding a plugin. Remove the last plugin you added, start the server, and read the console error — plugins that crash on boot almost always print the reason. Two plugins that do the same job (two economy plugins, two chat formatters) commonly conflict.
Config changes not applying. You edited the file while the server was running and it overwrote your changes on shutdown. Stop the server, edit, then start.
Need mods rather than plugins? Installing mods covers Forge and Fabric servers.