What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
On a Paper or Spigot server, installing GriefDefender means installing LuckPerms v5 first, placing the GriefDefender jar in plugins/, starting once to confirm it loads, setting spawn-protection=0 in server.properties, and then assigning GriefDefender permissions. Players have no claiming rights until you grant them. The same protection plugin has separate compatibility rules for Sponge and for Patreon-only Forge, NeoForge and Fabric builds.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Minecraft Java servers with free DDoS protection and up to three free backups a day.
This guide covers the complete setup path, the decisions to make before downloading anything, permission examples, configuration locations, verification tests and the failure modes most likely to prevent claims from working.
| # | 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 →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Choose the correct GriefDefender build first
GriefDefender is not one universal jar. Its supported server platform determines which build and dependency versions you need. Confirm the platform and API version before copying files into a live server.
| Server platform | Support noted in current documentation | LuckPerms requirement | What this means for installation |
|---|---|---|---|
| Paper, Spigot or another Bukkit-compatible server | Supported path; use an up-to-date Paper or Spigot server | LuckPerms v5 | Follow the Bukkit steps in this article and install both jars in plugins/. |
| Sponge 1.12.2 | Listed Sponge version | LuckPerms version appropriate to the Sponge API; latest for API 8/9, v5.3.98 for API 7 | Use the Sponge build and its platform-specific installation method, not the Bukkit jar. |
| Sponge 1.16.5 | Listed Sponge version | LuckPerms version appropriate to the Sponge API; latest for API 8/9, v5.3.98 for API 7 | Check the server’s API level before choosing LuckPerms. |
| Forge, NeoForge or Fabric | Builds are listed as Patreon-only | Depends on the loader build | Do not place a Bukkit jar in a mod-loader server. Obtain the correct eligible build and follow its loader-specific instructions. |
The compatibility list is time-sensitive. The current GriefDefender release number and release date were not established in the available documentation, so select the newest file shown by the project’s current download channel for your platform rather than relying on an old filename.
#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).
Java version caveat
The GitHub README for the Bukkit version lists Java 8, but that statement may be outdated as Minecraft server requirements change. Check the current GriefDefender and server documentation for the Java requirement that matches your Minecraft version before changing the runtime. Do not downgrade a working server’s Java installation solely because an older README mentions Java 8.
Prepare the server before changing files
Install from the server’s control panel or host file manager only when the server is fully stopped. A running server can overwrite configuration files during shutdown or leave a plugin half-loaded.
- Confirm the platform. In the console or startup panel, identify whether the server is Paper, Spigot, Sponge or a mod-loader server. The instructions below assume Paper or Spigot unless a section says otherwise.
- Make a restorable backup. Save the world directories,
server.properties, the existingplugins/directory and permission-plugin data. A plugin installation normally adds files, but a backup lets you undo a bad configuration or an incompatible jar. - Stop the server cleanly. Use the panel’s Stop control or the console’s normal stop command. Do not replace jars while the process is still running.
- Check file access. You need permission to upload jars, edit
server.propertiesand restart the process. On a managed host, these are usually separate file-manager and console controls. - Keep a maintenance window. The first start can generate configuration folders and produce dependency errors that require another stop and edit.
Install GriefDefender on Paper or Spigot
Paper and Spigot use the Bukkit plugin layout. LuckPerms is a required dependency, and GriefDefender supports LuckPerms v5 only.
1. Install LuckPerms v5 for your server
Download the current LuckPerms build for Bukkit (or Folia when that is the server software you actually run). Place its jar in the server’s plugins/ directory while the server is stopped. Do not substitute a LuckPerms build for a different platform, and do not install an older major version simply because it has a familiar filename.
2. Download the matching GriefDefender jar
Use the GriefDefender file from its Spigot listing for a Paper or Spigot server. Choose a release compatible with your Minecraft/server version. The exact current release number is not established here, so verify it at download time rather than copying a version from an old tutorial.
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).
3. Upload both jars
Place the LuckPerms and GriefDefender jars directly in plugins/, not inside a second folder and not in mods/. Keep only the files you intend to load; duplicate copies of a plugin can cause ambiguous or failed loading.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems4. Start once and read the console
Start the server and watch the complete startup log. A successful load produces a GriefDefender enable message and a LuckPerms enable message. If either plugin reports a dependency, platform or Java error, stop and correct that error before creating claims.
5. Stop before editing generated files
After confirming that the plugin loaded, stop the server normally. GriefDefender creates its data under a GriefDefender folder in the server’s configuration or plugins area; the exact parent location depends on the platform and server layout. Editing while the process is running risks having your changes overwritten.
Set the server’s spawn protection correctly
Open server.properties while the server is stopped and set:
spawn-protection=0Save the file and restart. Vanilla spawn protection can reject a player’s interaction before GriefDefender evaluates the claim, so leaving a nonzero value can make protection appear to malfunction around the world spawn. This setting controls the server’s built-in spawn area; it does not grant players permission to build elsewhere.
Free tools Windows power users keep installed
One-click scans. No signup required.
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.
Give players and staff the required permissions
GriefDefender does not give ordinary players claiming rights by default. Use LuckPerms, or another permission manager that is compatible with your server, to assign the nodes below.
| Role | Permission nodes | Purpose |
|---|---|---|
| Regular players | griefdefender.user.* |
Basic user and claiming functionality. |
| Staff or administrators | griefdefender.user.* and griefdefender.admin.* |
Normal user functions plus administrative controls. |
Assign the user node to the group that new players inherit, then add the admin node only to a controlled staff group. Avoid granting administrative permissions to the default group.
LuckPerms command examples
From the server console, a typical LuckPerms v5 setup can look like this (replace group names with the groups you actually use):
/lp group default permission set griefdefender.user.* true
/lp group moderators permission set griefdefender.user.* true
/lp group moderators permission set griefdefender.admin.* trueThese commands change permission data, not GriefDefender’s files. If your host or permissions setup uses a web editor, apply the same nodes there and allow LuckPerms to save before testing.
Configure GriefDefender after the first successful start
Open the generated GriefDefender folder only after stopping the server. Depending on the platform, it is under the server’s configuration directory or the plugins directory. Keep a copy of the original files before changing values.
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
Separate file settings from permission settings
Use configuration files for server-wide behavior and defaults. Use LuckPerms for who may perform an action. A player can have a correct configuration and still be unable to claim if griefdefender.user.* is missing; conversely, a player with permission cannot override a server-wide option that disables or limits a feature.
Change one setting at a time
Make a single change, save the file, restart and test. This makes a malformed value or an unexpected interaction easy to identify. Never edit generated files while the server is running, and do not delete a data file to solve a permission problem before taking a backup.
Verify that the installation works
Test with a non-operator account as well as an administrator. Operators can hide missing permission nodes, so an operator-only test is not sufficient.
- Confirm the console shows both LuckPerms and GriefDefender enabled without red error lines.
- Join with a normal player account that belongs to the group receiving
griefdefender.user.*. - Use the GriefDefender claim tool or command exposed by the installed version to create a small test claim in a disposable area. The exact in-game command and tool can vary by release; use the command list shown by that build rather than copying a command from an older version.
- Log out or use a second account to attempt a block break and placement inside the test claim. A non-member should be denied according to the claim’s defaults.
- Test outside the claim to ensure ordinary building still follows your server’s normal rules.
- Repeat near the world spawn. If actions there fail before claim checks occur, recheck that
spawn-protectionis exactly0and that the server was restarted after saving. - Check the permission plugin’s verbose or audit view if available. It should show the player’s group receiving the GriefDefender user node.
Sponge installation: what changes
Sponge is a separate platform, not a drop-in replacement for Bukkit. The supported versions listed for GriefDefender are Sponge 1.12.2 and Sponge 1.16.5. Use the Sponge GriefDefender build and its platform-specific directory and startup process.
Match LuckPerms to the Sponge API
For Sponge API 8 or 9, use the latest LuckPerms release that supports that API. For API 7, the documented LuckPerms version is 5.3.98. Determine the API level from the Sponge server information, not just from the Minecraft version.
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
Install through the Sponge layout
Stop the server, back up its files, download the Sponge-compatible GriefDefender and LuckPerms files, and place them where that Sponge distribution expects plugins. Start the server and inspect the log for both modules. The configuration folder is still named GriefDefender, but its parent directory can differ from a Bukkit installation.
Some hosting guides direct administrators to obtain Sponge builds through the GriefDefender Discord rather than a fixed download URL. Treat those instructions as secondary: verify that the file is an official, current build for your Sponge version before installing it.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Forge, NeoForge and Fabric builds
GriefDefender builds for Forge, NeoForge and Fabric are listed as Patreon-only. They are not interchangeable with the free Bukkit or Sponge jars. If you run one of these loaders, obtain the eligible loader build, follow its supplied installation notes and confirm that its dependency versions match the loader and Minecraft version. Do not copy the Paper/Spigot steps into a mod-loader server.
Troubleshoot the common installation failures
| Symptom | Likely cause | Correction |
|---|---|---|
| GriefDefender is marked as failed or missing a dependency | LuckPerms is absent, the wrong platform build is installed or LuckPerms is not v5. | Stop the server, install the Bukkit/Folia LuckPerms v5 build that matches the server, remove duplicate or wrong-platform jars and restart. |
| The jar is in the folder but no enable message appears | The file is in the wrong directory, the server is not Bukkit-compatible, or the filename is not a valid jar. | Confirm the server platform, place the jar directly in plugins/ for Paper/Spigot and read the startup log for the first load error. |
| Players can join but cannot claim | Players have no GriefDefender user permission by default. | Grant griefdefender.user.* to their LuckPerms group, reconnect or refresh permissions, then test with a non-operator account. |
| Administrators lack management commands | The admin node is missing even though the user node is present. | Grant griefdefender.admin.* in addition to griefdefender.user.* to the staff group. |
| Actions fail near spawn but work elsewhere | Vanilla spawn protection is intercepting the action. | Set spawn-protection=0 in server.properties, save while stopped and restart. |
| Changes revert after a restart | The file was edited while the server was running, or the wrong GriefDefender folder was changed. | Stop cleanly, identify the generated GriefDefender folder under the active server directory, edit once, save and restart. |
| Sponge reports an API or compatibility error | The Sponge version or LuckPerms API build does not match the supported combination. | Check whether the server is Sponge 1.12.2 or 1.16.5, identify API 7 versus 8/9 and install the corresponding LuckPerms version and GriefDefender build. |
| The server will not start after adding the jar | Platform, Minecraft, Java or plugin-version incompatibility. | Stop, restore the backup or remove the new jar, read the earliest error in the log, and verify current Java and release requirements before trying again. |
Updating or removing GriefDefender safely
Update procedure
- Announce maintenance and stop the server normally.
- Back up the world,
server.properties, theGriefDefenderfolder and LuckPerms data. - Replace the old GriefDefender jar with the current build for the same platform. Keep LuckPerms on a supported v5 release for Bukkit or on the documented Sponge API version.
- Start the server and inspect the complete log before allowing players to return.
- Test a normal player claim, a staff action and a protected-area interaction.
Because release and Java requirements can change, check the current project documentation whenever you update rather than assuming an older version’s requirements still apply.
Removal procedure
Stop the server before removing the jar. Preserve the GriefDefender data directory and a backup of the world if you may reinstall later. Removing the plugin does not automatically make a safe policy decision about existing claim data; keep that data until you have confirmed what your replacement protection system will do.
Operational checklist
- Server platform identified before downloading.
- LuckPerms v5 installed for Bukkit/Paper/Spigot, or the API-matched version installed for Sponge.
- GriefDefender jar placed in the correct platform directory.
- Startup log confirms both plugins load.
spawn-protection=0saved inserver.propertiesand followed by a restart.griefdefender.user.*assigned to the player group.griefdefender.admin.*assigned only to trusted staff, alongside the user node.- Configuration edited with the server stopped and backups retained.
- Claims tested with a normal account, an administrator account and a player outside the claim.
The Bottom Line
For Paper or Spigot, the dependable order is: install LuckPerms v5, add the GriefDefender jar to plugins/, confirm both load, set spawn-protection=0, then grant player and staff permission nodes. Choose a separate, platform-matched build for Sponge or for the listed Patreon-only mod-loader versions.
Recommended Free Tools
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.
