How to read these pages

Message pages

Each message has one page covering both directions:

  • Used by shows the icon of every game that sends or receives the message. Hover over an icon for the game's name.
  • Client → Server and Server → Client list the fields in the order they're sent. A section labelled "For each …" repeats.
  • Remarks explain behaviour that the field lists can't show.
  • Appears in links to the connection sequences that use the message.
  • Sources and credits say where the facts came from, and credit the BNETDocs authors who documented the message first.

Confidence

Every field, value and sequence step carries a mark:

Mark Meaning
✅ Verified Confirmed against a real client, or by two independent sources.
⚠️ Single source From one source only, or worked out rather than captured. Treat with care.
🛑 Unknown Not known. Don't guess in code; capture it.

When you confirm something marked ⚠️ or 🛑, please update the page and say how you confirmed it.

What this site never hosts

This site documents protocols. It never hosts or links to game files, version-check (hash) files, CD keys, patches that get a game past a server's security checks (such as Warcraft III's server signature), or ways around anti-cheat. Pages explain how those things work, not where to get them.

Guides may link to open-source projects that only improve how a game runs, such as display wrappers, and to bots in the BNET.cc archive.

Sources and credit

Pages are written in our own words. When research came from BNETDocs or another project, the page links to it and names the people behind it. Nothing is copied. See Credits.

Last edited September 16, 2026 by tagban.
Edit on GitHub | Page history | Edit with Discord