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 Apr 11, 2015I use this on my server 1.7.10 and it works great. But I need to disable mobs from spawning in the claimed land. This plugin does not have an option of doing that. So I tried getting Flags . Flags is not working with the 1.7.10 Grief Prevention download. Does anyone know of any version of flag that works with the 1.7.10 Grief Prevention download? Or does anyone know any way to allow players to disable mob-spawning in their claimed land?
-
View User Profile
-
Send Message
Posted Apr 11, 2015Great to see the explosions fixed, still a few issues:
-
View User Profile
-
Send Message
Posted Apr 11, 2015@DannyPokemon
I did exactly what I did when I updated when my network was running on Linux, but through Git on Windows. However, when I run it I get this error:
http://www.hastebin.com/eyoguxedek
Perhaps I need to open a port on the Windows firewall?
-
View User Profile
-
Send Message
Posted Apr 11, 2015Hey everytime I try to add a world and make a claim in it, I'll restart the server and the claim will be gone and the world will be deleted from the config. Any ideas?
Here is my config:
-
View User Profile
-
Send Message
Posted Apr 11, 2015@LeeTheENTP
lol, have you extracted it with Git? it takes about 15mins to extract. also download the latest one from here:
https://hub.spigotmc.org/jenkins/job/BuildTools/lastSuccessfulBuild/artifact/target/BuildTools.jar
also go here for instrutions: http://www.spigotmc.org/threads/bukkit-craftbukkit-spigot-1-8.36598/ press page down once and it's at the bottom of that screen.
-
View User Profile
-
Send Message
Posted Apr 10, 2015Version 1.3 on Spigot 1.8.3 I appear to be able to break items out of items frames in other players' claims but not put them back without permission.
-
View User Profile
-
Send Message
Posted Apr 10, 2015@screamingaxe
If you don't allow players to create land claims in worlds where they can also claim using factions, then yes (you can choose which worlds grief prevention allows land claims in by editing the config file).
GriefPrevention does all the anti-grief WG does and a lot more. However, WG does have some features which are NOT anti-grief, for example preventing monsters from spawning in a region or stopping players from getting hungry in a region. On my test server, all protections are grief prevention EXCEPT for the spawn, because there I also want to prevent players from getting hungry.
-
View User Profile
-
Send Message
Posted Apr 9, 2015im >< close to getting this plug in i have 2 questions 1 will this plugin work well with factions? and 2 can this fully replace worldguard? BTW love the vid well done.
-
View User Profile
-
Send Message
Posted Apr 9, 2015@bigscary
Ah, if it's pulling who tamed it from MC - That's possibly where the "who's owner" issue comes from - Horse trading is big on our server. It's very possible PlayerA tamed it, and sold it to PlayerB - but GP is showing "PlayerA" as the owner because of that. Our horse manager handles ownership differently, and doesn't care who tamed it originally.
I have not yet turned off Creature Protection (active server :P) to see if that will prevent the problem with Horses. Of course, that'd be a whole new set of problems, but one step at a time, I guess. :)
-
View User Profile
-
Send Message
Posted Apr 9, 2015@bigscary
Crap, I'm stuck on 1.8 until I can get BuildTools to work. I heard I needed to already have BuildTools stuff run at least once before in order for the 1.8.3 update to build, but I don't know which version of BuildTools I should run before running a 1.8.3 build.
Man, I used the word "build" a lot in that post.
-
View User Profile
-
Send Message
Posted Apr 9, 201511.3 Updates
DO NOT Update GriefPrevention to 11.3 or later until you've updated your server to 1.8.3. If you do, explosion protection features will NOT WORK. This is unavoidable, and due to a change made by the Spigot/CraftBukkit team.
@raum
GP isn't storing information about who owns the animal - minecraft does to track who tamed it, and GP just looks at that information (and /givepet will make GP change minecraft's data). GP only uses land claims when the animal hasn't been tamed yet. I'll experiment with toggling the pet protections off to see if I can reproduce the problem and fix it. Sorry for the trouble!
@fungreenfox
If you're getting that warning, it means whatever server version you have is missing the BlockPistonRetractEvent.getBlocks() method which was added somewhere in 1.8.1 after the initial release. You might try updating your buildtools.jar first, then running it. If that doesn't help, maybe executing the "version" command in console and sharing the output with me would give me a hint to work from.
-
View User Profile
-
Send Message
Posted Apr 9, 2015@bigscary
I am getting this [18:00:29 INFO]: 103 [18:00:30 INFO]: GriefPrevention: Your server is running an outdated version of 1.8 which has a griefing vulnerability. Update your server (reruns buildtools.jar to get an updated server JAR file) to ensure playres can't steal claimed blocks using pistons. [18:00:30 INFO]: GriefPrevention: Your server is running an outdated version of 1.8 which has a griefing vulnerability. Update your server (reruns buildtools.jar to get an updated server JAR file) to ensure pl... it just goes on and on and on four times them pauses a bit and again spamming.
-
View User Profile
-
Send Message
Posted Apr 8, 2015@mitchgib In the config.yml, set AdminsGetSignNotifications: false
@MrHollick for Pistons, set: LimitPistonsToLandClaims: false
Also, You can completely turn off GP for certain worlds By setting 'Claims.Mode.<world>' to Disabled
-
View User Profile
-
Send Message
Posted Apr 8, 2015@bigscary
If the player uses /givepet, nothing occurs. If anyone tries to click on the horse, hits the horse, tries to ride the horse, tries to shoot the horse, etc, it says it belongs to someone else. There's no claims, aside from the ACTUAL owner of the horse's claim (not who it says is the owner).
The message states "That belongs to <Player>. To override, use /IgnoreClaims" for the staff. For the players, it says roughtly the same thing, but that the owner can use /givepet. The big problem is: <Player> Doesn't even own the claim, nor have they ever. Half the time, the players don't have any claims anywhere NEAR the location, nor are they trusted to the claim where the horse is having the problem.
This issue seems to be popping up all over the place - Have had about 50 new reports of it occurring in the last few days. Rather frustrating, considering that GP isn't even supposed to be touching our horses. :P
Edit 1: Furthermore, WHERE does GP save horse info? I can't find anything regarding the horses in any of the player files - searching by the Horse's UUID OR the player's UUID.
Edit 2: Is it possible GP is incorrectly seeing horses as 'Creatures' as far as the config is concerned? (ProtectCreatures IS on - I will turn it off and see if that corrects the issue.)
-
View User Profile
-
Send Message
Posted Apr 8, 2015When someone places a Sign, it logs it in the chat? How to prevent this from happening? Thanks :)
-
View User Profile
-
Send Message
Posted Apr 7, 2015@OddWhirled
Thanks OddWhirled but i can't seem to locate the option to change it. Also It is effecting worlds that Im not even using claims in like Skyblock. Well Im using multiverse so they are connected but thought grief prevention wasn't even used in other worlds. Can you tell me where/which config file to can override to allow pistons anywhere?
-
View User Profile
-
Send Message
Posted Apr 7, 2015@MrHollick
Pistons only work inside of land claims now because it is less stressful on the server to handle them this way. If you are okay with the increase on server load you can change the config to allow pistons to work anywhere. :)
-
View User Profile
-
Send Message
Posted Apr 7, 2015After switching over from Bukkit to Spigot and updating to 1.8.3 from 1.7.9. All the pistons in my sever don't work anymore. Players are getting error messages from grief prevention. Is there something Im missing? Never experienced this before and all current builds have stopped working where pistons are concerned.
Everything else seems just fine. So if you could please tell me how to get pistons to work again that would be great.
-
View User Profile
-
Send Message
Posted Apr 6, 2015Ok, I had version 11.0.1 and Spigot version 1.8.0 and that bug where PvP rules are enabled in disabled worlds was annoying me, so I thought maybe I had errors in my config. I deleted config.yml, messages.yml, and _schemaVersion as well to be safe... Then I reloaded the server and suddenly all claims belonged to "administrator". I think it was cause I deleted _schemaVersion but I don't know what to do. All my players' claims are admin claims now! I even stopped the server, and updated to 11.2.2 and Spigot build 1.8.3 and it is still this way. I think I have screwed myself over and I'm not blaming anyone but if there is any help please tell me! :(
Also, I did not even TOUCH the ClaimData and PayerData folders
-
View User Profile
-
Send Message
Posted Apr 6, 2015@bigscary
The Spigot folks broke MobArena without warning, too.