Plugins are the easiest way to add protection, economy, mini-games and management features to your server. Their biggest advantage: a plugin runs only on the server, so players install nothing — everyone connects with standard Minecraft.

Plugins or mods?

It comes down to one question: do you want to change the rules of the game, or add capabilities to the server? New blocks, dimensions and machines mean mods, and everyone must install them. Protection regions, economy, leaderboards and player management mean plugins are enough. For the mod side, see the mods and modpacks guide.

To run plugins your server software has to be from the plugin family: Paper, Purpur, Spigot or CraftBukkit. Vanilla accepts no plugins, and neither do mod loaders.

1) One-click installs from the store

In the server panel, open the Addons section from the side menu. The search box covers three sources at once: SpigotMC, Modrinth and PaperMC Hangar. You can sort results by most downloaded, newest or recently updated.

When you click a plugin, version compatibility is checked automatically and incompatible content is clearly marked. A compatible release installs with one click, which noticeably reduces the risk of installing the wrong version and crashing the server.

Installed plugins are collected in the Installed list. From there you can disable one temporarily without deleting it, then re-enable it — the single most useful feature when hunting a problem. Restart once so changes take effect.

2) Uploading your own .jar

For a plugin that isn't in the store, or one distributed externally, go to the Files section and upload the .jar into the plugins folder. Restart the server afterwards; the plugin creates its own configuration folder on first boot.

With manual uploads, version checking is on you — make sure the file matches both your Minecraft version and your server software.

Version compatibility — the most common mistake

For a plugin to work it has to match both the Minecraft version and the server software. Install the wrong release and the server disables that plugin at boot and writes an error line to the console.

The first thirty lines of the console give away most of these problems: which plugin failed to load and which version it expected. Watching the first boot in the console after installing something is a good habit.

Configuration files

Most plugins keep their settings in plugins/PluginName/config.yml. You can edit these from the panel's file manager. In YAML, indentation is meaningful: one space too many or too few invalidates the file and the plugin won't start.

Copying the file before editing lets you undo a bad change in seconds. After editing, restart the server or use the plugin's own reload command if it has one.

For files you edit often, use the search in the file manager; it beats walking through folders.

Permissions

On a server run by more than one person you need control over who can run which command. That's what a permissions plugin is for: you define groups (player, moderator, admin) and grant command rights to groups.

Without permissions management your only options are making everyone an admin or giving nobody any rights; in a growing community neither is sustainable.

In a small, familiar group you may not need a permissions plugin at all: making a few people operators from the panel's Players section can be enough.

The plugin types usually installed first

  • Land and region protection — stops players wrecking each other's builds. First on the list for an open community server.
  • Administration and essential commands — teleports, home points, player info and other daily needs in one package.
  • Permissions management — the group and rights structure described above.
  • Ground item cleanup — one of the cheapest performance wins available.
  • Logging and rollback — who changed what and when; it makes recovery after griefing far easier.

How many plugins is too many?

The plugin counts on the package cards are guidance, not a closed door. You can install more; the panel simply reminds you performance may be affected.

Even so, count alone isn't decisive: one badly written plugin can cost more than ten light ones. If your server gets heavy, finding which one generates the load beats cutting the number blindly — the performance guide covers the diagnostic steps.

Common problems

  • Plugin installed but doing nothing — check the console; it was most likely disabled over a version mismatch.
  • Server stops at boot — disable the plugin you installed last and start again.
  • A command doesn't work — usually a permissions issue; grant the right to the group in your permissions plugin.
  • Two plugins conflict — two plugins doing the same job can break each other. Remove one.
  • The Addons section won't open — your server software isn't in the plugin family. Switch to Paper or Purpur from the Software section.

Plugins are supported on every package; mod software needs 8 GB or above. Watching the server for a few days after installing something new catches both compatibility and performance problems early.