SMSG_CHAR_ENUM

Client Version 1.12

Response to CMSG_CHAR_ENUM.

Wowm Representation

Autogenerated from wowm file at wow_message_parser/wowm/world/character_screen/smsg_char_enum.wowm:44.

smsg SMSG_CHAR_ENUM = 0x003B {
    u8 amount_of_characters;
    Character[amount_of_characters] characters;
}

SMSG have a header of 4 bytes.

SMSG Header

OffsetSize / EndiannessTypeNameDescription
0x002 / Biguint16sizeSize of the rest of the message including the opcode field but not including the size field.
0x022 / Littleuint16opcodeOpcode that determines which fields the message contains.

Body

OffsetSize / EndiannessTypeNameComment
0x041 / -u8amount_of_charactersClient can not handle values larger than 10
0x05? / -Character[amount_of_characters]characters

Examples

Example 1

Comment

Empty character list.

0, 3, // size
59, 0, // opcode (59)
0, // amount_of_characters: u8
// characters: Character[amount_of_characters]

Client Version 2.4.3

Wowm Representation

Autogenerated from wowm file at wow_message_parser/wowm/world/character_screen/smsg_char_enum_2_4_3.wowm:3.

smsg SMSG_CHAR_ENUM = 0x003B {
    u8 amount_of_characters;
    Character[amount_of_characters] characters;
}

Header

SMSG have a header of 4 bytes.

SMSG Header

OffsetSize / EndiannessTypeNameDescription
0x002 / Biguint16sizeSize of the rest of the message including the opcode field but not including the size field.
0x022 / Littleuint16opcodeOpcode that determines which fields the message contains.

Body

OffsetSize / EndiannessTypeNameComment
0x041 / -u8amount_of_characters
0x05? / -Character[amount_of_characters]characters

Client Version 3.3.5

Wowm Representation

Autogenerated from wowm file at wow_message_parser/wowm/world/character_screen/smsg_char_enum_3_3_5.wowm:3.

smsg SMSG_CHAR_ENUM = 0x003B {
    u8 amount_of_characters;
    Character[amount_of_characters] characters;
}

Header

SMSG have a header of 4 bytes.

SMSG Header

OffsetSize / EndiannessTypeNameDescription
0x002 OR 3 / Biguint16 OR uint16+uint8sizeSize of the rest of the message including the opcode field but not including the size field. Wrath server messages can be 3 bytes. If the first (most significant) size byte has 0x80 set, the header will be 3 bytes, otherwise it is 2.
-2 / Littleuint16opcodeOpcode that determines which fields the message contains.

Body

OffsetSize / EndiannessTypeNameComment
-1 / -u8amount_of_characters
-? / -Character[amount_of_characters]characters