|Transport Layer:||User Datagram Protocol (UDP)|
|Application Layer:||Battle.net v1 UDP Messages (PKT)|
|Direction:||Peer to Peer|
|Used By:||Starcraft Original, Starcraft Broodwar|
Starcraft Shareware, Starcraft Japanese
Diablo Retail, Diablo Shareware
Warcraft II BNE
(does not include protocol header)
Calculated from all of the data in this packet starting at Length. See here for the function, and more details on this protocol.
Includes everything you see here (EX: 12 + length of Payload).
Number of packets sent.
Number of packets received.
Can be 0, 1, or 2.
||Internal packets: Handled by network provider and sent to the game as high level events. Command is used by network provider.|
||Asynchronous packets: Payload sent to StarCraft, Diablo, or WarCraft II game. Can be sent any time. Command is 0.|
||Synchronous packets: Payload sent to StarCraft, Diablo, or WarCraft II game. Can be buffered but must be sent once per game turn. Command is 0.|
The packet ID of CLS 0 packets. 0 for other packets.
The player ID. If unknown (first few packets from client) set to
0xFF means "everyone".
||Normal: Handle this normally.|
||Verify: Used to verify Seq1 and Seq2.|
||Resend: Resend request.|
||Callback: Resend response.|
Packet name was invented.
See Storm Messages for CLS 0 packets.
See SCGP Messages for CLS 1 and 2 packets for StarCraft, BW, JP, and SHR.
See W2GP Messages for CLS 1 and 2 packets for WarCraft II BNE.
See D1GP Messages for CLS 1 and 2 packets for Diablo and SHR.
no one has commented yet.