0x02 MCP_CHARCREATE

ProtocolMCP
DirectionsClient → Server and Server → Client
Used byD2DVD2XP

Creates a character. The new character becomes the one the client plays straight away.

Client → Server

TypeFieldNotesConfidence
UINT32 Class See the table below. ✅ Verified
UINT16 Flags Hardcore, expansion and ladder, from the creation screen's checkboxes. Easy to miss: it is 16 bits. ✅ Verified
STRING Name 2 to 15 letters, with at most one - or _, not at either end. ✅ Verified

Classes

ValueMeaningConfidence
0x00Amazon✅ Verified
0x01Sorceress✅ Verified
0x02Necromancer✅ Verified
0x03Paladin✅ Verified
0x04Barbarian✅ Verified
0x05Druid (Lord of Destruction only)✅ Verified
0x06Assassin (Lord of Destruction only)✅ Verified

Server → Client

TypeFieldNotesConfidence
UINT32 Result ✅ Verified

Results

ValueMeaningConfidence
0x00Created.✅ Verified
0x14A character with that name already exists. BNETDocs also lists this for reaching the character limit.✅ Verified
0x15Name, class or flags not allowed.✅ Verified

Remarks

No MCP_CHARLOGON follows. A real client that has just created a character goes straight on to MCP_MOTD and entering chat as that character. A realm should treat the new character as selected.

When the player ticks Ladder, the client shows its own ladder notice before sending this message. That notice isn't a server error.

Appears in

Sources and credits

This page is written in our own words. BNETDocs is credited for its research; none of its text is copied. See Credits.

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