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 Oct 13, 2014Please read! I need your input/help.
I'd like to redesign the bucket limiting option.
Players don't like that they can't dump water to water their farms in the early game, before they have a golden shovel to claim their farm separately from their house. Yes, they can work around this by farming on top of or under or in their house, but still they don't like it. When players don't like it, admins hear about it, and admins don't like that.
The reason for the current rule about not placing water outside of land claims is twofold. First, griefers can use buckets to make a REALLY big mess with only a few block changes (due to water spreading mechanics). Second, it's expensive for grief prevention to track the flow of fluids, which means server lag. Restricting water dumping to inside land claims very much limits griefing with buckets, and also makes tracking water flow from those dumps almost free (due to technical reasons I don't want to try explaining here).
I would love to hear your ideas on other approaches to preventing griefers from griefing widely using buckets while still allowing players to build their ideal farms in early game. I don't think there's a great solution to this problem, but I hope I'm wrong. :)
-
View User Profile
-
Send Message
Posted Oct 13, 2014@mohawkguy360
Sponge guys have said they will allow vanilla clients to connect, and yes, they know that means changes to Forge will be required.
@Bobcat00
Show me the names? In private message, if you're feeling they're private data. Yes, it could be that they were denied entry for whatever reason - older versions of GP would generate player data files for players even if they didn't fully connect and play. Starting with the next version, GP will not create a player data file until they log out (assuming they're not banned before first log out - then they will not get one at all).
-
View User Profile
-
Send Message
Posted Oct 13, 2014@bigscary
For these "mystery names", is it possible they tried to login to the server but weren't on the whitelist? But even then, where would the names come from? They're not in the world playerdata folder.
-
View User Profile
-
Send Message
Posted Oct 13, 2014Though SpongePowered has lots of support from the community, it is built on Forge. Being required to download Forge will make the server experience more complicated for simple players like myself. I think CanaryMod (canarymod.net) would offer a good future and it would not be hard to port your plugin over :)
-
View User Profile
-
Send Message
Posted Oct 13, 2014@dutchrastacraft
Thanks! I've been thinking on your top 5 there all weekend and I haven't come up with a damn thing. I might be hitting a wall here - but if so, 1.18% is a good place to hit one. :) I think you can stop sending me these reports for now - we've done a great job, here! I will be shifting my focus to boot speed.
-
View User Profile
-
Send Message
Posted Oct 13, 2014@jaciloy
I recently removed that option entirely.
@LordDWT
Doesn't work - when world seed changes or Mojang updates their world gen code, using WorldEdit's regen command often generates an entirely new chunk which does not match its surroundings (e.g. snowy field chunk in a desert).
Also, many don't like that chunk regeneration puts trees and ores back.
@Bobcat00
I have a fix for that issue with underscores - I haven't published it yet, it will be in the next version. If you don't want to redo your whole migration, you could manually fix them by renaming those files to the correct UUID for that player (which you can get from handy websites to do that conversion, do Bing/Google search).
About names, GP looks in your player data folder and treats every file there as a player (when a player logs in for the first time, GP generates a player data file for him/her). Maybe I'm forgetting about something, though... otherwise, they must have joined at some point?
@Queketth
Alright so the files are there (claims and players?), but when you're in the world, you can't get the claims to show up with the stick (right click)? This is very bizarre. If the claims were expired, then the files should have been deleted. I don't think that's the case, and anyway the default is that most claims don't expire at all, and those which do expire slowly over time, not all at once during boot.
I guess you'll have to zip up all your data and get it to me somehow? Maybe post on some file sharing site where I can grab it.
-
View User Profile
-
Send Message
Posted Oct 12, 2014I am currently experiencing an issue possibly due to expired claim data: (online, flat file storage) I ran through the UDID conversion and everything went well and all the data was converted successfully according to my logs. However my server has been offline for approximately 1 and a half months due to hardware maintenance issues and now when you log into the server nothing is claimed. I am unsure of wether this issue has arisen due to all the claims timing out or how this has occurred but the files are still present in the ClaimData and all my PlayerData still exists and now is converted to UDID format as well, any help on restoring this data would be greatly appreciated as obviously I can't get the server back live until I have my claim data back / being read.
Note: This issue was also present before the 8.0 update / this morning so could as I stated be due to expired claim data? I updated the server to 8.2.3 incase the issue was non converted PlayerData but the same problem persists. New claims etc are all working perfectly.
-
View User Profile
-
Send Message
Posted Oct 11, 2014Just used my test server to upgrade from 8.0.3 to 8.2.3, running CraftBukkit, online, flat file storage. Everything seemed to work OK except for two users whose names start and end with underscores. Their files weren't converted to UUID format and their block count was reset to 100. They didn't have any land claims, so I can't check what would have happened to them.
One very strange thing during the conversion process: After the note "Calling Mojang to get UUIDs for remaining unresolved players", there are about 70 players listed, most (maybe all?) of whom have never been on the server. Where is it getting those names from?
-
View User Profile
-
Send Message
Posted Oct 11, 2014~ Time for daily timingssssssssss ~ http://timings.aikar.co/?url=8541049
-
View User Profile
-
Send Message
Posted Oct 11, 2014@LordDWT
I often use WorldEdit to manually restore stuff, it can be a pain sometimes when near other claims and it's nice to have GriefPrevention's restore nature. WorldEdit regen includes tree and ore generation. Trees and ores (including gravel, sand, dirt, clay, coal, and three different new 1.8 stone types) expand into areas outside the selection. This is because it relies on the default generation code which is assumed to only run once when a chunk is loaded for the first time. Although it sounds good in general, it could be used to grief or to create an endless source of easy to obtain-without-travel clay, sand, or even coal (exposed in extreme hills biomes) for a keen individual.
-
View User Profile
-
Send Message
Posted Oct 11, 2014@bigscary
@bigscary There's not a warning if the option is false in the config. Take a look at it. I also noticed the restore option doesn't handle stained glass at all.
Suggestion: Make the restore option work similar to WorldEdits Regen command.
-
View User Profile
-
Send Message
Posted Oct 11, 2014@bigscary
Suggestions:
when option:NoSurvivalBuildingOutsideClaims: true
if people don‘t have any claims then they can place a Chest to claim.it will great!
oh,my bad English。。。。
-
View User Profile
-
Send Message
Posted Oct 10, 2014@dutchrastacraft
Dunno how devvy you are, but this change was responsible for the perf boost:
https://github.com/ryanhamshire/GriefPrevention/commit/e7b649810ecb7d0f424b5b5ea62286ca078c2d68
I found the problem only because LostWave reported a different issue with UUID conversion with the same root cause.
-
View User Profile
-
Send Message
Posted Oct 10, 2014@bigscary
Thanks! And yea, just letting you know :) Good luck!
-
View User Profile
-
Send Message
Posted Oct 10, 2014@jyrgas
What do you mean by "use villagers"?
@dutchrastacraft
:) Yes I've been having some success with perf improvements. Thanks for the updated timings, I will dig into those this weekend.
Oops! Thanks for that report - I actually know exactly what those errors are about, and will have it fixed today. They're very low severity - no damage done.
-
View User Profile
-
Send Message
Posted Oct 10, 2014@bigscary: Wow!? WHAT? Is it me or is this massive improvements since 8.2.3! http://timings.aikar.co/?url=8535852
And only 2 minutes to load the plugin! I'm impressed! Can't wait to see more coming soon :D (Loginevent?)
I'm also getting two errors, but I have no idea what reproduces them. (checked my logs from today): Error 1: http://pastebin.com/GahWYBqU Error 2: http://pastebin.com/SsseiipK
-
View User Profile
-
Send Message
Posted Oct 10, 2014How do you make so players can use villigers outside claim?
-
View User Profile
-
Send Message
Posted Oct 10, 2014@LordDWT
Hmm... I don't think I should have that option there at all. It's my intent to always restore nature in creative mode worlds when land is unclaimed, because otherwise there are no real limits on how much a griefer can build. Here's what a griefer would do if unclaimed creative mode land were not automatically restored:
There is a warning about unclaimed land being restored when players try to unclaim.
-
View User Profile
-
Send Message
Posted Oct 10, 2014@bigscary I have a problem with GP restoring abandoned claims in creative even when the config is set to not auto restore. https://mega.co.nz/#!ZB1ggB7Z!YBL7FcVhO0narP2mfKI6MadlCVEFKLBh7aEondL3hWw
-
View User Profile
-
Send Message
Posted Oct 10, 2014@NeO_Anderson2005
Hmm... I think you have two not-fun options. You could restore your backup and re-upgrade with 8.2.3 for better UUID conversion results. Or, you could manually go and edit the problematic land claims - for example if you use /transferclaim, I think the player's UUID will be written into the owner field so that you won't get that error anymore for that claim.
I think the first option, while it will lose changes since your backup, is the better one. It's faster and will result in players having the right claim block counts and immediate access to their land claims.
The latter will keep changes since your backup, but you'll have to give all players some amount of claim blocks which may not be close to what they actually had, and you'll have to use /transferclaim on all the admin land claims to restore the proper owners.
Now that LostWave has had success with his enormous server, my confidence level on UUID upgrade is high. :)
@Phreag
I will look into both of these as soon as possible, thanks for the report. :) I know that on my test server at least, I don't have the "anybody can break blocks" issue. In fact, outside of /ignoreclaims mode, even I can't do anything in land claims. Maybe the problem is specific to patched Spigot?