SMSG_ITEM_TEXT_QUERY_RESPONSE
Client Version 1, Client Version 2
Wowm Representation
Autogenerated from wowm file at wow_message_parser/wowm/world/queries/smsg_item_text_query_response.wowm:1.
smsg SMSG_ITEM_TEXT_QUERY_RESPONSE = 0x0244 {
u32 item_text_id;
CString text;
}
Header
SMSG have a header of 4 bytes.
SMSG Header
| Offset | Size / Endianness | Type | Name | Description |
|---|---|---|---|---|
| 0x00 | 2 / Big | uint16 | size | Size of the rest of the message including the opcode field but not including the size field. |
| 0x02 | 2 / Little | uint16 | opcode | Opcode that determines which fields the message contains. |
Body
| Offset | Size / Endianness | Type | Name | Comment |
|---|---|---|---|---|
| 0x04 | 4 / Little | u32 | item_text_id | |
| 0x08 | - / - | CString | text | mangoszero: CString TODO max length 8000 |
Client Version 3.3.5
Wowm Representation
Autogenerated from wowm file at wow_message_parser/wowm/world/queries/smsg_item_text_query_response.wowm:16.
smsg SMSG_ITEM_TEXT_QUERY_RESPONSE = 0x0244 {
ItemTextQuery query;
if (query == HAS_TEXT) {
Guid item;
CString text;
}
}
Header
SMSG have a header of 4 bytes.
SMSG Header
| Offset | Size / Endianness | Type | Name | Description |
|---|---|---|---|---|
| 0x00 | 2 OR 3 / Big | uint16 OR uint16+uint8 | size | Size 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 / Little | uint16 | opcode | Opcode that determines which fields the message contains. |
Body
| Offset | Size / Endianness | Type | Name | Comment |
|---|---|---|---|---|
| - | 1 / - | ItemTextQuery | query |
If query is equal to HAS_TEXT:
| Offset | Size / Endianness | Type | Name | Comment |
|---|---|---|---|---|
| - | 8 / Little | Guid | item | |
| - | - / - | CString | text |