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 26, 2012Typo: typing /trust says "Graants a player permission to build..." Using GP 6.2
@jtaker6619 & daltonj123: you have to set up a price in config
@overload1525: Try this plugin
-
View User Profile
-
Send Message
Posted Aug 25, 2012If you use /spawnmob to summon an enderdragon and the dragon dies over someone's claim, it makes a portal on that person's claim and destroys blocks. I had a shop up once and was letting people fight a dragon because they were bored and it destroyed a big chunk of the shop. Please make it so this does not happen to claimed areas.
-
View User Profile
-
Send Message
Posted Aug 25, 2012Is there a way to disable pvp in claimed zone? or set it to false by default after claiming the land?
-
View User Profile
-
Send Message
Posted Aug 25, 2012I am using last version of GriefPrevention to versaso 1.2.5 of my tekkit server. There is a issue that the player get negative value of blocks to claim. How can I fix it ?
-
View User Profile
-
Send Message
Posted Aug 25, 2012When ever i go to buy claims with the command nothing happens and im the server owner so i have enough money to buy them whats wrong?
-
View User Profile
-
Send Message
Posted Aug 25, 2012@CayleRose
Type /ignoreclaims
Or /ic for short.
-
View User Profile
-
Send Message
Posted Aug 25, 2012As the owner of a server, how am i supposed to break blocks/open chests that are protected by one of my users?
-
View User Profile
-
Send Message
Posted Aug 24, 2012Seems like /buyclaimblocks does nothing when I enter it. No response in the chat or console.
I'm using the latest version for 1.2, since I'm using Tekkit. Any ideas what's going on?
-
View User Profile
-
Send Message
Posted Aug 24, 2012-
View User Profile
-
Send Message
Posted Aug 24, 2012@Smudge202
well.. that was a stupid mistake by my part ¬¬
Thx Smudge
-
View User Profile
-
Send Message
Posted Aug 24, 2012Hi and Thank you for the program. Can you please tell me where the jar file should be installed to? Very new to server mods so not sue where it should be located.
Thank you again
-
View User Profile
-
Send Message
Posted Aug 24, 2012@Jabulba
One of two things...
1) You've downloaded the wrong version of GP. Click 'Files' at the top, and pick the one that is supported by Tekkit. If you don't know which one is supported, type version into the console which should list the API version at the end. Tekkit 3.1.2 I believe is MC 1.2.5-R4.1.
2) Wrong Java. Uninstall JRE 6, download and install JRE 7.
If it's not one of those two, hopefully someone else can help.
Cheers.
-
View User Profile
-
Send Message
Posted Aug 24, 2012Hi, I am getting the following error when i try to start my server: I tried with a clean tekkit version 3.1.2 with just grief-prevention, as well as with my main server. both give this error.
http://pastebin.com/eCbCJjPT
any clue on how to fix it?
-
View User Profile
-
Send Message
Posted Aug 24, 2012@bigscary
bigscary,
Thanks for the quick reply. In truth, I'm a little thankful that you don't support it yet, but purely because it means I didn't overlook some super-sized-multi-coloured print that explains how to do it somewhere! =)
Good point regarding protecting more than is necessary, I may wire that up in a test world and see how it fairs. Up to now I've tried to be incredibly meticulous with what is enabled, disabled, protected, permitted, etc, so if the option to keep the granular control was there, I'd certainly go for it.
WRT to Tekkit catching up, piece of string I'm afraid, and I'm probably not the guy to ask - anything I may say would likely be wrong or at least get me slapped. =)
If you spent the next 48 hours solid, coding a 1.2.5 back-compat fix, on the 49th hour the next tekkit would be released. If you decide you'll wait, it's bound to be months... ^^
Being that data values exists in both 1.2.5 and 1.3+, I imagine the back-compat, if not too much extra work, would earn you even more of my heart...
I respect your decision either way
-fellow coder (though not modder)-
Cheers!
-
View User Profile
-
Send Message
Posted Aug 24, 2012@SweetMopy
You'd be doing me a great service if you spread the word on your favorite server administration forums. :) Too many people are doing anti grief the hard way.
@Smudge202
It's because data values aren't supported yet. So you can put 250, but not 250:3. This was an oversight on my part, and I will correct it soonish. I'm just waiting for Tekkit to catch up to 1.3.1. If I get really impatient, I might release a back-compat version for 1.2.5. If you're worried about protecting too many blocks by doing something like "250", it's probably not an issue. Remember that it only stops players from interacting with those blocks in claims using right click. So protecting too much isn't going to cause you a problem.
Do you know how long it is usually between MC updates and the associated Tekkit updates?
-
View User Profile
-
Send Message
Posted Aug 24, 2012bigscary;
First off, thank you for all your work on this! That the average player doesn't *need* to run command makes this, in my mind, the best anti-grief tool out there, let alone all the other features!
I'm not sure if I'm doing it wrong, using the wrong version (hampered by running versions compatible with tekkit), or if you've posted this already, but is it me or does the config file not seem to appreciate metadata values? In particular, I've tried a couple formats for Container Trust for say, a Macerator which in 3.1.2 tekkit should be 250:3. Any time I enter metadata onto the block id in the config though, it seems to strip the record out?
I'm sure it's just me, but if you or anyone else could point me in the right direction...? I'd love to drop LWC and switch to GP, but can't until I've worked this out! =(
Cheers!
-
View User Profile
-
Send Message
Posted Aug 24, 2012@bigscary
Awesome! I'm running a survival server, so the config won't affect me. Thanks again that's exactly what I needed to know! Seriously amazing plugin btw. Much more effective and simple (infinitely more simple) than any other anti-griefing plugin I've used. If you are looking at this and thinking about it, seriously just try it!
-
View User Profile
-
Send Message
Posted Aug 24, 2012Okay so here's my plan for refining the automatic claim rollback in creative worlds (for when land is unclaimed). Please tell me if you see any potential problems. :)
1. Treat ores above sea level as player placed blocks. Some natural ores will be removed, but nobody in creative mode needs to mine them, anyway. This will prevent griefers from building stupid stuff (giant penises) out of ores to make them safe from automatic cleanup.
2. When I remove sandstone, I'll try to backfill with stand when there's sand on top of it and beside it. This should remedy the mess I'm seeing in desert regions after cleanup, but still remove any griefer builds made out of sandstone.
3. For claim resizes and abandons, I'm going to clean up after 10 minutes or so. There are two advantages. First and most importantly, this will ensure that griefers can't experiment rapidly to see what will be cleaned up versus what will not. They might even leave the server before the cleanup happens, and be none the wiser. Second, this will give me an opportunity to warn players that unclaimed land might be changed by other players or reverted by admins, and then they'd have time to change their minds and reclaim the land if they want. The only downside is that when you /reload or restart your server, any pending restores won't happen.
4. I'm also considering adding a "recently deleted" claims feature, so you can see who use to own an area, which will help you catch griefers who actually manage to succeed in building something that isn't automatically cleaned up. Basically, you'd use the stick to check an area - if there's no active claim there, then I'll search recently deleted claims and show you one of those when available.
5. My creative server is full of claims with practically nothing built in them. Seriously, I have 2500+ claims and only about 10 regular players. I'm planning to start scanning and removing claims for any inactive player when the claim is smallish (close to the max initial claim blocks) and includes few player-placed blocks. Hopefully, this will make it easier for new players to find unclaimed land. Unfortunately, this last will probably involve me writing a lot of new code. :P I might also use it to automatically remove those damned lava towers.
All this will probably come next week. I plan to publish a new plugin this weekend to fix Tekkit (an item banner which is easier to use than all of its competitors, and which comes pre-configured for Tekkit).
-
View User Profile
-
Send Message
Posted Aug 24, 2012@Yorkforce
Give your players more claim blocks and tell them to make their own borders. Better yet, clear out your "players ignoring all claims" so that machines can't make changes to claims. Because Tekkit doesn't tell Bukkit everything it does, you'll always have some trouble with plugins which will involve you looking for workarounds. This is one of those cases.
@Ta6akus3
There's not enough there for me to tell what's going on for your case. Can you link me a paste bin of the whole thing? It looks like you stopped right before the line number with the problem. Yes, I'll update the code soon, I forgot last night.
@SweetMopy
Just replace the jar. There was a config update, but unlike the NoCheat guy, most of my config updates don't involve you having to actually do anything. You only have to update your config if you're running a creative mode world and you want to try the new "allow players to unclaim land in creative mode" option.
-
View User Profile
-
Send Message
Posted Aug 24, 2012has the config file been changed in the most recent update, or can I just replace the old .jar with the new one?