The stack we actually run on production SMP servers — not a list of everything with 5 stars on SpigotMC. Each one below earns its slot, with the config gotcha that will bite you if you skip it.
The de-facto permission plugin. Web-based editor, per-group and per-player permissions, tracks, prefixes. No serious server runs anything else.
Gotcha: Create groups (default/member/moderator/admin) rather than assigning permissions per-player — it scales and survives staff changes.
Logs every block place/break, chest open, container transaction and sign edit. Roll back a griefer's session in one command.
Gotcha: The MySQL backend handles big worlds better than SQLite. Also check `inspect-distance` so players can see who griefed them.
Homes, /spawn, /warp, /tpa, kits, chat formatting, economy commands. The glue that makes an SMP feel like a server instead of a bare world.
Gotcha: EssentialsX is huge — disable the modules you don't use (spawner, geoip, protect) to cut config surface and startup time.
Players claim land with a golden shovel. No commands, no learning curve — just right-click two corners. Better for small friendly SMPs than a full towny setup.
Gotcha: Tune `initial-blocks` and blocks-per-hour so one player can't claim the whole map on day one.
Town and nation claims for bigger, more structured servers. Players form towns, buy plots, declare wars, pay upkeep. The economy-driven claim system for serious SMPs.
Gotcha: Towny is a commitment — it reshapes the whole server economy. Don't layer it on top of GriefPrevention; pick one claim system.
Not a plugin you use directly — it's the economy/permission bridge every economy plugin depends on. Install it once and forget it.
Gotcha: No config to worry about. Just make sure it's installed before plugins that 'depend on Vault'.
Player-run shops with chests and signs. The simplest player economy: players set prices, buy and sell. Pairs with Vault + an economy plugin.
Gotcha: Requires an economy backend (EssentialsX economy or similar). Without it, transactions silently fail.
Define protected regions — spawn, arenas, admin zones — with flags (pvp, build, entry). Works alongside GriefPrevention or Towny for the shared areas.
Gotcha: Requires WorldEdit as a dependency even if you never use WorldEdit for building.
Pre-generates chunks so players don't cause TPS spikes exploring new terrain mid-game. The single biggest performance win for a new SMP.
Gotcha: Run it overnight before you open the server. Pre-gen in a circle around spawn, not the whole world at once.
Profiles TPS, memory and lag spikes. When the server stutters, spark tells you which plugin or entity is responsible in one report.
Gotcha: Run `/spark profiler` during the lag, not after. The report URL is shareable so someone else can read it.
A web dashboard of player activity, playtime, sessions and server health. Great for understanding who's actually active.
Gotcha: Runs its own small web server — pick a port and remember the login. Disable geolocation lookups if they feel invasive to your players.
Bridges in-game chat to a Discord channel and back. Players can see server chat from Discord and admins can read it on the go.
Gotcha: Use a dedicated bot token and a dedicated channel. Broadcasting every join/leave is noisy — configure it to only sync chat.
Lets players on newer (and older) Minecraft versions join your server. In 2026 this matters less with modern versions, but it still smooths the update window.
Gotcha: Don't run ViaVersion + ViaBackwards + ViaRewind together unless you genuinely need three-version compatibility — each adds overhead.
Restores skins for offline-mode (cracked) servers, where Mojang's skin server doesn't apply. Makes offline servers look normal.
Gotcha: Only needed for offline-mode servers. On online-mode servers skins work natively and this plugin does nothing.
A 3D web map of your world, viewable in a browser. Players love watching the world take shape; it's also the best 'look what we built' link for your Discord.
Gotcha: Rendering a large world is CPU-heavy. Run the render once after big builds, not continuously.
Install in this order to avoid dependency confusion: Vault first (everything economy depends on it), then LuckPerms (permissions underpin every other plugin's commands), then EssentialsX and your anti-grief pick (GriefPrevention or Towny), then CoreProtect and Chunky, and finally the integrations (DiscordSRV, BlueMap, Plan).
Every plugin above is a single click on a panel host that supports Hangar (CoalHost does) or a jar upload everywhere else. Start with the core five and add the rest as your server grows — a new SMP with 15 plugins on day one is a server where you spend more time reading configs than playing.
The non-negotiable core is: LuckPerms (permissions), CoreProtect (anti-grief logging), EssentialsX (homes/spawn/chat), Vault (economy bridge) and Chunky (pre-generate chunks). Everything else depends on what kind of server you want to run.
There's no hard number, but each plugin adds startup time, memory and a config surface. Most healthy SMPs run 10–25 plugins. If you're past 40, audit: many 'essential' plugins are redundant, and every extra plugin is one more thing that can lag or crash.
Yes. All of these are built for the Paper/Spigot/Purpur family. They don't work on vanilla or Forge/Fabric servers — plugins and mods are different ecosystems.
For a small friendly SMP, GriefPrevention is the right call — golden-shovel claims, zero learning curve. CoreProtect should sit behind it as a logging safety net regardless of which claim system you pick. For larger public servers, Towny scales better.
Yes, for the initial install. A `/reload` re-reads some configs but doesn't fully initialize a new plugin's listeners the way a restart does. For new plugins, restart; for config tweaks, check the plugin's docs for whether reload is safe.
CoalHost spins up Paper/Purpur with Hangar one-click plugin install — every plugin on this list is a couple of clicks away.
View Minecraft Hosting →