fixed /worldguard reload sometimes removing custom flags
set logging level for world saving to finest
it won't spam your console anymore
added setting to determinate when the flags should be saved
name: flag-saving
values: save (save on world saving), unload (save on world unloading) and change (save on flag change)
added getFlagValue function for developers to get a flag value at a location
checks parents and priorities
Version 1.4.3
fixed NullPointerException
Version 1.4.2
fixed for CB 1.4.4-R0.1
Version 1.4.1
recompiled for Java 6
fixed plugin sometimes not using logger
Version 1.4
added utility class to check CustomSetFlags at locations
Version 1.3.1
fixed flag values not saving
Version 1.3
added reconnect function if sql server closed connection
full release
Version 1.2.5
another important bugfix for database users
added CustomLocationFlag and CustomVectorFlag
Version 1.2.4
important bugfix for database users
Version 1.2.3
added CustomSetFlag class => use this to prevent the WorldGuard error message when working with set flags
Version 1.2.2
reworked the way flags are saved -> you need less files and tables; the get method of WorldGuard should work correctly now
Version 1.2.1
added support for custom flags
Version 1.2
the region group property is now saved too -> you need to update your database
added VectorFlag support
added LocationFlag support
added SetFlag support
Version 1.1
fixed StateFlag not working
fixed unused flags did not get deleted in database
fixed most flags not saved in database
Version 1.0
initial release
You get errors from WorldGuard when you set flags, but this does not affect the behaviour of the server. (only if you do not use my Custom flag classes)
this is an error of WorldGuard that will probably fixed in a future update
the /region command of WorldGuard sometimes produces errors.
