S>C 0x4E SID_TOURNAMENT

Transport Layer:Transmission Control Protocol (TCP)
Application Layer:Battle.net v1 TCP Messages (SID)
Message Id:0x4E
Message Name:SID_TOURNAMENT
Direction:Server to Client
Options: In Research
Used By:Starcraft Original, Starcraft Broodwar
Message Format:
(does not include protocol header)
(UINT8) Unknown
(UINT8) Unknown, maybe number of non-null strings sent?
(STRING) Description
(STRING) Unknown
(STRING) Website
(UINT32) Unknown
(STRING) Name
(STRING) Unknown
(STRING) Unknown
(STRING) Unknown
(UINT32)[5] Unknown

Remarks

Sent after a successful logon to an account in a WCG tournament.

Research requested.

The C>S 0x0C SID_JOINCHANNEL message sent with 0x01 (First join) flags would automatically have the user join channel WCG planetname #.

Packet Log:

FF 4E 58 00
01
03
57 6F 72 6C 64 20 43 79 62 65 72 20 47 61 6D 65 73 20 28 53 61 74 75 72 6E 29 00
00
68 74 74 70 3A 2F 2F 77 77 77 2E 77 63 67 2E 63 6F 6D 00 57 43 47 00
00 00 00 00
80 07 01 00
00
00
00
00 01 01 00
02 02 00 00
00 00 01 05
00 00 00 00
32 00 00 00
| Edited: Leaky

Comments

brew

The 0x4E packet is sent to Starcraft/Brood War clients, however there is no code in battle.snp to parse that packet. Maybe it's used by warcraft 3 as well, but that's just a guess.

RealityRipple
xboi209

From what I can tell, SEXP 1.17.0 does handle this packet.
See Battle.snp+0x20BF00 / 0x190217F0