GriefPreventionFlags
Have you ever wanted to have flags in the plugin Grief Prevention? Did you ever wanted to stop those horrible monsters from infesting your spawn house without running 2 anti-grief plugins? Well now there is a solution... GriefPreventionFlags!
GriefPreventionFlags is the most comprehensive flag plugin for Bukkit! It extends Grief Prevention to allow you to customize the behavior of the game in each claim by setting flags.
Announcement
GriefPreventionFlags has now been succeeded by Flags. Due to changes being implemented by Mojang regarding UUID, keeping GPFlags working would require an excessive amount of time and effort when Flags duplicates its functionality. For this reason I am officially discontinuing work on this plugin. It is strongly reccomended that users update to Flags. Thank you for your support. - Alshain01
Features
- Over 70 Flags
- Designed for Grief Prevention
- Simple Localization
- Trust Lists
- Customizable Flag Clusters
- Custom New Claim Defaults
- Unclaimed Area Flags
- Multi-world support
- Vault Support by Extension
- Fast, easy to edit YAML data storage
Usage
To set flags for a claim, simply stand inside the claim that you would like to set a flag for and issue the command /setflag <flag> [value]. Setting a global flag allows you to choose the default behavior for all claims in the world that have not had a value previously set, this does not alter behavior in unclaimed area. For a list of flags see below.
Other great plugins by john01dav
- AntiSwear - A language filter plugin.
- CastCraft - Adds spell casting to Minecraft!
- BetterReload - Enhanced server reloading.
Other great plugins by Alshain01
- Flags - Multi-system interface for 3rd party plugins to add their own flags.
- TradeShop - A shop plugin designed to sell items through unattended bartering.
- NoMoreZombies - A small plugin developed to disable zombies spawning more zombies.
- HardcoreClaims - Addon for Grief Prevention that deletes claims and restores the land when a player dies.
@Archcry Glad to be of service!
@n33dy1 I created a ticket with your request. Thanks for the suggestions!
@ManBeastPigDev Welcome Home!
OMG so many options now, this plugin has come along a lot. I'm coming home!
Can you make it so I can set it so players can't move trapdoors? I setup an idea with trapdoors set a certain way and don't want them to mess them up. However, in the same area I would like them to still use stone pressure plates.
@john01dav
I am very happy to see that the bugs I reported are fixed in this build. Thanks for the fast support on this issue :D
~ Archcry
In addition to john01dav's comments on 1.5. See the coming soon page for more information. We will reserve updating the main page until it is approved to avoid confusion.
New Features
Behavior Changes
Ok, everyone new update! 1.5! In this update we have a brand new public api making add on plugins possible! You can also create your own flags with flag clusters! All flags now have default values. You can localize the messages to your language (or whatever you want). Old flag date for deleted claims get removed (can take up to 30 seconds). Full change log below
- Bug fixes
- Remove creeper explosion flag
- Added Flag Clusters. Create your own flags!
- Bug fixes: If someone with only the gpflags.setflag permission created a claim then logged out (or the server reloaded) they would lose access to set flags in that claim.
- Updated to cb 1.5.2R1.0
- A few new flag types, mostly separated exiting ones further.
- Flags now have default values
- Code Improvements
- Localization - Flags and messages
- Flags are now enumerations
- Events for other plugins to hook into added
- Javadocs are added
- New Public Api
- Tightened control on methods/classes other pluigns have access to
- Added task to clean up the database by removing deleted claims every 30 seconds
- Added warning when a development build is being used
- Reorganized the code into packages
As soon as it is approved go get it!
I've added a new FAQ page. Please take the time to check there for answer before posting. Thanks!
@nefty2
PvP is the inverse of what people think. It effectively turns PvP OFF not ON. You have to configure server.properties to have PvP turned on and then you can turn it off using the flag inside your claims. Without the Server PVP on, I have no way of monitoring PvP action.
It won't let me PvP no matter what I do. Please help
@Garrash
Try using a newer version with mcpc+. It should work ok. however we will not provide support for it or fix any bugs that are only occurring in old versions of minecraft.
I'm not expecting you to work backwards (I know a lot of devs get mad when I bring up older versions) but is there any support at all on the 1.4.7 version for Tekkit Lite? Grief Prevention works on it but I can't seem to get flags to create a config folder.
I really like this addon, can't wait till 1.5 is released. These custom enter and exit claim messages is a very good VIP feature for my server :D Thank you for sharing your awesome work with us :)
~ Archcry
@MCLegendServer
Yes and no. Right now GriefPrevention does not identify one sub-claim from the other, though it does tell me the parent ID of the sub-claim. So the only way I could set a flag for a sub-claim would set them for all sub-claims in the parent and it's really not worth it to me to code that... because:
GriefPrevention's Beta & Alpha versions now support sub-claim ID's, but I don't develop for Beta and Alpha, so we all just have to wait.
Back to the multi-world, I may look into this for 1.6, but not 1.5. We've also had people request that we also allow flags for all unclaimed area, and we want to allow this but we have to be very careful because some events could bring your server to it's knees if we went all the way thorough our code everywhere in the world, right now we only progress to the bottom of the code tree if your in a claim. So long story short, multi-world support for global would be most likely to come when we add "world" flags, which would need to be multi-world as well. This requires massive testing and as such I don't want to over complicate the 1.5 build which has a pretty big list of new features already. Fortunately, GP claim ID's are unique across all server worlds, so claim flags are already multi-world by nature.
Okay I see. Thanks for answer :)
Is it possible to set flags just in some sub-claims? (or is this something you may add?)
@MCLegendServer
Our only criteria for global is that there is a claim at the location and there is not a value set for the flag at that claim. It doesn't differentiate between worlds.
Hello. I just wonder if the global flags are global for all worlds, or just one world? As I have a multiworld system, do I want to use different global flags for different worlds. Is this possible?
@Absolutionmc In general, the Coming Soon page represents items that we have already put in code, so unless there is some fatal flaw discovered in testing that causes us to remove it, you should see it in the next version. However, I'm sorry to say, we are still a little ways out from a 1.5 release (we just released 1.4 after all).
@Kaiser_Steve You can't right now. I could look into that though.
Actually, I just read that you can show the owner's name with {1} on the message. Is that only on 1.5 build? And if yes, when is it going to be out? :P
Thanks
Hey Alshain01 I have a pretty simple question.
Can I customize the NotifyEnter and NotifyLeave flags to say what i want? For example:
"You're now entering $PLAYER's protection"
How can I block the teleportation of Dragon eggs?