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 17, 2012SUGGESTION
A PVP ON/OFF flag for a plot?
It would be so useful.
People are building bases and hotels and they want to stay there without being attacked.
If possible for the next version it would be great.
-
View User Profile
-
Send Message
Posted Nov 17, 2012Awesome plugin! We've just migrated all our land ownership to Grief Prevention!!
But is there a way to allow all users to do /trustlist? I would like anyone to be able to see the trust list for any claim.
-
View User Profile
-
Send Message
Posted Nov 17, 2012@Zilacon
It does. I have it running on MySQL atm.
-
View User Profile
-
Send Message
Posted Nov 16, 2012GriefPrevention does not work through a mySQL database. The plugin doesn't even function at all. Once i deleted the database information it worked. Please fix this!
-
View User Profile
-
Send Message
Posted Nov 16, 2012Hello All,
I have been running GP for about 2 months, switched to SQL halfway through. Recently I get this in the console:
http:pastebin.com/e5KAgkqc
No apparent trigger, I thought it was after a player join, but now find it in the log at random places. Not able to duplicate error yet.
I run a Tekkit Server 3.1.2, GriefPrevention 5.5.1, craftbukkit is 1.2.5 R4.1
Any insight into this? Any input would be awesome. I also run PermissionEx which is the modify world in the paste. These two seemed to run together well for a very long time, doubtful if that is the issue at this point - gone over the permissions.yml multiple times... even switched from Essentials to Commandbook
-
View User Profile
-
Send Message
Posted Nov 16, 2012@bigscary
"The claim itself is gone, but part of it is not restored to natural - is that what you mean? Or is part of the area still protected and owned by the claim owner?"
Parts of the build are not restored to nature with /deleteclaim. Usually slices.
-
View User Profile
-
Send Message
Posted Nov 16, 2012Is there any way to turn off auto-banning users with the same IP? It is very annoying
-
View User Profile
-
Send Message
Posted Nov 16, 2012Also, can you please add me on Skype, I would need some help with my plugin. (In the config, I need &a and etc!) Thanks! Skype: CraftThatBlock (Oh and BTW, im CharlesWCrete :) )
-
View User Profile
-
Send Message
Posted Nov 16, 2012@bigscary
I do test automation for a living :D but if you want, I can send you my script. Maybe it'll help cut down some time? I already have a small prototype running already that tests BOSEconomy and WorldBorder. I'll start expanding to other plugins such as GP.
Obviously don't only depend on the automated tests but it should cut down some time, especially if you emulate some of the player commands using the spoof plugin or something similar.
Is there any chance you can add the claim ID to the /claimslist and allow a parameter for /deleteclaim so that you can delete a claim without actually being physically there?
-
View User Profile
-
Send Message
Posted Nov 16, 2012@bigscary
Let me know if you need any more info from me. I'll gladly try to help you find the problem :)
-
View User Profile
-
Send Message
Posted Nov 16, 2012@watarimon
Thanks, I see. I will think about it to try and guess the issue. It seems players aren't having their claim blocks discounted given then claims they have in place.
-
View User Profile
-
Send Message
Posted Nov 16, 2012@bigscary I'll attach a screenshot trying to explain my problem further.
I use a stick to show the details of the claim I'm inside. which shows Blackboss02 as the owner of the claim and then I type /claimslist Blackboss02 which gives only the number blocks he has available.
https://dl.dropbox.com/u/6898448/claimslist.jpg
I've found two players so far which gives the same info, I know both players have claimed areas on the server.
-
View User Profile
-
Send Message
Posted Nov 16, 2012@krisdestruction
Thanks, I'll check it.
You make it sound like automation is easy. :) Unit testing is doable, but it's not sufficient - I'd only be satisfied with end to end automation (actually driving player actions in the game and measuring results through hooks in Mojang code). Anything less would be a lot of work for a little confidence, which I'd then have to supplement with manual testing, defeating the purpose. Building an automation platform capable of that would be a project almost as big as bukkit itself, I think. And you see how even a team of really smart guys working only on that one project has difficulty maintaining pace and quality simultaneously.
@CraftThatBlock
It's already released. Click "repository" at the top of this page.
@missingscrews
Do you want players to be spawn camped by jerks? Well if you do, there's an option in the config file to disable the respawning player protection. :)
@watarimon
It means they don't have any land claims. That's accrued claim blocks + bonus claim blocks = total claim blocks, which is followed by a list of land claims when the player has some.
-
View User Profile
-
Send Message
Posted Nov 16, 2012For most players when i do /claimslist player I get the list of claims with sizes and coords but for some I only get i.e 14886(+361)=15247 and similar.
I know they have at least one claim.
bug or feature? and if feature could someone explain it to me?
-
View User Profile
-
Send Message
Posted Nov 16, 2012How do I turn off defenseless player?
-
View User Profile
-
Send Message
Posted Nov 16, 2012Hey Ryan! This is STILL the best plugin in the whole world! Im thinking about doing a addition plugin to this but i would need the source code if possible! THanks!
-
View User Profile
-
Send Message
Posted Nov 16, 2012Type "claimslist <player>" in the console.
Error log:
16:41:30 [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:185)
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
Automate your tests to reduce time for releases. I'm trying to automate plugin testing right now :P
-
View User Profile
-
Send Message
Posted Nov 16, 2012@notif
The claim itself is gone, but part of it is not restored to natural - is that what you mean? Or is part of the area still protected and owned by the claim owner?
@Blazex224
It only happens for your very first chest. If you already have a land claim, then placing a chest doesn't create another land claim. The chest is the best choice for the block which triggers a player's first claim, because it's the most valuable block in the game (because it usually stores valuables), it's always built early by new players, and usually indicates a permanent building investment (because moving a chest and all its contents is a pain).
@krisdestruction
Sorry, I don't have enough free time to maintain two different versions (for two diff platforms) of Grief Prevention. It's a very big project on its own, and I also have other plugins and four test servers to look after. I will continue to monitor other platform projects - if one gets toa point where it does everything I currently need from Bukkit, shows good adoption rate, and also supports mods, then I will seriously consider switching.
@w3thax
Sorry no, I think you'll find it extremely rare that you update GP's configuration. Please just use the /reload command provided by Bukkit.
@joalin
Bukkit can't keep up with Mojang, sorry. If you want to take the risk in running a development build on your server, then you can go ahead and use an outdated Grief Prevention as well. I'll release a new version when the Beta build comes out, or when I get impatient, whichever comes first. Since there are only bug fixes in the latest build, I'm not in a hurry because I don't expect any new grief openings as a result of the most recent patch.
@ManBeastPigDev
There's a configuration option to automatically lock all wooden and/or trap doors in the config file. Turn that on, and you can then ditch lockette entirely.
For stopping cheaters, I recommend NoCheatPlus + AntiXRay.
-
View User Profile
-
Send Message
Posted Nov 16, 2012This plugin is fantastic.
You can see it running on my server below.
If the dev ever bundled it with a no cheat type module it would replace nearly every plugin most people use.
Personally i still use lockette as people like to lock doors with it.
I'm running it on 1.4.4 with no known issues.
-
View User Profile
-
Send Message
Posted Nov 16, 2012@ferds814
Running 1.4.4 with it. No major issues yet but the minor ones might have went unnoticed.