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 Apr 30, 2012@bigscary
Nope, and now when you select the gold shovel nothing happens.
-
View User Profile
-
Send Message
Posted Apr 30, 2012@ChazimMC
Assuming we're not talking about people in creative mode, those are cheats, not griefs. Use NoCheat or NoCheatPlus. I run NoCheat on my server. If you mean some players are giving themselves creative mode, then the solution is to take away their op mode so they can't use /gamemode, and put them permanently in survival mode.
@Lyndon321
The admin details page has an /ignoreclaims command.
@codedonut
I used to have it that way, but I got a few complaints that admins accidentally made changes to another player's claim because they didn't realize they had wandered into one.
@JustinM511
Are you running that command from the console?
@zedadiaswick
Yes, it should save to file immediately. One other person has reported something like this to me, and we haven't figured it out yet. Try other claims? Also check your log file when you use /trust to see if there's any error message about not being able to access the file.
@Lius98
Are you also using MultiVerse, like ThisUserNameIsMine? It could be that I need to ensure I load after MultiVerse. I'll look into it.
@Munkyman587
TPS = ticks per second? Do you see this with and without users online, or only when the server has players actively playing? Try Cvx's suggestion to use NoLagg's examiner and let me know if you come up with anything.
@Munkyman587
Okay a few things. First, good job collecting data, but now you need to get that over into Excel and try to get an idea for how much time your server spends on GP versus other plugins (proportionally speaking). Finally, unless you're noticing a problem, you don't have a problem. :) If you eventually have a problem, then come back and tell me.
@Gamemasher
How are they abusing it? Please provide some details.
I haven't done it the way it's described in that post due to the expense of scanning a player's inventory every time he tries to give or receive PvP damage. It would probably lag live servers horribly. If Bukkit ever gives me a "player inventory changed" event, then I'll update accordingly.
@shutka
No, because WorldGuard isn't just about grief. It has features unrelated to grief, which I will never add here.
-
View User Profile
-
Send Message
Posted Apr 29, 2012@ryvix
I like that idea. On my server, a lot of people abuse the PvP immunity ability and since my server is PvP based that is a problem.
-
View User Profile
-
Send Message
Posted Apr 29, 2012Hey, did you guys see this before? http://dev.bukkit.org/server-mods/deathcontrol/forum/issues/35276-grief-protection-conflicts/#p2
I don't use the PVP features on my server but just thought I would point it out because it sounds like it could be a good idea.
-
View User Profile
-
Send Message
Posted Apr 29, 2012@mrcheesete0
might i ask why you say that? its neither informative or helpful if anything it seems like ur asking for some random person to offer to teach you? :S
-
View User Profile
-
Send Message
Posted Apr 28, 2012I'd love to make some of these requested add-ons, unfortunately I'm to lazy to teach myself Java. its really hard
-
View User Profile
-
Send Message
Posted Apr 28, 2012@Munkyman587
ill begin checking through it now, this is the exam files contents correct?
run the nolagg exam with Greifprevention loaded and then again with it unloaded (if you can) and upload those files somewhere or pm me for my email ;)
too much data to chew through lol.. if u get some exam files i.you can see the clear problem in less than a minute :P
http://dev.bukkit.org/server-mods/nolagg/pages/nolagg-examine/
-
View User Profile
-
Send Message
Posted Apr 28, 2012Can you see anything strange here? I am bad at interpreting the results, I just know higher times are bad
http://pastebin.com/pfmS3n8f
Restarted the server a couple hours ago
-
View User Profile
-
Send Message
Posted Apr 28, 2012@ThisUsernameIsMine
this is what happens when u pull the trigger with gun pointed down
shoot urself in the foot lol
-
View User Profile
-
Send Message
Posted Apr 28, 2012@Munkyman587
first up i'd call it a conflict not GP, as GP doesnt affect my ticks at all, and running an examiner showed that, try nolagg's examiner to see which plugins are taking the longest
-
View User Profile
-
Send Message
Posted Apr 28, 2012Not sure what happened to my comment, so I will post a new one. I have an issue with TPS with the server with this plugin installed. The timings look alright, but the TPS falls to about 10 when I am using this plugin, and back to 20 when I remove it.
There is no noticeable lag to the end user, but I definitely see it in my logs. Is there a conflict with Essentials Protect? Thanks
-
View User Profile
-
Send Message
Posted Apr 28, 2012@cvxx7q
Yes, he probably will ;)
edit: erm, i think i've fixed it (forgot to import the world using multiverse)... :$
-
View User Profile
-
Send Message
Posted Apr 28, 2012@ThisUsernameIsMine
alright im pretty sure bigscary will get onto it ;)
-
View User Profile
-
Send Message
Posted Apr 28, 2012@cvxx7q
Thanks, but the same thing happened. Its probably world-name related.
-
View User Profile
-
Send Message
Posted Apr 28, 2012@ThisUsernameIsMine
take my config, enter in the worlds and options u already have, and see if it works, just to be sure, mine is formatted how GP creates it, so i figure its worth a shot, i know it shudnt matter, but just to be sure ;)
-
View User Profile
-
Send Message
Posted Apr 28, 2012@cvxx7q
Those worlds belong to each other so my guess is that Grief-Prevention isn't capable of handling random (unrelated) worlds.
Edit: The config was freshly (re)generated. I only changed some settings ;)
-
View User Profile
-
Send Message
Posted Apr 28, 2012@ThisUsernameIsMine @Lius98
how strange, mine works fine, but i do not use extra worlds, so that may be where the problem lies, im not sure
http://dev.bukkit.org/paste/5238/
EDIT: i think ur missing claims enabled?
-
View User Profile
-
Send Message
Posted Apr 28, 2012@cvxx7q
the case is correct, no tabs or white-space probs, parses just fine :-/
http://dev.bukkit.org/paste/5237/
@Lius98
Bummer!
-
View User Profile
-
Send Message
Posted Apr 28, 2012@ThisUsernameIsMine
@cvxx7q
Yeah I have the same problem, but I use world as the world. And world is the main world on the server :/
-
View User Profile
-
Send Message
Posted Apr 28, 2012@ThisUsernameIsMine
tried the correct CaSe?
and are you entering the worlds name or the worlds folder name?
can u slap your config.YML in a pastebin?
lastly check your config for white space, i don't think there is any by that error, but still worth a look ;)