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 Jan 14, 2014@BC_Programming
Hmm,
ill look at rules and do some tweaking:) But shouldn't it be doors, fence and such locked by default? To me its logical to be, but... its only me.
As for deleted claim, - no capitals. And we were together online 10ish hours before.
In past i deleted couple of times "GriefPreventionData" but it gets back every reboot. Ill try to delete it again if plugin is not using it anymore because its confusing me (obviously).
Many thnx for your help.
-
View User Profile
-
Send Message
Posted Jan 14, 2014@Desertive
I managed to sell admin subclaim with Real Estate now
This is not a good idea. subclaims are not supposed to have different owners than their parent claims- in fact it's not really possible since it doesn't save the subclaims owner and saves it as the owner of the top level claim associated with that owner.
Basically the subclaims are not 'really' separate claims, and are considered part of the data for their top level claim. Deleting and adding claims causes the entire top-level claim to be rewritten; this means wiping all data associated with the claim and inserting all data affiliated with that claim, and this is done using separate queries, which means each time you are causing around 500 SQL queries ( 232 delete from's, and 232 Insert Into's). Because it removes all subclaims and rewrites them. Additionally, the subclaims are not indexed by chunk like top-level claims, so it's a case of finding the top level claim by inspecting the chunkmap lookup, grabbing that top level claim, and searching sequentially through all child claims and seeing if the chosen location is in that area. More subclaims=more to search through and more comparisons.
In Grief Prevention version 1.6
The earliest version that was made public was version 4, I think?
@ha11oga11o
Can you please, when you have time, explain what rules are you talking about?
7.8 Configuration page
I took those settings from GP config.yml i did not make it up. They exist.
I never said you made them up. I said they don't exist. They stopped existing beyond 7.7. Sounds like you are looking in GriefPreventionData. That is no longer used.
It should NOT remove claims from one of mine admins.
it shouldn't be removing it because they were online, not because they are an admin. Administrators get no special treatment by GriefPrevention. Does their player name contain capital letters? #235 should fix that if so.
-
View User Profile
-
Send Message
Posted Jan 14, 2014Hello again! I want to continue my reports according to my last post:
@Desertive
So the subclaim problem isn't really now that bad. Somehow the subclaims keep their place, but it's just the GriefPrevention handling them. I managed to sell admin subclaim with Real Estate now, so the priority for that isn't that high right now.
But I wanted to talk to you about that another problem which I mentioned: lag. We really just cannot use Grief Prevention now because Spawn protection lag. I have done one admin claim (dimensions: 953x895 blocks) and that admin claim owns 232 subclaims. When I try to create, modify or delete a subclaim in that admin claim, the whole server freezes to something like 10 seconds. Even when I just try to give a trust to one subclaim to another player, it just freezes the whole server. Sometimes me and my friend gets kicked out because of that. We use GriefPrevention #244 (MySQL-database used and it's localhost) and Spigot #1240.
I have tested that when I do a new admin claim, it won't cause lag. And when I do a few subclaims it isn't a problem either. So it's just that when you have hundreds of subclaims, it causes too much lag.
There is definitely no performance problems in our server (32 GB RAM and i7-4770). In Grief Prevention version 1.6 there were no performance problems when we had that much subclaims (plus thousands of player claims too).
So that is really what I need to get fixed. Here is even my claimdata table if it's any help. If you need any extra information, tell me. Thank you.
-
View User Profile
-
Send Message
Posted Jan 14, 2014@alexboyg2012
Getting the world.yml from the WorldConfigs folder is what's needed so we can see what the problem is. And don't put that whole thing in a comment, use pastebin :P
-
View User Profile
-
Send Message
Posted Jan 14, 2014@BC_Programming
Hello,
As for "Those settings don't exist. Fencegates, trapdoors, and doors are handled by Rules."
Can you please, when you have time, explain what rules are you talking about? I took those settings from GP config.yml i did not make it up. They exist.
Also, as for dev build #243 many players are complaining that they have negative block amount value. Its not that bad, mine server is kinda small and i can /acb it back, but could be info to take look at it.
An i have some problems about loading player data as stated here:
http://pastebin.com/YXXZ9vdS
Example:
[GriefPrevention] Removed alvar_m's unused claim @ Jugoslavia_nether(-302,74,118)
We were together online last night. It should NOT remove claims from one of mine admins.
Many thnx for great work. I hope you will polish it soon.
-
View User Profile
-
Send Message
Posted Jan 14, 2014Anyone familiar with getting Applied Energistics 1.6.4 machines protected? I was able to in 1.4.7 and 1.5.2 but in 1.6.4 I can't get them to get locked up no matter what I do, starting to get frustrated.
-
View User Profile
-
Send Message
Posted Jan 13, 2014Hi,Im unable to claim I am using a Golden Shovel buts its not working.Ive tried to uninstall then reinstall the plugin but it does nothing. Also the plugin is banning players before they have even joined. I have my config file below:
GriefPrevention: Groups: Names: [] DataStore: flat DebugLevel: None Claims: MaxAccruedBlocks: 5000 AutoSubClaimsSwitch: false DeleteWithUnrecognizedOwner: false InitialBlocks: 100 Mods: Containers: IncludeRE: \schest\s|\schests\s|\sfurnace\s|\sgrinder\s|\sextruder\s|\smachine\s|\sengine\s|\sturtle\s|\saccumulator\s|\sprecipitator\s|\sAssembler\s|\sinfuser\s|\smachine\s|\sreceptacle\s|\s.*chest\s|\sTank\s|\sCrucible\s|smelter\s|\sworkbench\s|\stable\s|sAutoCrafters|sChargers|sIceGens|sSawmills|sTransposers|sWaterGenss.*Shelfs|s.*Cases|s.*Racks|s.*Labels|s.*Desks|s.*Stands ExcludeRE: '' Access: IncludeRE: \sbutton\s|\sswitch\s|\sDoor\s|\sTrapdoor\s ExcludeRE: '' Trash: IncludeRE: \sOre\z|\sdirt\s ExcludeRE: '' PerformConfigSearch: false Economy: ClaimBlocksPurchaseCost: 25.0 ClaimBlocksSellValue: 15.0 EnableMoveWatcher: false Siege: CooldownTime: 3600000 WorldConfig: SingleWorld: <None> TemplateFile: plugins/GriefPrevention/WorldConfigs/_template.cfg
-
View User Profile
-
Send Message
Posted Jan 13, 2014@TJW28
This is a result of additions to Player Data. In particular, the added flag to indicate, per player, whether their inventory should be cleared the next time they join. (This is used by some of the siege and PVP handling to combat PVP Logging).
Anyway, the message is most likely misleading. The Player Data is loaded successfully, but an error occurs when it tries to read the last line (since with previous data, that line will not exist).
The PlayerData should be loaded (except for that value, which will default to false) and it should be saved when the server shuts down and no more messages should be displayed.
@seriosbrad
You should be able to specify /trust [some.player.permission] to give trust to any player with the permission you specify in square brackets. You can also define groups on Config.yml and specify them using /trust G:groupname.
@kr8tors
That's how I've always done it.
-
View User Profile
-
Send Message
Posted Jan 13, 2014Since updating to build 243, my console is showing Loads of messages similar to below
5:10:18] [Server thread/INFO]: [GriefPrevention] Unable to load data for player "selov": null [15:10:19] [Server thread/INFO]: [GriefPrevention] Unable to load data for player "selov": null [15:10:19] [Server thread/INFO]: [GriefPrevention] Unable to load data for player "selov": null [15:10:19] [Server thread/INFO]: [GriefPrevention] Unable to load data for player "selov": null
The player "names" are different, and im unsure if there is any adverse affects taking place that I should be aware of. This is the first time I have seen these type of messages
-
View User Profile
-
Send Message
Posted Jan 13, 2014Is it possible to allow the trust commands for usergroups rather than specific players in Admin Claims?
-
View User Profile
-
Send Message
Posted Jan 12, 2014How would i give claim blocks to another player , would i use /acb {player} [amount] ?
-
View User Profile
-
Send Message
Posted Jan 12, 2014@BC_Programming
Perfect, thanks.
-
View User Profile
-
Send Message
Posted Jan 12, 2014@Stryker76
https://github.com/Tux2/GriefPrevention/tree/381bebf44fad1286e0fd56262c0c45a83e834a3c
-
View User Profile
-
Send Message
Posted Jan 12, 2014just now I started getting an error when buying and selling claim blocks, "Sorry, buying and selling claim blocks is disabled."
-
View User Profile
-
Send Message
Posted Jan 12, 2014Just so you know, you can get hurt and hurt others inside the claim if you use fishing rod.
-
View User Profile
-
Send Message
Posted Jan 12, 2014@stgram
@BC_Programming
The Event error I mentioned earlier happened again, with a bit longer stacktrace. http://pastebin.com/LABbeE71 #1237 Spigot #240 GP
-
View User Profile
-
Send Message
Posted Jan 12, 2014http://pastebin.com/bKVVExRD Now that is an interesting error. It is not possible for a player named demontuuls' to have logged in due to forbidden char, but somehow your plugin thinks it existed. Could that be a simple /trust error, database data handling error, or a reason to be concerned for an exploit?
-
View User Profile
-
Send Message
Posted Jan 11, 2014Is it possible to get the source as it was released for 7.7 on bukkit?
The source @ https://github.com/ryanhamshire/GriefPrevention seems to be 7.6.2 and the source @ https://github.com/Tux2/GriefPrevention seems to be the latest.
Neither have branches or tags, so I'm not able to get what was actually released for 7.7, which I'm still running.
Thanks
-
View User Profile
-
Send Message
Posted Jan 11, 2014@ha11oga11o
i did what you told me for /ignore command and i have this when reload plugin: http://pastebin.com/t1ejSK4Y But, i still have samme issue as i posted at picture below.
It is probably not GriefPrevention then, since disabling that prevents it from even registering the command handler for that command.
also i have LockWoodenDoors: true LockTrapDoors: true LockFenceGates: true But doors are not locked for untrusted player.
Those settings don't exist. Fencegates, trapdoors, and doors are handled by Rules.
@stgram
Looks like the useful part of the trace is cut off the end. (need the part that points at where in GP the exception occurs)
-
View User Profile
-
Send Message
Posted Jan 11, 2014@BC_Programming
Having the following error appear multiple times in a row, but rarely: http://pastebin.com/5dAq2Sdh