Change behavior to check TargetedDatabase.
Since classic we had problems to clearly define which fields are used in which DB.
Intead of ranges (which was okay as long blizzard only moved forward) we now set flags for the supported database version.
Tho it's still a lot of manual work for classic, because we have to add the AnyClassic/Classic/WotlkClassic flag to any field which has retail flags set (if they are valid for Classic too).
I also added CreatureTemplate parsing for 3.4.0 as example and to test
Change behavior to check TargetedDatabase. Since classic we had problems to clearly define which fields are used in which DB.
Intead of ranges (which was okay as long blizzard only moved forward) we now set flags for the supported database version. Tho it's still a lot of manual work for classic, because we have to add the AnyClassic/Classic/WotlkClassic flag to any field which has retail flags set (if they are valid for Classic too).
I also added CreatureTemplate parsing for 3.4.0 as example and to test