SMSG_TRANSFER_PENDING

Client Version 1.12

Wowm Representation

Autogenerated from wowm file at wow_message_parser/wowm/world/movement/smsg/smsg_transfer_pending.wowm:1.

smsg SMSG_TRANSFER_PENDING = 0x003F {
    Map map;
    optional has_transport {
        u32 transport;
        Map transport_map;
    }
}

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
0x044 / -Mapmap

Optionally the following fields can be present. This can only be detected by looking at the size of the message.

OffsetSize / EndiannessTypeNameComment
0x084 / Littleu32transport
0x0C4 / -Maptransport_map

Examples

Example 1

0, 6, // size
63, 0, // opcode (63)
1, 0, 0, 0, // map: Map KALIMDOR (1)

Client Version 2.4.3

Wowm Representation

Autogenerated from wowm file at wow_message_parser/wowm/world/movement/smsg/smsg_transfer_pending.wowm:1.

smsg SMSG_TRANSFER_PENDING = 0x003F {
    Map map;
    optional has_transport {
        u32 transport;
        Map transport_map;
    }
}

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
0x044 / -Mapmap

Optionally the following fields can be present. This can only be detected by looking at the size of the message.

OffsetSize / EndiannessTypeNameComment
0x084 / Littleu32transport
0x0C4 / -Maptransport_map

Client Version 3.3.5

Wowm Representation

Autogenerated from wowm file at wow_message_parser/wowm/world/movement/smsg/smsg_transfer_pending.wowm:1.

smsg SMSG_TRANSFER_PENDING = 0x003F {
    Map map;
    optional has_transport {
        u32 transport;
        Map transport_map;
    }
}

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
-4 / -Mapmap

Optionally the following fields can be present. This can only be detected by looking at the size of the message.

OffsetSize / EndiannessTypeNameComment
-4 / Littleu32transport
-4 / -Maptransport_map