Essential Plugins for a New Survival Server

It’s tempting to install fifty plugins on day one. Every plugin costs performance, adds configuration and becomes something to update, so the best survival servers start with a small, solid core and add features when players actually ask for them. This article covers that core and how to manage plugins over time.

All of these run on Paper (and Purpur). Download plugins only from trusted sources — Hangar, Modrinth and SpigotMC — and check that each supports your Minecraft version.

The core stack

LuckPerms — permissions

LuckPerms is the standard permissions plugin. It lets you create groups (default, member, moderator, admin), assign permissions to them, and give players ranks without handing out operator status. Operator (/op) grants everything, which is rarely what you want. LuckPerms has a web editor for managing permissions visually and can store data in MySQL so ranks are shared across a network. See permissions done right with LuckPerms.

EssentialsX — everyday commands

EssentialsX provides the commands players expect: /home, /sethome, /spawn, /tpa, /msg, kits, warps, AFK detection and more. Install only the modules you need — the core EssentialsX, plus EssentialsX Spawn and EssentialsX Chat if you want them. Pair it with Vault, a small library many plugins use to talk to permissions and economy systems.

CoreProtect — block logging and rollbacks

CoreProtect records block changes, container transactions and more, so you can see who broke, placed or took what, and roll back griefing precisely:

/co inspect                      # toggle inspector, then click a block
/co rollback u:Griefer t:2h r:20  # undo a player's changes in the last 2 hours within 20 blocks

It’s the single best defence against griefing on an open server. For busy servers, store its data in MySQL instead of the default SQLite — see connecting Minecraft plugins to MySQL.

A land claim or protection plugin

Players want to protect their builds. Two common approaches:

• GriefPrevention — players claim land with a golden shovel; claims grow with playtime. Simple and player-driven.
• WorldGuard (with WorldEdit) — admin-defined regions with detailed flags. Ideal for protecting spawn and event areas.

Many servers use GriefPrevention for players and WorldGuard for spawn.

spark — performance profiling

When lag appears, spark tells you why. It costs nothing when idle and is invaluable when something goes wrong. See fixing Minecraft server lag.

Chunky — world pre-generation

Pre-generate your world before launch to avoid exploration lag, then keep Chunky around for when you expand the border. See pre-generating your world with Chunky.

Worth adding early

• WorldEdit — fast building and editing for admins; also required by WorldGuard.
• A map plugin — BlueMap (3D) or Dynmap (2D) give players a live web map of the world. Map rendering uses CPU and disk; configure render limits and pre-render after pre-generation.
• DiscordSRV — links your Minecraft chat with a Discord channel. See linking Minecraft and Discord with DiscordSRV.
• Geyser and Floodgate — let Bedrock players join your Java server. See letting Bedrock players join with Geyser.
• ViaVersion — lets players on newer client versions connect to your server (use carefully; gameplay differences between versions can confuse players).

Nice to have (add when asked)

• An economy plugin and shops, if your community wants trading.
• Jobs, McMMO or other progression systems.
• Chest shops or auction houses.
• Graves or death-chest plugins.
• Scoreboards and tab list customisation.
• Anti-cheat — valuable on public servers, but test carefully; aggressive anti-cheat causes false positives and can be heavy.

Add one at a time, and watch performance after each.

Plugins to be careful with

• “All-in-one” mega plugins that do everything — often heavy and hard to configure.
• Abandoned plugins not updated for recent versions.
• Plugins from unknown sources or “cracked” premium plugins — a common way malware gets onto servers.
• Anything that scans the whole world regularly without configurable limits.
• Several plugins doing the same job (two permission plugins, two chat formatters) — they conflict.

Keeping plugins healthy

• Keep a list of every plugin, its version and why you installed it.
• Update regularly, reading changelogs for breaking changes. Test big updates on a copy of the server first.
• Back up before updating — plugin configs and data, as well as worlds. See Minecraft server backups.
• Remove what you don’t use. An unused plugin still loads, still costs memory and can still have vulnerabilities.
• Check spark occasionally to make sure no plugin has become a performance problem.
• Read the startup log after every change. Errors and warnings there point to incompatible or misconfigured plugins.

A starter setup order

1. Install Paper and configure server.properties.
2. Add LuckPerms and set up groups before inviting anyone.
3. Add EssentialsX (+ Vault), then configure spawn, homes and chat.
4. Add CoreProtect and a protection plugin.
5. Add spark and Chunky; pre-generate the world.
6. Add Discord integration and a map if you want them.
7. Launch — then add features based on what players ask for.

Hosting and help

On Kerit Cloud’s Minecraft hosting, staff can install and configure plugins for you, or you can manage everything yourself through full panel access — console, file manager and one-click restarts. Every paid server includes a free MySQL or PostgreSQL database for plugins like LuckPerms and CoreProtect, and daily automated backups.

Summary

Start a survival server with a lean core: LuckPerms for permissions, EssentialsX and Vault for everyday commands, CoreProtect for logging and rollbacks, a protection plugin like GriefPrevention or WorldGuard, spark for profiling and Chunky for pre-generation. Add maps, Discord integration and Bedrock support when you want them, and everything else when players ask. Download from trusted sources, update carefully with backups, and remove what you don’t use.