How to Install Plugins on a Minecraft Server (Spigot & Paper)

Plugins are the reason most survival and minigame servers run Paper or Spigot instead of vanilla. The best part: only the server needs them — players just connect with a normal client. This guide covers installing and managing plugins the right way.

Plugins vs mods (know the difference)

Mods (Forge/Fabric) change the game and require every player to install them. Plugins (Bukkit/Spigot/Paper) run only on the server and are invisible to the client, which is why they are ideal for public survival servers. You cannot run Forge mods on a Paper server, or Bukkit plugins on a vanilla server. If you are still choosing a server type, read Paper vs Spigot vs Purpur.

Get a Paper or Spigot server first

Paper is the recommended modern choice — a high-performance fork of Spigot. Download the latest build for your version from papermc.io and boot it once:

mkdir -p ~/paper && cd ~/paper
wget -O server.jar "https://api.papermc.io/v2/projects/paper/versions/1.20.4/builds/499/downloads/paper-1.20.4-499.jar"
echo "eula=true" > eula.txt
java -Xmx4G -Xms4G -jar server.jar nogui

That first run creates a plugins folder.

Install a plugin

Download the plugin .jar (SpigotMC, Hangar, or Modrinth) that matches your Minecraft version and drop it into plugins:

cd ~/paper/plugins
wget -O EssentialsX.jar "<direct-download-url>"

Restart the server so it loads. On the console:

stop
java -Xmx4G -Xms4G -jar server.jar nogui

The plugin generates its config in plugins/<PluginName>/config.yml. Edit that file, then apply changes.

Reload vs restart

Some plugins support /reload confirm or their own reload command, but a full restart is safer — /reload can break plugins that register events at startup. For config-only changes, many plugins offer a specific command like /essentials reload. When in doubt, restart.

Managing multiple plugins

Keep versions current and check dependencies. A permissions plugin like LuckPerms is a common dependency for others. Useful commands once plugins are installed:

/plugins          # list loaded plugins (green = ok, red = failed)
/version <plugin> # check a plugin's version

A red plugin name in /plugins means it failed to load — check logs/latest.log for the reason, usually a version mismatch or a missing dependency.

A starter plugin set

For a survival server, most admins start with EssentialsX (homes, warps, kits), LuckPerms (permissions), Vault (economy bridge), and a land-claim plugin. Our best plugins for a survival SMP rundown goes deeper, and for player control see how to whitelist players.

Where to download plugins safely

Stick to trusted sources: SpigotMC, Hangar (PaperMC's official plugin site), Modrinth, and BukkitDev. These vet uploads and show which Minecraft versions each plugin supports. Avoid random download mirrors — a malicious plugin has full server access and can wreck your world. Always match the plugin's supported version to your server.

Understanding plugin configs (YAML basics)

Most plugins configure via YAML files in plugins/<PluginName>/. YAML is whitespace-sensitive — use spaces, never tabs, and keep indentation consistent. A typical snippet:

settings:
  spawn-protection: false
  max-homes: 3
messages:
  welcome: "Welcome to the server!"

A single misplaced tab or colon breaks the whole file, so after editing, restart and watch the log for "could not load config" errors. Many editors have a YAML linter that catches these before you restart.

Updating and removing plugins

Keep plugins current, especially after you update the server version — an outdated plugin is the most common cause of a broken upgrade. To update:

# stop the server, then:
cd ~/paper/plugins
mv EssentialsX.jar EssentialsX.jar.old
wget -O EssentialsX.jar "<new-version-url>"
# start the server; the plugin keeps its existing config

To remove a plugin, delete its jar (and optionally its config folder) and restart. Check /plugins afterwards — a name still showing means an old jar is lingering. For a curated starting lineup, our best survival SMP plugins guide covers what to install, and the EssentialsX guide walks through the most important one in depth.

Handling plugin dependencies

Some plugins need another plugin to function — the classic example is anything using an economy needing Vault, or permission-aware plugins working best with LuckPerms. If a plugin loads red and the log says "depend: Vault" or "could not find dependency," install that plugin first, then restart. A plugin's SpigotMC or Modrinth page lists its dependencies under requirements. Load order is handled automatically once the dependency jar is present, so you don't need to do anything beyond dropping it in plugins. Keeping a short, well-understood set of plugins — rather than dozens of overlapping ones — makes dependencies easy to reason about and keeps performance healthy, which is exactly the philosophy behind our survival plugin picks. When you eventually update the server version, update dependencies alongside the plugins that rely on them.

FAQ

Do players need to install plugins?

No — that is the whole point. Plugins live only on the server. Players connect with an unmodified client.

Why is my plugin red in /plugins?

It failed to load, usually a version mismatch or a missing dependency. Check logs/latest.log for the exact error.

Can I use plugins and mods together?

Not directly, but hybrid servers exist. Loaders like Mohist or Arclight run Forge mods and Bukkit plugins together, at the cost of stability. For most people, pick one.

Where are plugin settings stored?

In plugins/<PluginName>/config.yml (and sometimes extra YAML files). Edit them and restart to apply.

Plugins are lightweight, but a busy public server still needs headroom. Nxeon's Minecraft server hosting runs Paper beautifully on NVMe VPS plans with full root access.