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.
Please add flags flying and creative in the region
@Roenie82
You can't possibly be having the same issue as crunkazcanbe prior to 1.6 because that event wasn't monitored until 1.6, The SiegeStartEvent didn't exist until GP 7.8. Are you sure you downgraded, you weren't putting the file in the wrong place?
1.5.3 works just fine with GP 7.7.
FYI, I had the same issue as crunkazcanbe when I updated gpflags from version 1.2 to 1.5.2, running bukkit version 1.5.2 and GP 7.7.
I downgraded gpflags trying every version on Curse one by one down to 1.3 which was the first (newest) that worked. Every version above 1.3 failed with that same error: SiegeStartEvent does not exist.
Looks like GP 7.7 only works with gpflags 1.3 or older, which I did not expect.
@crunkazcanbe
Because GPFlags 1.6.0 is not compatible with GriefPrevention 7.7
Why do i get this in the console
[18:55:44] [SEVERE] [GriefPreventionFlags] Plugin GriefPreventionFlags v1.6.0 has failed to register events for class src.john01dav.GriefPreventionFlags.listeners.GPListener because me/ryanhamshire/GriefPrevention/events/SiegeStartEvent does not exist.
I would like to bring everyone's attention to a new project I am working on that will be the successor to GriefPreventionFlags. If you haven't found it already, the plugin is called Flags and has now been moved into Beta testing.
To the end users, Flags operates much the same as GriefPreventionFlags, with only slight tweaks to the command structure. However, internally it is much different plugin. This new re-write allows for more than just Grief Prevention, you can use it with Residence and WorldGuard as well, and can support many more in the future.
If you still prefer Grief Prevention (and why wouldn't you, it is the best) there are some new abilities that Flags can do that the GriefPreventionFlags architecture simply will not allow. I've tried to answer any questions and concerns about this new plugin and how it will affect GriefPreventionFlags in the Flags FAQ so be sure to check it out!
@RagingPG13 The InvalidFlagError was added in 1.5.0. It sounds like somehow it got removed. Try editing data.yml and setting the version 1.4.0. That should force it to rebuild that data file. Don't worry, it won't mess with the flag data unless it's already in the wrong format.
EDIT: Oh! If your using the release build, set it to 1.4 NOT 1.4.0. I didn't change the handling of that till 1.6 and it insists on a real number... which obviously doesn't have 2 decimals.
I just now updated this plugin on my server and now whenever i try to set a flag it says "ERROR: Invalid Messages.yml for InvalidFlagError". So i don't know what to do now i tried uninstalling and reinstalling the plugin. I don't think this is a known bug since this version came out 20 hours ago.
@bullhone
All the values are boolean (true or false).
In most cases you can omit the value in order to behave like a toggle switch. The setflagcluster command is the exception to that because it wouldn't know which flag to toggle. The notation of the documentation on the Commands page is [brackets] mean optional while <angle brackets> mean required.
when it ask for the value when setting flags can anyone tell me what the values are so I know what to use ...
Alright everyone, after much confusion and delayed approval Beta 2 is now available. This should fix some of the complaints with monsters spawning where they shouldn't and branches out the damage flag.
If you are running Beta 1, be sure to edit data.yml and change the database version from 1.6.0 to something earlier, like "1.5.0" doesn't matter what, as long as it is lower. This will force a new update and it is only required for the beta versions.
@ManBeastPigDev
It's in plugins\GriefPreventionFlags\config.yml. For more information, click the "Configuration & Permissions" link above.
@Alshain01
I dont know how to disable an event listener but it sound cool. :)
@ManBeastPigDev
'Lag' is a subjective term. It depends on the server hardware, how many plugins your using, and of course which flags your monitoring. There is really no way to answer the question. All plugins have a certain degree of load that will be added to your server. If your server has difficulty running it, you can disable event listeners in the configuration file for flags your not using. The beta build expands this configuration further, but the most intensive is the player move event, especially with that many players. The flags in the list above are now separated by their configurable event, for right now the first list can not be disabled. Some of those are only able to be disabled in the beta.
Will it cause lag on a server with 100+ users?
@Dennisburnsjr
You can try older plugin versions, the version 1.3 should work with 1.4.7, but I'm not sure about newer ones.
The problem is everyone wants something different. Tekkit wants 1.3 to work, Minecrack wants 1.4.7 to work, CraftBukkit wants 1.6 to work. Supporting them all is a testing nightmare and I'm sorry to say I'm just not going to do it, at least not anytime in the foreseeable future.
Hello :) I was curious if you have one for MC 1.4.7? I have a Mindcrack server and use Griefprevention.
@hkirste
Sorry I missed your ticket somehow, but yes I am checking them regularly.
Is anyone checking tickets?
@GodsDead
"I set the flag to turn PVP off in areas, does not work at all." - That really tells me nothing. I can't troubleshoot "it doesn't work".
"Does this not work with admin claimed plots?" - Yes it does. It doesn't work with ops though, they have a bypass on all player flags. Then there is the bypass permission, then there is the grief prevention combat timer, and then there is siege mode.
"only some commands work, really really buggy." - Its really really not. Again, I can't troubleshoot this, I need to know what isn't working and what happens when it doesn't work.