CMD_AUTH_LOGON_PROOF_Server

Protocol Version 2, Protocol Version 3

Reply to CMD_AUTH_LOGON_PROOF_Client.

Wowm Representation

Autogenerated from wowm file at wow_message_parser/wowm/login/cmd_auth_logon/proof_server.wowm:2.

slogin CMD_AUTH_LOGON_PROOF_Server = 0x01 {
    LoginResult result;
    if (result == SUCCESS) {
        u8[20] server_proof;
        u32 hardware_survey_id;
    }
}

Login messages have a header of 1 byte with an opcode. Some messages also have a size field but this is not considered part of the header.

Login Header

OffsetSize / EndiannessTypeNameDescription
0x001 / -uint8opcodeOpcode that determines which fields the message contains.

Body

OffsetSize / EndiannessTypeNameComment
0x011 / -LoginResultresult

If result is equal to SUCCESS:

OffsetSize / EndiannessTypeNameComment
0x0220 / -u8[20]server_proof
0x164 / Littleu32hardware_survey_id

Examples

Example 1

1, // opcode (1)
0, // result: LoginResult SUCCESS (0x00)
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, // server_proof: u8[20]
239, 190, 173, 222, // hardware_survey_id: u32

Protocol Version 5, Protocol Version 6, Protocol Version 7

Reply to CMD_AUTH_LOGON_PROOF_Client.

Wowm Representation

Autogenerated from wowm file at wow_message_parser/wowm/login/cmd_auth_logon/proof_server.wowm:35.

slogin CMD_AUTH_LOGON_PROOF_Server = 0x01 {
    LoginResult result;
    if (result == SUCCESS) {
        u8[20] server_proof;
        u32 hardware_survey_id;
        u16 unknown;
    }
}

Header

Login messages have a header of 1 byte with an opcode. Some messages also have a size field but this is not considered part of the header.

Login Header

OffsetSize / EndiannessTypeNameDescription
0x001 / -uint8opcodeOpcode that determines which fields the message contains.

Body

OffsetSize / EndiannessTypeNameComment
0x011 / -LoginResultresult

If result is equal to SUCCESS:

OffsetSize / EndiannessTypeNameComment
0x0220 / -u8[20]server_proof
0x164 / Littleu32hardware_survey_id
0x1A2 / Littleu16unknown

Examples

Example 1

1, // opcode (1)
0, // result: LoginResult SUCCESS (0x00)
25, 255, 233, 250, 100, 169, 155, 175, 246, 179, 141, 156, 17, 171, 220, 174, 128, 
196, 210, 231, // server_proof: u8[20]
0, 0, 0, 0, // hardware_survey_id: u32
0, 0, // unknown: u16

Protocol Version 8

Wowm Representation

Autogenerated from wowm file at wow_message_parser/wowm/login/cmd_auth_logon/proof_server.wowm:61.

slogin CMD_AUTH_LOGON_PROOF_Server = 0x01 {
    LoginResult result;
    if (result == SUCCESS) {
        u8[20] server_proof;
        AccountFlag account_flag;
        u32 hardware_survey_id;
        u16 unknown;
    }
    else {
        u16 padding = 0;
    }
}

Header

Login messages have a header of 1 byte with an opcode. Some messages also have a size field but this is not considered part of the header.

Login Header

OffsetSize / EndiannessTypeNameDescription
0x001 / -uint8opcodeOpcode that determines which fields the message contains.

Body

OffsetSize / EndiannessTypeNameComment
0x011 / -LoginResultresult

If result is equal to SUCCESS:

OffsetSize / EndiannessTypeNameComment
0x0220 / -u8[20]server_proof
0x164 / -AccountFlagaccount_flag
0x1A4 / Littleu32hardware_survey_id
0x1E2 / Littleu16unknown

Else: | 0x20 | 2 / Little | u16 | padding | |

Examples

Example 1

Comment

Reply to CMD_AUTH_LOGON_PROOF_Client.

1, // opcode (1)
7, // result: LoginResult FAIL_NO_TIME (0x07)
0, 0, // padding: u16

Example 2

1, // opcode (1)
8, // result: LoginResult FAIL_DB_BUSY (0x08)
0, 0, // padding: u16