Recommended Free Tools
For a conventional Java survival server running Paper, start with EssentialsX, LuckPerms, CoreProtect, one land-protection system (GriefPrevention or WorldGuard), and WorldEdit for trusted staff. Add cross-play, maps, chat, economy bridges, pre-generation, or diagnostics only when your server has that specific need.
If you need a hosted environment for this Paper/Java stack, Godlike.Host offers Minecraft Java servers with a Pterodactyl-based game panel, SFTP access and a built-in mod installer; see the current plans for availability.
As an Amazon Associate I earn from qualifying purchases.
The recommended baseline stack
These plugins solve different operational problems, so they work well together when their permissions are separated carefully.
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 →| Plugin | Primary job | Who should use it |
|---|---|---|
| EssentialsX | Everyday commands such as homes, warps, teleportation, moderation and kits | Players and moderators, with command access controlled by rank |
| LuckPerms | Permission groups and rank-based access | Administrators configuring what each role can run |
| CoreProtect | Activity logging, inspection, investigation, rollback and restore | Moderators and administrators handling grief or disputes |
| GriefPrevention or WorldGuard | Primary protection for land and server areas | Choose one according to whether players or staff should control protection |
| WorldEdit | Large selections, copying, replacing and staff construction | Trusted builders and senior staff only |
Install one primary land-protection model rather than stacking overlapping claim and region systems by default. Two systems that both decide whether a block may be changed can produce confusing ownership, flag and permission results.
#1 Best Overall
EssentialsX: the everyday command layer
EssentialsX is the broad command suite in this stack. Its current official site describes it as an essential plugin suite with more than 160 commands for servers of all sizes and says it is free, open source and built for Paper and Spigot.
What it adds
- Player conveniences such as homes, warps and teleportation.
- Moderation commands for staff workflows.
- Kits and other routine server commands.
- A consistent command layer that reduces the need to install a separate small plugin for every basic function.
How to deploy it safely
Do not give every player the full command set. Use LuckPerms to create a normal-player group, a moderator group and one or more administrator groups, then grant only the EssentialsX permissions each role needs. Test teleportation, home limits, warp access and moderation commands with accounts in each group before opening the server.
Keep the default configuration under version control or in a protected backup. When you change teleport delays, cooldowns, kits or chat-related behavior, record the reason so another administrator can understand the policy later.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11LuckPerms: make permissions predictable
LuckPerms should be configured before public launch. It is the control plane that prevents a useful command plugin from becoming an accidental escalation path.
A practical group design
- Default: survival gameplay and the small set of EssentialsX commands intended for everyone.
- Trusted player: optional community conveniences that require a history of good behavior.
- Moderator: investigation and moderation permissions, but not unrestricted world editing.
- Builder: WorldEdit permissions needed for approved construction, without rollback or server-administration access.
- Administrator: configuration, protection and recovery permissions, limited to the smallest possible group.
Permissions that deserve extra caution
- WorldEdit can change a very large area in seconds; restrict it to trusted staff and consider separate build worlds.
- WorldGuard region and flag permissions can override normal player expectations around PvP, TNT, mobs and building.
- CoreProtect rollback and restore permissions can remove legitimate work if used with an overly broad selection.
- Teleportation and moderation commands can affect player safety and disputes even when they cannot edit blocks.
After every plugin addition or upgrade, review newly available permission nodes rather than assuming the old group configuration remains complete. Test with a non-operator account; operator status can hide a broken permissions design.
CoreProtect: audit first, then recover
CoreProtect supplies the evidence and recovery layer. Its project describes it as a fast data-logging and anti-griefing tool for inspecting, looking up, rolling back and restoring damage, with previews, multi-world logging, inventory rollback and multiple storage backends. The project says it has been actively developed since early 2012. Those are project claims; verify behavior on your own Paper build before relying on it during an incident.
What to log and why
Activity history lets a moderator answer who changed a block, what changed, where it happened and when it happened. That is more reliable than screenshots or player recollections, especially when several people share a base or a public build.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteA careful grief-recovery workflow
- Stop additional damage. Temporarily restrict the affected area or remove the suspected player’s access while preserving the server world and logs.
- Inspect a sample. Use CoreProtect’s inspection feature on several damaged blocks to establish whether the changes came from a player, a machine, an explosion or another event.
- Run a narrow lookup. Limit the search by world, coordinates, time window and actor when possible. A focused result is easier to validate than a server-wide history dump.
- Preview the proposed recovery. CoreProtect supports previews; use one to confirm that the selected changes match the incident and do not include legitimate construction.
- Rollback only the verified scope. Prefer a small region and a precise time range. Broad rollbacks can erase unrelated work by innocent players.
- Reinspect the result. Check the repaired build, nearby inventories and connected areas. If the first rollback was too narrow or too broad, use the restore capability rather than making another guess.
- Document the decision. Record the affected world, time range, actor or cause, operator and result. This creates a consistent moderation trail for future disputes.
Use the command help available in your installed CoreProtect version for the exact syntax and filters. Command options can change between releases, while the underlying inspect, lookup, preview, rollback and restore workflow remains the important operational pattern.
Choose your primary protection model
The deciding question is who should create and manage protection: players themselves or staff operating a central region policy.
| Decision factor | GriefPrevention | WorldGuard |
|---|---|---|
| Typical owner of protection | Players claim their own land | Staff define and manage regions |
| Best fit | Community survival where self-service claims are central | Spawn, shops, arenas and carefully governed builds |
| Protection style | Claims covering player bases and other personal areas | Regions with detailed flags and area-specific rules |
| Controls highlighted by project documentation | Build and break protection, theft, spam and spawn-camping prevention | PvP, TNT, mobs, item blacklists, piston machines and other per-area rules |
| Version information in the cited listing | Native major version 1.21; tested major versions 1.21, 26.1, 26.2 and 26.3 | Check the project’s documentation and release information for your exact Paper and Minecraft build |
When GriefPrevention is the better choice
Choose GriefPrevention when ordinary players should claim land without opening a staff ticket. Its listing says it prevents forms of grief including build and break damage, theft, spam and spawn camping without a database. That self-service model scales well for a conventional SMP, but you still need clear rules for claim size, abandoned bases, shared projects and staff intervention.
When WorldGuard is the better choice
Choose WorldGuard when the server needs precise, centrally managed regions. It is suited to a protected spawn, an arena with different PvP behavior, a shop district, an event area or a build where staff must control several flags at once. Its documentation covers region creation, per-area rules, PvP and TNT controls, mob behavior, item blacklists and protection against abuses such as TNT cannons and piston machines.
Can both be installed?
Only layer them for a documented reason, such as player claims in the survival world plus staff-controlled regions in a separate event area. Define which system has authority in each world or region, test edge cases at boundaries and publish the resulting rules. Without that design, players and moderators may not know why a block, redstone machine or combat action is allowed in one place and denied in another.
Rank #3
- The classic UNO card game builds fun on game night with a Minecraft theme.
- UNO Minecraft features a deck and storage tin decorated with graphics from the popular video game.
- Players match colors and numbers to the card on top of the discard pile as in the classic game.
- The Creeper card unique to this deck forces other players to draw 3 cards.
- Makes a great gift for kid, teen, adult and family game nights with 2 to 10 players ages 7 years and older, especially Minecraft and video game fans.
WorldEdit: powerful staff construction
WorldEdit is the efficient tool for selections, copying, replacing and large edits. It is not a player convenience plugin; treat it as an administrative capability.
- Grant it only to trusted builders or senior staff through LuckPerms.
- Use a staging or build world for experiments before changing the live survival world.
- Take a backup before large replacements or imports.
- Keep CoreProtect logging enabled so accidental edits can be identified and reversed.
- Review the selected region before executing an operation; a mistaken selection can affect far more terrain than intended.
Optional plugins: add only for a defined need
Optional plugins are valuable when they solve a known requirement. They also add another compatibility surface, configuration file and permission set.
| Need | Plugin or combination | Deployment note |
|---|---|---|
| Bedrock players joining a Java server | Geyser plus Floodgate | Verify the current compatibility matrix before deployment and test authentication, movement, inventories and combat with Bedrock clients. |
| Newer clients connecting to an older server | ViaVersion and related Via plugins | Test gameplay and plugin behavior after every protocol or server upgrade. |
| Browser-based live map | BlueMap, Dynmap or squaremap | Choose one map renderer, decide which worlds and builds are public, and account for the extra rendering and storage workload. |
| Discord and in-game chat synchronization | DiscordSRV | Define moderation, privacy and account-linking rules before enabling two-way chat. |
| Shared economy, chat prefixes or shops | Vault | Install it only when another plugin needs its service bridge; it is not an economy by itself. |
| Controlled world pre-generation | Chunky | Run generation deliberately, preferably before peak player hours, and monitor storage and tick impact. |
| Lag and tick-time diagnosis | spark | Use it as a troubleshooting and profiling tool rather than treating it as a permanent gameplay feature. |
Cross-play with Geyser and Floodgate
Geyser translates Bedrock connections for a Java server, while Floodgate supports Bedrock players joining without a separate Java account flow. Compatibility is not automatic: check the current matrix for your Minecraft, Paper, Geyser and Floodgate versions, then test account identity, permissions, chat, inventory behavior and combat before advertising Bedrock access.
Free tools Windows power users keep installed
One-click scans. No signup required.
Protocol support with ViaVersion
ViaVersion can help newer clients connect to an older server, but protocol translation does not guarantee identical gameplay. Test movement, items, commands, combat, resource packs and every major gameplay plugin after an upgrade. Keep a rollback plan in case a newly supported client exposes a plugin incompatibility.
Maps, chat and service bridges
A live map can help players orient themselves and discover community builds, but public rendering may reveal bases that players expected to keep private. DiscordSRV changes where moderation obligations apply because messages move between two communities. Vault is appropriate only when an economy, chat, shop or similar plugin needs a common bridge; adding it without a dependent plugin creates configuration without a useful outcome.
Compatibility and installation: a low-risk order
Plugin compatibility is tied to the exact Minecraft version and Paper build, not merely to a broad version family. Confirm the Java runtime required by that Paper release, then verify every plugin’s supported versions before downloading.
Rank #4
- Now Minecraft lovers can play a special version of UNO!
- Same as Basic UNO but features Minecraft characters and includes special Creeper rule card. Draw this card and the other players have to draw three more cards from the pile!
- The goal is to get rid of all the cards in your hand.
- First player or team to 500 wins.
- When you're down to one card, don't forget to yell "UNO"!
- Record the target build. Write down the Minecraft version, Paper build and Java runtime that will run the server.
- Download from an official project site or trusted repository. Check the release notes and dependencies for that exact build.
- Back up the server. Include worlds, configuration files, permissions data and any CoreProtect data before adding or replacing jars.
- Install the baseline first. Add EssentialsX, LuckPerms, CoreProtect, your chosen protection system and WorldEdit. Start the server once and let each plugin generate its configuration.
- Read the startup log. Stop and resolve dependency, Java, version or configuration errors instead of ignoring warnings that may disable protection.
- Configure permissions before public access. Build groups in LuckPerms, remove unnecessary operator access and test with ordinary accounts.
- Test in a staging world. Verify a player claim or protected region, spawn rules, teleportation, staff editing and a CoreProtect investigation and recovery.
- Add optional plugins one at a time. Restart and test after each addition so a failure has a clear cause.
- Open the server gradually. Invite a small test group, watch logs and performance, and only then announce the public address.
Testing checklist before launch
- A normal player can build in permitted terrain but cannot modify another player’s protected area.
- Spawn, shops, arenas and event areas obey their intended PvP, TNT, mob and item rules.
- Moderators can inspect activity without receiving unrestricted WorldEdit or administrative permissions.
- A test grief incident can be identified, previewed and rolled back without affecting an unrelated build.
- Homes, warps, teleport delays, kits and cooldowns match the server’s written rules.
- Backups can be restored and the restore procedure is known to more than one administrator.
- Optional cross-play, protocol, map and chat features work on the exact client versions your community uses.
Common failure modes and fixes
Players can run commands they should not have
Check whether they are operators, inherit a permissive LuckPerms group or receive a wildcard permission from another plugin. Test with a fresh account, inspect inherited groups and remove broad grants before adding narrow permissions.
Protection behaves differently at a boundary
Determine whether GriefPrevention claims, WorldGuard regions or both apply at that coordinate. If both are intentional, document precedence and flags; otherwise remove the overlapping system from that world and retest corners, vertical limits and entrances.
A rollback changes too much
Use CoreProtect’s restore capability to reverse the mistaken rollback, then repeat the investigation with a smaller time range, actor filter and region. Always preview a recovery when the incident is not completely understood.
A plugin disables itself after an upgrade
Read the first relevant error in the startup log, verify the Java runtime and Paper build, then compare the plugin’s supported versions. Restore the previous server and plugin backup if protection or permissions cannot be confirmed.
The server lags during exploration
Use Chunky to pre-generate planned exploration areas under controlled conditions, and use spark to diagnose tick-time problems. Do not assume that adding more feature plugins will solve a generation or entity-load bottleneck.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Upgrade and maintenance routine
Before any Minecraft or Paper upgrade, make a full backup and inventory every plugin. Re-check each project’s compatibility information because a plugin that worked on one exact build may fail on the next. Upgrade in a staging copy first, then test permissions, claims or regions, rollback, teleportation and every optional integration that matters to your players.
After the live upgrade, watch the startup log and run the launch checklist again. Pay special attention to protection and CoreProtect: a server that starts successfully is not necessarily a server whose claims, flags or audit records are functioning correctly.
Which stack fits your server?
Small, player-led SMP
Use EssentialsX, LuckPerms, CoreProtect, GriefPrevention and tightly restricted WorldEdit. Add Geyser and Floodgate only if Bedrock access is a real requirement. This keeps claims self-service while preserving staff recovery tools.
Staff-governed community server
Use EssentialsX, LuckPerms, CoreProtect, WorldGuard and WorldEdit. Define regions for spawn, shops, arenas and events, and publish the rules that differ from normal survival terrain.
Multi-platform or community-focused server
Start with one of the two baseline protection models, then add Geyser/Floodgate for Bedrock, ViaVersion when client-version policy requires it, and DiscordSRV or a map renderer only after privacy, moderation and performance tests.
The strongest baseline is therefore not the longest plugin list. It is a small set with clearly separated jobs: EssentialsX for daily commands, LuckPerms for authority, CoreProtect for evidence and recovery, one protection model for land, and WorldEdit for trusted construction.
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.
