WorldGuard Custom Flags

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

• [IMPORTANT] flags are not saved when using YAML files
• 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)