I am not sure exactly if this is the source of the problem, but when i tried registering my handlers using ExitFlag.FACTORY as "after" like how the javadocs said it, it seemed that my handler was running before the ExitFlag handler which means mine will run even if ExitFlag returns false. I used null as after and it worked then. Maybe i understand the "after" incorrectly but in my mind my customHandler should run after the "after" not the other way around if that makes sense. Let me know if I didn't undertstand it correctly.
Sorry for my english!
* Add Timings for third-party session handlers.
These often cause WorldGuard to get blamed by timings.
* Add config option to turn off extra timings.
* Move relocation to the right build file.
* Move config to a map for potential future expansion.
* Calculate timing immediately per-factory.
Instead of on each handler creation.
* Fix material loading from config requiring minecraft: namespace.
* Fix disallowed-lightning blocks. Lightning entities are weird.
* Fix /wg reload overwriting config changes.
* General around thread usage/naming/shutdown. If anyone was actually
making their own managers/indices you deserve to break.
* Start work on abstracting commands out of worldedit-legacy
* A lot more work towards abstract commands
* Move a lot of code to WorldEdit
* Setup the exception converter
* Use WorldEdit styling and move more of the RegionContainer across.
* Abstract away the debug commands and a few other things - Only the matcher to go.
* It compiles
* It now seems to run fine
* Fixed version typo
Joo200
LoaiDev
wizjany
TheMolkaPL
Matthew Miller