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 Sep 30, 2014@bigscary
Okay then, I guess it would be a better idea for people to create subdivisions for the horse area then /ct the subdivision. Thanks again for the help :D
-
View User Profile
-
Send Message
Posted Sep 30, 2014@bigscary
INFO UUID of player <premium acc> is 490ba3e3-df48-3e8c-8ad8-xxxxxxxxx . INFO GriefPrevention: <premium acc> > 490ba3e3-df48-3e8c-8ad8-xxxxxxxxx
It works mate :) But I'm not using the protocol updates if that's what you mean. But don't worry, let's hope it's done converting tomorrow and I'll test everything as good as I can and post everything here! As long as we believe in it, it'll be fine :D
-
View User Profile
-
Send Message
Posted Sep 30, 2014@dutchrastacraft
If the UUID when the player logs in matches the UUID GriefPrevnetion guessed for that player, woohoo it's working! I'm not an expert on Bungee, but it's my understanding that online mode players may NOT match, since GP's guess on UUID is under the assumption that all players are offline players (because that's what's in your server properties file).
@Turbotailz
That's right, the world configs don't do anything now. There's only one config for the whole server, config.yml.
That's a bummer about the shops. :\ Yes, /ct is the correct workaround. I guess if the player buys a horse, the seller has to be online to /ct until the horse is gone, then /untrust again to prevent thieving.
Sorry for the trouble, I hope you agree it's worth it to get all the bugs out.
-
View User Profile
-
Send Message
Posted Sep 30, 2014@bigscary
Thanks for the response. I am not sure which version I am using, but the .jar file says GriefPrevention-295 - I'm guessing that's the build number?
In my World config there is a setting - HorseTrust: Standard, you're telling me there is no horse related option, but then what is this?
Am I able to change it so that people don't require /ct to ride horses in other people's claims? It's okay if not, I will just have to let everyone know they need to give /ct to whoever they would like to give horse riding access to (some people have shops selling horses).
Thanks again, this plugin is amazing :)
-
View User Profile
-
Send Message
Posted Sep 30, 2014@bigscary
Just did a little test. Those are offline players.
30.09 23:07:54 [Server] INFO GriefPrevention: temdeserlegal > 39493a19-deb6-3c33-a1c3-89f870270c16
On join to hub: 30.09 23:08:54 [Server] INFO UUID of player temdeserlegal is 39493a19-deb6-3c33-a1c3-89f870270c16
AND
30.09 23:06:16 [Server] INFO GriefPrevention: fuudidoo > abbae142-c411-38d4-a159-6cc8363a0dfb
On join to hub: 30.09 23:11:12 [Server] INFO UUID of player fuudidoo is abbae142-c411-38d4-a159-6cc8363a0dfb
It seems to be working?
-
View User Profile
-
Send Message
Posted Sep 30, 2014@dutchrastacraft
Yeah sorry sir, that problem has me stumped.
@Turbotailz
Okay first, if you're on the latest version, you're looking at the wrong config file - there is no horse-related option in GriefPrevention today. All GP does with horses is require the claim owner's permission (/containertrust) to ride a horse when the horse is in a land claim - this prevents griefers from riding horses to steal them. Horses outside of land claims have Vanilla behavior.
@jahangir13
By design, subclaims always have "owner" blank. To work with latest GP builds, dynmap needs an update to display the parent claim's owner as the subclaim owner (or just not bother to show owner information for subclaims, since it's always the same as the parent claim's owner).
@GodsDead
Won't call async to write to the database - otherwise reads may pick up stale data, which means players will get cheated out of their claim blocks. In all the time I've been working on this plugin (measured in years), you're the only person to ever complain of this problem. That's why I'm (so far) unwilling to do a lot of coding (and testing, and later code maintenance) around it.
If anyone else is having a similar problem to GodsDead, please do comment.
-
View User Profile
-
Send Message
Posted Sep 30, 2014@bigscary
About the mysql issue, If you havent already its been suggested using async calls to a database, making the blocking call a now nonblocking call. Ive been asking for advice on the spigot forums for this matter too, There needs to be a saftey-net feature anyway if the server does loose connection to the mysql server, or the server gets overloaded or whatever, theres loads of reasons it could break, either taking the server with it or creating server wide havock.
-
View User Profile
-
Send Message
Posted Sep 30, 2014Hi,
if I create a subclaim with any version > 8.1, this shows up as Admin Claim on my dynmap. I saw in the changelog that there has been a problem with a similar issue. Is this a GP problem or maybe one of the dynmap-gp plugin (but this just using claim.isAdminClaim() to decide if it's an admin claim or not). Only happens with subclaims, but all of them.
How can I see in the claims files if this is judged as an admin claim or not (so to see that dynmap is only showing it wrong)?
-
View User Profile
-
Send Message
Posted Sep 30, 2014Where is the documentation about Horses?? I can't find it anywhere and I have no idea what I should set in the config to allow people to ride horses freely without any restrictions (currently people can't ride horses they did not tame - something like that, not too sure). I see there is a HorseTrust option, but no idea what other settings I can use other than "standard"?
-
View User Profile
-
Send Message
Posted Sep 30, 2014@bigscary
Haha allright! Can't really test since I'm still converting :P I guess it'll be done by tomorrow evening (still 24 hours to go[wild guess]) and then I'll test the new update! I'm scared that the offline UUID convertion will not work correctly but yeah, we'll see! Not trying is deffinately not winning!
PS: Thank you so much for editing the docs, it was impossible to read ;)
EDIT: Well shit, just read this... " At this time, it seems this process works well for offline mode and online mode servers, but not for the hybrid "Bungee Cord" configuration. For now, any BungeeCord servers should NOT update to 8.1 or later."
-
View User Profile
-
Send Message
Posted Sep 30, 2014Overhauled the documentation today. :) It's been a long time coming.
-
View User Profile
-
Send Message
Posted Sep 30, 2014@z1379228
Please read the manual (see administrative details link above). You want either /adjustbonusclaimblocks or /adminclaims, depending on your situation.
@dutchrastacraft
In the last version, I made some minor improvements to boot time and the amount of work done in some of the scheduled recurring tasks. I'm not sure whether you'll notice a significant difference with only those changes or not.
-
View User Profile
-
Send Message
Posted Sep 30, 2014How to increase the can be set size?
-
View User Profile
-
Send Message
Posted Sep 29, 2014In contrast to the other people here I am willing to give in some of the features for better server performance. That is one of the reasons I'm updating. I was hoping that the new builds would have better performance because the beta builds were killing the cpu.
-
View User Profile
-
Send Message
Posted Sep 29, 2014@LeeTheENTP
In the latest version, yes. In future versions, yes but you will have the option to limit tree growth.
-
View User Profile
-
Send Message
Posted Sep 29, 2014@bigscary
So if I planted a tree on the outside of a claim, its leaves might spill into the claim?
Making that and the piston thing configurable would be great. I know that my server can definitely handle them (it's had no problems with them for almost 2 years), but I'd imagine there are a few servers that need those resources devoted elsewhere.
-
View User Profile
-
Send Message
Posted Sep 29, 20148.1.5 Updates
Thanks all for your feedback on trees/pistons. I'll get the tree code back in but configurable in the next version, and I'll also add a config option for the piston thing. Not sure which setting I will default to for those - I'll think on it some more.
-
View User Profile
-
Send Message
Posted Sep 29, 2014I completely agree with AdvanceGamingNextLvl. I like the trees being cut off and the pistons the way they are. If it's configurable I think that would solve the issue for side servers.
-
View User Profile
-
Send Message
Posted Sep 29, 2014@bigscary
I'd be willing to continue sacrificing performance in order to keep pistons as is. And while I've never had issues with GriefPrevention's performance, I can see where your coming from, and do believe this can be/is a problem for some servers. (but not most) My recommendation: Make it configurable. Give server owners the choice to keep pistons as is, or to go for the better performance (but may annoy some players) option.
Trees getting 'cut off' when overlapping land claims is a feature I really like. And once again, would be willing to sacrifice performance to keep. And of course I can understand what your saying, checking which blocks were affected and acting on them when ever a tree grows is a performance eating task. But I (and I'm sure I'm not alone) like that way trees were/are. So once again, please just make it configurable. Add an 'if' statement checking a true or false option in the config before you even check/act on the event, and the world can be a happier place knowing they have the option. :)
-
View User Profile
-
Send Message
Posted Sep 29, 2014@LordDWT
Pistons only stop working when they'd push a block into a claim or pull one out of a claim.