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).
Thank you for this mod. It's very easy to use. :)
I think I may have found a bug. When using bonemeal to grow trees around the spawn area, I'm getting the following texts on right click:
This happens both inside and outside of the protected area. I'm using bukkit 1.1-R1 and Grief Prevention 1.5.
@cvxx7q
I think that's a perfect example of shooting yourself in the foot - building a structure out of silverfish blocks, then giving players silverfish eggs LOL. In my original post there, I should have said "without the help of plugins, griefing with silverfish seems impossible". Of course, if you install a plugin which does something very different from the standard gameplay, it's likely griefers could find some way to use that other plugin to circumvent griefprevention. For example, consider the very common plugin which allows players to set their "home" location and later teleport back to it. Today, I see a new player is building a hut. I walk over there and set my home right in the middle of it. Two weeks later, it's a castle with super max security, and I use /home to teleport right in to PvP him with my diamond sword, and there's nothing he can do about it.
As for how a typical player without the help of game altering plugins could shoot himself in the foot with silverfish, the only thing I can think of is either building a house near an ender gate, or building a house out of stone and then very patiently luring silverfish to it. Now when he changes his house and/or fights a silverfish nearby, his house starts falling apart. That's what he gets for not considering the implications of an exceedingly uncommon course of action, like building a trap with lava and pistons or constructing an underwater home (you'll probably kill yourself a few times in the process), or building a very tall treehouse (you'll likely fall out a few times).
Anyway regardless, I'll look into how tough it will be to fix.
@bigscary
well.. ill forgive you just his once... lol! just kiddin ;) been great author to me, ive filed a million bugs and u ahvent even got sick of me yet hahaha!
how will he shoto himself in the foot with silverfish? also i have made a public area (a HUB if u will, actually thats its name... haha) and its made of mostly block 97 and i sell mob eggs (high prices of course *adds more 0's*) and yeah if the spawn one silver fish and everyone belts it, all the blocks smash and silverfish pop out and eventually all the blocks are chewed out and yeah... griefed
if its possible please "fix" or make it configurable, otherwise ill have to find a new material, your call ;)
EDIT: is it possible to block silverfish spawns in claims or all together, if this means alot of code just to fix one little thing, ill have to find something else
EDIT2: elaborating on the silverfish blocking IF possible, maybe stop them in admin claims, but allow in player claims so they can still shoot em selves in the foot :P
1.5 Updates!
Sorry guys, but you MUST clear claim data before upgrading to this version. Delete the "ClaimData" folder, but NOT the "PlayerData" folder. This way claims will disappear, but players will keep their claim blocks (allowing them to recreate those claims). I've been trying hard not to do this, but it IS still officially Beta, and this time I don't think I could reasonably avoid it. :\
Players may now use /permissiontrust to give another player permission to share his permission level with other players. /permissiontrust does NOT grant a player permission to use /permissiontrust in your claim, delete your claim, resize it, or create claims on your behalf. This could be useful for a tenant scenario. For example, you build a hut and grant someone /containertrust and /permissiontrust. Now he can't change the hut, but he can give his friends access to open the door and even to use the chest you placed for him inside the hut. Like other permission levels, /untrust will undo /permissiontrust. There's also a new convenient /untrust all to clear all the permissions which have been granted in a claim, useful when you're evicting a tenant (and his friends, of which you don't have a list).
Nether and End claims will no longer disappear on server reboot, and the associated error messages during boot are gone (assuming you deleted your claim files like I recommended).
Placing and breaking paintings now requires build permission.
Fluid flow seems to be working fine, now.
Administrative claims now correctly allow for killing animals, operating buttons and switches, and opening containers, as they did previously before I broke them.
@cvxx7q
I think I'm actually okay with allowing ender eggs to teleport. They're extremely rare, and it'll be a challenge for players to find a way to show them off while preventing them from teleporting.
Similarly, with silverfish... I studied carefully about how they operate, and I think it's incredibly difficult (maybe impossible) to purposefully grief with them. So I want to leave their default behavior in, so that if a player chooses to play with silverfish, the grief prevention plugin will allow him to shoot himself in the foot. This thinking is similar to allowing for buckets of lava to be dumped within claims, provided the dumper has build privileges - it's good to allow players screw themselves over, since that's part of the fun in Minecraft.
another request of strange origins lol, Ender Dragon eggs, if i place it in a claimed zone and punch it etc it teleports, once again it is only a decoration, but i guess if some gets one of these and uses it on their land and someone TP's it out of the claim and steals it (or just TP's it away to grief) then that person would be quite annoyed ;)
hope this is possible to fix and in your interests ;)
@bigscary
haha chill chill :P
well hopefully you can tell the plugin to convert "old" strings to your new ones when it loads the claim files, shudnt be too hard for users but may be difficult for the coder ;)
luckily i dont have many claims yet so if u do change it i would just go in with NPP
has some pretty neat string tools, find replace etc
if anyone wants something for editing there YAML and flatfiles in a very neat manner use this http://notepad-plus-plus.org/download/v5.9.8.html
instead of notepad or wrodpad, its far far easier to use and it natively understands YML formatting (bonus)
@cvxx7q
Yeah, that's my suspicion too, from the moment you mentioned your problem. I'm really kicking myself now for being stupid enough to use the underscore as a delimiter. I'll confirm and fix. Hopefully I can fix it in a way that will keep most claims intact rather than forcing everyone to clear their data out. Adding to my stupidity, this is a direct conflict with my other plugin, which creates a new standard world with underscores in its name. So much fail!
@bigscary
sure thing, and i suspected a name difficulty
if you want to see the water thing/check my servers plugins or watever join my alpha testing server (the server is a WIP) and u can see it for yourself ;) (i'll PM you the necessary info on request)
EDIT: oh wait i forgot my server is open for viewing please go here
http://cvx.power.on.net/MCServer
its a public directory so if anyone wants to view configs or watever go ahead ;)
EDIT2: you will see 4 claims for the nether, its the same one. its just me repeatedly doing the claim
EDIT3(its my last i swear!): bukkit adds "_nether" automatically, i think your plugin is viewing the underscore as a seperator
so its proabbly loading CVX.POWER.ON.NET_NETHER_CO-ORD_CO-ORD
instead of
CVX.POWER.ON.NET_NETHER_CO-ORD_CO-ORD_CO-ORD
in short, its counting the word "nether" as a co-ord and thinks i am telling it to load a level name and 4 CO-ORD's
@burtthaman
like i said, paintings really mean nothing to me, i wouldnt even craft them haha but to others they do and when you run a server your somewhat obliged to make sure everyone gets what they want out of your server
as for the creepers try out CreeperHeal (i havent used it in quite awhile tho) it does wat it says regenerates explosion damage t a per-block rate you set, so for tnt ppl can blast the hell out of the ground if they wish to mine and grab the ores etc they want and leave it will heal block per block while they are there so adds a time factor to the mining ;)
go too deep/take too long and ur entry u just blasted open is gone, ;P
@cvxx7q
I just have creeper explosions and creeper damage turned off so that they don't mess up anything anywhere. They are so annoying. Lol
@cvxx7q
I'll look into the water issue when I have my internet back, and I'll also check on silverfish and paintings.
Regarding the issue with the nether, will you please find that claim's file and send me the contents? You can open the file in notepad. It's under plugins/griefpreventiondata/claims. I can probably fix it, just have to figure out why the problem. Could be related to the name of your world.
@bigscary
definitely no flow inside claims, i can make floating water sources (since they wont flow down) dont get me wrong lol this has been useful to make some cool effects :P
villagers were used as decoration lol, its not a big deal (to me) but wud be nice ;)
also paintings inside calims get broken by explosions like creepers etc, paintings always have that issue in every plugin ive had, are they just impossible to protect? lol
doesn't mean much to me but it does to others
EDIT: silverfish destroy stonebricks inside claims, block ID 97, just regular stonebrick, when they "wake" eachother they break the stonebrick and spawn, this is probably a somewhat unlikely situation to occur (silverfish in a claim) but its worth fixing i think
@bigscary
i think i found a somewhat major issue, i make an admin claim in the nether and thats fine but upon stopping and starting the server your plugin reports the the string is invalid and therefore does not apply that region in the nether basically removes it, and too bad about the snow and power etc :S is really crappy when ur stuck inside and cant even work on something...
16:45:40 [INFO] GriefPrevention: Grief Prevention enabled. 16:45:40 [INFO] GriefPrevention: Unable to load data for claim "CVX.POWER.ON.NET _nether_-47_64_27": Expected four distinct parts to the location string. 16:45:40 [INFO] GriefPrevention: Unable to load data for claim "CVX.POWER.ON.NET _nether_-47_64_29": Expected four distinct parts to the location string. 16:45:40 [INFO] GriefPrevention: Unable to load data for claim "CVX.POWER.ON.NET _nether_-47_65_31": Expected four distinct parts to the location string. 16:45:40 [INFO] GriefPrevention: Unable to load data for claim "CVX.POWER.ON.NET _nether_-48_64_28": Expected four distinct parts to the location string. 16:45:40 [INFO] GriefPrevention: 8 total claims loaded.
good thing this isnt a live server yet :P (in progress)
boy do i feel stupid... The piston thin is a false alarm, sorry, i must have pulled a block right on the edge (outside the zone) i shall test more thoroughly in future
Hi all, sorry for the delay in releases and responses. I've been buried in the snow with intermittent power and internet. I can't do dev work until I get both services back at 100%.
Also, before releasing the subdivision feature (which will complete the Beta), I'll be running a COMPLETE test pass, re-testing everything. I'm also planning to create three youtube videos demonstrating the player scenarios, power player scenarios, and administrative scenarios. Please tell me what you think are the most important features to be covered in each of these videos. I will be demonstrating only the most important functionality to keep the videos short.
@ValawynV
Yes, there are MANY advantages to always running claims up to the sky, including simplicity in creating and managing claims, elegant visualization, and grief-avoidance (by building overtop someone's claim).
@Qwahchees
Economy integration is already done. If you configure GriefPrevention to work with a Vault-compatible economy, players can trade blocks by selling, then giving money, then purchasing. See the administrative details link.
Any player can check available claim blocks be equipping the golden shovel. Did you mean to request an admin command to check another player's blocks?
AFK is a separate issue, in my opinion. I do understand how a player could use AFK to get extra claim blocks, and I don't like it, but I think managing things like AFK and a login queue should be handled by a different plugin. My current promise is that GriefPrevention will work right out of the box to stop grief, so I have to avoid any potential conflicts with seemingly unrelated plugins. For example, I wouldn't want someone to have to configure grief prevention just because they're running a login queue or no-AFK plugin, and GriefPrevention interferes with that. I might change my mind - I'll keep that suggestion in the brain bank for later.
@cvxx7q
Are you sure about the piston thing? I can't test right now to check, but that was tested thoroughly and shown not to work previously. If you can steal blocks from a claim with a piston right now, that's a regression from previous quality and I'll have to fix it. Please check again, and make sure you're actually pulling blocks from inside the claim to outside the claim.
@burtthaman
Very doubtful on visualization. It's a huge deal here because claim boundaries are varied and unpredictable. The PopDensity boundaries are so straight, square, and HUGE that I don't see a big benefit. Players can easily determine a boundary just by walking across it and getting the region notification, and VERY few players can both fly and see far enough to see the whole region visualization, anyway.
@cvxx7q
Regarding fluid flow, check that again, too. Current behavior is to allow liquids to flow around inside a claim and even OUT of the claim, but never INTO another claim.
To delete a public (admin) claim, use /deleteclaim rather than /abandonclaim. This is intentionally to ensure admins don't confuse admin claims they have access to with their private claims. This way, an admin always knows when he's deleting a claim shared with other administrators rather than one of his personal claims. If /deleteclaim isn't working, please post again.
The suggestion about allowing fire that starts in a claim to spread within that claim is not a bad idea, but I won't implement it because it's too difficult to test completely. Fire is extremely dangerous to allow to spread in any case, and doesn't spread predictably (like lava), which means I can never be totally sure my code is right.
Cauldrons are easy enough to fix, I'll get that in soon.
When you earn more blocks, you're offline. I guess I could show players a message when they log back in, but other plugins also add login text, and I don't want to contribute to the spam. A player can very easily check is claim blocks by just equipping the golden shovel.
I'll check into the killing animals thing. As for villagers, that's by design for two reasons - first, nobody can "own" a villager, and they're not valuable for anything besides looking at. So when they're killed, neither a specific "owner" player or the general player population is really hurt. I don't think it should be considered a grief to kill a villager. A shame maybe, but not a grief.
Water can be "Stolen" from cauldrons, i use them for decorative purposes (like there is any other? lol) and they can be robbed with glass bottles ;)
and can players be notified of when they earn more blocks?
EDIT: ops cannot kill animals on admin land, and players can kill villagers i don't know if that's intended but its a problem for me :P
another thing, i cant unclaim an admin claimed zone
when im an OP (no perms system used)
EDIT: also when i claim some land the water/lava wont flow, now this CAN be great but sometimes it isnt, perhaps it should be configurable that if the owner places say fire or lava or water it burns/flows only inside the claim so if a tree is half in and out and i burn the side in my claim the fire wont burn the rest of the tree, same for the water/lava when it meets the end of the claim it cud stop
im not sure if those are difficult to do, but they sure would be handy ;)
@bigscary
Any chance we can get a boundary visualization for popdens regions akin to griefprev.?
@Qwahchees
I really like the afk no blocks earned idea. However your first idea about "giving" blocks will most likely not happen. Opens the window for griefers to trick others into giving them blocks then griefing with blocks they would normally have to pay for or play a long time to get. If two people are building together they can just connect their claims and give each other full trust etc.
@Qwahchees
slightly bigger issue, someone can eat the edge of the land away with pistons, i know its not a viable form of grief but those kinds of ppl are persistent
Oh, another BIG issue. You should create a command to count how many blocks a person has.