mirror of
https://github.com/Kelsidavis/WoWee.git
synced 2026-03-23 07:40:14 +00:00
game: fix Classic/TBC SMSG_TEXT_EMOTE field order
Classic 1.12 and TBC 2.4.3 send SMSG_TEXT_EMOTE with the field order: textEmoteId(u32) + emoteNum(u32) + senderGuid(u64) + nameLen(u32) + name WotLK 3.3.5a swapped senderGuid to the front: senderGuid(u64) + textEmoteId(u32) + emoteNum(u32) + nameLen(u32) + name The previous TextEmoteParser always used the WotLK order, causing senderGuid to be read as a mashup of textEmoteId+emoteNum for Classic/TBC. Emote animations and chat entries were associated with wrong GUIDs. TextEmoteParser::parse now takes a legacyFormat parameter; handleTextEmote passes it based on expansion detection.
This commit is contained in:
parent
a0979b9cd8
commit
c19edd407a
3 changed files with 22 additions and 7 deletions
|
|
@ -717,7 +717,9 @@ struct TextEmoteData {
|
|||
*/
|
||||
class TextEmoteParser {
|
||||
public:
|
||||
static bool parse(network::Packet& packet, TextEmoteData& data);
|
||||
// legacyFormat: Classic 1.12 and TBC 2.4.3 send textEmoteId+emoteNum first, then senderGuid.
|
||||
// WotLK 3.3.5a reverses this: senderGuid first, then textEmoteId+emoteNum.
|
||||
static bool parse(network::Packet& packet, TextEmoteData& data, bool legacyFormat = false);
|
||||
};
|
||||
|
||||
// ============================================================
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue