DB/Creature: Fix more triggers visibility
Why not figure out why these changes needed to be made instead of just modifying WDB data? If it was a bad parse, if there is something else that needs to be done to the core, etc....etc...
If you are going to just modify WDB data, then why aren't you setting the WDBVerified field to negative to show that this is n longer official data?
It's not modify WDB data instead CORRECT WDB data from sniffs.
So it was a bad parse from WDB .... that is all I asked. I know we had several issues back when the WDB parser was first written.... Thanks.
WPP swapped those in the SQL output somehow, i totally forgot about this issue. Thanks Aok.