Only show guides for your app
Add plugins to a Paper, Purpur, or Spigot server straight from the panel — search, install, restart, manage — with no file uploads.
Plugins are how a Minecraft server grows a personality — homes and warps, land claims, mini-games, moderation tools. Falix has a built-in Plugins page that searches the big plugin sites and installs with one click, so you never download a .jar or drag one anywhere.
| At a glance | |
|---|---|
| You need | A server on plugin-capable software (Purpur, PaperSpigot, Spigot, or another Plugin Servers option) |
| Time | Five minutes |
| Plan | Any |
⚠️ Heads up: On Vanilla or a Mod Loader, plugins won't load — switch to plugin-capable software first with the software guide.
Plugins only run on Bukkit-family software. If your Version Changer shows Purpur, PaperSpigot, Spigot, Pufferfish, or Leaf, you're set. If it says Vanilla or a mod loader, plugins have nowhere to load — see Minecraft software and versions to switch first.
Open the Plugins page from your server menu. The search box covers the major sources at once — Modrinth, CurseForge, Hangar, and Spigot — so you can find almost anything by name. Search for a plugin, open it, and press Install. Falix drops the plugin's .jar into your server's /plugins folder.
Minecraft reads /plugins at startup, so a freshly installed plugin does nothing until you restart. Press Restart on the Console page and watch the log — you'll see the plugin's name go by as it loads (usually a line like Enabling <name>).
💡 Tip: Add plugins one at a time — install, restart, confirm — so you always know which one caused a problem.
Most plugins create their settings the first time they run. After that first restart, look in the File Manager under /plugins/<PluginName>/ — you'll find a config.yml (and sometimes more). Open it in the File Manager's editor, change what you want, and restart to apply. Every plugin documents its own options; the config file is where they live.
The Plugins page has a My Addons view listing everything you've added. It matches each .jar against its source and shows you three things that matter:
/version <PluginName> in the console or in-game to print a plugin's exact version.)To remove a plugin, delete its .jar from the /plugins folder in the File Manager, then restart — with the file gone, the plugin is gone. (Deleting the .jar but keeping its /plugins/<Name>/ folder keeps your settings for next time; delete that folder too for a clean removal.)
After the restart, run the plugin's command or type /plugins (or /pl) in the console or in-game — your new plugin should appear in the list, shown green if it loaded cleanly.
.jar from /plugins and start again. Add plugins one at a time so you always know which one caused it.