Smsg_addon_info

[/dev/not/null]

Does it necessary to send packet with opcode SMSG_ADDON_INFO during World Server authentication process? What does this packet should contains ?
Not enough info about this at Network.

[/dev/not/null]

Well, I'm ready to answering to the one of my own questions. I have found what this packet should contains. Used source code for this: Ember emulator and JaNGOSRealm. If I understand it correctly, SMSG_ADDON_INFO sends information about client addon list. Each addon contains 5 bytes:

(addon type) + unk + unk + public key (optional) + unk + unk

In all examples which I saw, typical SMSG_ADDON_INFO packet has same structure: 2 + 1 + 0 + 0 + 0 (and 3 zeros at the end).
So each addon has BLIZZARD type (see below). Another flags I don't know what it means.


Addon types

BANNED,     // does what you expect it to
ENABLED,    // shows the addon in the list - probably intended for player-created addons
BLIZZARD    // hides the addon from the list

I still do not understand which addon list is taken. Does users addon also exists at this list ? Or only addons generated by the client.

And I still do not understand, why I need to send this packet.

[/dev/not/null]

I have found this thread, where TS said, that SMSG_ADDON_INFO need for CMSG_CHAR_ENUM. Currently my client stucks on 'Connected' even if I send SMSG_ADDON_INFO to it. Trying to realize what the reason can be.

[drolean]

This packet is not important for login

it enable the addons button in the chars list

Servidor-Wow/OnAuthSession.cs at mongo . drolean/Servidor-Wow . GitHub

Servidor-Wow/SMSG_ADDON_INFO.cs at mongo . drolean/Servidor-Wow . GitHub

you can send this on vanilla is default 12 addons by default blizzard

[/dev/not/null]

This packet is not important for login

it enable the addons button in the chars list

Servidor-Wow/OnAuthSession.cs at mongo . drolean/Servidor-Wow . GitHub

Servidor-Wow/SMSG_ADDON_INFO.cs at mongo . drolean/Servidor-Wow . GitHub

you can send this on vanilla is default 12 addons by default blizzard

Well, but what else is important for login after SMSG_AUTH_RESPONSE ? What else client waiting for ? What should happens after SMSG_AUTH_RESPONSE ?

[Icesythe7]

Just by reading this thread (while I have no proof this is just a logical guess) the packet is used to check the addons at login (ad after you login you can access the addons panel) to check for banned addons such as avr and tells the client not to display it and if result is blizzard just hide it from the list

[/dev/not/null]

Just by reading this thread (while I have no proof this is just a logical guess) the packet is used to check the addons at login (ad after you login you can access the addons panel) to check for banned addons such as avr and tells the client not to display it and if result is blizzard just hide it from the list

good explanation, thanks