Log in

View Full Version : Opcode 0x32f???


Zabeeble
08-31-2009, 11:19 PM
Okay. I searched and found only one post concerning this problem. It was back in 2006 and it wasn't answered - at least, not where I could see.

I set up my server according to the instructions in the sticky. After figuring out the left-out part about changing the server type from public to Minilogin (after a long string of EQEmuLoginServer.exe crashes,) I got the server to appear in the server list. I click on the server name, press the start button and the game locks tight. The only error I get is in the World.exe window, which looks like this:

[Debug] [WORLD__INIT] Loaded default rule set 'default'
[Debug] [WORLD__INIT] Clearing temporary merchant lists..
[Debug] [WORLD__INIT] Loading EQ time of day..
[Debug] [WORLD__INIT] Loading launcher list..
[Debug] [WORLD__INIT] Reboot zone modes ON
[Debug] [WORLD__INIT] Deleted 0 stale player corpses from database
[Debug] [WORLD__INIT] Deleted 0 stale player backups from database
[Debug] [WORLD__INIT] Purging expired instances
[Debug] [WORLD__INIT] Zone (TCP) listener started.
[Debug] [WORLD__INIT] Client (UDP) listener started.
[Debug] [NET__IDENTIFY] Registered patch 6.2
[Debug] [NET__IDENTIFY] Registered patch Titanium
[Debug] [NET__IDENTIFY] Registered patch SoF
[Debug] [WORLD__LS] Connecting to login server...
[Debug] [WORLD__LS] Setting World to MiniLogin Server type
[Debug] [WORLD__LS] Connected to Loginserver: eqs.zaphodsdeli.net:5999
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:1985
[Debug] [WORLD__CONSOLE] New launcher from 127.0.0.1:1985
[Debug] [WORLD__LAUNCH] Adding pending launcher 1
[Debug] [WORLD__LAUNCH] Launcher Identified itself as 'zone'. Loading zone list.

[Debug] [WORLD__LAUNCH] Removing pending launcher 1. Adding zone to active list.

[Debug] [WORLD__LAUNCH] zone: dynamic_01 reported state STARTED (1 starts)
[Debug] [WORLD__LAUNCH] zone: dynamic_02 reported state STARTED (1 starts)
[Debug] [WORLD__LAUNCH] zone: dynamic_03 reported state STARTED (1 starts)
[Debug] [WORLD__LAUNCH] zone: dynamic_04 reported state STARTED (1 starts)
[Debug] [WORLD__LAUNCH] zone: dynamic_05 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 0.0.0.0:0
[Debug] [WORLD__CONSOLE] Removing console (!tcpc->Connected) from 0.0.0.0:0
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:2009
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:2010
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:2012
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:2011
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:2013
[Debug] [WORLD__CONSOLE] New zoneserver #1 from 127.0.0.1:2011
[Debug] [WORLD__CONSOLE] New zoneserver #2 from 127.0.0.1:2012
[Debug] [WORLD__CONSOLE] New zoneserver #3 from 127.0.0.1:2010
[Debug] [WORLD__CONSOLE] New zoneserver #4 from 127.0.0.1:2009
[Debug] [WORLD__ZONE] [4] Zone started with name dynamic_04 by launcher zone
[Debug] [WORLD__ZONE] [4] Auto zone port configuration. Telling zone to use por
t 7000
[Debug] [WORLD__ZONE] [3] Zone started with name dynamic_02 by launcher zone
[Debug] [WORLD__ZONE] [3] Auto zone port configuration. Telling zone to use por
t 7001
[Debug] [WORLD__ZONE] [2] Zone started with name dynamic_01 by launcher zone
[Debug] [WORLD__ZONE] [2] Auto zone port configuration. Telling zone to use por
t 7002
[Debug] [WORLD__ZONE] [1] Zone started with name dynamic_03 by launcher zone
[Debug] [WORLD__ZONE] [1] Auto zone port configuration. Telling zone to use por
t 7003
[Debug] [WORLD__CONSOLE] New zoneserver #5 from 127.0.0.1:2013
[Debug] [WORLD__ZONE] [5] Zone started with name dynamic_05 by launcher zone
[Debug] [WORLD__ZONE] [5] Auto zone port configuration. Telling zone to use por
t 7004
[Debug] [WORLD__ZONE] New TCP connection from 67.228.211.210:1420
[Debug] [WORLD__ZONE] New TCP connection from 67.228.211.210:1773
[Debug] [WORLD__CONSOLE] Removing console (!tcpc->Connected) from 0.0.0.0:0
[Debug] [WORLD__ZONE] New TCP connection from 67.228.211.210:2935
[Debug] [WORLD__CONSOLE] Removing console (!tcpc->Connected) from 0.0.0.0:0
[Debug] [WORLD__CLIENT] New connection from 192.168.0.10:2024
[Debug] [NET__IDENT_TRACE] 192.168.0.10:2024: First opcode 0x32f did not match e
xpected 0x2792
[Debug] [NET__IDENT_TRACE] 192.168.0.10:2024: Tried patch 6.2_world, and it did
not match.
[Debug] [NET__IDENT_TRACE] 192.168.0.10:2024: First opcode 0x32f did not match e
xpected 0x2ec9
[Debug] [NET__IDENT_TRACE] 192.168.0.10:2024: Tried patch 6.2_zone, and it did n
ot match.
[Debug] [NET__IDENT_TRACE] 192.168.0.10:2024: First opcode 0x32f did not match e
xpected 0x4dd0
[Debug] [NET__IDENT_TRACE] 192.168.0.10:2024: Tried patch Titanium_world, and it
did not match.
[Debug] [NET__IDENT_TRACE] 192.168.0.10:2024: First opcode 0x32f did not match e
xpected 0x7213
[Debug] [NET__IDENT_TRACE] 192.168.0.10:2024: Tried patch Titanium_zone, and it
did not match.
[Debug] [NET__IDENT_TRACE] 192.168.0.10:2024: First opcode 0x32f did not match e
xpected 0x6c3c
[Debug] [NET__IDENT_TRACE] 192.168.0.10:2024: Tried patch SoF_world, and it did
not match.
[Debug] [NET__IDENT_TRACE] 192.168.0.10:2024: First opcode 0x32f did not match e
xpected 0x737e
[Debug] [NET__IDENT_TRACE] 192.168.0.10:2024: Tried patch SoF_zone, and it did n
ot match.
[Debug] [NET__IDENTIFY] Unable to identify stream from 192.168.0.10:2024, no mat
ch found.
[Debug] [WORLD__ZONE] New TCP connection from 208.43.133.130:3016


I have no idea what's going on. While running game servers is not new to me, EQEmu is. Any help that I can get is very much appreciated.

leslamarch
08-31-2009, 11:43 PM
[Debug] [NET__IDENTIFY] Unable to identify stream from 192.168.0.10:2024, no mat
ch found.
If you are using "minilogin" then you need to make sure you add your IP address to the account you wanna log in with. So find you account in the accounts table and look for minilogin_ip and add your IP there.

Zabeeble
08-31-2009, 11:55 PM
Excellent! I found a column for minilogin_ip in the PEQ DB account table. Problem is, I have no idea what other info I need to put there. Is there anything else I need to add?

Zabeeble
09-01-2009, 12:22 AM
Just adding the 192.168.x.xx address didn't help. Does anyone know else have an idea how to fix this?

leslamarch
09-01-2009, 07:51 AM
Are you getting a new error after filling in the account info?
what client are you running?

Zabeeble
09-01-2009, 09:33 AM
It was with the latest version of EQEmu, all maps and quests from SVN, following the directions in the Updated Window Server Setup Guide (http://www.eqemulator.net/forums/showthread.php?t=29043). But, after downloading and installing the AX Classic Server repack, I still get the same error. Could it be that after I install the game I let it upgrade to the latest version? Like I said, I'm a noob at EQ, so let me know.

leslamarch
09-01-2009, 09:41 AM
if it went to the patcher you will have to reinstall your client, and create the shortcut using the info on this page (http://www.eqemulator.net/wiki/wikka.php?wakka=EQEmuFAQ)

Zabeeble
09-01-2009, 10:04 AM
Okay. I goofed up then. No prob. I'll try that now. Thanks mucho for the help.