Grief Prevention
AUTOMATICALLY PREVENTS ALL FORMS OF GRIEF, including build/break, theft, spam, fire, spawn camping, lava dumping, chat trolling, advertising and more, so you don't have to undo any damage after the fact. It even teaches players how to use it so you don't have to! No configuration or database required. Stop responding to grief and prevent it instead. Grief Prevention will solve your grief problems without requiring you to manage a roster of trained administrators, juggle 10 different anti-grief plugins, take away cool standard game features, publish a training manual / tutorial for players, or add explanatory signs to your world. You can also choose to integrate PvP elements into build design to finally get a PvP experience befitting a sandbox game about creative building.
Grief Prevention stops grief before it starts automatically without any effort from administrators, and with very little (self service) effort from players. Solve all your grief problems with a single download, no database, and no configuration step.
Got a question or found some random bug? Check the documentation!
Got a problem or bug you can reliably reproduce? Or a feature request? Report it on the issue tracker!
Also, you might be able to catch me/others on the #GriefPrevention IRC channel for help (please state your question and exercise patience if you use this option).
Downloads for older Minecraft Versions
You may also view recent update notes on Github
The Manual
Feature List
Yes, everything is customizable.
- No database or world backups required.
- Extremely efficient CPU / RAM usage.
- Land claims are easy to manage.
- Players create and manage their own land claims, so you don't have to do it for them.
- New players get automatic claims around their first chests so they're protected even if they don't know how to create land claims yet.
- Players who ask for help in chat get an instant link to a demonstration video.
- Resizing claims and creating new claims is done with ONLY the mouse, no slash commands (slash commands are also available).
- When a player appears to be building something nice outside his claim, he's warned and shown his claim boundaries.
- Claim boundaries are easy to see, and don't require any client-side mod installation.
- Extremely easy-to-remember, single-parameter slash commands for giving other players permissions.
- Claim subdivision and granular permissions are available to organize towns and cities. Watch this video.
- It's IMPOSSIBLE to grief a land claim. Watch this video.
- No building or breaking.
- No stealing from ANY containers.
- No sleeping in beds.
- No button/lever usage.
- No adjusting redstone repeaters or other configurable blocks.
- No pushing blocks in with pistons.
- No pulling blocks out with pistons.
- No TNT damage (including cannons).
- No creeper damage.
- No explosive damage from other plugins, like Extra Hard Mode or Magic Spells.
- No enderman/silverfish block changes.
- All doors may be automatically locked (optional, see config file).
- No killing or luring animals away.
- No stealing water (e.g. buckets).
- No trampling crops by players, animals, or monsters.
- No building overtop, all claims reach to the max build height.
- No placing or breaking paintings / item frames / armor stands, etc.
- Fluids will not flow into a claim from outside.
- No placing blocks via TNT/Sand/Gravel cannon.
- Pets and death loot are protected.
- Players can't pick up what another player dropped on death without permission.
- All types of pets are protected everywhere, even outside of land claims (can be configured per-world).
- Excellent anti-spam protection
- Warns, then mutes, then may kick or ban spammers (configurable - you choose).
- Most spammers get only one message out before they're muted.
- Blocks server advertising (IP addresses).
- Blocks repeat message spam.
- Blocks ASCII art (ex. Nyan Cats) spam.
- Blocks similar message spam.
- Blocks unreadable (gibberish) message spam.
- Blocks CAPS.
- Blocks macro spam (very different messages in quick succession).
- Blocks login/logout spam, even when the spammer has multiple accounts.
- Blocks death spam.
- Blocks bot team spam.
- Blocks slash command spam, including /tell, /emote, and any more you add.
- Wilderness Protection and Rollback
- Fire doesn't spread or destroy blocks.
- Creepers and other explosions don't destroy blocks above sea level.
- TNT doesn't destroy blocks above sea level.
- No planting trees on platforms in the sky ("tree grief").
- Instant, point and click nature restoration for not-claimed areas. Watch this video.
- Insanely easy and fast fixes for penises, swastikas, and anything else unsightly.
- Point at what you don't like and click, and it's fixed. Even from far away.
- Never accidentally changes blocks inside land claims.
- No need to investigate who built it, who broke it, or when they did it.
- Doesn't matter if the griefer built with "natural" blocks, it will still be fixed.
- No database.
- No backups.
- No chunk regeneration (it's dangerous for technical reasons).
- Fixes bad chunk generations, like floating islands. It will be better than new.
- Fills holes, even next to water to correct big spills.
- Smooths noisy terrain.
- No griefer construction is safe. If it's unnatural enough to be noticeable by players, it will be removed or filled-in.
- Land claims can't be used as a griefing tool.
- It's impossible to get a player "stuck" inside a land claim.
- Land claims beyond the first require a golden shovel.
- Minimum claim size prevents sprinkling small claims to annoy other players.
- Max claim allowance grows with time played on the server, and can't be cheated by idling.
- A simple administrative slash command will instantly remove all of a griefer's claims, no matter where they are.
- Catches clever griefers.
- Enhances the /ban command to ban ALL a griefer's accounts (not just his IP address).
- Logs sign placements.
- /SoftMute command to shut down chat trolls without them knowing they're beaten.
- Abridged chat logs make reviewing what happened while you were away super-quick and easy.
- Automatically mutes new-to-server players who use racial or homophobic slurs.
- PvP Protections.
- When PvP is off, no setting fire or dumping lava near other players.
- Absolutely bullet-proof anti-spawn-camping protection including bed respawns, which requires no configuration.
- No logging out, stashing items, or using plugin teleportation to escape combat.
- Optional siege mode, to answer players who hide in their claimed houses to avoid combat.
- Supports your server growth.
- Permit players to exchange server currency for claim blocks (requires configuration and other plugins).
- Grant claim blocks automatically for votes, donations, etc (console command provided, other plugins required).
Please Vote for Grief Prevention
I've also posted Grief Prevention on the Spigot site, where plugins are ranked based on reviews. If you love GP, please take a couple of minutes to give GP your rating and leave a short review. Better rating and positive reviews will help server owners who look for plugins on the Spigot site make the safe choice (GP) instead of downloading something sketchy or incomplete. :) Thanks so much for all your support!
http://www.spigotmc.org/resources/griefprevention.1884/
Got a question or found some random bug? Check the documentation!
Got a problem or bug you can reliably reproduce? Or a feature request? Report it on the issue tracker!
Also, you might be able to catch me/others on the #GriefPrevention IRC chat channel for help (please state your question and exercise patience if you use this option).
-
View User Profile
-
Send Message
Posted Nov 24, 20141.8 doors do not register when Lock Wooden Doors is set to true in config. Can you add the new block IDs?
-
View User Profile
-
Send Message
Posted Nov 24, 2014@bigscary Thanks for the quick reply!
Wait.. Looks like the UUID is wrong.. The player UUID starts with 9eda8ab the translated UUID is different.. Will restore and try again..
Looks like it converted the name fine. I found it in the log where it converted it to UUID. I then read the UUID file in the Playerdata dir in 9.1 and compared it to the original 7.7 PRE-UUID name. Both files contain the same data.
UUID conversion of the players data: 2014.11.24.09.46.50 19820 100 Craftee15031613;-3011;-117;2708;;Craftee15031613;-1443;-66;2030
Original 7.7 Playerdata file: 2014.11.24.11.04.34 19820 100 Craftee15031613;-3011;-117;2708;;Craftee15031613;-1443;-66;2030
-
View User Profile
-
Send Message
Posted Nov 24, 2014I meant that players have to move at least 1 block after login (doens't matter if it's first join or not) to be able to chat. I think it's very useful.
-
View User Profile
-
Send Message
Posted Nov 24, 2014@Sckaletz
See setup and config page linked above.
@diskman2000
Restore from backup and send me your logs from when you booted after updating. I'll try to figure out why the UUIDs don't match actual player UUIDs - what's your in game name? I'll need it to search the logs.
-
View User Profile
-
Send Message
Posted Nov 24, 2014Alrighty. Updated from 7.7 to 9.1. Went OK but it doesn't know who the owners of the existing claims are. Logged in and it wont allow me to edit my claims. I can create new ones just fine.
Ideas?
-
View User Profile
-
Send Message
Posted Nov 24, 2014Where do I activate the command /BuyClaimBlocks? It says it's not active and I can't find anything about it in the config.
-
View User Profile
-
Send Message
Posted Nov 24, 2014@LeonardoGamer
Will do. :)
@xSnowBlitzz718
Sorry it didn't work - please send me that link you mentioned via private message and I will dig into it further.
@CKGAR
You can disable altogether the automation claim creation with chest placement, but no, there's no option to lift the one chest claim per player rule.
@cindy_k
That's much slower than it should be - I will review and try to guess why your server migrates so much more slowly than most. Please shrae your logs, if you kept them? Also are you in offline mode, online mode, or using Bungee?
@Turbotailz
I'll get transferclaim its own permission node. Right now, it's the adminclaims permission, since when I first created transferclaim, only admin claims could be transferred.
@mirolm
Thanks for the bug report, I'll check on that.
@ZacuXDMG
No sorry, claim blocks are per server, not per world.
@CloakedAlien
Impossible for vanilla servers - it wouldn't be vanilla after I modded it to run grief prevention. And then it wouldn't run other plugins. I can't predict the future either, but I think spigot is the short term best bet, and Sponge the best long term bet.
@mcly
It could - do you mean no chat before moving after the first join, or requiring movement between every two chat messages? Have to be careful not to mute normal chat.
@Disorbs
There's a workaround in the "how to" page. I do plan to stop players from creating land claims on top of world guard regions unless they also own the world guard region in the future.
@diskman2000
It should work, but please back up just in case!
@Luficer
Are you using vanilla client? if so which version? Several have reported this, but I havne't been able to reproduce it to fix it yet.
-
View User Profile
-
Send Message
Posted Nov 24, 2014@Disorbs
I ended up using GP with WorldGuard in my spawn for this reason. I also set the cost of using GP at a level where my players don't want to squander their claimblocks.
-
View User Profile
-
Send Message
Posted Nov 24, 2014Ok.. I have been running GP 7.7 since July 2013. Can I safely upgrade to the current version?? Or will I lose all of my server claims and such?
Thanks!
-
View User Profile
-
Send Message
Posted Nov 24, 2014@Disorbs
As of right now the only way to prevent claiming in a world guard region is to claim the region with an admin claim. At some point in time world guard MAY be supported but not right now.
-
View User Profile
-
Send Message
Posted Nov 24, 2014I have a problem that i need help with.
So i have world Guard and this plugin but how can i set it so people cant claim on my Spawn do i just claim it on my own or is there a command with world Guard that disables this something like /rg flag spawn "grief-prevention" deny ? thanks
-
View User Profile
-
Send Message
Posted Nov 24, 2014Can the Spam feature blocks sending message if the player hasn't moved at all?
-
View User Profile
-
Send Message
Posted Nov 24, 2014Just stepping in to make sure you guys are still with us =)
We're stuck in Bukkit 1.7 like everyone else. Fingers crossed any alternatives will turn up soon. Our server is still quite active and liked. Grief Prevention is pretty much the plugin that determine which platform we'll end up with.
I'm guessing it's a bit far-fetched to hope for a version that works with vanilla servers?
If nothing else it looks like Spigot has something in the works.
-
View User Profile
-
Send Message
Posted Nov 23, 2014==== Does it support Multiverse allowing a seperate ammount of claimblocks per world?
Ex. 12482 Blocks in survival 9821 blocks in creative
If so how do i enable it?? ==== ==
-
View User Profile
-
Send Message
Posted Nov 23, 2014How could I make it so every chest placed is automatically protected?
-
View User Profile
-
Send Message
Posted Nov 23, 2014@Bobcat00
The permission is definitely spelt correctly. They have access to all the admin claim stuff just not /transferclaim. I'm using verion 8.7.1, I probably should update.
-
View User Profile
-
Send Message
Posted Nov 23, 2014Got this today on my offline mode server. Running Griefprevention 9.1 and 20141113a spigot.
[15:59:15] [Thread-114/INFO]: GriefPrevention: Unable to load data for player "b9cedc37-dc49-35d6-a113-b18ba3c8e1ee": java.lang.NullPointerException [15:59:15] [Thread-114/WARN]: java.lang.NullPointerException [15:59:15] [Thread-114/WARN]: at java.text.SimpleDateFormat.parse(SimpleDateFormat.java:1380) [15:59:15] [Thread-114/WARN]: at java.text.DateFormat.parse(DateFormat.java:355) [15:59:15] [Thread-114/WARN]: at me.ryanhamshire.GriefPrevention.FlatFileDataStore.getPlayerDataFromStorage(FlatFileDataStore.java:481) [15:59:15] [Thread-114/WARN]: at me.ryanhamshire.GriefPrevention.PlayerData.loadDataFromSecondaryStorage(PlayerData.java:183) [15:59:15] [Thread-114/WARN]: at me.ryanhamshire.GriefPrevention.PlayerData.getAccruedClaimBlocks(PlayerData.java:149) [15:59:15] [Thread-114/WARN]: at me.ryanhamshire.GriefPrevention.DataStore$SavePlayerDataThread.run(DataStore.java:1292)
-
View User Profile
-
Send Message
Posted Nov 23, 2014@Turbotailz
griefprevention.adminclaims should work for /transferclaim. What version are you using? Also check that you spelled the permission properly.
-
View User Profile
-
Send Message
Posted Nov 23, 2014@Luficer
I want my Moderators to have access to /transferclaims, I have given them the adminclaims permission as well as adjustclaimblocks, which both seem to work fine for their intended purposes, just not /transferclaim.
It's not a huge deal because obviously I can just transfer the claims myself, but it would be nice to have my Moderators do this on my behalf.
-
View User Profile
-
Send Message
Posted Nov 23, 2014@Turbotailz
Looking at the GP repo, it would seem this may be a small issue in the current version. (At least on the version reflected on the repo). The plugin.yml specified the permission to be "griefprevention.adjustclaimblocks", however, by looking at the code handling the command, it looks to be checking the permission node "griefprevention.adminclaims".
I'm assuming, at least because of that permission node, that transferclaim is only for admins now, versus it being a player thing in BCProgramming's versions. So if you need your admins to have access to it, give them the adminclaims node, however, if you give it to other players, they'll have a lot of power you probably don't want them to have.