Core/GossipMenu: gossip_menu table shows incorrect data
osleyder85 opened this issue ยท 3 comments
osleyder85 commented
TrinityCore - WowPacketParser
Detected build: V9_2_5_44232
Detected locale: enUS
Targeted database: Shadowlands
In the output sql file, the gossip_menu table shows the wrong data.
In the TextID
column it shows the ID
of the broadcast_text
table, when here it should show the ID
of the npc_text
table
Data Show:
DELETE FROM `gossip_menu` WHERE (`MenuID`=21733 AND `TextID`=33157) OR (`MenuID`=14002 AND `TextID`=5715) OR (`MenuID`=14001 AND `TextID`=4793) OR (`MenuID`=14003 AND `TextID`=5006) OR (`MenuID`=14227 AND `TextID`=17176) OR (`MenuID`=13999 AND `TextID`=4985) OR (`MenuID`=14191 AND `TextID`=5001);
INSERT INTO `gossip_menu` (`MenuID`, `TextID`, `VerifiedBuild`) VALUES
(21733, 138726, 44232), -- 3287 (Hana'zua)
(14002, 8291, 44232), -- 3156 (Nartok)
(14001, 7476, 44232), -- 3155 (Rwag)
(14003, 7660, 44232), -- 3157 (Shikrik)
(14227, 47371, 44232), -- 39206 (Acrypha)
(13999, 7631, 44232), -- 3153 (Frang)
(14191, 7652, 44232); -- 39214 (Karranisha)
Correct data:
DELETE FROM `gossip_menu` WHERE (`MenuID`=21733 AND `TextID`=33157) OR (`MenuID`=14002 AND `TextID`=5715) OR (`MenuID`=14001 AND `TextID`=4793) OR (`MenuID`=14003 AND `TextID`=5006) OR (`MenuID`=14227 AND `TextID`=17176) OR (`MenuID`=13999 AND `TextID`=4985) OR (`MenuID`=14191 AND `TextID`=5001);
INSERT INTO `gossip_menu` (`MenuID`, `TextID`, `VerifiedBuild`) VALUES
(21733, 33157, 44232), -- 3287 (Hana'zua) - Broadcast_text - 138726
(14002, 5715, 44232), -- 3156 (Nartok) - Broadcast_text - 8291
(14001, 4793, 44232), -- 3155 (Rwag) - Broadcast_text - 7476
(14003, 5006, 44232), -- 3157 (Shikrik) - Broadcast_text - 7660
(14227, 17176, 44232), -- 39206 (Acrypha) - Broadcast_text - 47371
(13999, 4985, 44232), -- 3153 (Frang) - Broadcast_text - 7631
(14191, 5001, 44232); -- 39214 (Karranisha) - Broadcast_text - 7652
Shauren commented
Blizzard no longer sends npc_text id since 9.2.5
osleyder85 commented
Ok, so it is fixed manually?
mdX7 commented
will fix generator for it this week, likely tomorrow. It MAY require some manual adjustment in case its a not yet known npc_text in db. We gotta assign custom IDs in that case