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 Jan 24, 2014Okay did that and I save it, start the server and it defaults the .yml file every time. I tried both ways.
Then I did this:
And I get the same result, defaults it when I start the server.
-
View User Profile
-
Send Message
Posted Jan 24, 2014At present is there no way to limit what TNT blows up in a /siege? I see ExplosionBreakableBlocks, But TNT in a siege still blows everything sky high. World Config: http://pastebin.com/ccW8bUVa
-
View User Profile
-
Send Message
Posted Jan 24, 2014Duplicate claims are STILL being made with the latest dev build thus putting players into the negatives. This was found to be true whenever I issued /reload after players have made a claim.
Please do fix as I've already been forced to reset the entire damn plugin as a result of the bug a few builds back that resulted in data loss.
-
View User Profile
-
Send Message
Posted Jan 24, 2014By any chance, is there an event that is called when a claim is abandoned? If not, would this be a possible feature to consider? I have the ability for a plot to be made into a commercial plot to allow creation of shops, but I'd like to not allow the claim to be abandoned unless that status is removed by the player.
-
View User Profile
-
Send Message
Posted Jan 24, 2014@switorik
That PVP option was removed because it is RIPE for exploitation, I know because I was the victim of it a few years ago. Some more recent mentions of the issue and some people bringing up other issues with PVP made me decide to address those problems as well; in the previous implementation, if the server restarted, any player engaged in PVP or in a siege is killed, and they lose all their items.
Want to grief a player? Empty your inventory, go to a player you don't like when your server says "Server restarting in 5 minutes" and wait until it's going to restart and punch them. TROLLOLL! Now they have no items and everything they had in their inventory has been destroyed.
@Wolfen2448
You should be able to disable everything but Spam within the world configuration(s). Just be sure to leave GriefPrevention.Enabled set or GP will ignore any events that it receives from that world.
@AuGsReaper
You would need a Block Placement Override, to allow placing of Chests:
In fairness of course, I haven't gotten around to properly documenting the overrides. The idea here is that The overrides will take precedence over any other rule, and allow you to have material-specific overrides. This can also be used for standard rules (eg preventing players from placing Furnaces, for example).
In this case, the Override applies to Chests Only; we allow it in the wilderness and we allow it in claims, but in claims it requires build trust (as anything normally does).
Of particular note is the "SpecialRules"; In this case we flag the override as only applying if the player has no claims, after that it should be denied like any other block placement.
In the long term the idea I had was to re-introduce something like the verbose "NoSurvivalBuildingOutsideClaims" option from 7.7 and previous, and have it "silently" add the appropriate overrides internally, because even if the overrides were well documented it's not entirely obvious that you would use them to get this behaviour.
-
View User Profile
-
Send Message
Posted Jan 24, 2014I've an issue with BuildCraft's buckets with Oil and Fuel. GP don't protect region when the Fuel/Oil flows around. Please answer me.
-
View User Profile
-
Send Message
Posted Jan 24, 2014I am having an issue where skeletons can shoot out the items in item frames, including inside a claim. Here is my setup for item frames: http://pastebin.com/xpYQ7Yp3
I liked the way when you PvP logged on the older version. When you log out in PvP, you drop all your items right there and then instead of giving them to the player when you log back on. I do hope that is an option.
-
View User Profile
-
Send Message
Posted Jan 24, 2014this is the only plugin i have affecting TNT explosions. TNT doesnt damage blocks in wilderness like i want in the config.
http://dev.bukkit.org/paste/9203/
-
View User Profile
-
Send Message
Posted Jan 23, 2014i cant find the files button for tekkit server
-
View User Profile
-
Send Message
Posted Jan 23, 2014So my server is working perfectly except the claim block issue. When a player joins the server, the default claim blocks is 0. I set everything to 100 claim blocks (blocks that I want to start out with,) but still it doesn't work. I want the claimblocks for all players to be at 100 not 0. I don't want to manually adjustbonusclaimblocks or setclaimblocks. I've also reinstalled GriefPrevention, but the problem still rises when I ask a player how many claim blocks they can claim (the answer: 0.)
Issue: Player starts out with 0 claim blocks. I want players to start out with 100 claim blocks.
-
View User Profile
-
Send Message
Posted Jan 23, 2014@Cra2ytig3r Thanks for the reply, however if you change the BlockPlacement and BlockBreaking rules for each world config to force_deny in the wilderness, Like I did here:
Basicly I want to set it so the entire would is protected from sea level up. But If I set it like that, then you can't place a chest to protect your land. Is there something I missed?
-
View User Profile
-
Send Message
Posted Jan 23, 2014Build 260 player remaining claim blocks are going down instead of up....Remaining Blocks =-98
Edit: I miss read the /ClaimsList info. I am guessing that negative number is the amount of blocks player has left to use.
-
View User Profile
-
Send Message
Posted Jan 23, 2014The claim corners appear any time you place a block inside the claim. How do you disable this?
-
View User Profile
-
Send Message
Posted Jan 23, 2014Hey, Is it possible to disable everything but the chat protection? This is the best chat protection I have seen, but I am currently using another protection plugin.
-
View User Profile
-
Send Message
Posted Jan 23, 2014@AuGsReaper
That was answered like 4 posts ago and that info is in the documentation above. Please read before posting.
-
View User Profile
-
Send Message
Posted Jan 23, 2014Is there a way to set your world so players cant build but in there protected area?
-
View User Profile
-
Send Message
Posted Jan 23, 2014@BC_Programming
So pretty much I have to either edit around 200 players manually or delete all claims on the server via starting the plugin over so no one's in the negatives? =|
Fuuuunn...
-
View User Profile
-
Send Message
Posted Jan 23, 2014lol at refund :)
@BC using build #260 (with spigot) is still duplicating the 1st claim of all players upon doing a full server restart and thus causing the player to go negative if they have a large first claim. Should i adjust players data in the files, or will a later update fix this, therefore making my adjustments give players too many blocks?
Also could you take another look at ticket 491 (PvP dupe) as that is still an issue. I posted more testing results and an error from the log too. From what i can see, you are testing in a slightly different way to me.
Thanks in advance.
SMC
-
View User Profile
-
Send Message
Posted Jan 23, 2014Thanks for the tip! :)
-
View User Profile
-
Send Message
Posted Jan 23, 2014@squeezer2k
With 7.7, you can use the noSurvivalBuildingOutsideClaims option.
With 7.8, you can change the BlockPlacement and BlockBreaking rules for each world config to force_deny in the wilderness, which should give very much the same effect.
@Ruthless_Gamer
I rewrote the claim loading last May/June to load and save claims as worlds load and unload, instead of all at once. At the time I was testing with a MCPC+ Forge server and was able to successfully have claims save and load and persist across reboots in mod worlds such as Mystcraft worlds, The Biome O' Plenty Promise land, and so forth.
@Bras
1. No, however, there are several mods (Flags and GP-Flags are two I know of which are listed on the main page here) that can give you that functionality. I'm not versed in their specific capabilities or configurations but I'm quite certain that is one of their capabilities.
2. Subdivisions/subclaims. However, I do not recommend this approach- a subclaim is always considered owned by the owner of the top-level claim (some plugins that allow claims to be given to other players will change the owner, but GP now enforces the ownership to simplify permission checks and keep the model consistent). Additionally, with a large number of claims performance will be reduced quite spectacularly because it doesn't have the advanced optimizations in place as the top level claims do.
Otherwise, you can use subclaims in an admin claim and give full trust (/trust) to the player you want to give the plot to.
Depending on your use case, it might be worth investigating whether other plugins like Towny may fit your needs better than GriefPrevention.
@Smac3223
In the playerdata folder. They have the names of the players in question. The second line of each file is the number of accrued claim blocks the player has.
simply saying, "Do it yourself" is not exactly helpful
If you are unhappy with the level of support received I can issue a refund :P