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 Jun 25, 2013Is this plugin compatible with the new modpack Hexxit for online servers?
oLLyyy.
-
View User Profile
-
Send Message
Posted Jun 25, 2013@AmicusMCS
They are missing config entries or rather configurations that are used but weren't being initialized in two cases. The third looks like the bug with Java's Calendar.getInstance() returning null that I recently discovered myself.
-
View User Profile
-
Send Message
Posted Jun 25, 2013@BC_Programming
Please consider at least glancing at these and confirming that you glanced. I don't require a full explanation by any means, just some acknowledgement and perhaps reassurance of a solution (if it can be fixed - in order for me to use this plugin, they must be).
-
View User Profile
-
Send Message
Posted Jun 25, 2013@BC_Programming
Did you even look at the script I wrote? It doesn't check for events for that item, it is triggered when a player right clicks/left clicks or anything else you set it to check for. It doesn't matter what item you're holding, a mouse click is still a mouse click. Next it checks the id of the item you're holding. It doesn't matter what the item is, what it does, what events it has, what mod it's from, or anything else. If you right click while holding item x, while in a claim, or while targeting a claim, the right click is cancelled, not the item event that doesn't exist, the right click event that does exist.
I do use the skript plugin and it does exactly what you say can't be done. I use it to disable a lot of things with broken items. The only thing I can't do is use gp claims as a script condition, that's why I made a suggestion. I'll ask njol if he can add gp claim conditions if he is able, and if you're ok with that.
Also the nuke ray is just an example name.
Btw I am not trying to be rude, offensive, or insult you. I love GP and modded servers are starting to choose protection mods that work better for modded servers instead of GP. I still prefer GP and was only suggesting a way to make it better.
-
View User Profile
-
Send Message
Posted Jun 25, 2013@Tsugaga
The ones that don't raise events don't raise events. They don't raise other events. Even for the ones with which this would work, it would be completely pointless.
Let's say we made a Mining laser work only on an owned claim.
Great. So now a player just has to make a claim near another person's claim and they can set it to long range and decimate that other claim, because the only thing cancellable is whether it's shot at all. The actual laser itself does not raise any events when it breaks things. I don't know what this "Nuke Ray" item is you refer to or what it's from, but I don't see how it would be any different.
From what I could tell most objects, particularly things like thaumcraft wands, simply don't work. cancelling the Interact Event doesn't stop it from being activated.
I did look at the source. I'll reserve my comment on it, but as far as I can tell it just uses the same events. I looked into this when you commented and honestly I came away extremely annoyed because you wasted my time. Despite your protestations, the event cannot always be cancelled, and it depends entirely on the item. And even for those with which it does work, it won't protect anything anyway.
Oh, it's simple! cool. issue a pull request then. I'm not even going to bother iterating the performance and regressional implications of this idea, nor the fact that it relies on the items in question working a specific way. And that is ignoring the fact that many items cannot be prevented from working anyway (thaumcraft wands for example) And others don't work exactly as one would expect. A player could build a pillar on each side of a claim and target a long-range mining laser in such a way as to be able to shoot and break blocks within that claim, because the laser entity effects more then specifically what you are looking at. Other items, such as Wand of Equal Trade, even if the event could be cancelled in specific cases (they can't, since they don't appear to respect the cancel event at all) using it can affect nearby blocks and could easily be used to grief even with your 'simple' restrictions.
-
View User Profile
-
Send Message
Posted Jun 25, 2013@BC_Programming
That's why you use other events. As for using the item outside of claims I could do
with skript. of course "claimed" doesn't work, just put it there for the example. You could speak with njol(Skript dev) on how to achieve this, or just check the src, it's open. Basically GP would just take the item id's that owners add to the config and disable it completely if in an untrusted claim or targeting one.
These problem items basically make claims useless on some modded servers. I think if you got his feature added and working then GP would be a viable option for so many more servers.
-
View User Profile
-
Send Message
Posted Jun 24, 2013@GamersSynergy
It's whatever I happen to have written. It will contain debugging code. It will contain diagnostic println's. Why? Because when I'm investigating why something isn't working, I don't want to have to engineer some complex optional debug output feature- I want to be sure that I'll get the information I need, so they get hard-coded.
Because it's a dev build. Quite literally they are made automatically by jenkins whenever I push. This is part of the reason why I've been tempted to start pushing my changes to my fork rather than Tux2's upstream repository, and issue a merge for dev-build prepared stuff.
Fork it and remove the System.out.println() statements, or, you could use a bytecode editor and patch them out. There is no option for it because these are development builds. I'm not in the habit of engineering a entire framework just to support one-off debug statements.
Oh heavens no! Just debug statements. They will either be removed or, as Zlepper has previous suggested, could be provided as part of debugging options for diagnostic purposes when other issues are encountered.
@chrishillz
That doesn't really tell me anything.
-
View User Profile
-
Send Message
Posted Jun 24, 2013can you please make so people CAN build/break in claims in pvp combats?
-
View User Profile
-
Send Message
Posted Jun 24, 2013There's one glitch that makes the claim permissions not work. It only works if you set it to everyone when using permsbukkit. It may affect other perms systems.
-
View User Profile
-
Send Message
Posted Jun 24, 2013@BC_Programming I think I know a dev build when I see one, but I wanted to know WHY it was spamming my console and all I was wanting to know was how to turn it off, if possible. It's that simple. I wasn't sure if it was a new feature or not. No need to be an ass about it.
-
View User Profile
-
Send Message
Posted Jun 24, 2013@GamersSynergy
Oh, the answer is simple. It's a development build. Seriously. THIS is why I stopped pushing commits, because So many oblivious server owners seem to think that development builds are production ready and expect all these options to control debug output. Those are there because I just added those features and need to be able to track them.
@Tsugaga
I can see you really thought that through. Except for the part that wouldn't prevent griefing. Players could still use the items from outside the claim and aim inside the claim. Even if you restrict it entirely to owned claims, they could make a claim right next to another one and then use the item. Making the effort spent on such a "restriction" feature completely moot.
Also, I tested several items. None of them raise Any events; Thaumcraft Wands, for example, do not raise PlayerInteractEvent and it cannot be cancelled. I know because I had several builds that had debug output on all event handlers. And things like mining lasers and buildcraft quarries raised absolutely no events, and those that did either weren't cancellable or didn't respect the cancellation, or, even worse, would only sometimes appear to respect the cancellation.
@damndummie
If your server has multiple worlds, claims can be lost in a world if that world is not loaded when the claim is in 7.7.
It's also worth noting that Claims can be cleaned up automatically. if somebody makes a claim and has very little of value within it, it will be removed in a week or two. With that many claims and presumably that many players, No doubt some of the claims that are going "missing" are in fact from this. You can enabled and disable this feature I believe, or change the config options regarding it so that it won't be able to find claims that meet the criteria.
-
View User Profile
-
Send Message
Posted Jun 24, 2013@zlepper Well i am up to the latest 7.7 for CB 1.5.1. I'm using mysql. If I had to guess I would say there are at-least 4000 plus claims. I'm kinda freaking out because this seems like it may be the beginning of the end for my server. I cant spend all my time trying to replace everyone's losses.
-
View User Profile
-
Send Message
Posted Jun 24, 2013@zlepper
Well then why is the skript plugin able to achieve this? You can do things like
If an item is added to the config, and the player isn't trusted then the event can just be canceled.
-
View User Profile
-
Send Message
Posted Jun 24, 2013@Tsugaga
Sadly BC can't do that, since it would require either forge specific coding (which he stated he wouldn't include) or that some guy comes along and make all mods throw somekind of bukkit event he can use.
@damndummie
2 questions: What build are you on? both minecraft and griefprevention.
and are you using flatfile or MYSQL for data storage?
If you are using MYSQL try switching to flatfile, i had some problems with MYSQL myself in the dev builds, switched to flatfile, no problems from there, this however is very hard to do if you have a big server or a server with a lot of claims, since i think they will have to be reclaimed.
-
View User Profile
-
Send Message
Posted Jun 24, 2013Anyone else having random people lose their claims? I have had around 5 (that i trust) people in the last month including both of my accounts lose their claims. Generally I question anyone that says that, and basically tell them that they screwed up somehow. But its happened to both of my accounts and I'm the damn owner. If it wasn't for the fact that I dont make any changes to plots or add or remove anyone on one of my accounts, I would suspect myself of even screwing up. Anyone else?
-
View User Profile
-
Send Message
Posted Jun 24, 2013GP is amazing but it needs more features to keep up with modded servers. It has the config for adding more modded id's but it also needs a config for adding item usage. If a player uses that item in a claim they aren't trusted in, it doesn't allow it. This is a feature that is needed for servers that have many items that bypass claims.
-
View User Profile
-
Send Message
Posted Jun 24, 2013Players can siege while protected from pvp... This needs to be fixed. I also think there should be an option in the config to allow players to place blocks during a siege.
-
View User Profile
-
Send Message
Posted Jun 24, 2013Hello there,
I'd like to know why this is being spammed in my console so that I can have it stopped.
http://pastebin.com/XR6Aaxyp
It's as if EVERY action in-game is being spammed. Enderman pickup denied actions are also spammed.
-
View User Profile
-
Send Message
Posted Jun 24, 2013@BC_Programming
Evidently you did not see my post as you recently responded and had no input on the errors I was receiving, so please look at them.
Edit: Provided here again.
FOR THE LOVE OF ALL THAT IS GOOD AND PURE, SAVE US! This plugin spams so hard that it crashed a data center.
-
View User Profile
-
Send Message
Posted Jun 24, 2013@BC_Programming
I recall they all pass some kind of special forge events, that's why i suggested you made a seperate plugin.
Also, mods like buildcraft, redpower and computercraft have fakeplayers which plugins can use to prevent the usage of them, thus preventing grief.
And now that i mention them, i asked ryan quite long ago if he could add support for fake players with multiple name parts eg. "computercraft turtle 42", think this could be done?