For most Paper servers, install EssentialsX, LuckPerms and WorldEdit first. Add exactly one protection system—WorldGuard or GriefPrevention—then add CoreProtect for investigations and rollbacks. Use spark when you need performance diagnostics, and install Vault only when your economy, chat prefixes, TAB display or shop plugins require the shared bridge.
Playing with friends? Godlike.Host runs hosted Minecraft Java servers from 10 data-center locations, with free DDoS protection.
The right stack depends on whether your server is survival, creative, minigame-focused or private. Plugin builds must also match your exact Minecraft and Paper version; a plugin that worked on one release can fail after an upgrade.
| # | 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.
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 →The core plugin stack most servers need
These three plugins cover the common foundation: player commands and utilities, permission management, and large-scale building. They are not interchangeable. EssentialsX provides player-facing features, LuckPerms decides who may use commands, and WorldEdit supplies editing tools for trusted builders and administrators.
| Plugin | Primary job | Best fit | Important caution |
|---|---|---|---|
| EssentialsX | Homes, warps, teleportation, kits, private messages, moderation and a basic economy | Nearly every survival or community server | Its maintainers recommend Paper; other forks can create compatibility problems. |
| LuckPerms | Permissions, groups and inheritance | Any public server and any server with more than one staff rank | Plan groups before granting broad permissions. |
| WorldEdit | Fast construction and large-scale world changes | Creative, build-focused and administrated survival servers | Everyone is denied by default; grant access deliberately and keep backups. |
Why EssentialsX is usually first
EssentialsX consolidates the everyday commands that otherwise require several small plugins. Its documented scope includes homes, warps, teleportation, kits, private messaging, moderation and a basic economy. It supports CraftBukkit, Spigot and Paper, with Paper identified as the recommended server software. If you run a different fork, test it on a staging copy before putting it on a live world.
#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).
Why LuckPerms belongs beside EssentialsX
EssentialsX documentation recommends LuckPerms for permissions and groups. LuckPerms lets you create roles such as default, member, moderator and administrator, then assign only the commands each role needs. Its web editor can be opened with /lp editor; use the generated editor workflow to build groups and inheritance rather than handing every player a wildcard permission.
What WorldEdit adds
WorldEdit is for trusted builders and operators who need selections, transformations and bulk changes. The WorldEdit 7.4 documentation states: “By default, no one can use WorldEdit.” The permission worldedit.* grants full access, so it should be reserved for a very small administrative group. Teach builders to use //undo and make a world backup before any operation that changes a large area.
Protection, rollback and diagnostics: choose according to your server
After the core trio, select tools based on the problems your server must solve. A small private creative server may need only EssentialsX, LuckPerms and WorldEdit. A public survival server normally needs protection and an audit trail.
WorldGuard or GriefPrevention: install one protection system
Both tools are used to prevent griefing, but they approach protection differently. Guides commonly suggest GriefPrevention or WorldGuard for survival, while other guides favor WorldGuard for explicit region control. Installing both can create overlapping rules that are difficult to explain and troubleshoot. Pick one.
| Choose | When it makes sense | Decision question |
|---|---|---|
| WorldGuard | You need administrator-defined regions with precise flags and boundaries. | Do staff need to define and manage protected areas centrally? |
| GriefPrevention | You want a survival-oriented claim model in which players protect their own builds. | Should ordinary players create and manage their own claims? |
Before opening the server, test a normal player, a trusted builder and a moderator in a disposable area. Verify that building, container access, combat and entry rules behave as intended. Document which plugin owns each protection decision so staff do not try to repair a problem in the wrong configuration.
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).
CoreProtect for investigations and rollbacks
CoreProtect records block activity so staff can identify who changed an area and reverse damage. It is the standard recommendation when a public server needs grief investigations or rollbacks. Its official listing states that it runs on Bukkit, Spigot, Paper, Folia, MultiPaper and other compatible platforms.
Install it before an incident occurs; it cannot reconstruct changes made while it was absent. Set a retention policy that fits your storage capacity, and test an investigation and rollback on a copy of the world. Keep rollback authority limited to senior staff because a broad reversal can remove legitimate work as well as grief.
spark for performance diagnosis
spark is a diagnostic tool rather than a permanent gameplay feature. Use it when players report lag, tick delays or unexplained CPU use. Capture a profile during the slowdown, note the Minecraft and Paper builds, and compare results after one change at a time. Do not treat a profile taken during an empty server as evidence about a full player load. Because plugin and platform support changes, verify that the spark build you select supports your exact server version.
Vault: useful bridge, not an automatic requirement
Vault connects economy and permission providers to plugins that expect a common interface. EssentialsX documentation says Vault is needed for prefix and suffix support. Other guides describe it as essential only when economy, TAB or shop features need the bridge. The practical rule is simple: install Vault when you want chat prefixes, a shared economy or another plugin that explicitly requires it; otherwise, leave it out and reduce maintenance.
Bedrock cross-play tools are optional
Geyser and Floodgate are relevant only if Bedrock players are part of your audience. Their compatibility and configuration requirements should be checked against current project documentation before installation. Do not add them to a Java-only server merely because they are popular in cross-play setups.
Recommended Free Tools
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.
Check your platform and version before installing anything
Plugin compatibility is more important than a list assembled from old screenshots. EssentialsX identifies Paper as its recommended server software. Current guides differ on the Minecraft versions they target: one discusses Minecraft 26.2 with Paper or Purpur, while another lists Minecraft 1.20–1.21 support. Those ranges are not interchangeable, so use the version your server actually runs.
An unverified search summary claims that Paper may stop supporting obfuscated plugins from Minecraft 26.1 onward. That claim was not confirmed on a primary Paper page. Treat it as a warning to verify with current Paper documentation and each plugin’s release notes before upgrading; do not make it the basis for a migration without confirmation.
Pre-install checklist
- Write down the exact Minecraft version, server software and build number.
- Read the plugin’s current release notes and compatibility declaration.
- Back up the world, server configuration and plugin data.
- Keep a staging copy for testing upgrades and permission changes.
- Download only the build published by the plugin project or a trusted distribution channel.
- Record every installed version so a failed upgrade can be reversed.
Safe installation procedure
- Stop the server cleanly. Never copy or replace plugin files while the server is writing data.
- Back up the complete server. Include worlds, the
pluginsdirectory, configuration files and permission data. Store at least one copy outside the server machine. - Install Paper and confirm it starts without plugins. This isolates platform problems from plugin problems.
- Add one plugin at a time. Start with EssentialsX, then LuckPerms, then WorldEdit. Restart after each addition and inspect the console for errors.
- Configure permissions before inviting players. Create LuckPerms groups and assign the minimum commands needed for each role.
- Add one protection choice. Install WorldGuard or GriefPrevention, not both, and test permissions in a throwaway area.
- Add CoreProtect before opening to the public. Confirm that it records a test change and that authorized staff can investigate it.
- Add optional bridges and diagnostics. Install Vault, spark or cross-play tools only when the server’s feature set justifies them.
- Run a player-role test. Join as an ordinary player, builder, moderator and administrator. Check commands, teleportation, protected areas and rollback access.
- Document recovery. Keep the previous plugin jars and a written rollback plan until the new stack has survived normal use.
Configure EssentialsX without creating accidental power
Start by deciding which player conveniences your server actually wants. Homes and warps are useful on survival servers; kits and teleportation may be inappropriate on a tightly balanced challenge world. Private messaging and moderation commands are useful for community management, but they should not automatically be available to every group.
Use LuckPerms to expose only the selected EssentialsX commands. Give ordinary players their intended travel and communication features, reserve moderation commands for staff, and keep economy commands consistent with your server rules. After each permission change, test as a non-operator account; an operator account can hide mistakes because it bypasses normal restrictions.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Build a maintainable LuckPerms hierarchy
Start with roles, not individual exceptions
Create a small hierarchy that reflects how the server is operated. A default group can hold basic player commands, a member group can hold trusted conveniences, and staff groups can inherit player permissions while adding moderation powers. Keep administrator access separate from builder access so a person who edits terrain does not automatically gain every staff command.
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
Use the web editor carefully
- Run
/lp editorfrom an account authorized to manage permissions. - Open the editor session it provides and create or adjust groups.
- Assign nodes to groups rather than scattering one-off permissions across users.
- Define inheritance so higher roles receive lower-role permissions predictably.
- Apply the generated changes, then test each role with a non-operator account.
Keep a written list of high-risk nodes, including wildcard permissions. Review it whenever you add a plugin because a newly installed feature can expose commands that no existing role was designed to use.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Use WorldEdit with a recovery plan
WorldEdit can turn a repetitive build into a quick operation, but the same speed can damage an entire region. Limit access to trusted builders, avoid granting worldedit.* to ordinary players, and establish a maximum area policy for routine edits.
- Make a fresh world backup before a large selection, replacement or generation operation.
- Work in a test area first and verify the selection boundaries.
- Perform the smallest operation that achieves the goal.
- Check the result immediately and use
//undoif the change is wrong. - Restore from the backup if an undo is insufficient or the server crashes during the edit.
Do not rely on an undo command as your only backup. It is a convenience for recent mistakes, not a substitute for a known-good world copy.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Recommended stacks by server type
| Server type | Start with | Add when needed | Usually avoid at first |
|---|---|---|---|
| Public survival | EssentialsX, LuckPerms, WorldEdit, one protection plugin and CoreProtect | Vault for prefixes or economy; spark for diagnosing lag | Both WorldGuard and GriefPrevention together |
| Private friends’ server | EssentialsX and LuckPerms | WorldEdit for building; CoreProtect if trust is limited | Large permission hierarchies and unused economy bridges |
| Creative build server | LuckPerms and WorldEdit, plus EssentialsX for travel and moderation | WorldGuard for staff-managed plots; spark when build activity causes lag | Survival-oriented claim tooling that players will not use |
| Minigame server | LuckPerms and EssentialsX for administration | WorldEdit for map preparation; CoreProtect for shared lobby worlds | Economy and claim systems unless a minigame specifically needs them |
| Java server adding Bedrock access | The stack appropriate to its game mode | Geyser and Floodgate after verifying current compatibility | Installing cross-play components without a tested authentication plan |
Common failure modes and fixes
The server reports an incompatible plugin
Confirm the Minecraft version, Paper build and plugin release. Read the plugin’s stated support range rather than assuming a jar built for an older release will work. Remove the new jar, restore the previous backup and retest on staging if the server fails to start.
Players can use commands they should not have
Check LuckPerms inheritance and look for wildcard grants. Test with a genuinely non-operator account because operators can bypass permission nodes. Remove the broad grant, then add only the required command nodes.
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
WorldEdit appears installed but does nothing
This is expected when no permission has been granted: WorldEdit denies everyone by default. Grant the smallest appropriate permission to a builder group, verify that the group is inherited by the test account, and avoid using worldedit.* unless full access is intentional.
Protection rules conflict
Check whether both WorldGuard and GriefPrevention are installed. If so, choose one, remove the other from the live configuration after making a backup, and retest claims or regions from fresh player accounts.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rollbacks cannot find an old change
CoreProtect can investigate changes only after it has been installed and recording. Confirm that its data is present, that staff have the required permissions and that the requested time falls within your retention policy.
Performance complaints continue after adding spark
spark reports a cause; it does not automatically fix one. Capture a profile during the actual slowdown, note player count and active tasks, then change one suspected cause at a time. Re-profile after each change so you can identify which adjustment helped.
Maintenance rules that keep the stack reliable
- Review plugin releases before every Minecraft or Paper upgrade.
- Upgrade on staging first, then copy the tested versions to production.
- Keep backups before changing jars or configuration.
- Remove plugins that provide no feature your players use; every extra plugin adds configuration and update work.
- Audit LuckPerms groups and high-risk permissions after installing a new plugin.
- Retest protection, teleportation, WorldEdit access and CoreProtect investigations after upgrades.
- Record the exact versions that worked so you can return to a known-good stack.
A lean, tested stack is safer than a long list of popular jars. For most owners, the practical baseline is EssentialsX, LuckPerms and WorldEdit on Paper, plus one protection plugin and CoreProtect when the server is public. Add Vault, spark or cross-play components only when a concrete requirement justifies their maintenance cost.
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.
