Skip to content
LodgichostLodgichost
Back to Guides
7 min read

Installing and Managing Plugins

Find, install, and configure Bukkit/Paper plugins on your Lodgichost Minecraft server.

By Lodgichost Team · Last updated: August 19, 2026

Plugins are what turn a bare Minecraft server into a real community: the essentials that manage teleports and kits, the permission systems that keep griefers out, the economy that makes trade meaningful, and the logging tools that undo the damage when something goes wrong. But every plugin you add is also code running on your server — code that can cost CPU, cause conflicts, or open security holes if it is old or poorly maintained. The skill is not in installing as many plugins as possible but in choosing a small, trustworthy, well-configured set. This guide covers finding safe plugins, installing and verifying them, and managing them cleanly so they improve the server instead of degrading it.

Finding Plugins

Plugins extend your server's functionality with everything from minigames to economy systems. The most trusted sources for Minecraft plugins are:

  • SpigotMC (spigotmc.org) — The largest repository of free Bukkit/Paper plugins.
  • Hangar (hangar.papermc.io) — Paper's official plugin marketplace with verified publishers.
  • GitHub — Many open-source plugins are hosted on GitHub with source code available.

Always check plugin compatibility with your server version and read recent reviews before installing.

Installation Methods

To install a plugin, download the .jar file and upload it to your server's /plugins directory via SFTP or the portal's file manager. After uploading, restart or use /reload to load the plugin.

# After restart, verify the plugin loaded:
> /plugins

Plugins (3): EssentialsX, LuckPerms, WorldEdit
           [✓]       [✓]        [✓]

After restart, verify the plugin loaded correctly by running /plugins in-game or checking the console:

If a plugin shows [ERROR] or [FAILED], check the logs for version incompatibility or missing dependencies.

Configuration

Most plugins create configuration files in the /plugins/PluginName/ directory on first run. These files control behaviour, permissions, and integration options:

/plugins/EssentialsX/config.yml
/plugins/LuckPerms/luckperms-config.yml
/plugins/WorldEdit/config.yml

Edit these files directly through the portal's file manager or via SFTP. Some plugins also support in-game configuration commands.

Essential Plugins to Consider

  • EssentialsX — Core commands for teleportation, warps, kits, and server management.
  • LuckPerms — Advanced permission management with a web editor and group-based permissions.
  • WorldEdit — Powerful in-game world editing tool for building and terrain modification.
  • CoreProtect — Block logging and rollback tool for grief prevention.
  • Vault — Required dependency for economy and permission plugins to communicate.
  • ProtocolLib — Required dependency for many advanced plugins that modify network packets.

Updating and Removing Plugins

A plugin can become a liability the day it falls out of date. Managing them is as important as installing them:

  • Update one plugin at a time and test after each — updating several together makes it impossible to tell which change caused a problem.
  • Check each plugin's page for a changelog that lists breaking changes and the exact server versions the new build supports.
  • To remove a plugin, stop the server, delete the .jar from /plugins, and remove or rename its config folder so stale settings are not picked up again.
  • Watch server startup logs and /plugins for errors after every change, and roll back immediately if a plugin fails to load.

Troubleshooting

  • Plugin not loading: Check that the plugin version matches your server software and MC version.
  • Plugin conflicts: Disable plugins one at a time to identify conflicts.
  • Missing dependencies: Some plugins require Vault, ProtocolLib, or other libraries.

Best Practices

  • Keep plugins updated to the latest versions for security patches and bug fixes.
  • Remove unused plugins — every loaded plugin consumes memory and CPU.
  • Test new plugins on a separate test server before deploying to production.

Frequently Asked Questions

Can plugins be used on a vanilla or modded server?

Plugins require a Bukkit/Paper-style server (or Sponge), so they do not run on vanilla. Forge/Fabric use mods instead. If you host through the portal, pick Paper for plugin support or the loader your modpack needs.

What is the difference between a plugin and a datapack?

Plugins are server-side code that add commands, systems, and behaviours and need a server implementation like Paper. Datapacks are lighter JSON/data bundles that work on vanilla survival servers for things like custom recipes and loot.

Is it safe to download plugins from anywhere?

No. Stick to SpigotMC, Hangar, and official project GitHub repos, and prefer plugins with source code and reviews. A malicious plugin can steal player data or grant admin access, so never install random .jar files from unknown sites.

Why does my plugin show an error after a server update?

Server software updates frequently break plugins, especially API changes between Minecraft versions. Wait for the plugin author to release a compatible build, and roll back to the previous server version in the meantime if you must stay online.

How many plugins should I run?

Only what you actually use. Each plugin consumes CPU, RAM, and startup time, and adds surface for conflicts. A well-run server often needs fewer than fifteen — quality and configuration matter far more than quantity.

Related Guides

This site uses cookies to improve your experience. Learn more.