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 19, 2012This really does seem to have it all! Such amazing work. Going to try adding to my server tonight. If all goes well, I'll be back to click that donate button for you ;-)
All your plugins are amazing, thank you so much.
-
View User Profile
-
Send Message
Posted Aug 19, 2012@JustinM511
Try /ic and use the perm node associated to it.
-
View User Profile
-
Send Message
Posted Aug 19, 2012Greetings! I must say, this is a great plugin! I have experience with Towny, Residence, LWC, etc and I keep coming back to this one. It's simple enough that my players can use it without constant staff interference.
However, I am missing a few things and I was wondering if you could help me out with them:
Thanks!
-
View User Profile
-
Send Message
Posted Aug 19, 2012How can I restrict access to all GP commands for a particular group? I would like to block access to all GP access for my default group for users who login to the server without registering. I use Essentials Group Manager for permission management but I do not see the GP permissions in its configuration file.
Thoughts?
-
View User Profile
-
Send Message
Posted Aug 19, 2012@Gengarx33
Hi Gengarx33, I spent a few hours on Bigscary's GriefPrevention server he runs trying to make this 'BUG" happen. I used his server because I know he has it working in an Ideal way and that by being "The Developer" he would have it set up correctly. I tried every possible way to reproduce what you say is happening for you. I never once had it happen. I can only assume that you have some other mod or plugin causing this for you.
I don't want to be rude with my next statement, but I must say what I feel. In my opinion before you make a post about a "Bug" or problem, you may want to verify it is an actual bug with the plugin before posting. Also, it would be better in the future to give some info with your post, such as , version of plugin, version of craftbukkit, a list of other plugins you may be running, and anything else that may help. By posting the way you have here, you could cause people to decide in not downloading this wonderful and well designed, maintained, and error free plugin because they see "There's a bug" and "Please fix this!". I'm not trying to deter you from future postings or cause you to feel bad or upset with me or this developer, just hoping you handle yourself in a more professional and detailed manner in the future for the benefit of everyone.
-
View User Profile
-
Send Message
Posted Aug 18, 2012How install GriefPrevention on Tekkit ? I installed with versioin CB 1.2.5-R4.0 and worked =)
-
View User Profile
-
Send Message
Posted Aug 18, 2012There's a bug, where if you place a piston and activate it and the part that can move hits the other person's territory, the WHOLE territory will automatically belong to the person who placed the piston. Please fix this! D:
-
View User Profile
-
Send Message
Posted Aug 18, 2012Hi @bigscary, I will admit straight away that I am a noob. But I desperately need your help to get off all the crappy "grief" prevention tools and onto yours.
If you can't get to these pastebin files, please let me know... I have them set to Member login.
I think I may need help figuring out how to add the permissions commands (I'm using PermissionsEX) for Grief Prevention and maybe Population Density? Population Density is working like a charm and I LOVE LOVE LOVE it.
Thanks in advance!
-
View User Profile
-
Send Message
Posted Aug 18, 2012@bigscary
Well not quite an error message, just a notification:
You do not have an administrator's permission to build here.
And I'm pretty sure GriefPrevention is throwing it, since I was able to place boats when I removed the griefprevention.jar.
I'm placing boats ranked as regular player in a public adminclaim and I do not have any CreativeRulesWorld defined.
And correction, it's only occurring with boats.
-
View User Profile
-
Send Message
Posted Aug 17, 2012Config: http://pastebin.com/XUk0cLLF
GP 6.0
Bukkit b2327 (1.3.1)
Activating a dispenser via a button or lever immediately next to it does not work outside of a claim.
Also, players still get spammed by the 'Consider claiming land here' message if they have no griefprevention.claim permission node. (It's been taken away from them)
-
View User Profile
-
Send Message
Posted Aug 17, 2012Getting error when using golden shovel:
"Land claims are disabled in this world"
But i can't find anytihng about it in the config. Have tried using google to find a solution, but no luck. Is there other bukkit-servermods that is incombatible with GP? Server is also running Lockette (some users want the functionality of it). Is this what creates the error?
-
View User Profile
-
Send Message
Posted Aug 17, 2012@TheOneRelic
It's by design. If they fire outside of claims, then there's no way to know who they belong to, so it's unclear what permissions should be applied (for example, imagine an arrow is shot, and it hits a claimed pig - what to do if we don't know who it belongs to?).
@fungreenfox
There's nothing in there about GriefPrevention. It looks like LWC is the one not starting?
@Jaladon
Huh what now? There should be no problem. Are you getting an error message from grief prevention when you try and fail to place minecarts and boats? Are you trying to place them in the wilderness, in your own claim, or in someone else's claim? Is your world a creative rules world (see your config)?
@Esaych
Oh, I got it. Yes, that's already on my todo list. :)
@Feaelin
That's true, but it's too hard to watch players all the time and try to sort the bad apples. I do have that item on my todo list, because I'm a big fan of proactive (preventative) anti grief.
@BoboTheTwit
I've just checked and I don't see this happening on my end. Is the claimed area you're working with an administrative claim? Animals are allowed to be injured in admin claims. You can convert the admin claim to a more-restrictive private claim with /transferclaim.
-
View User Profile
-
Send Message
Posted Aug 17, 2012Other players are able to injure animals in claimed areas, with the latest griefprevention to date, and the latest 1.3.1 RB.
Players claim land, keep sheep or whatever in it, and other players (not /trusted in any way) can kill these sheep.
-
View User Profile
-
Send Message
Posted Aug 17, 2012@Esaych
Esaych, I'd say that access to the vanish command is a privilege that should be revoked if abused. Either the VIP loses VIP status or access to vanish command.
Further, I think granting anyone that isn't staff on the server access to vanish is a recipe for trouble. There are way too many potentials for abuse: Stalking a player invisibly to gather information about valuable locations (like a vast cavern I'm exploring on one server, its going to take me forever to plunder it. It'd suck if someone found it or learned of it via vanish), appearing out of nowhere and arrowing someone and then disappearing again (this one has happened to me), etc.
All my opinion, of course. Its your server! :)
-
View User Profile
-
Send Message
Posted Aug 17, 2012@bigscary
I like flexibility... But you're right. Over-complicating the feature set makes it more error prone and more likely to not achieve the main objective here. Stopping griefers/jerks from damaging the server.
@fungreenfox
Fungreenfox, I think you misread the error. Its indicating its having problems starting LWC up. I think perhaps you saw 'griefcraft' in the errors and read it as 'griefprevention'.
-
View User Profile
-
Send Message
Posted Aug 17, 2012Is there any way to allow players to place minecarts and boats? If not, perhaps it's an idea to implement in one of the next versions, or at least separate vehicle placement from building, so people can use WorldGuard to disallow it.
Love the plugin btw ;)
-
View User Profile
-
Send Message
Posted Aug 17, 2012Griefprevention cant startup anymore. Was working like a charm but suddenly..
13:09:40 [SEVERE] Error occurred while enabling LWC v4.3.0 (b736-git-1b1150b1) (August 08, 2012) (Is it up to date?)
java.lang.NullPointerException
at com.griefcraft.sql.PhysDB.precache(PhysDB.java:814)
at com.griefcraft.lwc.LWC.load(LWC.java:1387)
at com.griefcraft.lwc.LWCPlugin.onEnable(LWCPlugin.java:225)
at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:217)
at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:365)
at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:381)
at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:265)
at org.bukkit.craftbukkit.CraftServer.enablePlugins(CraftServer.java:247)
at org.bukkit.craftbukkit.CraftServer.<init>(CraftServer.java:199)
at net.minecraft.server.ServerConfigurationManagerAbstract.<init>(ServerConfigurationManagerAbstract.java:50)
at net.minecraft.server.ServerConfigurationManager.<init>(SourceFile:11)
at net.minecraft.server.DedicatedServer.init(DedicatedServer.java:105)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:378)
at net.minecraft.server.ThreadServerApplication.run(SourceFile:539)
This server is running CraftBukkit version git-Bukkit-1.3.1-R1.0-15-g12075d6-b2335jnks (MC: 1.3.1) (Implementing API version 1.3.1-R1.1-SNAPSHOT)
R: 6.0 for CB 1.3.1-R1.0 Aug 11, 2012
-
View User Profile
-
Send Message
Posted Aug 16, 2012Dispensers only work inside claims and not outside of claims. is this a bug or is that supposed to happen?
-
View User Profile
-
Send Message
Posted Aug 16, 2012@weja93
It's automatic, GP will do it for you. It will not be possible for you to return to flat file, so don't go there unless you have a strong reason for doing so (like you're an expert with SQL and feel 100% comfortable doing everything there, or you're absolutely certain that switching to SQL will noticeable improve your performance).
@woodsnake420
I'm very glad you like it. :) Please go to your favorite server administration forums and help me spread the word!
@Feaelin
In addition to the config file issue (which I admit you've mitigated with your suggestions), I'd also have to go and update EVERY grief prevention feature with additional code to turn it off in the designated worlds, and then test every one of those features first with it on, then with it off. And I'd have to repeat that testing regularly to make sure other changes aren't breaking it. All that for a very small minority of servers who want to do this kind of thing.
Putting two different player experiences on one server is irresponsible, whether it's a pvp world and non pvp, a creative and survival, a grief free and grief allowed. It adds a lot of complexity for the players who have to learn how to switch experiences (portals, slash commands, and so on), how to communicate across experiences if possible (complex chat system), and all just so that a server which isn't all that great at anything can boast a "high" player count, and its administrators can save themselves from having to two-box. Admins need to stop asking for plugin developers to support every ridiculous configuration imaginable. If they would, I think the overall quality of plugins would be much higher because developers could focus on core features and reduce complexity (= fewer bugs), and we'd all be a lot more friendly and patient. :)
@RemyPas
Hmm.. for one of the players who has negative claim blocks, please do /claimslist <player> and post the result. :) We'll see if the math looks suspect, or maybe some claims are being charged twice. Have you recently deleted any files, for example the playerdata folder? That would cause any bonus blocks to be reset to zero.
@Nallack
Yep, that's normal. If you want to further restrict permissions to one of those claims, use /transferclaim to convert it to a private claim. You can then optionally use /accesstrust public to grant the public access to buttons/levers without containers, if you like.
@MCZq
We already have /trust public, /containertrust public, and /accesstrust public. Can you be more specific about your problem with dispensers? What specifically are players trying to do that they can't?
@Esaych
I'll look into tiny.cc. For the short term, you can do this yourself by edited your messages.yml.
I don't undersatnd what you mean by "protection block commands". Can you explain a little more?
@SlyNine
/containertrust public (mentioned above in documentation)
@saintcrime
Yep, I know what you mean. I could clean it up, but I feel like it's an extremely small thing. :)
@Dilski
You're probably using a GP designed for minecraft 1.3.1 on a Tekkit (which is minecraft 1.2.5) server. The latest GP build you can use with Tekkit right now is 5.5.1.
-
View User Profile
-
Send Message
Posted Aug 16, 2012Yo,
I have Greif prevention and use it on a tekkit server, i fill out all the block IDs for the modded items, but evertime i restart the server, it resets that. Any help?
Is it an error in my config file? http://pastebin.com/YANVVRNs
EDIT I fixed the missing ' in the fakenames but it still wont work