Opcode mapping gone wrong?
Just compiled 0.6.4 (latest) from the /downloads.php page and noticed that I get a 1017 whenever I try to log on to it either from MiniLogin or normal EQEmu login. Before you get all fussy, I have correct files and I have played on other servers before the 0.6.4 release.
I guess my question is, did the 0.6.4 release change anything so that I couldn't log on to the newer servers, the 9/13 patch deadline should still be good right?
S2K (in IRC) said that I should try checking ports/firewall, but I'm not really convinced it's got something to do with that because I can log in to some servers and can't to others (like PEQ). On my server I get 1017'd and the server error is something like:
--------------------------------------------------------
(Through debug levels/prints)
S Translate EQ 0x2792 to Emu OP_Unknown (0)
[Debug] Starting Log: logs/eqemu_debug_world.log
[Debug] Unable to convert EQ opcode 0x2792 to an Application opcode.
Received 0x0000
(Packet Info Print Ommited)
[Error] Starting Log: logs/eqemu_error_world.log
[Error] Expecting OP_SendLoginInfo, got 0
Removing client from ip:192.168.1.1 port:3602
Removing connection
--------------------------------------------------------------
Although I'm no expert it looks like the server received a packet that I sent and labeled as OP_Unknown, even though the packet type 0x2792 should be mapped to the Emu OP_SendLoginInfo.
I'd try to debug further but I only have a few years C++ background and really don't know anything about reading/writing/debugging shared memory if thats where this is heading. Does anyone know why it's not translating this packet?
|
Threaded Mode
