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 Nov 21, 2012@bigscary
A hardcode to infinite or just an explanation of the command should work too. I'll test it tonight. Is there any chance you have a permalink setup to point to the latest download? Trying to script something with the AutoTest script I've been working on :P
-
View User Profile
-
Send Message
Posted Nov 21, 2012@xclucky
Sorry no, please choose items with different IDs.
@fungreenfox
You want WOOD_SPADE. The list is here:
http://jd.bukkit.org/doxygen/d6/d0e/enumorg_1_1bukkit_1_1Material.html
-
View User Profile
-
Send Message
Posted Nov 21, 2012As modification tool, can wooden_shovel be used (spelling) or is ID 269 useable?
-
View User Profile
-
Send Message
Posted Nov 20, 2012Could you please add support for data values? I want to make the info tool yellow dye and the selection tool red dye, however, it just resets the config if i do 351:1 or 351:11. Please fix. Thank you.
-
View User Profile
-
Send Message
Posted Nov 20, 2012@krisdestruction
Please update to 7.1, which I believe fixed this issue. :) Also note that /claimslist from the console without a player name parameter can't possibly give you any claim information, since it's not clear what player's claim info should be presented.
@sethgandy
Yes it has been a very long road. :) This is now the best anti grief plugin available, and it's not just a little ahead of the rest, but leagues ahead. There's absolutely nothing comparable to GP for anti grief.
@briankdk
There's no undo. There is an option in the config file to disable the automatic cleanup for expired claims, but there's no option to not clean up a claim which is deleted via /deleteclaim. If you as admin want to resize, move, or adjust permissions for a claim, you can do that without deleting it.
@chrishillz
No, here's an example. Suppose you had a permission node called "mycoolserver.donators", which you ONLY give to players have donated money to the server fund. To give those players 1000 extra claim blocks based on them having that permission node, you would do this:
/adjustclaimblocks mycoolserver.donators 1000
No, removing claim blocks from a player's allowance does not automatically change any of his existing land claims. The player would just have a negative claim block amount until he got more claim blocks, or manually removed or downsized one of his land claims.
-
View User Profile
-
Send Message
Posted Nov 20, 2012@bigscary
So it's
That would be extra 1000 blocks while this is active?
Edit: What would happen if they used this and the rank was removed, would it delete a random claim to remove the 1000?
Edit2: How can I make water not get removed when I unclaim a region?
-
View User Profile
-
Send Message
Posted Nov 20, 2012i think i have asked before, but i cant find the answer.....
1. can i disable "automatically cleaning up a claim after claim has been deleted" ?
2. if a claim has been resized or deleted, then buildings disapear - can they be restored somehow ?
-
View User Profile
-
Send Message
Posted Nov 20, 2012Wow, can't believe it's almost been a whole year since you started! I remember the infancy of this plugin and bugging you about coloring your text! lol I left the scene for 7 months and come back to this?! I'm completely impressed that you've lived up to the potential I saw for this plugin!
Great work BigScary!
-
View User Profile
-
Send Message
Posted Nov 20, 2012@bigscary
Yes those two commands would work well if the claimId was listed in /claimslist. If you feel that /trust is too hard to implement with your permission system, /deleteclaim <id> by itself should be a lot easier to implement.
I'm won't make any assumptions as I'm not maintaining the code but yes I've already look at the code multiple times before and know a few people who have tried to rebuild your plugin from scratch.
AutoTest found 2 errors from the console.
Input Console String:
claimslist
Actual Output String:
613,627d612
< 2012-11-20 05:03:16 [WARNING] Unexpected exception while parsing console command "claimslist"
< org.bukkit.command.CommandException Unhandled exception executing command 'claimslist' in plugin GriefPrevention v7.0
< at org.bukkit.command.PluginCommand.execute(PluginCommand.java:46)
< at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:186)
< at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:502)
< at org.bukkit.craftbukkit.CraftServer.dispatchServerCommand(CraftServer.java:494)
< at net.minecraft.server.DedicatedServer.al(DedicatedServer.java:258)
< at net.minecraft.server.DedicatedServer.r(DedicatedServer.java:223)
< at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:493)
< at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:426)
< at net.minecraft.server.ThreadServerApplication.run(SourceFile:856)
< Caused by: java.lang.NullPointerException
< at me.ryanhamshire.GriefPrevention.GriefPrevention.onCommand(GriefPrevention.java:1489)
< at org.bukkit.command.PluginCommand.execute(PluginCommand.java:44)
< ... 8 more
Input Console String:
claimslist krisdestruction
Actual Output String:
633,647d632
< 2012-11-20 05:03:22 [WARNING] Unexpected exception while parsing console command "claimslist krisdestruction"
< org.bukkit.command.CommandException Unhandled exception executing command 'claimslist' in plugin GriefPrevention v7.0
< at org.bukkit.command.PluginCommand.execute(PluginCommand.java:46)
< at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:186)
< at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:502)
< at org.bukkit.craftbukkit.CraftServer.dispatchServerCommand(CraftServer.java:494)
< at net.minecraft.server.DedicatedServer.al(DedicatedServer.java:258)
< at net.minecraft.server.DedicatedServer.r(DedicatedServer.java:223)
< at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:493)
< at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:426)
< at net.minecraft.server.ThreadServerApplication.run(SourceFile:856)
< Caused by: java.lang.NullPointerException
< at me.ryanhamshire.GriefPrevention.GriefPrevention.onCommand(GriefPrevention.java:1471)
< at org.bukkit.command.PluginCommand.execute(PluginCommand.java:44)
< ... 8 more
Can you make these two commands work from the console? I'll be aiming for player tests next :)
-
View User Profile
-
Send Message
Posted Nov 20, 2012@chrishillz
Use adjustclaimblocks <permission.node> <number of blocks>.
AFK "machines" won't work. I've tested with several variations, including auto-walking clients, auto-chatting clients, even clients that break blocks and then put them back so that they can be broken again. I've also tested Minecart tracks and boats. This water conveyor mentioned in your screenshot MIGHT work, but I will add a touch of code in the next version to ensure it doesn't.
@ekemsend
Is it too late to switch back to flat file mode? SQL mode really isn't better. It's just more complicated for you to deal with.
@add5tar
Okay, let me see if there's another node I can use for it. If not, I may create a new one.
-
View User Profile
-
Send Message
Posted Nov 20, 2012@bigscary
I understand /trustlist can be a privacy issue for some servers, but on my server I would like a way (via permission node) to allow people to use /trustlist but not have /ignoreclaims access. I definitely believe this should be disabled by default, but there should be a permission node to enable it. Most protection systems allow everyone to view claim members, and I really don't see a problem with that. And if it's controlled by a permissions node, server owners are free to choose.
This is an important feature for us and I hope you will agree to implement it :)
-
View User Profile
-
Send Message
Posted Nov 19, 2012@Bigscary Yes I am running Tekkit and have been running GP for about 2-3 months. I never got this error until about 2 months into using GP and after switching to SQL, although I dont know if that is related because the error didnt show up until a month after moving to SQL. I run GP 5.5.1 and always ask users in game if they have noticed any strange behavior with GP or anything else when the error occurs, and no one reports anything useful. I run a decent amount of plugins (but nothing extraneous and always a proper BC version) - but at the initial occurance of the error hadn't installed anything new. The only admin action I can remember doing that predates the error, but is close to it in time was moving the spawn with Essentials, however I have since removed Essentials - spawn is now default - and installed Commandbook and still recieve the error. I understand that I am not exactly using the most recent version of GP and you probably don't really want to offer support for an outdated version, but if there is any man to ask about this problem, i figure it is you. I have thought about looking at the SQL database for any glaring errors, but I am unsure if the error throws would suggest this. Thanks again for being so active in your forums and responding more diligently than any person is really capable of - its pretty amazing - it may be the reason you have one of the most useful server plugins I have seen and certainly the plugin that makes playing an enjoyable game of MC, Tekkit or any bukkit compatible mod even possible.
-
View User Profile
-
Send Message
Posted Nov 19, 2012@bigscary
Oh thanks for the help with PvP, I didn't know it was only for the rules and additions.
What's the best way to set up bonus blocks for members vs guests/players? I heard somewhere that you can give them bonus blocks, but if they're demoted they go away as well? How can I best give players bonus blocks?
EDIT: What about AFK machines giving fake points? http://puu.sh/1s8zM
-
View User Profile
-
Send Message
Posted Nov 19, 2012@krisdestruction
You suggested remote claim management. So commands like /abandonclaim and /trust would have to accept ID numbers for claims instead of assuming you're targetting the claim you're standing in. Right?
Also refactoring = lots of bugs and testing. Since I don't plan to add lots of new features going forward, refactoring probably wouldn't pay off. Also you're assuming it's badly coded and therefore in need of refactoring, I'm not sure you're right but it's a matter of opinion. See repository link above.
@JustinFatalx
I probably won't.
@ekemsend
Can you tellm e anything more about your server that may be helpful? Are you running any mods (like Tekkit)?
@Darkhand81
Yes if you have automatic nature restoration turned on, then chests are removed when claims expire because they don't occur naturally.
@chrishillz
I'm not doing anything at all with players' tools.
@lordskout
Well clearly you couldn't find the anti grief you wanted over there, so why did you go? It sounds like you've just set up your server for major griefage, right?
@chrishillz
You misunderstand. The PVP worlds doesn't determine where players can pvp. It just determines where the pvp rules added by grief prevention apply, for example on which worlds players will be protected from spawn camping, and where they will not be allowed to log out during combat. You have to use server.properties or another plugin to turn PVP on and off for various worlds.
-
View User Profile
-
Send Message
Posted Nov 19, 2012Oh and also I don't think the PvP setting is restricting PvP to the specified worlds...
-
View User Profile
-
Send Message
Posted Nov 19, 2012@bigscary
@bigscary We can dream. :) I am no coder, and while I can certainly understand not wanting to support two code bases and that Forge doesn't offer the resources you need yet... we can still dream. :) I love the functionality in concept, toyed with it on my test server under Tekkit 3.1.2... I'm just moved on from CB.
-
View User Profile
-
Send Message
Posted Nov 19, 2012Any relation this plugin has to a auto-repair glitch my users are reporting? Their tools are repairing themselves. Is it a Beta Bukkit problem?
-
View User Profile
-
Send Message
Posted Nov 19, 2012Quick question... When automated claim cleanup is performed, are chests removed along with everything else? If so, I'd love an option that leaves chests behind to provide players with a little treasure hunting. Old player leaves, claim is deleted and cleaned up, but his loot is left for a newer player to discover. :)
-
View User Profile
-
Send Message
Posted Nov 19, 2012hey @bigscary
I uninstalled modifyworld and am using bpermissions - so i am no longer using modifyworld.... and I still get the same error, just now its not followed by any other error in the console. So here is the log
http://pastebin.com/QCMr2ngA
-
View User Profile
-
Send Message
Posted Nov 19, 2012Can you add it so that players cant use the /sethome and /home command in another players claim unless they are trusted.