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 Oct 15, 2014@bigscary
lol well to be fair im using a build a pixelmon forums mod tweaked to make it work with pixelmon using version 293 the one linked here
http://pixelmonmod.com/viewtopic.php?f=127&t=17030
ill try and update to the newest ones and see if the data migrates/works correctly. xD
Would this help for your flat file testings? this is how many claims located int he claims folder
And player data:
-
View User Profile
-
Send Message
Posted Oct 15, 2014@bigscary Not sure if this is something you'd consider, but, when in a large area, with many sub-claims, If the stick is used, it does what its meant to, and highlights the area. Issue is, to "hide" the claim outlines, a player has to move Outside the claimed area and click again.
In Big claimed areas this can be a slight pain. Could a command or action be added to "dismiss" the claim outline?
-
View User Profile
-
Send Message
Posted Oct 15, 2014@bigscary I know its not over 5k, but I have 340 claims and 1370 users. Anyone higher?
I also have one feature request, that I would think would make GP even better. I would love if it was possible to have groups that you can assign players to, and instead of adding every friend to your claim, you would just add a group. I have two suggestions how to do this.
1. Let players with certain permissions be able to create groups that they can invite friends to. The player that started this would be the one in charge. and can add or remove people or even disable the group as he will. Every player would easily be able to add this group. Their might be a limit on how many groups a player could be part of, and every player must accept the invitation.
2. Every player can make their own "home-group" with their closest friend, this is unique to every player, and he is the only one that could add/remove players.
I prefer nr 1. but if that is not possible 2 is okay. I think this would get rid of some of the problems that is with GP, and also makes it easier for other plugins to take use of your API. Think if you could have a clan/town plugin that respects GP claims. where you as the mayor leader could assign clan/town claims. AWESOME!
-
View User Profile
-
Send Message
Posted Oct 15, 2014Hey all, I'm looking for a flat file data store with at least 5,000 claims - does anyone have one to share? I want to look into boot speed for both flat file and database mode (I can convert the flat to DB, but not the other way).
@delsolsi213
Wow, this is the first time anybody's sent me an animated image, haha. You're looking at the wrong file - the newest versions are now using the GriefPreventionData folder again, and the ProtectCreatures option is there. You're living in the past, it's time to go Back to the Future. =D
@Sinuce
Probably not on the cross-server thing. I don't even have a guess as to why your data would be converted and then somehow not used. During boot, does the # of claims loaded match your expectations (see logs)?
-
View User Profile
-
Send Message
Posted Oct 15, 2014@Sinuce
Try going from 7.8 to 8.1, and then from 8.1 to 8.3. I don't remember which version I jumped on board for when 8.x rolled around, but I didn't lose claims when I upgraded.
-
View User Profile
-
Send Message
Posted Oct 14, 2014@bigscary
Successfully upgraded from GriefPrevention pre-8.0 to 8.3.
Will cross-server accruded block be implemented for e.g. Bungeecord users? It doesn't seem to work currently through MySQL.
EDIT: Scratch my inital message regarding a successfull upgrade; All claims did indeed get converted, but the converted data is being ignored or not recognized => As if all claims were deleted.
I did make a backup of the claims. Reverting to the old GriefPrevention for now.
I am running the lastest Spigot and Bungeecord to date.
This message is not a cry for help, but merely meant as a status/bug report.
-
View User Profile
-
Send Message
Posted Oct 14, 2014I reran the conversion from 8.0.3 using the new 8.3, and everything looks good. Thanks for keeping this plugin updated.
-
View User Profile
-
Send Message
Posted Oct 14, 2014@bigscary
that option doesnt generate on the new versions, and it doesnt generate a folder calld GriefPreventionData anymore, its GriefPrevention now. and thats on the newest versions even the ones for minecraft 1.7.9
-
View User Profile
-
Send Message
Posted Oct 14, 2014@delsolsi213
That config option is still in the file (config.yml in GriefPreventionData folder). Are you saying it doesn't seem to work when you turn it off? Which version of GP are you on?
@Cra2ytig3r
I don't control ice now - it takes long enough for a griefer to get ice that I don't worry about it. I don't think 1000 claim blocks will work for a couple of reasons - by default, that's 9 hours of gameplay which is too late for early game farming. Also some servers start players with more claim blocks, so the efficacy will vary (very nuanced!) with claim block allowance settings.
Y 61-65 is a very narrow band, so many players will be left out in the cold because they're up on a hill or a mountain. Would be difficult to explain that to players (when they get an error message, I'd rather not give them a Y coordinate range).
I'm considering doing something with adjacent block types, maybe? :\
@theory18
See above - that option is still in the config file. It's not in yours? Be sure you're looking at the right config file.
@gnaxi
So those who didn't like it before will give it another try, and then I can decide based on feedback whether the config option is really needed anymore.
@LeeTheENTP
Yep that's similar to what I was thinking. Will wait a bit longer and see if anybody else comes up with something better, then take a shot at improving this.
@Bobcat00
Yep sure does, but you'd have to restore backup and re-migrate again to get it done for you. :\ Maybe not worth the effort - it's for you to judge.
-
View User Profile
-
Send Message
Posted Oct 14, 2014@bigscary
When a player dumps a bucket where it would normally be blocked, just have GP run a quick check of the surrounding blocks. If enough of them are farmland with crops of some sort, let the bucket dump. You could make the threshold for that configurable.
Or we could just tell people to farm near lakes and rivers.
-
View User Profile
-
Send Message
Posted Oct 14, 2014@bigscary
I'm basicly asking the same question as delsolsi213 to bring back the option for protectcreatures. This allowed players to create arenas in their claims and battle pokemon on their grounds.
Thanks in advance!
-
View User Profile
-
Send Message
Posted Oct 14, 2014"Removed the option to disable building outside claims warning (see above, should not be spammy anymore)."
- Why remove a feature, that some people might like to use, even if it isn't spammy anymore? :P
-
View User Profile
-
Send Message
Posted Oct 14, 2014Thanks
-
View User Profile
-
Send Message
Posted Oct 14, 20148.3 is not in Git and Jenkins. Can be added too?
-
View User Profile
-
Send Message
Posted Oct 14, 2014@bigscary
OK, I see it now. The names are in the GP folder, but not in the world player data nor the Essentials folders. These must have been people who tried to login, but weren't whitelisted. So that explains it.
Does 8.3 fix the problem with names beginning and ending with underscores not always being converted?
-
View User Profile
-
Send Message
Posted Oct 13, 2014@bigscary
how do you control ice now? would you not use the same config for handling ice (breaking turns into water source) as for water buckets?
You could allow player water dumping between y:61 & y:65, when play earned 1000 claim blocks, allow water dump anywhere.
-
View User Profile
-
Send Message
Posted Oct 13, 2014@bigscary
ok on version 7.7 you had an option to allow others to hurt animals inside claims, a lot of people use your plugin with pixelmon mod, pixelmon is a pokemon mod and the pokemons are treated as passive mobs, in 7.7 having the animals protection as fale it worked perfectly fine, but now since you removed that option players can not hurt pokemons that spawned inside someone elses claims and to a point it annoys players, what im asking is can you bring back that option?
EDIT: this option is what im asking if you can bring it back.
-
View User Profile
-
Send Message
Posted Oct 13, 20148.3 Updates
Please read! I need your input/help. I'd like to redesign the bucket limiting option.
Players don't like that they can't dump water to water their farms in the early game, before they have a golden shovel to claim their farm separately from their house. Yes, they can work around this by farming on top of or under or in their house, but still they don't like it. When players don't like it, admins hear about it, and admins don't like that.
The reason for the current rule about not placing water outside of land claims is twofold. First, griefers can use buckets to make a REALLY big mess with only a few block changes (due to water spreading mechanics). Second, it's expensive for grief prevention to track the flow of fluids, which means server lag. Restricting water dumping to inside land claims very much limits griefing with buckets, and also makes tracking water flow from those dumps almost free (due to technical reasons I don't want to try explaining here).
I would love to hear your ideas on other approaches to preventing griefers from griefing widely using buckets while still allowing players to build their ideal farms in early game. I don't think there's a great solution to this problem, but I hope I'm wrong. :)
@theory18
Please update to the latest and reassess performance. Lots of perf updates lately. If you still have the problem, please share your complete report.
What is involved in "battling"? I'm not familiar with Pixelmon.
@killje
Not quite following you on that suggestion about the buckets?
-
View User Profile
-
Send Message
Posted Oct 13, 2014@bigscary
you could make it a still water and catch when a block form event happens due to a block update and change it back to still water. still would need some thougt to catch some cases but might be an idea.
also dinnerbone has said that he personally would update bukkit as long as minecraft does not support native API support
-
View User Profile
-
Send Message
Posted Oct 13, 2014Could you please add a option for pixelmon in the config so we can battle inside our claims? I love your plugin but i cant run my server without it.
right now i'm having this
It's a modified old version to allow for battling but its getting outdated i think.