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 Mar 29, 2012@bigscary
Not pushing for this, but is there any plans to implement stacked claims? I doubt it, based on the way they're currently set up, but is it? :o
-
View User Profile
-
Send Message
Posted Mar 29, 2012@Fostenel
Assuming you're on the latest version of GriefPrevention, your players can put lava and fire outside of protections. The fire won't spread. Lava can't be placed above sea level outside of claims only because it's a huge mess to clean up, and in that case it's almost certainly a grief and not a legitimate "build" placement. If a player wants to place lava on the surface, they need to place a claim and wait for the claim to mature (an hour) before adding lava. If you REALLY want all of your players to have the option to dump lava in surface wilderness, then use a permission plugin to grant all players the "griefprevention.lava" permission.
RedPower may need an update. Mods which introduce "machines" or other gadgets that can modify the world often use a fake player account like "redpowermachine" when they make changes, instead of the owner of the machine. If the mod makes the world change the machine owner's name, then permissions will be correctly respected. You can imagine that it's pretty much impossible for me to fix an issue with a modified bukkit on my end, since the mod you're using doesn't play by the rules of the bukkit platform. It will have to be fixed on the mod's end. I've heard similar requests/feedback about tekkit and industrialcraft, and there's just no way for me to fix it from here.
I don't understand what you mean by "mod users"? The /trust commands don't look in the player data folder. They look in your server's list of offline players (check your world folders). If a "user" isn't a true player account which has logged into the server before, then you can't set permissions for that user.
@Phonix420
Claims always reach up to the sky (max height). They start pretty shallow in the ground (that's configurable), and extend downward as you build or break underneath them. Yes, that config option indicates how far below the lower of the two claim corners you set when creating or resizing the claim.
No, stacking claims is not possible.
I will look into the problem with the /trust commands. Remember you only need to use ONE of them, the command with the highest permission. If you follow /trust with /containertrust, for example, you're REDUCING that player's permission from /trust down to /containertrust.
-
View User Profile
-
Send Message
Posted Mar 29, 2012Love the plugin BigScary, and have a couple of requests.
First off, I really appreciate all the thought you put into the protections, and the great explanations of why they exist. It would be really nice if there was a bit more configuration though. I think the way you have things setup is a great default, but I'd like the option to be able to allow fire and lava outside of protections for instance (while keeping them from spreading into protections).
Second, I use a modded Bukkit with RedPower2, and just ran into an issue with block breakers not being able to place blocks. It works with my 1.1 server if I have [RedPower] user opped with full permissions, but it's not now with my 1.2.3. Ideally I'd like to be able to have users add the "mod users" that they choose to allow, but when trying, you get a "Player not found." error. Interestingly enough, the mod users show up in the PlayerData folder. I know the goal of your mod is to prevent grief, and this setup really creates a big hole, but it works for my particular situation, and your plugin does things that meet other needs.
-
View User Profile
-
Send Message
Posted Mar 29, 2012@bigscary
Thanks again BigScary. It just seems that sometimes I have to be standing next to the person for the /trust command to work. I'm definitely standing in the claim, and i'm not misspelling anything I get all the confirmations, but then they still can't build.
Then I tp directly beside them and repeat the command and it works. Idk seems strange but I could just be trippin out.
Also should players be making 3D (cuboid) selections with this? Like if they just put their corners at ground level how high up will it claim? I set it to claim 15 blocks below as well, does this mean it's claiming 15 below the claim markers?
And is there anyway to claim lets say a hotel room or a room on a multi-level building?
Thanks as always!
-
View User Profile
-
Send Message
Posted Mar 29, 2012Hi everyone, please take a couple of minutes to hop over to this plugin and tell the developer what you think of it. :) I think he's wasting his time and causing a major distraction for server owners, but maybe you have a different opinion.
http://dev.bukkit.org/server-mods/areaguard/
-
View User Profile
-
Send Message
Posted Mar 29, 2012@Qwahchees
You can disable claims, yes. Just go to the claims worlds list and include only a world that doesn't exist. Now claims will be disabled on all worlds.
The better thing to do is to place claims around all the shops. Use /containertrust public in those claims to make sure players can do everything except for break stuff. Now because the area is already claimed by the shop owner, nobody else can claim there. Fixed.
If it's an admin shop (meaning not player owned), just use /adminclaims and forget about /containertrust, even easier.
@mrcheesete0
Yes, the higher claim permissions always override the lower claim permissions. That's on purpose. Give individual players access to only the plots they should have access to. If you have a "manager" for the entire plot system, you would give that player access at the highest level, so that he would automatically be able to manage all the plots.
@shutka
Maximum plot size won't help. Players will just create multiple plots right next to each other, forming a giant claim area anyway. I can't fix this by restricting the total claim count per player, because then players will often have to choose between leaving the server or abandoning their previous hard work builds to start new ones. Those are both bad options.
@Phonix420
Just give the player /trust <playername>. If someone has the ability to build, they logically have the lower permission levels (if you can build, you can break through any door and break any chest to get the loot anyway).
You can set trust even on offline players. The only rule is that the player you're giving permission to must have logged onto the server at least once before.
-
View User Profile
-
Send Message
Posted Mar 29, 2012Hmmm, I'm kinda stuck here. I created a claim to be used as a town, created a subdivision, stood in that subdivision and did: /trust playername /permissiontrust playername /accesstrust playername /containertrust playername
but the player still could not build in his area. I dug down deeper and placed one of the corners above bedrock and repeated those commands but still nothing.
I finally tp'ed him to me and typed: /Trust playername /PermissionTrust playername /AccessTrust playername /ContainerTrust playername
And then it worked. I'm not sure if it's because of the case sensitivity due to the fact i get the proper output when I do /trust etc in lowercase. It appears I can only set trusts when players are directly beside me? I know this can't be right feel free to give insight thanks for all your help thus far!
-
View User Profile
-
Send Message
Posted Mar 29, 2012@cvxx7q I found these settings in plugin vampire. Now everything works good. "dropSelfOverrideMaterials": [ "GLOWSTONE", "WEB", "DEAD_BUSH", "BOOKSHELF" ],
-
View User Profile
-
Send Message
Posted Mar 29, 2012@QoTheGreat
well i tested with an adminclaim and i couldn't break anything including what you said, check ur claim with string maybe the blocks are outside by accident
also depth of claim is another thing, try digging to the lowest part (will extend your claim)
-
View User Profile
-
Send Message
Posted Mar 29, 2012@cvxx7q No. This happen on both userclaims and adminclaims. WorldGuard works fine.
-
View User Profile
-
Send Message
Posted Mar 29, 2012@TruthSeeker83
tell us something we don't know ;)
remember to make a big fuss over any bugs (please use latest bukkit 1.2.4 build)
it helps alot
-
View User Profile
-
Send Message
Posted Mar 29, 2012This plug is great.. trying it out now on my server :D
-
View User Profile
-
Send Message
Posted Mar 29, 2012@QoTheGreat
Uncomfirmed
i could not reproduce this, are you sure you haven't enabled Trust on your tester?
or enabled /ignoreclaims (i think thats the correct command)
-
View User Profile
-
Send Message
Posted Mar 29, 2012GP 3.1 Players can still grief the glowstone and bookshelfs
-
View User Profile
-
Send Message
Posted Mar 28, 2012Possible candidate for CraftBukkitUpToDate?
http://dev.bukkit.org/server-mods/craftbukkituptodate/
Thanks for everything! ;-)
-
View User Profile
-
Send Message
Posted Mar 28, 2012If you want immediate access to updated builds as soon as they are released
goto http://dev.bukkit.org/server-mods/grief-prevention/manage-subscriptions/
tick "File Updates" then click "Update" button
every time an update comes out, at least 1 person says they cant find the link :S
GP 3.1 http://dev.bukkit.org/server-mods/grief-prevention/files/40-3-1/
-
View User Profile
-
Send Message
Posted Mar 28, 2012@bigscary
Wow BigScary thanks for all your hard work!! I don't see the new version up just yet though I'll be checking minute by minute lol
-
View User Profile
-
Send Message
Posted Mar 28, 2012@bigscary
can do ;)
-
View User Profile
-
Send Message
Posted Mar 28, 2012OKAY GUYS read carefully. I saw the bukkit update come out, and I rushed to get my current changes stable and get this build out. I didn't test as much as I'd like to, but I did check the absolutely necessary stuff like anti theft and anti build/break, explosions, and fire/lava flow.
If you notice an issue, please post here. Do be careful and test a little yourself, okay?
Some changes:
config file has changed, you have a list of world names for both claims and siege now.
players in pvp combat will die if they log out. there's a config option to disable this
fire can be placed anywhere now, but when pvp is disabled in your world, it can't be placed within three blocks of another player.
lava can be placed on other players when pvp is on, but still not on the surface unless it's in a claim.
during pvp combat, players can't access containers, drop items, or build in claimed areas.
pvp combat is "over" when 15 seconds pass without taking or giving pvp damage.
updated some messages, you might notice them or you might not.
restore nature got some more small improvements, especially for water/lava hanging in the air and fixing "water craters". it still needs some work to cover dirt and clean up lots of items littering the ground.
there may be more, but like i said I'm in a hurry. will clean up this change list later.
-
View User Profile
-
Send Message
Posted Mar 28, 2012so 3.1 doesn't bring the game-breaker (new config)?