View Single Post
  #9  
Old 02-09-2011, 06:48 PM
tbf
Fire Beetle
 
Join Date: Feb 2011
Posts: 7
Default

I was under the impression that the EQEmuLoginServer was for a private server, not for running through the public login server - is this not the case?


Edit: Huppy, in regards to -march=native, it compiled fine (After removing the ::pair issue), I mean by "same issue" the issue causing my SoD client to not connect.


As I look into it, there's an unknown opcode being registered before the tutorialb zone is loaded:

Code:
22771 [02.10. - 06:38:02] Unable to convert EQ opcode 0x0924 to an Application opcode.
22771 [02.10. - 06:38:02] [WORLD__CLIENT_ERR] tbf: Received unknown EQApplicationPacket
22771 [02.10. - 06:38:02] [WORLD__CLIENT_ERR] [OpCode OP_Unknown (0x0924) Size=1]
22771 [02.10. - 06:38:02] [WORLD__CLIENT_ERR] 0000: 30                      -                          | 0
22771 [02.10. - 06:38:09] [WORLD__CLIENT] tbf: Attempting autobootup of tutorialb (189:0)
22771 [02.10. - 06:38:10] [WORLD__ZONE] [5] Setting to 'tutorialb' (189:0)
22771 [02.10. - 06:38:10] [WORLD__CLIENT] tbf: Entering zone tutorialb (189:0)
22771 [02.10. - 06:38:10] [WORLD__ZONE] [5] [tutorialb] Broadcasting a world time update
22771 [02.10. - 06:38:10] [WORLD__ZONE] [5] [tutorialb] Setting to 'tutorialb' (189:0)
22771 [02.10. - 06:38:10] [WORLD__CLIENT] tbf: Sending client to zone tutorialb (189:0) at EXTERNAL_SERVER_IP:7004
22771 [02.10. - 06:38:10] [WORLD__CLIENT] tbf: Client disconnected (not active in process)
I see that the zone start and move procedures are still running, so I'm not sure this is relevant, just trying to wade through this a bit more. I also see that the world is trying to send the client to the external_ip of the server instead of local or loopback, is this the desired behaviour? Is the opcode at 0x0924 really the OP_PlayerProfile packet?
Reply With Quote