SID_CHATEVENT
| Protocol | BNCS |
|---|---|
| Directions | Server → Client |
| Used by |
Everything that happens in chat: joins, leaves, messages, whispers and server notices.
Server → Client
| Type | Field | Notes | Confidence |
|---|---|---|---|
UINT32 |
Event ID | What happened. See the table below. | ✅ Verified |
UINT32 |
User flags | For user events, the user's flags. For EID_CHANNEL, the channel's flags. |
✅ Verified |
UINT32 |
Ping | The user's latency in milliseconds. | ✅ Verified |
UINT32 |
IP address | No longer used. Always 0. |
⚠️ Single source |
UINT32 |
Account number | No longer used. Always 0. |
⚠️ Single source |
UINT32 |
Registration authority | No longer used. Always 0. |
⚠️ Single source |
STRING |
Username | ✅ Verified | |
STRING |
Text | The message, the channel name, or the user's statstring, depending on the event. | ✅ Verified |
Event IDs
| Value | Meaning | Confidence |
|---|---|---|
0x01 | EID_SHOWUSER: a user already in the channel when you joined. | ✅ Verified |
0x02 | EID_JOIN: a user joined. | ✅ Verified |
0x03 | EID_LEAVE: a user left. | ✅ Verified |
0x04 | EID_WHISPER: a whisper to you. | ✅ Verified |
0x05 | EID_TALK: a message in the channel. | ✅ Verified |
0x06 | EID_BROADCAST: a server-wide announcement. | ✅ Verified |
0x07 | EID_CHANNEL: you are now in this channel. | ✅ Verified |
0x09 | EID_USERFLAGS: a user's flags changed. | ✅ Verified |
0x0A | EID_WHISPERSENT: your whisper was delivered. | ✅ Verified |
0x0D | EID_CHANNELFULL: the channel is full. | ✅ Verified |
0x0E | EID_CHANNELDOESNOTEXIST: no such channel. | ✅ Verified |
0x0F | EID_CHANNELRESTRICTED: you may not join that channel. | ✅ Verified |
0x12 | EID_INFO: an information message from the server. | ✅ Verified |
0x13 | EID_ERROR: an error message from the server. | ✅ Verified |
0x15 | EID_IGNORE: you are now ignoring (squelching) a user. | ⚠️ Single source |
0x16 | EID_ACCEPT: you stopped ignoring a user. | ⚠️ Single source |
0x17 | EID_EMOTE: an emote (/me). | ✅ Verified |
0x08, 0x0B, 0x0C, 0x10, 0x11, 0x14 | Not known. Don't assume these are unused. | 🛑 Unknown |
User flags
| Value | Meaning | Confidence |
|---|---|---|
0x01 | Blizzard representative | ⚠️ Single source |
0x02 | Channel operator | ✅ Verified |
0x04 | Channel speaker | ⚠️ Single source |
0x08 | Battle.net administrator | ⚠️ Single source |
0x10 | No UDP support | ✅ Verified |
0x20 | Squelched (ignored by you) | ⚠️ Single source |
0x40 | Special guest | ⚠️ Single source |
Remarks
Relaying chat text. A server must strip control characters from text before relaying it. A carriage return or line feed inside chat text makes real clients misbehave, and real Battle.net disconnected and briefly banned the sender.
A bad Diablo II statstring crashes every Diablo II client in the channel. A Diablo II 1.14d client reads the statstring of every other user it's told about, not only its own. If a statstring starts with a backwards Diablo II code (VD2D, PX2D, or the Japanese TS2D) and anything follows the code, the client copies the next two comma-separated fields into fixed-size memory. It stops only at a comma: it never checks for the end of the text or the size of the memory. With fewer than two commas, the copy runs on and overwrites the client's list of channel users, and the client crashes. The generic PX2D 0 0 0 0 0 0 0 0 PX2D form that other games use has no commas and does exactly that. ✅
Only two forms are safe, and they're the two the client itself produces: ⚠️
| Form | Statstring |
|---|---|
| No character | Just the code, such as PX2D, with nothing after it |
| A character | The code, the realm, a comma, the character's name, a comma, then the character's portrait: PX2DRealm,Name,… |
Three more limits in the same code: ⚠️
- The client only reads the statstring of some users. It skips users with flags
0x01,0x04or0x08(and a few others), but not channel operators (0x02). So a bad statstring seems to crash on some users and not others; the flags are a red herring. EID_USERFLAGSruns the same code. It has to carry the user's full statstring: an empty one blanks their portrait.- The client copies each username into a 50-byte field without checking its length. A name longer than 49 bytes overwrites the client's memory.
Appears in
Sources and credits
- Command Center: bnetcc-proto chat events
- Command Center: PROTOCOL-NOTES.md
- Command Center: DIABLO2.md §6: a real Diablo II 1.14d client crashed by a statstring with no commas on September 18, 2026, and the client code that explains it
- BNETDocs, SID_CHATEVENT (server to client): documented by joe[x86], and edited 5 times since.
This page is written in our own words. BNETDocs is credited for its research; none of its text is copied. See Credits.