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 10, 2012@sirmyllox
Why not, but if so, i would prefer it as separate small plugins not a bigone.
-
View User Profile
-
Send Message
Posted Oct 10, 2012@RasCas
Hey, that could be added to my plugin request for a GP addon :)
http://forums.bukkit.org/threads/req-griefprevention-addon.103434/ (GriefPreventionPlus)
The only problem i see with an addon is that it might not be maintained .. :( .. the best thing would ofcourse be if bigscary himself made the addon . .then it would have a greater chance of being maintained.
-
View User Profile
-
Send Message
Posted Oct 10, 2012Question about subdivided claims:
Here is, what i would like to to. Create a town, offer prebuild houses/ areas for the players to claim. A Player should be able to claim a house/area and get build access in the subdivision. This should be possible without an op to grant trust manually.
Maybe by placing a chest, a bed or buying the house, which i would prefer. Is this possible?
That is what i am thinking about:
-
View User Profile
-
Send Message
Posted Oct 9, 2012@Zidane3838
Actually, i was just reading your Public API Documentation. I am not very familiar with Java as of yet, but i do have a history in development with C#, Visual Basic .net and php, so i am thinking about giving it a try, although i cant really find a link to your source code anywhere, also i could use some tips like where to start, as far as i know i will be needing an IDE for java right? which one do you recommend for this? If you can help me a little bit i might be able to add in claim flags, and not just the one i mentioned, i think i can.. it will take some time though but i really have no idea where to begin xD
-
View User Profile
-
Send Message
Posted Oct 9, 2012@bigscary
would you be willing to add it in :s?
-
View User Profile
-
Send Message
Posted Oct 9, 2012Awww<sub> thats too bad.. It could have saved me a big ass plugin i really rather loose. Oh well, another question, how about a pvp enabled:disabled flag? That would be sweet as well, then i can remove worldguard XD which i seriously am only using for this :| what a waste of resources :P By the way, thank you so much one more time, all our problems have been solved xD</sub>
-
View User Profile
-
Send Message
Posted Oct 9, 2012@nicco00
Are you running a Tekkit server? If so, see "notes for tekkit servers" above.
@ChilleCharlie
No, not planning to add a chat feature into an anti grief plugin. :)
@ThisUsernameIsMine
None of them are useless, those players may return later. I run four test servers, and the biggest one has 11,098 player data files. The total size of all these files is only 340 kilobytes.
@Zidane3838
It's not more than one capital letter, it's some percentage of the entire message, I think 75%. No, there's no option to turn it off.
@schmidtbochum
Problem with auto claim : a griefer runs around putting a block here and there so everything is claimed up. If you limit total # of chunks claimed to fix this, then players get confused when they run into their limit, because they're not sure where all the chunks they claimed are, which makes it very difficult for them to clean up those unwanted claims to reuse the claim allowance. So then you give them a toggle command to turn off auto claiming so that they don't claim when they're not building, but then they forget to turn it back on, and end up getting griefed.
Also, keeping two copies of your map will be extremely expensive, and won't clean up weird land generation issues like those floating islands or gravel sticking out of the ground.
Finally, you're forcing players to learn what chunks are and how to find out where their edges lie, which will involve them learning about world coordinates and doing math. Even with GP's super simple "claim a rectangle with two clicks" approach, lots of players get frustrated and rage quit. Dealing with chunks is much harder for the average player to learn (most players aren't coders or server administrators, they're just kids or teens).
Good luck!
@RasCas
What gets in the way of normal gameplay is having to claim land just to go mining. Automatically expanding claims outward would hurt server performance (lag), and would lead to lots of confusion for reasons mentioned in my response to schmidt above. Also, players will run out of claim blocks and hit a "wall" anyway, so they'll have to climb back up and resize their claim for that reason.
Just turn the feature off. I never should have added it, it's a train wreck for survival mode. I only added it so people could run "adventure style" maps with GP, but now we have adventure mode so it's not needed. I'll probably remove it in a future version.
@Chaett
If the world where you want players to claim before building is in the creative rules worlds list, then I don't know what the issue is. Server.properties doesn't matter, because GP's config file list of creative worlds overrides that. Please check your boot logs to see if you're getting any error message from GP about not being able to find the world you mentioned in your file. Also, check your file again to make sure it didn't reset itself, which often happens with config files when there's a formatting error in the file.
-
View User Profile
-
Send Message
Posted Oct 9, 2012@bigscary In your GP config file, add that world's name to your "creative rules worlds" list. :)
I think well organized, complete documentation is best. Otherwise, folks waste time tooling around forums where information can be outdated, confused, and disorganized. The bit about creative mode worlds is described in the administrative details page. :) Only servers with both types of worlds (survival and creative) experience this problem, because the only "game mode" available to plugins is the one in your server.properties file, which is not world specific
@bigscary
I had added my creative world to the "creative rules worlds" list. So I guess it's a problem with it being a different gamemode than the server.config file like you said. Any work around?
-
View User Profile
-
Send Message
Posted Oct 8, 2012@bigscary
The problem is not depth. The problem is, that they cannot go right, left .... They have to go up to the overworld, resize claim go down again. That really gets in the way of normal gameplay.
-
View User Profile
-
Send Message
Posted Oct 8, 2012Your source code is a great learning resource, thank you for publishing it! The file data storage is well-done, as well as the event listeners.
One problem of your plugin is that it can't roll back the land when a player abandoned his claim in creative mode. restorenature works well, but not in all cases, especially not on flat maps.
I'm working on my own protection plugin only for my creative server. Players can claim chunks just by starting to build in them. It's possible to create snapshots of chunks, so the plugin can restore the nature perfectly.
-
View User Profile
-
Send Message
Posted Oct 8, 2012Any possibility to allow more than one capital letter per chat message, or "yelling". I don't see "yelling" as a big problem and the ability to toggle it off and on in the config file would be fantastic. Other than that pretty great plugin.
-
View User Profile
-
Send Message
Posted Oct 8, 2012@bigscary
No there isn't, sorry. Why is having a lot of files a problem? Player data is only loaded for online players (so no RAM damage), and the files are each very small (virtually no HD space). If you REALLY want to do a cleanup anyway, sort your files by last modified date and delete those you don't want (note this will not delete any land claims).
Oh well.. One more question though: how many useless file do you have (if any)?
-
View User Profile
-
Send Message
Posted Oct 8, 2012Hey bigscary,
Thanks it looks like it works perfect now :) I really really like your siege mode, but unfortunately we have factions... Do you have plans for making something similar to factions chat in the future in this? That would be suweet xD errr.. maybe i should just make another pvp world instead huh -.- the free for all one :P
-
View User Profile
-
Send Message
Posted Oct 8, 2012hi, i downloaded this pluing but i dident make it to work, all commands did work but the plug in dident protect anny area when i was put my first chest on the ground, and i tryed to use the golden shovel, but nothing worked, do i need anny more plugins for this should work, or edit anny files to make this work for me ? thanks (sorry for my bad english)
-
View User Profile
-
Send Message
Posted Oct 8, 2012@ChilleCharlie
The new sea level setting is per world. :) So yes, you can have for example one "flat" world and the rest of your worlds "standard". You'd only have to set sea level for the non standard worlds, because Bukkit already knows the default sea level for standard worlds.
@bman01
There's a limit to total number of entities in the claim at a time, so I guess players are using the egg near the edge of their claim, and waiting for the animals to wander out (or pushing them out with water) so that they can keep spawning. Rest assured - any extra animals or monsters will be automatically removed over time by an automated process. :)
@Infuscu
Use /containertrust to give access to everything EXCEPT building (it includes the lower level /accesstrust).
Your earlier suggestion didn't make sense, because of course if someone can build, then they have access to your containers because they can break them to get what's inside. :)
LWC can give you the rather odd "build but don't access containers" result, but will make it harder for people to work together, because in addition to giving a player /trust or /containertrust, you'll also have to give him explicit permission for each container block you want him to access, which can be very tedious.
Also, as you noted, it's possible another player could put a claim overtop an LWC-protected chest owned by another player. It gets messy.
@FordRacer2007
Ah yes, that is intentional, mr fordracer. :) Stopping lava from igniting nearby blocks was an accident. Have your players "fix" this in their areas by building fire proof blocks around their lava, for example for their incinerators and fireplaces.
@RasCas
I'm thinking of removing that option actually because it mostly just gets in the way of normal gameplay. But anyway if you set the initial depth of claims to 300 or so, then all claims will always go to bedrock by default, which will allow for mining. For current players, tell them to /abandonclaim and recreate.
@Harry4of4
Not yet. Still waiting for somebody to create an extension plugin with that kind of behavior. It would be very expensive (performance wise) for me to add and it's not necessarily a grief problem, so I won't put it in the base Grief Prevention plugin. Remember players can make themselves safe from PvP by installing iron doors with buttons (which require permission to use).
@Chaett
In your GP config file, add that world's name to your "creative rules worlds" list. :)
I think well organized, complete documentation is best. Otherwise, folks waste time tooling around forums where information can be outdated, confused, and disorganized. The bit about creative mode worlds is described in the administrative details page. :) Only servers with both types of worlds (survival and creative) experience this problem, because the only "game mode" available to plugins is the one in your server.properties file, which is not world specific.
@0dayRUDE
I don't think land claiming can be made any easier - either build a chest, or right click twice. AND there are videos actually explaining and demonstrating those processes. AND links to those videos appear when players ask about claiming land in the chat. I don't mean any offense, but if your players can't figure out something that simple with all that assistance, then they have no business playing public multiplayer Minecraft at all.
@yurikoma
/RestoreNature will work under water, but only if you swim down to the bottom and right click up close. :) The default behavior for /RN is to go from sea level up, UNLESS it's used lower.
@RasCas
In almost all cases, the list of all claims would be overwhelming to the point of being useless. To teleport to a claim, use /claimslist to get coordinates for a player's claim, then /tp <player> <x> <y> <z>.
@PsychoFad
It was your idea, and you're welcome. When was I a jerk? I took the time to investigate the issue with you, and gave you a detailed explanation for why I didn't want to make the change, and even gave you some alternative solution ideas. Most developers, in a similar situation, probably would have said "sorry no time for corner cases" or "sorry, not supporting weird sea levels" and left it at that.
I didn't want to do a lot of coding to fix a problem that I thought few players would have, which was caused by another developer being irresponsible, and when the best fix would be in Bukkit (and it's still the best solution). But then after I thought about it a while, I realized I could put a fix without taking on the risk that I described below, and that changed my mind.
Too bad you have such thin skin. I'm glad you're happy with the update. :)
@ThisUsernameIsMine
No there isn't, sorry. Why is having a lot of files a problem? Player data is only loaded for online players (so no RAM damage), and the files are each very small (virtually no HD space). If you REALLY want to do a cleanup anyway, sort your files by last modified date and delete those you don't want (note this will not delete any land claims).
-
View User Profile
-
Send Message
Posted Oct 8, 2012Is it possible to disable PlayerData file-creation for my guest group?
Had around 5000+ files and only 337 players had claimed areas.
-
View User Profile
-
Send Message
Posted Oct 8, 2012Thanks for finally setting the option for a custom Sea level! Too bad you had to be a jerk to me about it before it became your "own" idea to fix this problem for someone else. I still continue to use your plugin and promote it to other server ops, but really, I was just asking for a little help. I knew it wouldn't be that hard to implement the option for those of us that decide we just don't like to be constrained by the "normal" sea level when creating awesome worlds for our members. Thanks again, and I forgive you even if you don't think you did anything wrong!
@PsychoFad: Go
So what the TerrainControl guy is telling you is that he decided to implement his own sea level even though he knew Bukkit didn't support it, creating the opportunity for you to have this problem. You can submit a feature request to Bukkit for a world.setSeaLevel(), but really the TerrainControl guy should do it, since he'd be the one using it.
I won't add that config option because the danger is that Mojang will change the sea level, which would make everyone who uses GP and doesn't immediately update their config variable to the new level have a major problem with /rn. :\ The only safe fix is to get Bukkit to add a setSeaLevel(), as TC guy suggested.
-
View User Profile
-
Send Message
Posted Oct 8, 2012feature wish:
-
View User Profile
-
Send Message
Posted Oct 8, 2012@Harry4of4
Take a look here: http://dev.bukkit.org/server-mods/grief-prevention/pages/administrative-topics/#w-permissions
-
View User Profile
-
Send Message
Posted Oct 8, 2012Is there a permission node for mods to be able to build/destroy and access chests in claimed areas?