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 Jun 13, 2013GP has an entry in the config for using pearls. Can a plugin like pearlfix be skipped then?
-
View User Profile
-
Send Message
Posted Jun 13, 2013I've been testing the plugin and making changes to allow for better modded server support. Changes I've made so far, which should appear in the next development build:
-the plugin will now look for a config folder, which is created by most mods. It will find these folders and open all the configs, looking for their "block{" sections, and then will parse each entry to try to find entries that match a given pattern. (Words such as Chest, Chests, Furnace, Grinder, Machine, etc) and then add those to the container list. Currently appears to provide complete Out of the Box Support for most mods. The Regular Expression used for the test can be changed.
-Confirmed the problem with the Quarry. It doesn't fire any events on MCPC. One possible workaround would be to create a new configuration section that allows the server owner to define that certain blocks cannot be be placed a given distance from other players claims. This should solve that issue with quarries, since a player would not be able to place the quarry close enough to another players claim to cut into it with the appropriate configuration.
Otherwise, without configuration, GriefPrevention correctly blocked me from opening the chests from IronChests, ThaumCraft's Hungry chest, Thermal Expansion machines (Aqueous Accumulator, Igneous Extruder, etc). Without me having to change any of the GP configuration. Another powerful capability this adds is that you should be able to block most things by their name, rather than ID. (The name will need to be what the respective mod uses in their configuration file).
-
View User Profile
-
Send Message
Posted Jun 13, 2013@deleted_9935739
Not possible. in release. in the dev build you can change a number of options for Creature Damage, but they will apply through all claims. You could in that case change it to require Build Trust to damage animals. This would apply to all claims, however. Also the dev build usually has a lot of console spam messages used for debugging.
Deleting an admin claim requires the adminclaims permission.
-
View User Profile
-
Send Message
Posted Jun 13, 20132 questions. In an admin claim with public access trust, how can I prevent people from killing any mob/animal inside it, regardless of the owner. Or is that not a feature? If I give a group the ability to delete and ignore claims, can they do that to admin claims?
-
View User Profile
-
Send Message
Posted Jun 13, 2013does not work
ExtendIntoGroundDistance: 8
privat from bottom to top, from 0 to 255 block
-
View User Profile
-
Send Message
Posted Jun 12, 2013@Aleroh "if there is a need for supporting info let me know".
You mean things like the version of Bukkit, the version of the plugin, the version and whether you are using third party modded servers such as MCPC or Spigot, defining what the difference between "horrid" and "normal" scheduler violations are, and the context of the profiler you ran including other plugins? Yes. That could be rather useful. In fact, that's necessary before I would even consider any sort of investigation into anything.
-
View User Profile
-
Send Message
Posted Jun 12, 2013Horrid scheduler violations while running this. Stinks cause I truly enjoy the benefit of this plugin. over a course of 12 hours with 1 player (myself) on a test server I get 90% violations of the scheduler. If there is a need for supporting info let me know.
-
View User Profile
-
Send Message
Posted Jun 12, 2013@xbenas
You can already do this with the GP flags plugin.
-
View User Profile
-
Send Message
Posted Jun 12, 2013Add the ability to disable mob spawning in admin claims.
This would make WorldGuard useless fro me :D
-
View User Profile
-
Send Message
Posted Jun 12, 2013@BC_Programming
See my private message, i could help you with your problem.
-
View User Profile
-
Send Message
Posted Jun 12, 2013Update: Wasn't able to figure out how to get Forge mods installed into MCPC, so gave up on that. I did however get a working BukkitForge server, and let's just say it has earned it's rather negative reputation. Some issues I have so far noticed:
1. The golden Shovel is practically useless. GP cancels the "claim" mode when you switch away from the gold shovel, at which point, your first claim point, if you set one, is removed. BukkitForge never fires the itemheld Change event, so this never happens.
2. Blocks that are added by Mods pass very odd values to the events GriefPrevention uses. Many materials added by Forge mods are identified as "bedrock" and their location is always passed as 0-0. With mods such as the Aether, Tekkit, RedPower, etc. this is probably the cause of some people's issues with BukkitForge if they do indeed use it. This issue is not fixable from GP's side, since it's literally bukkitforge passing in completely wrong parameters to events.
3. Containers act very strange. This is probably related to yet more inaccurate information being passed in #2. In my test I was not able to open a normal chest within my own claim, and I received no message stating why from GP, so I have no idea what is wrong. I was, however, able to both place it and a Skyroot Chest (from Aether II) which I was able to access with no problem.
Fundamentally, it seems BukkitForge simply is not a solution for using Bukkit plugins in combination with Forge mods. MCPC seems more promising, though I'm having issues setting that up beyond a vanilla install (eg. with Forge mods).
-
View User Profile
-
Send Message
Posted Jun 12, 2013@fungreenfox
Notepad plus plus, however, is not Notepad. It's Notepad :P
I use EditPad Pro, For whatever that is worth.
Either way I'll probably make them save to .yml files, just so nobody else complains about syntax highlighting issues, as well as for the sake of consistency. (also, better to make this change in a dev build then, say, after it's been made into a beta).
In the interest of disclosing what I'm currently working on with GP: I'm trying to setup a BukkitForge or MCPC server with a few mods (Aether II Biomes o' Plenty and a few others) in the interest of trying to add configurable workaround features for the limitations presented by their API implementations, as well as hopefully making some things a bit more configurable. (one of my aims is to allow for a way to configure it so, say, any item with the word "Chest" in it's name is instantly considered a container for interaction purposes). This is brought on from Tux2 setting up an Aether II server and putting GP 7.7 on it, where there were quite a few issues as a result of strangeness implementing the Bukkit API. It won't be a supported configuration because it's not something that get's regularly tested during development, but I wanted to make an effort to take an active role in exploring what otherwise simple features can be added to make the plugin truly shine and stand above it's competition particularly on modded servers, where from what I hear GP is typically the most compatible.
-
View User Profile
-
Send Message
Posted Jun 12, 2013@BC_Programming
-
View User Profile
-
Send Message
Posted Jun 12, 2013@Sargewood
Notepad doesn't have syntax highlighting anyway.
-
View User Profile
-
Send Message
Posted Jun 11, 2013@BC_Programming
Thank you for your quick response. I will now review those config files. I must have overlooked this when I first looked at them. The .cfg opens as a default text file in Notepad and not as a .yml color coded format.
-
View User Profile
-
Send Message
Posted Jun 11, 2013@Sargewood The Documentation is for the Release version. (Apr 05, GP 7.7). And you are using a Dev build.
Or, that's what my psychic debugging powers tell me, since the current default config.yml in the dev build has two values in the claims section. You have two choices. You can either revert to 7.7 and use the documentation, or you can discover that the dev builds move almost all configuration options to their own world-specific files, within which you will find an appropriate option.
-
View User Profile
-
Send Message
Posted Jun 11, 2013I am trying to limit which worlds claims may be made in. I used the following reference: "Use the claims.worlds configuration variable to list which worlds players may create claims in." So, I place "Worlds:" one line below "Claims:", spaced inline with the two variables already there, and I place the world names each on a line additionally spaced out and with a "-" before their names. But when I start the server, the config file resets to default.
-
View User Profile
-
Send Message
Posted Jun 11, 2013@GodsDead
http://dev.bukkit.org/bukkit-mods/gp-region-market/
Will probably have what you are looking for, and if it doesn't, whatever you are looking for probably fits more within that add-on plugin than GP itself. :)
-
View User Profile
-
Send Message
Posted Jun 11, 2013Hello GriefPrevetion team!
Im not a fan of economy systems at all, But trading on the other hand improves gameplay, I wondered if you could suggest a method to implement a trade trade system for claim blocks or trading items for a pre claimed area, that Real Estate plugin would be great if it worked with an exiting trade system.
Thanks.
-
View User Profile
-
Send Message
Posted Jun 10, 2013@CoolGamrSms
1. A flag that disables the automatic item transfer in siege mode, because this interferes >> with some other plugins and it also doesn't seem to take the armor slots into account.
Added that today (Build #80) :)
Lots of players are using siege mode to grief the nature around bases instead of
breaking and entering. Would it be possible to restore the damaged blocks after the
siege has ended, when the player gets ejected from the claim?
I added that a few builds ago. I haven't been able to test it, so it's a shot in the dark whether it will actually work or not, or how well.
Also recently added:
More options using the expanded formats. "EnderPearlsRequireAccessTrust" has been changed to two separate option sets, one for the ender pearl target, and one for the source. This makes it possible to require access trust in a claim to enter it, but build trust to leave using an EnderPearl teleport.
I also changed that bit of logic to not use up the EnderPearl from such a denied teleport.
Options were changed to have that same set of options for Levers, Stone and Wooden Buttons, Wooden Doors, and TrapDoors. and Wooden Buttons hit with an arrow. There are values for the pressure plates now but they are not currently considered.
I'm finalizing some special API classes for use in Plugins; my EnderHoppers For GriefPrevention plugin will likely serve as a testbed. I also am considering some additional events to allow plugins to hook directly into the various permission checks themselves and override them.