And right after the AckPacket and WorldClientReady, I get this new opcode 0x58FB, which I am not sure about either:
Code:
25686 [12.13. - 03:48:16] [WORLD__CLIENT_TRACE] [OpCode OP_AckPacket (0x4d38) Size=4]
25686 [12.13. - 03:48:16] [WORLD__CLIENT_TRACE] 0000: 00 00 00 00 - | ....
25686 [12.13. - 03:48:16] [WORLD__CLIENT_TRACE] trevadmin: Recevied EQApplicationPacket
25686 [12.13. - 03:48:16] [WORLD__CLIENT_TRACE] [OpCode OP_WorldClientReady (0x2ebd) Size=0]
25686 [12.13. - 03:48:16] Unable to convert EQ opcode 0x58fb to an Application opcode.
25686 [12.13. - 03:48:16] [WORLD__CLIENT_TRACE] trevadmin: Recevied EQApplicationPacket
25686 [12.13. - 03:48:16] [WORLD__CLIENT_TRACE] [OpCode OP_Unknown (0x58fb) Size=8]
25686 [12.13. - 03:48:16] [WORLD__CLIENT_TRACE] 0000: 49 02 00 00 60 9f 4d 00 - | I...`.M.
25686 [12.13. - 03:48:16] [WORLD__CLIENT_ERR] trevadmin: Received unknown EQApplicationPacket
25686 [12.13. - 03:48:16] [WORLD__CLIENT_ERR] [OpCode OP_Unknown (0x58fb) Size=8]
25686 [12.13. - 03:48:16] [WORLD__CLIENT_ERR] 0000: 49 02 00 00 60 9f 4d 00 - | I...`.M.
25686 [12.13. - 03:48:16] [NET__NET_ACKS] 192.168.1.101:4753: Sending ack with sequence 24
25686 [12.13. - 03:48:16] [NET__NET_ACKS] 192.168.1.101:4753: Set Last Ack Sent to 24
25686 [12.13. - 03:48:16] [NET__APP_TRACE] 192.168.1.101:4753: Pushing non-sequenced packet of length 2
25686 [12.13. - 03:48:16] [NET__NET_COMBINE] 192.168.1.101:4753: Starting combined packet with non-seq packet of len 2
25686 [12.13. - 03:48:16] [NET__NET_COMBINE] 192.168.1.101:4753: Final combined packet not full, len 2
25686 [12.13. - 03:48:18] [NET__NET_TRACE] 192.168.1.101:4753: Received Stats: 0 packets received, 0 packets sent, Deltas: local 14, (14 <- 22 -> 31) remote 31
25686 [12.13. - 03:48:18] [NET__APP_TRACE] 192.168.1.101:4753: Pushing non-sequenced packet of length 38
25686 [12.13. - 03:48:18] [NET__RATES] 192.168.1.101:4753: Adjusting data rate to thresh 47662, decay 3574 based on avg delta 22
25686 [12.13. - 03:48:18] [NET__NET_COMBINE] 192.168.1.101:4753: Starting combined packet with non-seq packet of len 38
25686 [12.13. - 03:48:18] [NET__NET_COMBINE] 192.168.1.101:4753: Final combined packet not full, len 38
25686 [12.13. - 03:48:24] [NET__NET_ACKS] 192.168.1.101:4753: Set Next Ack To Send to 25
25686 [12.13. - 03:48:24] [NET__APP_CREATE] 192.168.1.101:4753: Creating new application packet, length 10
25686 [12.13. - 03:48:24] [NET__APP_CREATE_HEX] 0000: fb 58 41 01 00 00 60 9f - 4d 00 | .XA...`.M.
25686 [12.13. - 03:48:24] [NET__NET_ACKS] 192.168.1.101:4753: Sending ack with sequence 25
25686 [12.13. - 03:48:24] [NET__NET_ACKS] 192.168.1.101:4753: Set Last Ack Sent to 25
25686 [12.13. - 03:48:24] [NET__APP_TRACE] 192.168.1.101:4753: Pushing non-sequenced packet of length 2
25686 [12.13. - 03:48:24] [NET__NET_COMBINE] 192.168.1.101:4753: Starting combined packet with non-seq packet of len 2
25686 [12.13. - 03:48:24] [NET__NET_COMBINE] 192.168.1.101:4753: Final combined packet not full, len 2
25686 [12.13. - 03:48:24] Unable to convert EQ opcode 0x58fb to an Application opcode.
25686 [12.13. - 03:48:24] [WORLD__CLIENT_TRACE] trevadmin: Recevied EQApplicationPacket
25686 [12.13. - 03:48:24] [WORLD__CLIENT_TRACE] [OpCode OP_Unknown (0x58fb) Size=8]
25686 [12.13. - 03:48:24] [WORLD__CLIENT_TRACE] 0000: 41 01 00 00 60 9f 4d 00 - | A...`.M.
25686 [12.13. - 03:48:24] [WORLD__CLIENT_ERR] trevadmin: Received unknown EQApplicationPacket
25686 [12.13. - 03:48:24] [WORLD__CLIENT_ERR] [OpCode OP_Unknown (0x58fb) Size=8]
25686 [12.13. - 03:48:24] [WORLD__CLIENT_ERR] 0000: 41 01 00 00 60 9f 4d 00 - | A...`.M.
Judging by what I see from Titanium clients, this doesn't exist. At least not in the order I have seen them in. It could be that it is an error from not getting anything back from the CRC checks though. Either way, these are all coming in while getting to the char select screen, which loads fine. I don't think they are related to the reason I can't get in game, but worth noting at least.
EDIT: After looking into it a bit more, this 3rd unknown opcode does show up when connecting with Titanium as well, only it uses 0x6A5F, which from what I can tell is the auto-AFK opcode. It is "unknown" in Titanium as well and doesn't cause problems, so it shouldn't be an issue at all for SoF. I am pretty sure we can at least ignore this particular one (0x58FB), since it appears to be AFK related.