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 Jul 31, 2012I will! Also I had a question.
What does the NoSurvivalBuildingOutsideClaims: option do in the configuration? Does it make so that NOTHING can be built outside of the claims? Or just no large things? I'm tired of having newbies create giant wooden platforms after razing the forest and just leaving it there and quitting the server. Quite annoying. Would this help, and if so in what way?
-
View User Profile
-
Send Message
Posted Jul 31, 2012@bigscary
You are a gentleman and a scholar.
-
View User Profile
-
Send Message
Posted Jul 31, 2012@Schlumpfpirat
I don't see anything in your list which can't be accomplished in the config file. See the "administrative details" link above to get all the details on what each configuration option can do for you. For example, you can disable the anti spawn camp, reduce the pvp cooldown to zero, and disable anti-theft so that lwc can handle that.
I won't add explicit worldguard integration, but that's a good candidate for an extension plugin, I think. Maybe you'd like to write it? :) I totally understand the headache in converting from another plugin. But for me to add code for each of the other plugins which would be a one-time-use for only some servers would be a giant pile of coding and testing effort for a little payoff (and I'd have to keep testing going forward, in case the other plugins make a change, or a bukkit change introduces an issue for me). So you can see where it would be best for someone who's a WG expert to do the WG integration, a Residence expert to do the Residence integration, etc.
For a migration to GP from WG, I have suggested to server owners before that instead of trying to manually go around and create all the GP claims with /transferclaim, they instead use something like ConsoleScheduler (with the /say command) to notify their players that they have a week or so to create GP claims, after which WG will be removed (or at least restricted to administrative usage). This will reduce your workload, and the only players who will be upset will be those who are gone for the entire grace period, and then return after, who happen to have been griefed in the meantime. I think those players will be few, because usually when players disappear for a week or more, they've moved on to another server or worn out their Minecraft experience altogether, and not every unprotected build will be immediately discovered and griefed. You can even do something in the middle - do the above, then supplement that with your /transferclaim by ensuring a few "key" builds that you want to preserve are protected.
If after reviewing the admin details page you feel there are some features which get in your way, please let me know. I can probably help with that.
@Sinistralis777
To answer your question directly, yes. There is a public API which you can use to create an extension plugin. Or, you can download the GP source code and modify it for use on your server.
However, there is already someone working on a real estate extension. :) Do check it out before you try to code anything yourself. There's a link above in the extensions section.
-
View User Profile
-
Send Message
Posted Jul 31, 2012I am in love with this solution and plan to implement it immediately. I was curious about something though.
I know you want to keep this strictly about grief protection. Is there a way to implement a command or plugin that will allow you to rent owned land to other players? (AKA they pay for X time and when the time is up it goes back to the original land owner)
I could really use something like this because I need to rent off land in my marketplace and would prefer to use as few plugins as possible for this.
-
View User Profile
-
Send Message
Posted Jul 31, 2012Hello. I really like the idea of your plugin.
How ever there are some features, that I really don't like and I'd love to toggle what the plugin handles and what it keep its fucking hands off. I want toggleable features, for example I don't want it to handle PvP at all or chest protection, sign protection, door protection - I want my LWC to overwrite all of the Grief Prevetion's protections.
In addition it would be nice if WorldGuard areas would get automatically claimed - if no player is registered, then it should be an administrator area, if an owner is added / listed - the owner should get the protection right. If multiple owners are listed the region is not getting converted or something. This is just, because we use a lot of WorldGuard and already have +1500 WorldGuard areas and it's such a pain to claim every single one of it.
I REALLY love the idea of this! And I understand why there are so many features - because you want no other plugin to be needed but this one to protect stuff. But for people which use multiple plugins, for good reason, that much features, which are not able to get turned off, are just too much.
- Regards,
Schlumpfpirat
-
View User Profile
-
Send Message
Posted Jul 31, 2012@myCraftServer
I think this may be too expensive. I'd have to check the list of allowed blocks EVERY time a player placed a block. Also, there's no option to blow up anything inside a claim. It seems very backward to me. Griefers would probably abuse this anyway if you had it - they'd claim a big area, blow it up, move the claim, blow that up... and so on.
@midnighte2
It's never possible to blow up claimed blocks. This is necessary due to TNT cannons, which allow a player (because of game physics) who doesn't have permission in a claim to move TNT into that claim. For this reason, I can never be sure that TNT blowing up in a claim was put there by the claim owner.
@sinnikin
I'm glad you figured it out. :)
@Peregrin5
Thanks for the compliment! PLEASE consider going to your favorite Miencraft server forums and telling others how much you like this plugin. Many server owners are doing anti grief the hard way, and they don't listen when I blow my own whistle.
-
View User Profile
-
Send Message
Posted Jul 31, 2012This is honestly the most and advanced grief prevention system out there, and it is SO easy to use. =] Thank you very much for creating this.
-
View User Profile
-
Send Message
Posted Jul 31, 2012EDIT: Found the command is /accesstrust public
May want to post that in the command list so it's easier to find. :3
--------------------------Is there a way to allow EVERYONE /accesstrust or /containertrust in a claim without having to type names manually? I tried /accesstrust * and that didn't work.The server I play on uses this plugin, and I've made a shop that I have protected with it. My problem is I can't setup a "Free Items" box or dispenser for anyone to use unless I filter through every name on the server, and add the new people who join every day.
A quick way to do this would be super wonderful if you decide to add more to the plugin.
Thank you for your time and consideration! -Sinnikin
-
View User Profile
-
Send Message
Posted Jul 30, 2012I can't seem to figure out how I can allow players with trust to be able to use tnt in their own areas, allowing them to break blocks. I do not wish to turn off surface damage. But I'd like it to be able to use tnt underground. We use mcMMO and one of the perks uses TNT.
-
View User Profile
-
Send Message
Posted Jul 30, 2012@bigscary
To explain what I need, I'll give an example. Nuclear Reactors, when they explode damage a huge radius of land. I can enable them to explode inside a claim, with your config setting, but I don't want them to blow up land outside a claim. However, if they are placed outside a claim and explode, they will be stuck in a never ending loop trying to explode and failing.
What I want is, a list in the config that lets me set blocks that CAN ONLY be placed inside a claim. This way, I can make the land inside a claim explode, but not let them place it outside, so they never get stuck in the loop.
Really my question is, is it possible to have a list of blocks inside the config that can only be placed inside a claim? I would have a few uses for this.
If this is at all possible, it would help me un-blacklist soo many blocks on my Tekkit server. Thanks for the reply, -Semajnad
-
View User Profile
-
Send Message
Posted Jul 29, 2012@McKezieSprinkles
I'm not planning on that, no.
@newfiekids
Just set bedrock as the only block, then. Nobody can break it, and since the list isn't empty, you won't get the default list back.
You understand this list is only for siege mode, right, which is off by default? If you're not running siege mode, then you can ignore the list entirely because no claimed block will ever be breakable without permission.
@myCraftServer
Explosions never break claimed blocks. It sounds to me that maybe you're worried that playres will blow up a large portion of nature, right? If so, maybe just turn the "explosions don't damage surface blocks" back on? I imagine that these nuclear reactor things are mostly a bad thing, from an anti grief perspective. Probably not many legit reasons to use one. Even with the option to block surface damage to blocks by explosions turned on, players could still use those to hollow out large caverns underground.
@Praqoon
If it was his only claim, and it happened to be the same size as a newbie claim would have been, then it will be removed. This may be the first and only case of this actually happening, sorry about that. But I don't keep track of how a claim is made. :)
@zedadiaswick
Which version are you on? You say filenames aren't complete? Your filenames should be all numbers, now. If you're still on a version where the filenames are locations, please update to solve that problem.
It's configurable now, so you can change it to whatever you think is best. Sticks are by far the easiest item to come by which doesn't build anything when you right click, AND is also in the creative mode menu (for easy access on creative servers). That's why I picked it.
String is harder to come by - it's true you get it by accident generally, but you can imagine some situations where you'd want one and don't see any spider around. You're even more likely to have some wood in your inventory or in a nearby box, and if not, you can punch a tree and create a stick without even building a crafting table first.
@seiterseiter
/acb [permission] <amount>
/acb [citizens] 10000
@ProfessorGazlow
I'm very glad you were able to figure it out. :) I'm sorry I took so long to respond, but I doubt I could have helped in this case.
@Willbbz
Someone mentioned he's working on one. :) I assume he'll contact me when it's ready for use, and then I will post a link here.
@sirmyllox
/ignoreclaims. Thanks myCraftServer for the help. :)
-
View User Profile
-
Send Message
Posted Jul 29, 2012@myCraftServer
There we go, it was that simple. Thanks :)
-
View User Profile
-
Send Message
Posted Jul 29, 2012@sirmyllox
You can type '/ignoreclaims' or alias: '/ic' in the chat. This will make anyone with the permisson 'griefprevention.ignoreclaims' bypass any claim limitations. -Semajnad
-
View User Profile
-
Send Message
Posted Jul 29, 2012How can admins bypass claims? didnt find a permission node for it .. and from what i understand the PlayersIgnoringAllClaims permission is not for players but for mods.
sorry for the perhaps basic question, i just started using this awesome plugin :D
-
View User Profile
-
Send Message
Posted Jul 29, 2012@Willbbz
havent seen any .. im also interrested in that if you find any :)
-
View User Profile
-
Send Message
Posted Jul 29, 2012Did anybody ever make an extension to this plugin to add claim flags like disabling PvP? :)
-
View User Profile
-
Send Message
Posted Jul 29, 2012Been trying to get this working for awhile now but it doesn't seem to want to work. The claim commands show up and all and I can claim things, however outlines never show up for the claims and whenever I use the shovel, it seems to always STAY on the first coordinate I right click irregardless of what I do until I relog. Example, I right click a block to try to make a small thing claimed near spawn, It won't let me make anything because either it says the claim is too small, or it will setup without any outlines.
Can't figure out a fix. Tried looking through comments and the pages and could find nothing.
EDIT: Believe I got it working, but still no outlines for claims. Anyone got any idea?
EDIT2: the plugin CreeperHeal was the problem.
-
View User Profile
-
Send Message
Posted Jul 29, 2012does anyone know of a way to give different ranks different amounts of area that they can protect
-
View User Profile
-
Send Message
Posted Jul 29, 2012It appears my old issue of claim files not being saved properly is still present. Some new claims have been hit with the issue of their state being saved between server restarts. I've checked the file names, and they are indeed not complete.
Would you like my ClaimData folder again? I'm not sure if it would give you any more information over last time I reported this.
Also, just as a comment on the decision to switch to sticks (something which hadn't occurred to me until after the switch): String was a good choice because it was readily available. You end up with it in your inventory without having to actively put it there, as it is gained by killing mobs. Sticks, however, the only way you'd really expect to have it with you is if you decided to make some, and bring it with you. I would say another mob drop would be more appropriate; feathers perhaps. I can see the argument that changing this so soon after changing it once too many already would not be so great, just wanted to share my thoughts.
-
View User Profile
-
Send Message
Posted Jul 28, 2012Hi there BigScary,
I upgraded to bukkit 1.2.5-R5 earlier today. Thought I might mention that because it's probably got something to do with a little problem I'd like to ask you about...
I've just had a player claim expire because the guy didn't login for 7 days. Claims.IdleLimitDays has not been set and this wasn't an unaltered "newbie" claim when he placed his first chest. This claim he made himself with a golden shovel, in fact I helped him do it.
Any ideas as to what caused this?
Thanks. ;)