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 24, 2013@zlepper
I was kinda thinking it could be useful for Vanilla too; eg. only allow redstone and stuff inside a claim and stuff like that. Unlike say the feature that inspects Forge mod config files for IDs, this one is more mod agnostic. It doesn't seem like TekkitCustomizer has any hooks, at least nothing that seems applicable here.
Thanks :P The way I understand it though, the issues with MCPC and things like buildcraft quarry's, Thaumcraft wands, turtles, etc. is mostly something that can only really be addressed by patching either MCPC itself or the mods in question, since ideal support for MCPC requires support on the mod side in certain ways. I'm not even sure if it's possible to add that support with an add-on forge mod. (Even if it is though I doubt I'd ever be involved in such a thing)
-
View User Profile
-
Send Message
Posted Jun 24, 2013Many things prompt an excessively spammy "could not pass event" error, for example:
The first time a player logs in, this occurs:
-
View User Profile
-
Send Message
Posted Jun 24, 2013@BC_Programming
I completely understand what you are trying to do, and i really hope you can make it, was just implying one of his earlier alternatives he made.
Also, have you tried it(tekkitCustomizer), i recall it having some hooks you might be able to use, though i would think you might want GriefPrevention being independant from other mods.
You might also want to make this feature a seperate plugin which uses the hooks from griefprevention, this way you can avoid having it in the vanilla plugin, and you have a chance of including forgespecific coding, which i think will be able to help a bit in the case, though with your coding abilities you might be able to find ways not even Ryan could.
BTW: items = held items and placeable blocks in my head ;)
-
View User Profile
-
Send Message
Posted Jun 24, 2013@zlepper
The new 'feature' will deal with block placement rules, not items, and is more for restricting where and how they are placed, ideally for the purpose of making the item available, but not everywhere. For example, Machines could be restricted to only be placed inside claims. The idea is to allow restriction rather than requiring some blocks to be banned entirely.
-
View User Profile
-
Send Message
Posted Jun 24, 2013is there a way to give moderators ability to bypass player claim but not be able to acess admin claims?
-
View User Profile
-
Send Message
Posted Jun 24, 2013@BC_Programming
Ryan actually made TekkitCustomizer for cases like these, so you could either restrict or completely ban mod items using their ID-value.
I do realize this is not the same as what you are trying to create, but it's quite a lifesaver.
@The_Epic_Yak
http://forums.technicpack.net/threads/patch-for-ee-mining-tools-no-more-griefing-with-them.6642/
That will take care of the EE tools, however you might still want to read this: http://dev.bukkit.org/bukkit-plugins/grief-prevention/#w-notes-for-tekkit-servers
-
View User Profile
-
Send Message
Posted Jun 23, 2013@sh474
No problem. I've been reorganizing configs a lot, usually the best way to get a template for a given build version is to generate a default config as normal and them copy it to _template.cfg (This will probably change to _template.yml) you can change the template file using GriefPrevention.WorldConfig.TemplateFile of the core config, however be sure to refer to start the filename with an underscore, otherwise it will be regarded as a world configuration (for example if you set world.yml of a server as the template, when the world config loads it will be overridden with the defaults). Since the config arrangement is in a state of flux, a template file will usually be made obsolete with a new build, too.
Some of the default cfgs you noticed were actually the result of bugs in the defaults. eg. the Villager trades were supposed to be just inside claims but the logic that retrieved the appropriate internal perm structures for inside claims was only retrieving it for Above Sea level.
Right now I'm trying to fix multiworld support which I somehow broke. I've only observed the issue with the Biomes O'Plenty "Promised Land" losing it's claims but I'd like to fix that before pushing a new build.
On a side note of a feature I'm trying to add- explicit block placement control, which includes support for controlling where specific blocks and block IDs can be placed as well as saying that those specific blocks can not be placed closer than a given minimum to claims for which the 'placer' doesn't have certain permissions. They won't be present by default but will be loaded (and resaved) if found. Could be useful for addressing in particular Buildcraft quarries, but only partly. (not being able to place them within the default quarry size). Of course in that case a player could place landmarks all around the other players claim and create a larger quarry too, but at least it makes using a quarry for griefing a bit more troublesome. Could also be used for stuff like only allowing the creation of redstone mechanisms inside claims or something.
-
View User Profile
-
Send Message
Posted Jun 23, 2013I just want to say this plugin is amazing and super easy to configure. Great work and please don't drop support any time soon!!!
Better than WorldGuard IF you want one or more claims for each person on a server!
-
View User Profile
-
Send Message
Posted Jun 23, 2013I run a Tekkit classic server and I was having an issue. My spawn is griefable even though I have grief prevention installed....They're able to grief it by using tekkit classic items such as red matter tools..
-
View User Profile
-
Send Message
Posted Jun 23, 2013@smilydevil
Use /adminclaims to claim an area for the server. There is no block limit for admin claims. Or you could do /adjustbonusclaimblocks <player> 10000.
-
View User Profile
-
Send Message
Posted Jun 23, 2013hello i just download this plugin and I've just made a spawn which i want to claim its about 4000 blocks and all i have is 100 i went into the data and found players and i found the bit which says how many blocks i got but when ever i do it resets is the another way of getting me 10000 claim blocks quickly
-
View User Profile
-
Send Message
Posted Jun 23, 2013@BC_Programming
Yeah sorry. It was late and a lot of what I said was uncalled for. I actually really love the plugin and even made a donation when Mystcraft support was added. It was meant to be a bug report. If there is a better place to post those let me know (Doh! Just found the Tickets tab... now I feel like an idiot). If a template does not exist and a world for does not exist then a default config is generated for the world. My frustration was with this default. When deleting everything but the template and then reloading I still got the default config rather than what I defined in the template. I reverted to build #89 and it works fine again. Also, after editing world.yml while the server was running, doing /gpreload would revert my changes.
When I said that it didn't make any sense I couldn't figure out what it was doing not that it was senseless. Thanks for explaining it to me.
-
View User Profile
-
Send Message
Posted Jun 23, 2013@BC_Programming
Thanks for clearing that up. If only bukkit and forge played nice. Great work anyways
-
View User Profile
-
Send Message
Posted Jun 23, 2013@sh474
Wow, if I didn't know any better, I'd think it was a development build. In order to load the template the template file has to exist AND the world in question cannot have a config file. No defaults are loaded from the template file if the template file doesn't exist or if a world configuration exists for that world. I already moved some of the configuration, moving those sets of rules to a more appropriate "Rules" section. Though I did it because I didn't like how the existing setup separated the groups of rules from each other.
If you want docs for these configurations, do not use a development build, as they don't have documentation by definition. I've been writing some documentation for the config setup more thoroughly and making adjustments where they seem applicable. ClaimControl only controls the trust required if it is 'allowed'. In your example It denies explosions above and below sea level. TNT Explosions have no attached player so ClaimControl is not used for that particular rule. In the cases where it does apply (which will be the docs, we don't want to put up pages yet on account of people likely and understandably thinking it applies to the current release)
Thank for telling me how little sense and how crappy the results of my hours of contributory efforts were though. Makes it all worthwhile. Oddly, that's only partly sarcastic.
-
View User Profile
-
Send Message
Posted Jun 22, 2013Build #90 broke world configs. The template file isn't read and so new worlds default to the really crappy default configs that don't let players trade with villagers within their own claims. It also doesn't let them use water buckets within their own claims either. Another config issue is that if I modify world.yml them /gprelaod, those changes are reverted back to the crappy defaults. Also, is there any were I can go for documentation on the dev build configs? Some of it just doesn't make any sense. Why are VillagerTrading and EncironmentalVehicleDamage under the Claims heading?
This seems to mean that TNT works like normal outside of claims but doesn't inside of claims. ClaimControl seems to define what level of trust you need within a claim for it to work. In this case I read this as you don't need any trust to set off TNT in someone else's claim. Doesn't make much sense to me.
This one makes the least sense to me. You are not allowed to trade with villagers underground? Why? And, you need /TrustAccess to trade with villagers within a claim. That is fine with me but the only way I've gotten trading to work at all for anyone, in or out of claims is to set all to Allow. If someone could explain what these configs actually mean or at least point me in the right direction that would be great.
-
View User Profile
-
Send Message
Posted Jun 22, 2013@FoxKitsune
http://www.minecraftwiki.net/wiki/Shovel
-
View User Profile
-
Send Message
Posted Jun 22, 2013@BC_Programming
what resources do i use to craft it?
-
View User Profile
-
Send Message
Posted Jun 22, 2013@BC_Programming
Can I show you the problem on the Server? Do you have time to connect? :D
Server adress: cwlclan.hu
-
View User Profile
-
Send Message
Posted Jun 22, 2013@FoxKitsune
You craft it.
-
View User Profile
-
Send Message
Posted Jun 22, 2013ummm, so i was wondering how i as a player on a server obtain a golden shovel to start editing the size of my land claim. i've already placed my first chest for my initial claim and i've looked everywhere and watched all the tutorial videos on this plugin but i haven't found anything. Do i need to contact the server admin(s) to obtain a golden shovel or do something special?