SMSG_QUERY_TIME_RESPONSE

Client Version 1.12

CMSG_QUERY_TIME and this reply does not actually appear to set the time. Instead SMSG_LOGIN_SETTIMESPEED seems to correctly set the time. Running the client with -console will print the date when SMSG_LOGIN_SETTIMESPEED is received, but not when this message is received.

Wowm Representation

Autogenerated from wowm file at wow_message_parser/wowm/world/queries/smsg_query_time_response.wowm:3.

smsg SMSG_QUERY_TIME_RESPONSE = 0x01CF {
    u32 time;
}

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	time	Seconds since 1970, 1st of January (Unix Time).

Examples

Example 1

0, 6, // size
207, 1, // opcode (463)
148, 152, 80, 97, // time: u32

Client Version 2.4.3, Client Version 3

Reply to CMSG_QUERY_TIME.

Wowm Representation

Autogenerated from wowm file at wow_message_parser/wowm/world/queries/smsg_query_time_response.wowm:22.

smsg SMSG_QUERY_TIME_RESPONSE = 0x01CF {
    u32 time;
    u32 time_until_daily_quest_reset;
}

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	time	Seconds since 1970, 1st of January (Unix Time).
0x08	4 / Little	u32	time_until_daily_quest_reset	Units need confirmation, but it's likely in seconds, since many other time related things are also seconds.

Wowm Language