For a conventional Java survival server running Paper, start with EssentialsX, LuckPerms, CoreProtect, and exactly one primary land-protection plugin: GriefPrevention for player-managed claims or WorldGuard for staff-managed regions. Add WorldEdit for trusted builders, then install cross-play, mapping, chat, world-generation, or diagnostics plugins only when your server has that need.
This stack separates everyday commands, permissions, accountability, and protection instead of asking one plugin to do everything. Compatibility is tied to your exact Minecraft version, Paper build, and Java runtime, so verify every project before installing and retest after upgrades.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Minecraft | Java & Bedrock Deluxe Collection | Windows Digital Code | $39.99 | Buy on Amazon |
| 2 |
|
Minecraft | Java & Bedrock Ultimate Collection | Windows Digital Code | $49.99 | Buy on Amazon |
| 3 |
|
Minecraft | Standard Edition | XBOX Digital Code | $19.99 | Buy on Amazon |
| 4 |
|
Minecraft | $6.99 | Buy on Amazon |
| 5 |
|
Minecraft - Bedrock Edition PS4 | $42.98 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The core plugin stack
A survival server is easiest to operate when each plugin has a clearly bounded job. The following baseline covers the problems that appear on almost every Paper SMP: players need safe utility commands, staff need permission control, grief incidents need an audit trail, and builds need a protection model.
| Job | Recommended plugin | What it contributes |
|---|---|---|
| Everyday commands | EssentialsX | Homes, warps, teleportation, moderation, kits, and a broad command layer. The EssentialsX team describes it as a suite with over 160 commands for servers of all sizes. It is free, open source, and built for Paper and Spigot. |
| Permissions | LuckPerms | Groups and rank-based access. Use it to keep ordinary players away from administrative and destructive commands. |
| Audit and recovery | CoreProtect | Searchable block and activity history, inspection, lookup, rollback, restore, previews, multi-world logging, inventory rollback, and several storage backends. |
| Player-owned protection | GriefPrevention | Players create and manage their own claims, covering build and break protection, theft, spam, spawn camping, and similar grief. |
| Staff-controlled regions | WorldGuard | Precise regions and flags for spawn areas, arenas, shops, and staff-protected builds, including PvP, TNT, mobs, item restrictions, and piston or TNT-machine abuse controls. |
| Large-scale building | WorldEdit | Staff selections, copying, replacing, and other large edits. Its permissions should be limited to trusted builders. |
Install only one primary land-claim system unless you have documented why both are required. Overlapping claims and region rules make it harder for players to understand where they can build and harder for staff to identify which protection stopped an action.
#1 Best Overall
- DELUXE COLLECTION — Includes Minecraft: Java & Bedrock Edition, three Bedrock add-ons, three exclusive Character Creator items, and 700 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
EssentialsX: the everyday command layer
EssentialsX is the first plugin most survival players notice because it supplies the commands that turn a raw server into a usable community. Homes and warps reduce needless travel; teleportation and moderation tools give staff practical ways to handle routine situations; kits can support onboarding or events.
The official project site currently describes EssentialsX as “the essential plugin suite for Minecraft servers, with over 160 commands for servers of all size and scale.” That figure is the suite’s published command count, not a guarantee that every command is appropriate for every server. Decide which abilities fit your rules and expose only those through LuckPerms.
Good first uses
- Set a limited number of homes for regular players and reserve higher limits for trusted ranks.
- Create public warps for spawn, shops, community farms, or event areas.
- Give moderators narrowly scoped teleportation and moderation commands instead of broad operator access.
- Use kits for starter equipment or scheduled events, with contents that cannot undermine your economy.
What EssentialsX does not replace
EssentialsX is not your land-claim database, rollback system, or permission manager. Pair it with LuckPerms, CoreProtect, and either GriefPrevention or WorldGuard so each responsibility remains clear.
LuckPerms: make permissions safe before opening the server
LuckPerms should be configured before players arrive. Create groups such as default, member, moderator, builder, and administrator, then grant only the nodes each role needs. The important security boundary is between normal gameplay and commands that can teleport, alter protected areas, edit large sections, inspect inventories, or roll back other players’ work.
Permission design principles
- Start with no elevated access for the default group, then add player-facing EssentialsX commands deliberately.
- Keep moderation commands in a moderator group rather than adding them to every staff member.
- Restrict WorldEdit and WorldGuard editing to a small builder or administrator group.
- Give CoreProtect lookup and inspection to trusted moderators; reserve rollback and restore for a smaller incident-response group.
- Review inherited groups after every staff change so a rank does not retain a dangerous permission accidentally.
Do not treat operator status as a convenient substitute for permissions. A rank-based model leaves an audit trail of who is allowed to do what and makes it possible to revoke one capability without removing a person’s entire role.
CoreProtect: your audit trail and rollback tool
CoreProtect records activity so staff can answer two different questions: what happened, and how can we reverse only the damage? Its project description calls it “a fast, efficient data logging and anti-griefing tool” that can inspect, look up, roll back, and restore damage. The project page dated July 21, 2023 says it has been actively developed since early 2012.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
- ULTIMATE COLLECTION — Includes Minecraft: Java & Bedrock Edition, five Bedrock add-ons, five exclusive Character Creator items, and 1000 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
What it records and why it matters
- Inspection: examine a suspicious block or area in place while investigating.
- Lookup: search historical actions by player, time, world, or area to establish a timeline.
- Rollback: reverse selected changes after grief, theft, or an accidental mass edit.
- Restore and previews: preview or reapply changes when a rollback was too broad or an innocent build was affected.
- Multi-world logging: keep investigations consistent across survival, resource, event, and staging worlds.
- Inventory rollback: address theft or accidental item changes as well as block damage.
CoreProtect supports several storage backends. Choose the backend that fits your server’s operational policy, keep its data on reliable storage, and include it in your backup plan. Logging is useful only if the data survives a crash or mistaken maintenance operation.
A practical grief response
- Stop further damage if possible: temporarily restrict the suspected account or close the affected area.
- Use inspection and lookup to identify the time window, actors, and worlds involved.
- Take a current backup before changing history.
- Preview a narrowly scoped rollback around the confirmed damage.
- Apply the rollback, then inspect nearby builds and inventories for collateral changes.
- Restore legitimate edits if the first pass removed them, and document the incident and final scope.
Rollback is not a substitute for prevention. Pair CoreProtect with claims or protected regions and use LuckPerms to ensure only trained staff can run destructive recovery operations.
Choose one primary land-protection model
The key decision is whether protection should be self-service for players or centrally managed by staff. Both approaches can work; mixing their rules without a written policy is what causes confusion.
GriefPrevention for player-managed claims
Choose GriefPrevention when your community should claim land as it explores. Its listing says it “PREVENTS all forms of grief – build/break, theft, spam, spawn camping, and more without a database.” Players can protect homes and projects without asking staff to create every region.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →The listing reports native major version 1.21 and tested major versions 1.21, 26.1, 26.2, and 26.3. Treat those as the versions reported by that listing, not as a promise that every future Paper build will work; verify the current release against your exact server before deployment.
WorldGuard for staff-defined regions
Choose WorldGuard when staff need exact boundaries and per-area rules. Its documentation covers region creation and flags for PvP, TNT, mobs, item blacklists, and protection against abuses such as TNT cannons and piston machines. That makes it a strong fit for spawn, arenas, shops, roads, event grounds, and curated builds where players should not decide the boundary themselves.
Rank #3
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that is unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world full of surprises.
- SURVIVAL ADVENTURES — Face mysterious foes, travel across varied landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play solo or join friends in local split-screen and cross-platform play across console, mobile, and PC. Online multiplayer supports up to 8 players.
- COMMUNITY PLAY — Connect with players on community servers, or subscribe to Realms Plus (sold separately) to play with up to 10 friends on a private server.
Decision table
| Question | GriefPrevention | WorldGuard |
|---|---|---|
| Who creates protection? | Players create and manage claims. | Staff create regions and set flags. |
| Best scope | Homes, bases, farms, and player projects across a survival world. | Spawn, arenas, shops, events, and precisely controlled builds. |
| Rule style | Claim ownership and trust relationships. | Per-region flags and staff-defined behavior. |
| Operational trade-off | Less staff work, but players must learn claim boundaries and trust settings. | More central control, but staff must maintain regions and explain the rules. |
Use CoreProtect with either model. Claims and regions prevent many incidents; the logger tells you who changed a block and gives you a recovery path when prevention fails.
WorldEdit: powerful construction for trusted staff
WorldEdit accelerates selections, copying, replacing, and other large edits. It is valuable for spawn construction, terrain cleanup, event arenas, and repairing a large area after a documented incident. It is also one of the easiest ways to destroy a world accidentally.
Recommended Free Tools
- Keep WorldEdit permissions out of the default, member, and ordinary moderator groups.
- Use a staging world to test selections and replacements before touching production.
- Require a backup before broad edits and record who performed them.
- Combine WorldEdit access with CoreProtect logging so an accidental edit has an identifiable actor and time window.
Optional plugins: install for a stated need
Bedrock access: Geyser and Floodgate
Add Geyser plus Floodgate when Bedrock players must join a Java server. Cross-platform behavior depends on the current compatibility matrix and your server version, so verify that matrix before deployment and test login, movement, inventory screens, commands, and protected areas with an actual Bedrock client.
Newer clients on an older server: ViaVersion and related plugins
ViaVersion and related Via plugins can allow clients on newer versions to connect to an older server. Compatibility at the login screen does not guarantee identical gameplay: test combat, redstone, inventory behavior, and every plugin that interacts with version-sensitive mechanics after an upgrade.
Browser maps: BlueMap, Dynmap, or squaremap
A browser-based live map helps players orient themselves, find community builds, and plan travel. Add one when that information is a real community benefit. Maps consume storage and rendering resources, so schedule rendering and monitor the effect on exploration and backups.
Discord bridge: DiscordSRV
DiscordSRV is useful when your community needs synchronized Discord and in-game chat. Define moderation ownership clearly: decide whether a mute, ban, or deleted message in one channel should carry over to the other, and test identity linking before public launch.
Rank #4
- Skins! We have biome settlers, city folk, town folk, and more!
- The Nether and all its inhabitants. Fight Ghasts and make friends with Pigmen
- Cross platform play for up to five players between Pocket Edition and Windows 10
- Revamped touch controls, controller support, and a controller mapping screen
- Enhanced Weather effects! Accumulating snow and more
Shared services: Vault
Install Vault only when another plugin needs a common bridge for economy, chat prefixes, shops, or a related service. Vault is an integration layer, not an economy or permissions policy by itself; keep the actual provider and its permissions explicit.
World pre-generation: Chunky
Use Chunky when unexplored terrain is causing exploration-time load. Pre-generate a defined border or radius during a maintenance window, watch disk usage, and avoid running an unrestricted generation job on a live server.
Performance diagnosis: spark
Use spark when diagnosing lag or tick-time problems. It is a diagnostic tool rather than a permanent feature requirement. Capture data during a reproducible lag event, fix the identified cause, and remove or disable unnecessary diagnostics afterward.
Example stacks by server style
| Server situation | Start with | Add when needed |
|---|---|---|
| Small private SMP | EssentialsX, LuckPerms, CoreProtect, GriefPrevention | WorldEdit for one trusted builder; Chunky if exploration spikes are visible. |
| Public survival community | EssentialsX, LuckPerms, CoreProtect, GriefPrevention | DiscordSRV for community chat, a browser map for orientation, and Geyser/Floodgate for Bedrock access. |
| Staff-curated events and shops | EssentialsX, LuckPerms, CoreProtect, WorldGuard, WorldEdit | Vault when an economy or shop plugin requires its bridge; ViaVersion when your client policy needs it. |
| Older server kept open to newer clients | EssentialsX, LuckPerms, CoreProtect, one protection model | ViaVersion and related plugins, followed by gameplay and plugin regression tests. |
Install safely on Paper
Plugin compatibility is tied to the exact Minecraft and Paper build, not merely to the word “Paper.” Confirm the Java runtime required by that server build as well as each plugin’s supported versions.
- Record the target environment: write down the Minecraft version, Paper build number, Java runtime, world list, and whether Bedrock or older-client access is required.
- Download from authoritative project pages or a trusted repository: match each file to that environment and avoid mixing unrelated builds.
- Back up before the first launch with plugins: include world folders, configuration, permissions data, and CoreProtect’s logging data.
- Install the baseline in a staging copy: EssentialsX, LuckPerms, CoreProtect, one protection plugin, and WorldEdit only for the staff who need it.
- Start the server and read the startup log: resolve dependency, version, Java, or configuration errors before inviting players.
- Configure permissions: create groups and test commands as a default player, moderator, builder, and administrator rather than testing only as an operator.
- Test protection and recovery: create a sample claim or region, try allowed and blocked actions, inspect a change with CoreProtect, and run a rollback in the staging world.
- Add optional plugins one at a time: after each addition, restart, inspect logs, and test the feature it was meant to provide.
- Promote the tested configuration: take a fresh production backup, copy the verified files, and repeat the smoke tests after deployment.
Pre-launch test checklist
- Default players can use intended homes, warps, chat, and other everyday commands but cannot run administrative commands.
- Moderators can investigate with CoreProtect without automatically receiving WorldEdit or rollback authority.
- Trusted builders can edit the intended worlds and no others.
- GriefPrevention claims or WorldGuard regions block build, break, container, PvP, TNT, mob, and piston behavior exactly as your rules describe.
- CoreProtect records actions in every production world and can preview and reverse a test change.
- Backups restore to a separate test location and include plugin configuration and logs.
- Cross-play or version-bridge users can log in and complete ordinary survival actions if those options are enabled.
- Optional maps, chat bridges, and pre-generation jobs have documented schedules and resource limits.
Maintenance after Minecraft or Paper updates
Re-check every plugin after an update. A plugin that worked on one Paper build can fail on another even when the Minecraft major version looks unchanged. Read the project release notes, stage the upgrade on a copy of the server, and inspect the startup log for dependency or API warnings.
- Stop writes to the live server and make a complete backup.
- Clone the server to staging and update Paper and Java as a planned pair.
- Install versions of each plugin that explicitly support the target environment.
- Test login, claims or regions, permissions, CoreProtect inspection and rollback, inventories, redstone, and any bridge or map service you use.
- Only then schedule the production restart and keep the pre-upgrade backup until the new build has operated normally.
When diagnosing tick-time problems, use spark to capture evidence rather than guessing which plugin is responsible. For exploration load, use Chunky to pre-generate a controlled area instead of allowing an unbounded first visit to generate terrain during peak hours.
Best Value
- Play and share with friends on console, mobile and Windows 10
- discover community creations in the new in-game store
- access new mini games and game modes through servers
Troubleshooting common failures
Players can enter but cannot use basic commands
Check LuckPerms group inheritance and the specific EssentialsX permissions first. Confirm that the player is not in a group with an unintended denial and that the command is enabled in the current configuration.
A claim or region does not protect an area
Verify that the player is inside the intended claim or that the WorldGuard region actually covers the coordinates. Check for overlapping regions, priority, and flags, then retest as a normal player rather than an operator.
Rollback removes legitimate work
Stop and restore from the backup if necessary, then narrow the CoreProtect time, actor, world, and area filters. Preview before applying and inspect adjacent builds afterward.
A version bridge connects but gameplay is broken
Test the exact client and server versions against the current compatibility information. Reproduce the problem without unrelated optional plugins, then check version-sensitive mechanics and plugin integrations before deciding whether to keep the bridge.
The server lags during exploration
Capture a spark diagnostic during the lag, check whether new chunk generation is the trigger, and pre-generate a bounded area with Chunky during maintenance. Monitor disk space and tick time while the job runs.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
