iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
For a conventional Java survival server running Paper, install EssentialsX, LuckPerms, CoreProtect, one primary protection system, and WorldEdit for trusted staff. Choose GriefPrevention if players should claim their own land, or WorldGuard if staff need tightly controlled regions and flags. Add cross-play, maps, chat, economy bridges, pre-generation, or profiling only when your community has that need.
This stack covers everyday commands, permissions, accountability, grief recovery, and staff building without forcing every server to run a large collection of overlapping plugins. Compatibility is tied to the exact Minecraft version, Paper build, Java runtime, and plugin release, so test the complete combination before opening the server.
| # | 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 |
The core plugin stack
A survival server needs five different capabilities: player-facing commands, authorization, an audit trail, protection against unwanted building or combat, and safe administration tools. No single plugin does all of these well. The following baseline keeps responsibilities clear.
| Role | Recommended plugin | What it adds | Who should use it |
|---|---|---|---|
| Everyday commands | EssentialsX | Homes, warps, teleportation, moderation, kits, and a broad command suite | Players and moderators, with permissions limited by rank |
| Permissions | LuckPerms | Groups, inheritance, and per-command access | Administrators configuring ranks |
| Logging and recovery | CoreProtect | Inspection, searchable lookup, rollback, restore, previews, multi-world logging, and inventory rollback | Moderators and administrators |
| Player-managed claims | GriefPrevention | Self-service land claims and protection against common grief | Survival players and staff |
| Staff-managed regions | WorldGuard | Regions and flags for spawn, shops, arenas, and special builds | Trusted staff |
| Large-scale editing | WorldEdit | Selections, copying, replacing, and construction tools | Trusted builders only |
Install only one primary land-protection model unless you have a documented reason to layer them. Combining claim systems and region rules without a clear precedence plan can leave players unsure where they may build and can make staff investigations harder.
#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 broadest day-to-day addition in the baseline. The project describes it as an “essential plugin suite” with over 160 commands for servers of all sizes. It is free, open source, and built for Paper and Spigot.
What players use it for
- Setting and visiting homes so players can return to a base without memorizing coordinates.
- Using server warps for public destinations such as a marketplace, spawn, or community farm.
- Teleport requests and other convenience commands that reduce routine travel friction.
- Kits for starter equipment or scheduled server events.
What moderators use it for
- Basic moderation and communication controls.
- Temporary or permanent restrictions for players who break server rules.
- Administrative teleports and other operational commands.
Do not treat the command count as a reason to expose every command to everyone. Start with a small player group, a moderator group, and an administrator group. Grant only the commands each role needs through LuckPerms, and review inherited permissions after every rank change.
Recommended Free Tools
LuckPerms: make permissions explicit
LuckPerms should be the authority for who can run powerful commands. Create groups that reflect how your server is actually operated rather than giving every player a broad “default” package.
A practical group layout
- Default: ordinary survival commands, approved homes or warps, and no administrative tools.
- Helper or moderator: moderation and investigation permissions required for assigned duties.
- Builder: WorldEdit access only if the person is trusted to make large edits.
- Administrator: protection configuration, rollback, and server-management permissions.
Keep WorldEdit, WorldGuard administration, and CoreProtect rollback permissions away from normal players. A mistake with a large-edit or rollback command can affect an entire world, so use a separate staff group and grant access to as few people as practical. Test each group with a test account before public launch.
CoreProtect: your audit trail and recovery system
CoreProtect records block and inventory activity so staff can determine what changed, who changed it, and when. Its project description calls it a fast logging and anti-griefing tool with inspection, lookup, rollback, restore, and preview workflows. The project page dated July 21, 2023 says it has been actively developed since early 2012.
Why logging belongs in the baseline
Protection prevents some actions; logging explains incidents that still occur. A player may have permission to build in a claim, an explosion may bypass a poorly configured region, or a staff member may need to undo an accidental edit. Without history, the server is left to guess. With CoreProtect, staff can investigate a location, narrow the time window, identify the responsible player, preview a proposed change, and then roll back or restore the affected data.
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).
A safe grief-recovery workflow
- Preserve the scene. Ask players to stop modifying the affected area. Additional changes make the original incident harder to isolate.
- Inspect representative blocks. Use CoreProtect’s inspection feature on damaged and nearby untouched blocks to establish whether the incident is localized or widespread.
- Run a targeted lookup. Restrict the search by world, area, player when known, and a time range that covers the incident. Narrow searches reduce the chance of including legitimate building.
- Preview the rollback. Use the preview function before applying a change. Check that the proposed restoration covers the grief and does not remove later, legitimate work.
- Apply the smallest effective rollback. Roll back only the affected area and time range. Avoid a global operation unless the evidence shows a server-wide event.
- Verify the result in-game. Walk the restored area, check containers when appropriate, and confirm that unrelated structures remain intact.
- Document the decision. Record the incident, the responsible account, the time window, and the scope used. This helps staff handle appeals consistently.
CoreProtect also supports restore operations when a rollback was too broad, plus multi-world logging and inventory rollback. Restrict these capabilities with LuckPerms; a recovery tool is valuable only when its operators understand the scope of the change.
Choose one primary protection model
The most important design decision after the baseline is whether players claim land themselves or staff define protected regions.
| Question | GriefPrevention | WorldGuard |
|---|---|---|
| Primary audience | Players who need self-service claims | Staff managing fixed regions |
| Protection style | Player-owned plots and claim rules | Named regions with configurable flags |
| Typical uses | Homes, bases, farms, and ordinary survival plots | Spawn, arenas, shops, events, and public builds |
| Reported compatibility | Native major version 1.21; tested major versions 1.21, 26.1, 26.2, and 26.3 | Check the project documentation against your exact server build |
When GriefPrevention is the better fit
Choose GriefPrevention when the server’s central promise is player-owned survival territory. Its listing says it prevents “all forms of grief” including build and break damage, theft, spam, and spawn camping without a database. That self-service model reduces staff workload: players can establish a claim instead of opening a ticket for every new base.
Explain the claim rules at spawn. New players need to know how claims are created, expanded, abandoned, and transferred, and what happens when a claim is inactive. Also define how claims interact with public roads, community projects, and staff-reserved areas. The plugin protects the claim model; your rules still need to settle disputes.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →When WorldGuard is the better fit
Choose WorldGuard when staff need precise control over areas with different rules. Its documentation covers region creation and per-area flags, including PvP, TNT, mob behavior, item restrictions, and protection against abuses such as TNT cannons and piston machines.
WorldGuard is well suited to a spawn where combat is disabled, an arena where combat is expected, a shop district with controlled interactions, or an event area with temporary rules. Staff must understand region priorities and overlapping boundaries before creating many regions. Keep region administration restricted through LuckPerms and document the intended flag set for each area.
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.
Can both systems be used?
They can be layered for a deliberate design, such as player claims in the wilderness with staff-managed regions at spawn. If you do this, define which system owns each area, how boundaries are communicated, and which rules win when they overlap. Do not install both merely because each is popular.
WorldEdit for trusted construction staff
WorldEdit speeds up selections, copying, replacing, and large construction tasks. It is a staff tool, not a general survival convenience. A single command can change thousands of blocks, so give it to a small builder group and test permissions with a non-operator account.
Free tools Windows power users keep installed
One-click scans. No signup required.
Use a staging world for complicated edits, keep CoreProtect logging enabled, and require a backup before large changes. If an edit goes wrong, stop further changes, identify the edit window in CoreProtect, preview a narrowly scoped rollback, and verify the restoration before allowing work to continue.
Optional plugins by server need
Add optional plugins only when they solve a problem your players actually have. Each addition introduces another compatibility check, configuration surface, and possible source of performance or permission issues.
| Need | Plugin or combination | Important qualification |
|---|---|---|
| Bedrock players joining a Java server | Geyser plus Floodgate | Check the current compatibility matrix before deployment |
| Newer clients connecting to an older server | ViaVersion and related Via plugins | Test gameplay and plugin behavior after upgrades |
| Browser-based live map | BlueMap, Dynmap, or squaremap | Choose one mapping approach and account for its rendering workload |
| Discord and in-game chat synchronization | DiscordSRV | Define moderation and account-linking rules before enabling chat relay |
| Shared economy or chat service | Vault | Install only when another plugin requires the bridge |
| Controlled world pre-generation | Chunky | Schedule generation and monitor resource use |
| Lag and tick-time diagnosis | spark | Use it for diagnosis rather than as a permanent feature plugin |
Cross-play with Geyser and Floodgate
Geyser and Floodgate are appropriate when Bedrock users must connect to a Java server. Cross-play is not a guarantee that every interaction behaves identically across editions. Verify the current compatibility matrix, then test joining, movement, inventories, commands, combat, and any custom mechanics in a staging world.
Version bridging with ViaVersion
ViaVersion can help clients on newer versions connect to an older server. Treat that as a compatibility layer, not as a substitute for upgrading. Test the activities your server depends on—redstone, combat, containers, claims, and plugin commands—after every Minecraft or Paper update.
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
Maps, chat, economy, and performance tools
A browser map is useful for orientation and showcasing community builds, but rendering can consume resources. DiscordSRV is valuable for communities that coordinate outside the game; establish moderation rules for relayed messages. Vault is a service bridge, so installing it alone does not create an economy. Chunky can move exploration work into a controlled pre-generation job. spark is most useful when diagnosing a specific lag or tick-time problem.
Installation plan for a new Paper survival server
- Record the target environment. Write down the Minecraft version, Paper build, Java runtime, and operating system before selecting plugin files.
- Obtain plugins from official project pages or trusted repositories. Match each download to the target environment; do not assume a plugin that worked on one Paper build will work unchanged after an upgrade.
- Create a complete backup. Back up the world, configuration files, and permission data before the first installation.
- Install the baseline in stages. Start with EssentialsX, LuckPerms, CoreProtect, your chosen protection model, and WorldEdit. Restart between logical groups so startup errors are easy to identify.
- Read the startup log. Look for missing dependencies, unsupported versions, configuration errors, and permission or database warnings before allowing players online.
- Configure permissions before opening the server. Build groups in LuckPerms, test with representative accounts, and keep rollback, region administration, and WorldEdit away from ordinary players.
- Use a staging world for functional tests. Create a claim or region, test protected and unprotected actions, trigger a controlled block change, and verify CoreProtect inspection and rollback.
- Add optional plugins one at a time. Test cross-play, version bridging, maps, chat, economy integrations, or pre-generation separately so a regression has an obvious cause.
- Promote the configuration only after recovery works. Confirm that backups can be restored and that staff can undo a test incident before public launch.
Permissions and protection checks before launch
- Log in as a normal player and confirm that administrative commands are unavailable.
- Create a test GriefPrevention claim or WorldGuard region and verify the intended build, break, container, PvP, TNT, mob, and item rules.
- Test a staff-only WorldEdit operation in a disposable area and confirm that the permission is denied to other groups.
- Make a controlled block change, locate it with CoreProtect, preview a rollback, and restore it without touching neighboring work.
- Check every world separately; a rule that works in the overworld may not automatically match a nether or event world.
- Write player-facing explanations for claims, protected spawn rules, appeals, and reporting grief.
Compatibility and maintenance
Plugin compatibility is version-specific. Re-check every plugin after a Minecraft or Paper upgrade, including plugins that appeared unaffected in a previous update. The exact Minecraft version and Paper build matter, as does the Java runtime required by that server release.
Upgrade procedure
- Read the server and plugin release notes for breaking changes.
- Clone or back up the live server before changing the jar files.
- Upgrade in a staging environment first.
- Test login, commands, claims or regions, protection flags, CoreProtect logging, rollback, and any cross-play or version-bridging layer.
- Review the startup log and monitor tick time while exploring and loading new chunks.
- Schedule the live upgrade during a maintenance window and retain the previous working files until the new build is verified.
Common failure modes and fixes
Players can use commands they should not have
Review LuckPerms group inheritance and direct grants. Remove broad permissions from the default group, then test with a clean account. Check whether another plugin is granting an equivalent command or bypass permission.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesA claim or region does not protect an area
Confirm that the player is inside the intended boundary and that the correct world is selected. For WorldGuard, inspect region membership, priority, and flags. For GriefPrevention, verify that the claim exists, belongs to the expected owner, and has not been abandoned or subdivided.
Rollback removes legitimate work
Stop, restore the affected change if necessary, and repeat the investigation with a narrower time range, area, or player filter. Always preview before applying and keep an incident record so staff can explain the decision.
Players on another edition or version cannot connect
Check the Geyser/Floodgate or ViaVersion compatibility information for the exact server build. Confirm that the connection layer and all dependent plugins are updated together, then test the affected gameplay paths in staging.
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
The server becomes slow after adding a plugin
Review startup warnings, map-rendering schedules, pre-generation jobs, and new chunk activity. Use spark to diagnose tick-time problems, disable the suspected optional plugin in staging, and compare behavior before changing the live server.
Example stacks by server style
Small friends-only SMP
Use EssentialsX, LuckPerms, CoreProtect, and GriefPrevention. Add WorldEdit only if a trusted builder needs it. This keeps self-service claims and recovery available without a large administrative surface.
Public community server
Use the baseline with GriefPrevention for wilderness claims and carefully scoped WorldGuard regions for spawn or events. Add DiscordSRV or a browser map only after moderation and resource requirements are defined.
Staff-curated adventure or event server
Use EssentialsX, LuckPerms, CoreProtect, WorldGuard, and WorldEdit. WorldGuard’s flags are more suitable than player claims when staff must control arenas, scripted spaces, and temporary events.
Cross-platform community
Use the baseline protection and recovery stack, then add Geyser and Floodgate after checking compatibility. Test Bedrock movement, inventories, commands, and combat rather than assuming Java behavior will be identical.
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
Final selection checklist
- Choose EssentialsX for the everyday command layer.
- Use LuckPerms to separate player, moderator, builder, and administrator access.
- Install CoreProtect before the first public build so incidents are auditable from day one.
- Pick GriefPrevention for player claims or WorldGuard for staff-controlled regions.
- Restrict WorldEdit to trusted staff and keep backups before large edits.
- Add Geyser/Floodgate, ViaVersion, a map, DiscordSRV, Vault, Chunky, or spark only for a defined need.
- Test the complete set on the exact Minecraft and Paper build, then repeat those tests after upgrades.
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.
