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.
It's approved! Go get it!
@piritacraft
A large number of flags are fixed in 1.4 which is uploaded however not approved yet (Should be by tomorrow). I would give you a link to download it early however bukkit doesn't like that and would probably just get mad and try to get the project deleted or something. If you somehow managed to get your hands on 1.4 then great job! and please create a ticket that way there are not like 50 bug reports going on in the comments.
the flag AllowEntry is not working :(
Ok everyone new update! 1.4 This update adds a whole bunch of new flags (type /flags in game for a list) along with a new yaml data storage system don't worry it will automatically convert your flag data to the new system, just update the plugin and then all data will be converted. Full change log below:
- Bug fixes
- Added Metrics
- Changes /flags command to look more like the /help command of essentials
- Added a bunch of new flags (type /flags in game for a list)
- Added gpflags.bypass permission node to bypass flags (only works for some)
- New yaml storage system - Subdivisions now inherit there parents flags.
- New file to yaml conversion system. To use it simply start the server with the old data in place and it will automatically be converted
- Memory usage improvements
@SonarBeserk
This is fixed in 1.4. This version is uploaded to bukkitdev right now it just needs to be approved.
the gpflags.flags.* perm needs to have gpflags.flags.pvp added to it. it doesnt give that permission at the moment.
@MCLegendServer
The first one is beyond any plugin dev's control. The way it works is Bukkit tells us when a player (actually any entity) is being damaged. It tells us nothing if no player is being damaged. If server PvP is turned off, it never tells us anything (about player entities) because no player is ever being damaged, so we have no way to react to a lack of damage.
Go ahead and submit a ticket with your request for unclaimed area flags. I can't promise anything, but that's the only way to guarantee it at least gets looked at.
Okay i see.
But if i set the server settings to PVP:false, can i then get pvp:true in some of the claims?
I need to have PVP denied where its not claimed/ none flags.. Are it any way this can be done? Or do i then need to use worldguard etc?
@MCLegendServer
Right now there is not global flags. With the old file system (in 1.3 and earlier), it would cause your server to be unplayable. With new file system, it might could be done, but right now there is no plan for it. This is after all and extension of Grief Prevention so it exceeds the scope
Greeting and Farewell messages are coming real soon. There is a "coming soon" section above that lists features for the upcoming build.
@roggbart
Sorry about that, use gpflags.flags.spawnmob and gpflags.flags.leafdecay
That one got ahead of us, in the future, the same code will generate both the flag name and the permission so they will always be the same. Dashes are going away, so spawnmob will be the new flag in 1.4. This will automatically convert upon first run of 1.4 in the database.
The Perm for mob-spawning seems not to work, while perm for PVP do work at the same time gpflags.flags.Mob-Spawning gpflags.flags.PVP
Staff can then only toggle PVP
Hi. Are there any global flags? Like flags for unclaimed area and where its none flags (like a default)? I want to disable PVP, in every area that not have the flag PVP:allow or not have been claimed yet. I want something like the worldguard "global" claim.
Also, can you plz greeting and farewell flags? (like worldguard)
This plugin looks amazing :)
@Garrash
Glad you got it working. You won't need to worry about it for much longer, once we get 1.4 out, the problem will be gone.
@nathanlevi
That's an interesting idea, but PvP is somewhat touchy because of the GriefPrevention siege functionality. It's difficult to insert our own control over it when GP is fighting against us. That's not saying it isn't possible but I would need to know more about what you are looking for.
Just an idea but what about adding into the gp flags plugin a way where being in your own region gives you certain benefits for the duration you stay in your area, that way you can still pvp but have an advantage in your territory.
@Alshain01
I think I must have been standing in a subclaim on accident or something because it started working when I retried it, I'll keep this in mind in the future, thank you!
@Xarniia
Ah I see what you mean. Actually they are the same thing, in terms of Bukkit, but they are differentiated by "spawn reasons". In Version 1.4 we have split the different spawn reasons into separate flags. This is coded and tested. The new "spawnmob" flag prevents only monster spawning by "natural" means, which basically means low lighting.
"Mob-Spawning" prevents all sources of mobspawn, but a flag that only prevents natural (hostile) monsters (eg. Creeper, Zombies,..) from spawning would be very nice.
@Xarniia
Either I don't understand what your asking for or that's already in the current release. Please clarify if I misunderstood.
A "monster-spawning" flag would be very nice, so we have safe homes with cows and so on! =)
@Garrash
Did you set the flag from within a subdivision? Or, are the mobs spawning within subdivisions? There is a known issue in 1.3 and earlier where subdivisons are not handled correctly that is fixed in 1.4.
I did /setflag mob-spawning, got confirmation it is set to false, did /butcher, around 30 mobs promptly respawned within the admin claim.