Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

DB/Creature: Fix more triggers visibility

Closes #8178
  • Loading branch information...
commit 0f82a5fa8b2e8f61e41a5a4a509a710fbf2dac4f 1 parent 18823bc
@Aokromes Aokromes authored
Showing with 2 additions and 0 deletions.
  1. +2 −0  sql/updates/world/2014_02_09_03_world_creature_template.sql
View
2  sql/updates/world/2014_02_09_03_world_creature_template.sql
@@ -0,0 +1,2 @@
+--
+UPDATE `creature_template` SET `modelid1`=169, `modelid2`=11686, `flags_extra` = `flags_extra` | 128 WHERE `entry` IN (40091, 43280, 43281, 43282);

4 comments on commit 0f82a5f

@runningnak3d

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?

@Aokromes
Owner

It's not modify WDB data instead CORRECT WDB data from sniffs.

@runningnak3d

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.

@Warpten
Collaborator

WPP swapped those in the SQL output somehow, i totally forgot about this issue. Thanks Aok.

Please sign in to comment.
Something went wrong with that request. Please try again.