SMSG_CREATURE_QUERY_RESPONSE

Client Version 1.12

Wowm Representation

Autogenerated from wowm file at wow_message_parser/wowm/world/queries/smsg_creature_query_response.wowm:1.

smsg SMSG_CREATURE_QUERY_RESPONSE = 0x0061 { u32 creature_entry; optional found { CString name1; CString name2; CString name3; CString name4; CString sub_name; u32 type_flags; u32 creature_type; (u32)CreatureFamily creature_family; u32 creature_rank; u32 unknown0; u32 spell_data_id; u32 display_id; u8 civilian; u8 racial_leader; } }

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 / Littleu32creature_entryWhen the found optional is not present all emulators bitwise OR the entry with 0x80000000.``

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

OffsetSize / EndiannessTypeNameComment
0x08- / -CStringname1
-- / -CStringname2
-- / -CStringname3
-- / -CStringname4
-- / -CStringsub_name
-4 / Littleu32type_flags
-4 / Littleu32creature_typecmangos: CreatureType.dbc wdbFeild8
-4 / -CreatureFamilycreature_family
-4 / Littleu32creature_rankcmangos: Creature Rank (elite, boss, etc)
-4 / Littleu32unknown0cmangos: wdbFeild11
-4 / Littleu32spell_data_idcmangos: Id from CreatureSpellData.dbc wdbField12
-4 / Littleu32display_idcmangos: DisplayID wdbFeild13 and workaround, way to manage models must be fixed
-1 / -u8civiliancmangos: wdbFeild14
-1 / -u8racial_leader

Examples

Example 1

0, 46, // size 97, 0, // opcode (97) 69, 0, 0, 0, // creature_entry: u32 // Optional found 84, 104, 105, 110, 103, 0, // name1: CString 0, // name2: CString 0, // name3: CString 0, // name4: CString 0, // sub_name: CString 0, 0, 0, 0, // type_flags: u32 0, 0, 0, 0, // creature_type: u32 0, 0, 0, 0, // creature_family: CreatureFamily NONE (0) 0, 0, 0, 0, // creature_rank: u32 0, 0, 0, 0, // unknown0: u32 0, 0, 0, 0, // spell_data_id: u32 0, 0, 0, 0, // display_id: u32 0, // civilian: u8 0, // racial_leader: u8

Client Version 2.4.3

Wowm Representation

Autogenerated from wowm file at wow_message_parser/wowm/world/queries/smsg_creature_query_response.wowm:30.

smsg SMSG_CREATURE_QUERY_RESPONSE = 0x0061 { u32 creature_entry; optional found { CString name1; CString name2; CString name3; CString name4; CString sub_name; CString description; u32 type_flags; u32 creature_type; (u32)CreatureFamily creature_family; u32 creature_rank; u32 unknown0; u32 spell_data_id; u32[4] display_ids; f32 health_multiplier; f32 mana_multiplier; u8 racial_leader; } }

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 / Littleu32creature_entryWhen the found optional is not present all emulators bitwise OR the entry with 0x80000000.``

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

OffsetSize / EndiannessTypeNameComment
0x08- / -CStringname1
-- / -CStringname2
-- / -CStringname3
-- / -CStringname4
-- / -CStringsub_name
-- / -CStringdescriptionmangosone: 'Directions' for guard, string for Icons 2.3.0
-4 / Littleu32type_flags
-4 / Littleu32creature_typemangosone: CreatureType.dbc wdbFeild8
-4 / -CreatureFamilycreature_family
-4 / Littleu32creature_rankmangosone: Creature Rank (elite, boss, etc)
-4 / Littleu32unknown0mangosone: wdbFeild11
-4 / Littleu32spell_data_idmangosone: Id from CreatureSpellData.dbc wdbField12
-16 / -u32[4]display_ids
-4 / Littlef32health_multiplier
-4 / Littlef32mana_multiplier
-1 / -u8racial_leader

Client Version 3.3.5

Wowm Representation

Autogenerated from wowm file at wow_message_parser/wowm/world/queries/smsg_creature_query_response.wowm:61.

smsg SMSG_CREATURE_QUERY_RESPONSE = 0x0061 { u32 creature_entry; optional found { CString name1; CString name2; CString name3; CString name4; CString sub_name; CString description; u32 type_flags; u32 creature_type; (u32)CreatureFamily creature_family; u32 creature_rank; u32 kill_credit1; u32 kill_credit2; u32[4] display_ids; f32 health_multiplier; f32 mana_multiplier; u8 racial_leader; u32[6] quest_items; u32 movement_id; } }

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 / Littleu32creature_entryWhen the found optional is not present all emulators bitwise OR the entry with 0x80000000.``

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

OffsetSize / EndiannessTypeNameComment
-- / -CStringname1
-- / -CStringname2
-- / -CStringname3
-- / -CStringname4
-- / -CStringsub_name
-- / -CStringdescriptionmangosone: 'Directions' for guard, string for Icons 2.3.0
-4 / Littleu32type_flags
-4 / Littleu32creature_typemangosone: CreatureType.dbc wdbFeild8
-4 / -CreatureFamilycreature_family
-4 / Littleu32creature_rankmangosone: Creature Rank (elite, boss, etc)
-4 / Littleu32kill_credit1mangosone: new in 3.1
-4 / Littleu32kill_credit2mangosone: new in 3.1
-16 / -u32[4]display_ids
-4 / Littlef32health_multiplier
-4 / Littlef32mana_multiplier
-1 / -u8racial_leader
-24 / -u32[6]quest_items
-4 / Littleu32movement_idmangosone: CreatureMovementInfo.dbc