SMSG_PET_NAME_INVALID

Client Version 1.12

Some emulators have this with fields, but it has been verified to be empty on 1.12 through reverse engineering.

Wowm Representation

Autogenerated from wowm file at wow_message_parser/wowm/world/pet/smsg_pet_name_invalid.wowm:2.

smsg SMSG_PET_NAME_INVALID = 0x0178 {
}

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

This message has no fields in the body.

Client Version 2.4.3, Client Version 3

Some emulators have this with fields, but it has been verified to be empty on 1.12 through reverse engineering.

Wowm Representation

Autogenerated from wowm file at wow_message_parser/wowm/world/pet/smsg_pet_name_invalid.wowm:32.

smsg SMSG_PET_NAME_INVALID = 0x0178 {
    (u32)PetNameInvalidReason reason;
    CString name;
    DeclinedPetNameIncluded included;
    if (included == INCLUDED) {
        CString[5] declined_names;
    }
}

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
-	4 / -	PetNameInvalidReason	reason
-	- / -	CString	name
-	1 / -	DeclinedPetNameIncluded	included

If included is equal to INCLUDED:

Offset	Size / Endianness	Type	Name	Comment
-	? / -	CString[5]	declined_names

Wowm Language