SMSG_ATTACKSTOP

Client Version 1.1, Client Version 1.2, Client Version 1.3, Client Version 1.4, Client Version 1.5, Client Version 1.6, Client Version 1.7

Wowm Representation

Autogenerated from wowm file at wow_message_parser/wowm/world/combat/smsg_attackstop.wowm:1.

smsg SMSG_ATTACKSTOP = 0x0144 {
    Guid player;
    Guid enemy;
    u32 unknown1;
}

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
0x048 / LittleGuidplayer
0x0C8 / LittleGuidenemy
0x144 / Littleu32unknown1vmangos: set to 0 with comment: unk, can be 1 also

Client Version 1.8, Client Version 1.9, Client Version 1.10, Client Version 1.11, Client Version 1.12, Client Version 2, Client Version 3

Wowm Representation

Autogenerated from wowm file at wow_message_parser/wowm/world/combat/smsg_attackstop.wowm:10.

smsg SMSG_ATTACKSTOP = 0x0144 {
    PackedGuid player;
    PackedGuid enemy;
    u32 unknown1;
}

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
-- / -PackedGuidplayer
-- / -PackedGuidenemy
-4 / Littleu32unknown1cmangos/vmangos/mangoszero/arcemu/azerothcore/mangostwo: set to 0 with comment: unk, can be 1 also

Examples

Example 1

0, 10, // size
68, 1, // opcode (324)
1, 23, // player: PackedGuid
1, 100, // enemy: PackedGuid
0, 0, 0, 0, // unknown1: u32