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 Aug 11, 2012@Peregrin5
Sorry Perr, I tried to see if I could make this happen on my end, and I couldn't. Are there maybe some important specific details you left out?
@Praqoon
Glad you got it figured out. :) Sorry if it seems a little complicated - but the complication comes from performance considerations.
@Luficer
I really don't want to add direct integration with any other plugin. It will make my life difficult going forward. Maybe if you create that extension plugin, then everybody can toss out WG altogether, and then there will be no need for integration. :)
@Praqoon
I don't think that fixes my problem, because it doesn't prevent the player who abandoned his claim from how claiming a different area to create another giant cobblestone penis, you see. :)
@S4BRE
Sounds like you're using a 1.2.5 server with a 1.3.1 grief prevention. Either upate your server to 1.3.1, or use an older grief prevention version.
@kaitoshijo
I want to help, but I need more information. Are you running any mods? Are you running many other plugins? Are there specific player actions which appear to coincide with this error?
@Blockia
Fixed in the next version, apologies.
@mvdhoning
Resetting claim blcoks is easy, just delete your playerData folder.
For the other, do a file search for files in your claimsData folder which include the name of your world, and delete those.
Do both of these with your server turned off, because some data is saved during shutdown (which will restore some of the files).
@spacedestroy
No, claims don't stack.
@AssRealm
Fixed in the next version. Awesome job catching this bug. :)
@mvdhoning
What do you specifically want to konw about the player data files?
-
View User Profile
-
Send Message
Posted Aug 11, 2012@Praqoon:
Can you explain the format of the PlayerData files?
-
View User Profile
-
Send Message
Posted Aug 11, 2012@HexaDroid
I'm having the same issue(s) with lockable wooden doors, etc. As a test, i set my config like this:
LockWoodenDoors: true LockTrapDoors: true LockFenceGates: true LockAllDoors: true
This didn't solve the problem of doors, fence gates and trapdoors being unlocked and available for anyone to open/close.
-
View User Profile
-
Send Message
Posted Aug 11, 2012@mvdhoning
In order for you to achieve what you're suggesting, I believe it would be easiest to manually edit the config and data files for the players and claims on your respective worlds and then merge the files under one world. Then run it.
-
View User Profile
-
Send Message
Posted Aug 11, 2012@pgirl
lol. Try it. guaranteed crash for the weak machines out there.
-
View User Profile
-
Send Message
Posted Aug 11, 2012@AssRealm
I'm sorry - that's a terrible thing to have a server crash - but now I have a mental image of this arrow forever bouncing all over the place! :D
-
View User Profile
-
Send Message
Posted Aug 11, 2012@bigscary
Just found somewhat of a bug..
A player apparently is not a member of a claim and there are lots and lots of animals confined into an area. so he shot a arrow cheekily and the plugin rejects the arrow. Causing it to bounce off. However, since there are so many animals in a small area. the arrow keeps rebouncing unable to reach the floor, the plugin spams the chat "That belongs to playername" to the player Please fix it and allow the arrow to be gone. It crashed my server. :(
-
View User Profile
-
Send Message
Posted Aug 10, 2012@bigscary
I know it might be a little "hard" for some server owners, but I think it is pretty easy for a coder of your caliber to just add one config option where owners can enable explosions to happen on certain worlds and just turn if off by default on all worlds. Surely a simple toggle like that would be appreciated by many, especially those who run multiple worlds. It's just a request though, I just wish it gets implemented if it ain't that hard to do - that would be a dream come true for me, and please call me miss. :D
-
View User Profile
-
Send Message
Posted Aug 10, 2012@Blockia
Same problem for me. With the latest update of griefprevention. I set to lock all doors and trapsdoors to true
LockWoodenDoors: true LockTrapDoors: true LockFenceGates: true
Still they can be opened by everyone.
-
View User Profile
-
Send Message
Posted Aug 10, 2012@spacedestroy
That's on his to-don't list XD He intentionally disallowed "stacking" claims. http://dev.bukkit.org/server-mods/grief-prevention/#w-the-to-dont-list I guess the next best idea is to just make plots on a single layer unless you use WorldGuard
-
View User Profile
-
Send Message
Posted Aug 10, 2012it's possible to make a subclaim on the top of another subclaim? D: couse I make some kind of a bilding and I want to give floors for the players, is that possible?
-
View User Profile
-
Send Message
Posted Aug 10, 2012on my server i plan to moving to a new survival world on my server and remove the old one, but i have also setup an creative world that is going to stay.
how do i easy remove the claims in the survival world only and keep the claims in the creative world?
also is there an easy way to reset the amount of claimblocks for all players?
-
View User Profile
-
Send Message
Posted Aug 10, 2012Everything seems to be working find up until now on the latest build and recommended build of bukkit, however wooden doors are not locked to the public even though I have:
LockWoodenDoors: true
Set in the config. Is this just me or is this the same for everybody?
-
View User Profile
-
Send Message
Posted Aug 9, 2012This error is spamming my console.
http://pastebin.com/9whTNVvp
R: 5.9 for CB 1.3.1-R1.0
-
View User Profile
-
Send Message
Posted Aug 9, 2012HI i am trying to get grief prevention to work on my server... when i start the server it throws up errors: at net.minecraft.server.MinecraftServer.t(MinecraftServer.java:387) at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:374) at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:208) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:438) at net.minecraft.server.ThreadServerApplication.run(SourceFile:492) Caused by: java.lang.ClassNotFoundException: org.bukkit.event.player.AsyncPlayerChatEvent at java.net.URLClassLoader$1.run(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:41) at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:29) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) ... 11 more if i remove the mod it plugin they go away. i can run all the / commands but can make no claims and the golden shovel doesnt work
btw i am on the latest tekkit.
I know it worked on the version before
-
View User Profile
-
Send Message
Posted Aug 9, 2012@bigscary
Re: your request for suggestions in creative mode...
How about making it so that the newly (deleted) unclaimed land cannot then be claimed by another player for a random number of hours/days? Or maybe allowing claim owners to transfer their claim to "Administrator" instead of deleting them?
If I'm being a noob please let me know! :D
-
View User Profile
-
Send Message
Posted Aug 9, 2012@bigscary
Ah that seems simple enough in theory. Assuming I could import the plugin as a library reference as per usual. Also, along the lines of not replacing WorldGuard, it'd be cool if it could at least tie a bit more into WG by checking if there is a region before triggering that alert about building outside claims, since it'd be claimed by WG. Maybe even tie into WE a bit and allow users to make claims with a WE selection however that'd work. XD That may also make the transition from WG to GP a little easier for some people.
-
View User Profile
-
Send Message
Posted Aug 9, 2012@Bigscary
I'm guessing you are right about the fluke with the claim blocks. I thought i'd accrued approx. 30 blocks while being AFK in-game but, as you suggested, when I tested again I received only 2 over a 60 minute period. The anti-idle is indeed working very well! Sorry to have troubled you. Thanks again. :D
-
View User Profile
-
Send Message
Posted Aug 9, 2012Thanks scary. Also I think I've found a bug. Abandoned a subdivision within a claim, and the visible subdivision goes away, but when trying to resize another subdivision over where the old subdivision used to be, or add a new subdivision, the plugin states that it can't resize because it will overlap another subdivision (that doesn't exist anymore).
-
View User Profile
-
Send Message
Posted Aug 9, 2012Hey all, I could use some suggestions. I don't like that I have to deny creative mode players the option to delete their land claims, but I know that a griefer with unlimited blocks could use claim deletion to make a mess of any size by claiming/building/unclaiming repeatedly, or to build something offensive and get away with it.
Does anyone have a suggestion that might allow non-griefers to delete their claims without giving griefers an opportunity for unlimited wilderness grief?
@Luficer
I think all you need from GP is claim.getID() and datastore.getclaimat(location). You'd use the location of an event (like monster spawning) to see if there's a claim there, then that claim's ID to check your own data and see whether or not you've set any flags there, then take action (like cancelling the monster spawn) based on the flags which have been applied, if any.
@Praqoon
This might have been a fluke. How many claim blocks did you get? If it was just a very few (much less than you'd get for a full hour), then probably you get credited for the last time you moved before you went idle, and got just that sliver of blocks. If this doesn't sound right to you, let me know and I will investigate further to confirm the anti-idle is still working as it has before.
@Schlumpfpirat
griefprevention.lava permission
@Peregrin5
You can get started by going to wiki.bukkit.org. You'll have to learn some basic java first, and you'll find some youtube videos to help you get your environment set up (eclipse free software). From there, you'll see a few examples of simple plugins right there in the wiki, and many of the plugins posted on bukkit dev have also released their source code.
The design you describe is the default for creative worlds when running grief prevention. Although it does make grief pretty much impossible, users are always whining about how they can't figure out how to claim land with the shovel (ugh, kids) despite having a video demonstration available, and also complain that they can't delete their claims (even though the video warns them about that). So I'm just saying - yes it's doable, but maybe it's not worth the effort.
@beastfeaster
Not directly, but maybe there's a plugin where you can trade items in your inventory for server cash? In that case, a player could go items > server money > claim blocks.
@pgirl
Hmm... I'm not sure. But maybe check into coreprotect or essentialsprotect?
@Alchael
Sorry sir, there's no support for a separate "wild west" kind of world. At least not where ALL rules are disabled. Some have asked for something like that, and the trouble is that you can imagine how complicated and difficult to understand the config file would become if I turned every true/false option into a list of worlds. :\
@lol768
It's necessary because restore nature often places blocks. So it's possible the player could be trapped in a block and suffocated. I agree it's a little annoying. I've considered teleporting players out of the chunk for safety's sake, but it could sometimes be very jarring for players (like if they're underground, then suddenly on the surface). Let me think about it a little and see if I can smooth out that experience for you.
@jbanto
You can add it yourself in messages.yml. Look for a regular expression, I think near the end of the file. I will add your suggestion as a new default. :)