Install Minecraft mods and plugins (Paper, Forge, Fabric)

The target folder for a .jar file depends on the server software: plugins go on Paper/Spigot, mods go on Forge/Fabric. Mixing them up causes crashes.

Cause / The problem

A plugin dropped into /mods won’t load, and a mod dropped into /plugins throws an error on startup. Also, mods (Forge/Fabric) must be installed on players’ clients too, unlike plugins.

Solution

1. Identify your server type in the Pelican panel (tab Startup or Settings). The software is shown: Paper, Spigot, Purpur (plugins) or Forge, Fabric, NeoForge (mods).
2. For plugins (Paper/Spigot/Purpur):
   • Stop the server.
   • Open the file manager → /plugins folder.
   • Upload the plugin’s .jar file.
   • Start the server. The plugin creates its own config folder on first launch.
3. For mods (Forge/Fabric/NeoForge):
   • Stop the server.
   • Open the /mods folder (create it if it doesn’t exist).
   • Upload the mod’s .jar file.
   • Start the server.
   • Share the mod list with your players: they must install the same ones on their client via the appropriate launcher.
4. Check the version: a mod/plugin built for 1.20 won’t work on a 1.21 server. The Minecraft version and the mod version must match.
5. Watch the console on restart: a plugin that loads prints [Plugin] Enabling PluginName. An error here points to a conflict or an incompatible version.

Never install a Fabric mod on a Forge server (or the other way around): the APIs are incompatible.