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 Nov 14, 2012Request
Make BlocksAccruedPerHour configurable for multiple permissions EDIT for clarification: Permissions with static +Blocks/hour values attached, configurable of course.
&
Add a command for a +Multiplier to the block gain rate. With this, players on my server could buy "/protectionrate upgrade" or something similar to increase the multiplier by a set amount.
-
View User Profile
-
Send Message
Posted Nov 14, 2012@jayfella
@bigscary
I run a couple of servers with GriefPrevention, so it's possible that the one we were testing on isn't updated. I'll run an update and check again. Thanks.
Looks like you've released a new version (7.0), so it's time for an update anyway.
-
View User Profile
-
Send Message
Posted Nov 14, 2012Too bad you removed the teleport blocking. It was working excellently to avoid players using teleportation runes from runecraft during combat, and runecraft doesn't use any commands. (the teleport rune works by inking a spell on the ground, and then activating it with a tool, that tool can then be used to teleport a limited amount of times to where the spell was inked)
Perhaps make this a configuration option? I don't know, not sure how common my problem here is.
-
View User Profile
-
Send Message
Posted Nov 14, 20127.0 Updates!
@arrexel
I don't know how to explain your problem. Perhaps a redstone powered machine is repeatedly stopping and then re-releasing water somewhere?
@jayfella
Use claim.getPermissions(). You pass in empty array lists, and it gives you back all the permissions. It doesn't include permissions inherited from the top level claim (for the subdivision case).
@leiger
Are you sure you're on the latest version? That was tested and was okay in the last version I released (last week I think).
@jayfella
Sorry I don't plan to give them an ID. It saves me IDs, and using -1 as an ID for those also helps me tell a subclaim apart from a top level claim (in addition to there being no owner). Giving them IDs would require me to rewrite and retest a lot of the save/load code, including that dreaded SQL code that's easy to break and where bugs would be severe.
-
View User Profile
-
Send Message
Posted Nov 14, 2012@leiger - I just checked myself and item frames are not breakable if the person does not have build permission, neither are paintings. Are you using the latest build for 1.4? Maybe its another plugin causing interference? Im writing an extension plugin for this, and using a vanilla bukkit server and everything seems fine here.
@bigscary - Also, another problem I have with the API, and I'm hoping you reply so I don't have to write your whole plugin myself (:/) which would take a long time, is that sub-claims do not have a unique ID, so I cannot determine one from another. Could you give them an ID? Using the corner locations is unreliable since they can be resized, and you dont have any events i can hook into to determine any size changes either. An ID would be ideal.
Hoping you reply, because this plugin has a lot of potential to make your plugin just like towny, except with all of the awesome features you currently have.
-
View User Profile
-
Send Message
Posted Nov 14, 2012Hmm, there doesn't seem to be a ticketing system anywhere that I can see (here on BukkitDev, nor on GitHub or anywhere else for that matter).
Where shall we report problems and/or check if an issue has already been reported?
Item frames are not covered under a user's claim. Other players that do not have trust in the area can not only break them, but can also place them again inside the claim. I have reason to believe that paintings act the same way, but have not completely tested their behaviour.
This WorldGuard commit recently fixed the same/similar issue: GitHub: WorldGuard
-
View User Profile
-
Send Message
Posted Nov 14, 2012@bigscary
Any help with this? http://dev.bukkit.org/server-mods/grief-prevention/?comment=3229
Im actually more or less into developing the plugin into a towny-like situation where you can name plots/sub-plots, buy plot/subplots/adminclaims/subplots with money or items, and want to use your plugin to manage the build/trust permissions. I can get around a lot of what i'm doing by implementing it myself and using the unique ID as an identifier, but without being able to manage the permissions, and more specifically, obtaining a list of who has permissions per-plot, its going to result in me implementing that too, which is silly since your plugin does that extremely well. All I need is a list of who has permission per-plot.
-
View User Profile
-
Send Message
Posted Nov 14, 2012@bigscary
If that is the case, what could be causing the fluid checking event to run at such a high level? I'm assuming after (at most) a minute that all water will have reached its destination, or have been stopped by GP. If water has already followed its allowed path, does GP continuously check it?
PS, just donated a little :) Considering my server would be a wasteland without this plugin. Keep up the great work.
-
View User Profile
-
Send Message
Posted Nov 14, 2012@fungreenfox
Oh, I think I might know. Is the claim near the spawn? It could be that the player can't build in part of the claim because it's too close to the world's spawn point. That would explain why it only effects part of the claim, and why an op can build there while the player who owns it can't.
@arrexel
Switching to limit surface water won't stop already-dumped fluids from continuing to expand, it will just prevent anyone from dumping new puddles.
Unfortunately no, there's nothing I'm aware of that will help you locate where water is spreading. By the way, please understand that water which seems to be flowing (it's animated) isn't necessarily causing any lag. It's only when air is turning into water that there's any processing done.
-
View User Profile
-
Send Message
Posted Nov 14, 2012@bigscary
I have switched to limit surface water, however the lag is persisting. Is there a way to cleanup or find any current spills in the world?
PS I greatly appreciate your help. Your plugin does wonders on my server.
-
View User Profile
-
Send Message
Posted Nov 14, 2012@bigscary
The world is totally newly created yesterday as a flatland and only npc villages.
The only claim there, is one made by me, as i havent opened up for anyoneelse yet.
There are WE claims around the nearest npc villages but not where i claimed a little area.
Its not possible to build outside claims, so i guess it has discovered the world fine in the config file.
The problem is probably a permission i dont know about, as the player who claimed it can not, but the admin can build fine with override claims at my test alts claim. If i as admin make a claim, i have no problems building and smashing without override. Can you find the permission?
-
View User Profile
-
Send Message
Posted Nov 14, 2012I must say that your new video is fantastic and captures the effectiveness of GP to its very best.
Keep up the great work!
-
View User Profile
-
Send Message
Posted Nov 14, 2012@jayfella
Very glad to hear someone's working with the API!
Use claim.clearPermissions() and then claim.managers.clear() to 100% clear all permissions in a claim.
I'm not sure I understand all the details of your last paragraph there. In GP's design, the owner of a claim always has full permissions for any sub-claims, which makes sense because as owner of the top level claim, he could always resize or even delete a subclaim. If you're trying to change that dynamic, I'm not 100% sure it's doable without actually forking GP itself and making core code changes. What I'm sure you CAN do is "lease" and "rent" subdivisions, and "sell" top-level claims.
@arrexel
That's probably the reason for your performance problem. The water-handling code is efficient as I believe it can be. It's just that every time water spreads, the new block itself spreads, and so on... and then downhill starts the process over. So allowing a player to say, dump a bucket of water on a hillside, results in lots of processing for all that water spreading. It could be even worse if some griefer uses a redstone clock to rapidly switch a dispenser on and off.
By not allowing water to be dumped above sea level by default outside of land claims, GP is avoiding both the potential lag problem and the guaranteed wilderness griefing problem (water dumped everywhere just to make a mess).
@Chaett
Sorry to disappoint you on this. :\ If you're a coder or know someone who is, you could potentially get the source code for GP and adjust it to fit your rather unique scenario. Good luck with the server! :)
@Harry4of4
Okay, I'm looking into it. I have some doubts about resolution though, since there are MANY factors which aren't visible to me, like the details of your data, the database configuration, and so on. Even if I had those details, I'm not sure I could pin down the exact problem because I'm no database expert.
Have you been using GP for long? If there are only a few claims, it may be easier for you to start over in file system mode rather than wait for me to guess at the database issue.
@ManBeastPigDev
I'm already making a change which will allow players to list their own claims. Expect it this week.
@ryvix
I've heard it once before, but I don't think I'll implement it in the base plugin. It would involve adding another level of trust which depends on the type of block being placed or broken, which will be hard to maintain - for example you saw in the last patch that more farming was added. If you think about it, I think you'll agree that it's probably not worth the effort when you consider how many players would actually use it. Using subdivisions or separate claims for the farming area is "pretty close" to the same result.
@fungreenfox
Hmm... sorry, I don't even have a guess as to what could be the cause. Try right-clicking-around with your stick to see which claims it highlights. That may provide some clues.
@xbenas
Folks keep asking for this, but there are two issues which make it unnecessary (first) and a bad idea (second).
1. It's not griefing to attack another player on a server where pvp is enabled, and players can make themselves safe by using an iron door + stone button combination.
2. I think you'll agree that in general, allowing players to designate their own pvp-free areas on a whim is full of potential for exploitation and griefing. For example, griefers could create claims next to claims belonging to their victims, so that they can safely lie in wait for the victim to leave his protected area, then run out and kill him the moment he steps out.
@RamizWWW
It works on Tekkit servers. First, you need to list the tekkit blocks which are containers and those which are explosives (steam engines, etc) in the config file. Second, make sure you have the right version - if you're running Tekkit for Minecraft 1.2.5, then you need GriefPrevention 5.5.1. Third, Tekkit is seriously broken, and many of its items bypass ALL anti grief plugins - so you need to install the Tekkit Customizer plugin, which bans the problematic items.
In general, I recommend against running any Tekkit server that isn't private just for your group of friends. After more than a year of coding many plugins and running many servers, I still hate my Tekkit server for all the trouble it gives me. Tekkit is fun, but it's not quality software and requires LOTS of work and expertise to administrate.
-
View User Profile
-
Send Message
Posted Nov 14, 2012Why this plugin don't work on tekkit servers?
-
View User Profile
-
Send Message
Posted Nov 14, 2012Man, this plugin IS THE NEXT BIG THING!
Tough, my server players have been asking for one little thing I'm sure you can do of:
Globaly turn off PvP in any claimed areas. That's it. No configs, just simple one line in the same config. That would really turn the tables and make the WorldGuard useless for a lot of people, since I'm using WG just for PvP denial -.-
Thanks.
-
View User Profile
-
Send Message
Posted Nov 14, 2012I am using newest beta bukkit, (always), griefpevention and multiinv and multiverse.
5 survival worlds and one creative world.
when building creative, it is random where i can build inside my claim, and random where i can destroy those blocks again, or just digging. Sometimes i can set a block but not smash it. The world is added to
CreativeRulesWorlds:
- museum
Any clue what this can be?
-
View User Profile
-
Send Message
Posted Nov 14, 2012I have a feature request from a player.
Add a command that lets friends farm on ones land, "/trustfarm PlayerName" maybe? This would allow them to take or plant things. wheat, trees, pumkins, sugarcane, etc.
I think you can use /trust for that right? But it lets you do a lot more things than just farm the land.
Thanks!
-
View User Profile
-
Send Message
Posted Nov 14, 2012FEATURE REQUEST
***CURRENT STATE***
Permission: griefprevention.adjustclaimblocks
The /claimSlist command will list all of a player's claims along with their sizes and locations, and summarize the claim block math for you.
***SUGGESTION***
Permission: griefprevention.claimslist
The /ClaimList command to see your OWN claims only.
***RATIONALE***
Some of my players loose the plot (literally) and then i have to find it for them and top to it, and bring them there etc. It's just a pain. if they could get /claimlist themselves it would save admin time. Which is what the plugin it all about.
Thanks.
-
View User Profile
-
Send Message
Posted Nov 13, 2012@Chaett
Hey, to answer your question, you are protected from PVP when you get killed for a short duration to prevent spawn campers or if the player under protection picks up a block. Players also cannot pick up blocks for a period of time preventing spawn campers to throw blocks at them to disable their protection. This gives players a head start to get away so they can't get instantly killed :) I hoped i answered you.
@Chaett
@Chaett
Sorry, this is how i would solve that issue - In the settings of your server config , change pvp = false to pvp = true instead of using worldguard to specify pvp areas. Then use worldguard to protect 'safe' areas to deny pvp :) Im not sre if it will work but its worth a try :)
-
View User Profile
-
Send Message
Posted Nov 13, 2012@Chaett
Hey, to answer your question, you are protected from PVP when you get killed for a short duration to prevent spawn campers or if the player under protection picks up a block. Players also cannot pick up blocks for a period of time preventing spawn campers to throw blocks at them to disable their protection. This gives players a head start to get away so they can't get instantly killed :) I hoped i answered you.