View Single Post
  #3  
Old 09-11-2011, 07:46 PM
Dekt
Fire Beetle
 
Join Date: Aug 2010
Location: FairyVille
Posts: 27
Default

Yeah, when I first encountered the problem I ran into your post on the forums allready and tried it. It didnt work for me, so I just made sure I did every patch 1900+ and still no change.

However I have noticed that when I log into the server from server select, it will say that SoF_patch did not match, SoD, Titanium 6.2 none of them match.

Here is a cut out of the log file..

[09.11. - 18:39:37] [ZONE__INIT] Starting EQ Network server on port 7004
[09.11. - 18:40:51] The next weather check for zone: nexus will be in 7380 seconds.
[09.11. - 18:40:51] Zone: nexus has weather of type 0.
[09.11. - 18:40:51] Zone: nexus(152) has no weather type. The weather timer has been disabled.
[09.11. - 18:40:52] [WORLD__CLIENT] New connection from 192.168.1.3:62090
[09.11. - 18:40:52] [NET__IDENT_TRACE] 192.168.1.3:62090: First opcode 0x3594 did not match expected 0x2792
[09.11. - 18:40:52] [NET__IDENT_TRACE] 192.168.1.3:62090: Tried patch 6.2_world, and it did not match.
[09.11. - 18:40:52] [NET__IDENT_TRACE] 192.168.1.3:62090: First opcode 0x3594 did not match expected 0x2ec9
[09.11. - 18:40:52] [NET__IDENT_TRACE] 192.168.1.3:62090: Tried patch 6.2_zone, and it did not match.
[09.11. - 18:40:52] [NET__IDENT_TRACE] 192.168.1.3:62090: First opcode 0x3594 did not match expected 0x4dd0
[09.11. - 18:40:52] [NET__IDENT_TRACE] 192.168.1.3:62090: Tried patch Titanium_world, and it did not match.
[09.11. - 18:40:52] [NET__IDENT_TRACE] 192.168.1.3:62090: First opcode 0x3594 did not match expected 0x7213
[09.11. - 18:40:52] [NET__IDENT_TRACE] 192.168.1.3:62090: Tried patch Titanium_zone, and it did not match.
[09.11. - 18:40:52] [NET__IDENT_TRACE] 192.168.1.3:62090: First opcode 0x3594 did not match expected 0x6c3c
[09.11. - 18:40:52] [NET__IDENT_TRACE] 192.168.1.3:62090: Tried patch SoF_world, and it did not match.
[09.11. - 18:40:52] [NET__IDENT_TRACE] 192.168.1.3:62090: First opcode 0x3594 did not match expected 0x737e
[09.11. - 18:40:52] [NET__IDENT_TRACE] 192.168.1.3:62090: Tried patch SoF_zone, and it did not match.
[09.11. - 18:40:52] [NET__IDENT_TRACE] 192.168.1.3:62090: First opcode 0x3594 did not match expected 0xff4
[09.11. - 18:40:52] [NET__IDENT_TRACE] 192.168.1.3:62090: Tried patch SoD_world, and it did not match.
[09.11. - 18:40:52] [NET__IDENT_TRACE] 192.168.1.3:62090: First opcode matched 0x5a6b and length matched 68

So, what I thaught this could have been I was that somehow my DB was out of sync and something was newer. So I Deleted to patches from my server folder and updated the resources folder via SVN, then re copied them back into my server folder after the update.

Any other ideas?

Thanks!
Reply With Quote