Minehost
Home/Blog/How to install plugins on a Minecraft server? A step-by-step guide

How to install plugins on a Minecraft server? A step-by-step guide

8 min readMineHost Team

A freshly launched server is a bit like an empty flat. Everything works, but there is nothing in it yet. Plugins are the furniture that starts to make the place your own. Land protection, ranks, an economy, shops, a world map in the browser. You add all of it on the server side, and players do not have to do anything on their end. In this guide we walk through it calmly: where to get plugins, how to put them on the server and what to watch out for so nothing breaks on the first start.

A plugin adds features, it does not change the player's game

Let us start with something worth keeping in mind the whole time. A plugin lives purely on the server side. You install it once, on your end, and the player joins with the plain, unchanged game and downloads nothing. That is a huge convenience, because you can add a new feature or remove something at any moment and the crew notices nothing beyond a fresh thing appearing on the server. That is exactly why plugins are so popular on survival and public servers, where an easy way in matters for everyone.

A plugin is not a mod

If you want to change the gameplay itself, add new blocks, mobs or dimensions, that is a job for mods, and those have to sit on every player. A plugin works differently, which is why you cannot combine it with mods on one engine. They are two separate worlds, more on that in a moment.

First check which engine your server runs on

This is where most first attempts fall apart. Plugins will not run on a plain Vanilla server or on modded engines. You need software that understands plugins at all, and that is the family descended from Bukkit. In practice today it most often means Paper. Before you download anything, make sure your server runs on the right engine:

EngineSupports pluginsNotes
PaperYes, the default choice todayFast and stable, accepts plugins written for Spigot and Bukkit
PurpurYes, fullyPaper with extra options, compatible with the same plugins
Spigot / BukkitYes, the classic of the genreAn older base, today more often replaced by Paper
VanillaNoThe original Mojang server has no concept of a plugin
Fabric / ForgeNoThese are mod engines, they take mods, not plugins
In short: plugins go with Paper, Spigot and relatives. Vanilla, Fabric and Forge will not handle them.

Changing the engine does not wipe your world

If you set the server up on Vanilla and only now want plugins, relax. On hosting, switching to Paper is one click in the panel, and your existing world stays put. It is only worth making a backup first, just in case.

Where to download plugins without running into trouble

A plugin is a .jar file that you let into the very heart of your server. That is why it matters where you get it from. A random file from a forum or a shady link can do more harm than good. Stick to trusted places where authors publish their work and where you can see community activity:

SourceWhat you will findWhat to watch for
SpigotMCThe largest base of plugins for Spigot and PaperCheck the update date and the supported game version
ModrinthA modern platform with plugins and mods togetherFilter by the plugin category and by your engine
HangarThe official repository from the Paper teamA smaller selection, but reliable and tidily documented
BukkitDevA classic base with a long historyMany entries sit untouched for years, mind the version

The plugin version has to match the game version

The most common reason a plugin will not start is a version mismatch. A plugin written for an older release may fail to load on the newest game and the other way round. The download page almost always states which Minecraft versions a given plugin supports. Give that line ten seconds and you save yourself hours of hunting for the culprit.

Installing a plugin step by step

The process itself is genuinely simple and comes down to dropping the file in the right place and reloading the server. On hosting you do it in a browser panel, without touching the console. At MineHost it looks like this:

  1. 1

    Download the right version of the plugin

    Go to one of the trusted sources and download the .jar in a version that matches your game release. If the author offers several variants, pick the one for your engine and your Minecraft version.
  2. 2

    Find the plugins folder

    Every server with plugins has a directory called plugins. That is where all add-ons go. In the panel you open it in the file manager, with no extra tools.
  3. 3

    Upload the file to the server

    Drag the .jar into the plugins folder through the panel or an SFTP connection. Do not unpack the archive or rename the file, the plugin should stay exactly as you downloaded it.
  4. 4

    Restart the server

    A new plugin is only read on a full server start. Click restart in the panel and wait for the server to come back. That is a safer route than the reload command we mention below.
  5. 5

    Check the console on start

    While starting, the server prints which plugins it loaded. If something went wrong, you will see a red message with the plugin name there. That is your first hint where to look.
  6. 6

    Tune the configuration

    After the first start the plugin creates its own folder with a settings file. That is where you change how it behaves: messages, permissions, numbers. More on that in the next section.

Avoid the reload command

It is tempting to use the /reload command instead of a restart, because it works in a second. The trouble is that reloading on the fly can leave the server in a strange, unstable state, especially when a plugin hooks into the world or the economy. For adding a new plugin, always do a full restart. It is a few seconds more and it spares you plenty of mysterious errors.

Configuration and dependencies between plugins

Most plugins, on their first launch, create a subfolder inside plugins with a settings file, usually config.yml. It is a plain text file you open right in the panel. Inside you change messages, limits, prices or permissions. One rule always holds: stick exactly to the layout you found. In these files indentation and colons matter, and a single missing character can block the whole plugin from loading.

The second thing that surprises beginners is dependencies. Some plugins do not work on their own, because they rely on another plugin that has to be present alongside. The classic example is the economy, where a lot of add-ons talk to each other through a shared connector. If the console shows a message about a missing dependency, it means you need to add one more plugin, the one the given add-on requires.

Read the description on the download page

Authors usually state plainly whether their plugin needs anything extra. Before you wonder why something will not start, check the requirements section in the description. Two added files and the problem is gone.

Plugins worth starting with

There is no point uploading everything at once. It is better to build a solid base and add the rest over time, as ideas come. Here is a set that works on most survival servers and gives you a proper foundation:

  • EssentialsX is a bundle of basic commands: home, spawn, teleporting, private messages. The foundation most servers stand on.
  • LuckPerms handles permissions and ranks. With it you decide who can use which commands and how they look in chat.
  • WorldGuard together with WorldEdit gives you land protection against griefing and fast tools for building large areas.
  • CoreProtect logs who placed and broke what, so you can undo the effects of griefing with a single command.
  • Vault is the quiet connector that economy plugins use to talk to one another. It does nothing on its own, but many other add-ons require it.

Add plugins one at a time

Instead of dropping ten plugins in one go, add them one by one and start the server each time. If something stops working, you immediately know which add-on is to blame. Upload everything at once and you are left disabling them one by one.

Common mistakes when installing plugins

  • Uploading a plugin to a Vanilla or modded server and wondering why nothing happens. Plugins need an engine from the Paper family.
  • Downloading a plugin in a version that does not match the game. That is the most common reason an add-on refuses to start.
  • Using the reload command instead of a restart, which pushes the server into a strange state and throws errors with no clear cause.
  • Breaking the settings file by hand through a lost indent or colon. The whole plugin stops loading.
  • Skipping a required dependency, so the plugin starts halfway or not at all.
  • Uploading a dozen plugins at once and having no idea which one causes the lag or the error.

Quick FAQ

Do players have to install anything to use plugins?

No. That is the whole convenience of plugins. They run purely on the server side, and the player joins with the plain game and uses the new features right away. They download and configure nothing on their end.

How many plugins can a server handle?

There is no hard limit. What matters more than the sheer number is how the plugins are written and how much memory and processor power your server has. A few light add-ons make no difference, but heavy plugins can load the machine, so for an elaborate server it is worth taking a package with some headroom.

Can I remove a plugin I do not like?

Yes. Just delete its .jar file from the plugins folder and restart the server. Keep in mind, though, that if the plugin wrote something into the world or the economy, that data may be left orphaned after removal. Always make a backup before a bigger cleanup.


Launch a plugin-ready server in minutes

Pick a package, set the Paper engine with one click and upload plugins from the panel. A ready address, protection against DDoS attacks and backups within reach. We take the technical rest off your hands.

See Minecraft packages