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 Jul 10, 2013@BC_Programming
I think it should be changed to containertrust. A lot of guests will arrive to a good claim, and notice their horses will get stuck else. You dont make a claim just to make it public.
-
View User Profile
-
Send Message
Posted Jul 10, 2013Hi,
Using the adjust bonus claim blocks command seems to add blocks on to existing blocks that the player has. Is it possible to set the total for a user?
Or even better, is it possible to set the total (or maximum) via group permissions? i.e, Players will have 8000 blocks, VIPs will have 16000 blocks etc.
Thanks
-
View User Profile
-
Send Message
Posted Jul 10, 2013@gameofblocks
give public access trust in the claim, that let players mount horses they dismounted.
-
View User Profile
-
Send Message
Posted Jul 9, 2013Having an issue, no one can mount a horse in an admin claim. They can ride through the admin claim but if they get off they have to push the horse out of the admin claim or to a subdivision that they have trust on. This a big issue for me because my server has a large admin claim around spawn. Using the lastest Dev build of GP.
-
View User Profile
-
Send Message
Posted Jul 9, 2013@Ahmet094
GP is a bukkit plugin. FTB doesn't use Bukkit.
In Eclipse you would add the plugin jar as an "External JAR", though.
-
View User Profile
-
Send Message
Posted Jul 9, 2013Hey,
i'm writing a plugin vor my FTB server. The problem is, that I added your 1.4.7 GriefPrevention file as a library, but I can't import "Claim" for example.. What am I doint wrong? Is there another extra API-File?
Thanks in advance!
-
View User Profile
-
Send Message
Posted Jul 9, 2013@Absolutionmc
I Honestly have no idea.
@Eelviny
you can delete the player data files for players that logged in before the change from /GriefPrevention/PlayerData/<playername>.dat As far as GP is concerned it will be a "fresh" login. if those players have claims, you'll want to make sure the claims stay by making sure "GriefPrevention.Claims.DeleteWithUnrecognizedOwner" on the config.yml file is set to false.
-
View User Profile
-
Send Message
Posted Jul 9, 2013Hey, having some troubles setting up the starting claim blocks. My setup is that players start with 400 claim blocks, and vote for more. (So BlocksAccruedPerHour is set to 0.0) I've edited my config but it isn't working. Am I missing something? http:pastebin.com/km2A1sDa This is on Dev build 120. EDIT: Found that it was at 100, then adjusted it. Now players that logged in during the update have 100 there, while other after I changed have 400. Any way of fixing this?
-
View User Profile
-
Send Message
Posted Jul 9, 2013@deleted_9935739
Yes, in the newest dev builds, its /gpreload
-
View User Profile
-
Send Message
Posted Jul 9, 2013@BC_Programming
I'm restarting the server, not reloading anything. Is there a reload command now?
-
View User Profile
-
Send Message
Posted Jul 9, 2013Hey BC_Programming just a quick question. I was wondering if performance has improved since 7.7?
-
View User Profile
-
Send Message
Posted Jul 8, 2013@deleted_9935739
The "error" is not actually an error but a purposeful stack trace being emitted that I left in from fixing some other issues.
Are you reloading the configuration for the appropriate world?
-
View User Profile
-
Send Message
Posted Jul 8, 2013@BC_Programming
Set the threshold to that and people still get banned after 3 duplicate messages. Could there be a way to disable it with 0 or -1?
Did you see the error I pasted below? http://pastebin.com/4NtcdmUV
-
View User Profile
-
Send Message
Posted Jul 8, 2013@deleted_9935739
It might need to be one lower, I might have been off. I would set to 32768 (just arbitrarily). The actual check checks if the player's "spamcount" (which is incremented in certain cases, and decremented for 'good' messages) exceeds the value. Really I would think 100 should do in most cases, a player would have to work very hard to get a spamCount that high.
@fungreenfox
7.8 and the dev builds add a Rule for FireSetting as well as FireExtinguishing. I'm not sure what you mean by "expect claims to allow after an hours claim use".
-
View User Profile
-
Send Message
Posted Jul 8, 2013Why is there not a permission for setting fire? I cant find that. I can find
FireSpreads: false
FireDestroys: false
and enabling does not allow to set fire?
Until now, i have had to use worldguard to stop this, but then i would expect claims to allow after an hours claim use?
-
View User Profile
-
Send Message
Posted Jul 8, 2013@deleted_9935739
lol, i have had a player getting banned for loggin in, and just saying Hi.
-
View User Profile
-
Send Message
Posted Jul 8, 2013I set the threshold to that highest number and somehow it banned someone for spam when they said only one thing.
I'm also noticing this error showing up every once in a while. http://pastebin.com/4NtcdmUV
-
View User Profile
-
Send Message
Posted Jul 8, 2013@AwsomeG2
The dev build Already protects horse inventories, riding, and using leads and nametags on animals in claims without the appropriate permission- so yes.
-
View User Profile
-
Send Message
Posted Jul 8, 2013@AdvanceGamingNextLvl
Alright cool
-
View User Profile
-
Send Message
Posted Jul 8, 2013@AwsomeG2 Of course it will, just give them some time