Quote:
Originally Posted by Zothen
Tyvm for the info! 
Having a clean Titanium install, how come I get an op_code error for "titanium_patch" ? Thats still the part I dont get. |
You get it because it's an opcode that has no purpose and we never mapped it to something that has a purpose, it's not needed for running a server because we don't need it (or we haven't found a use for it)
Quote:
[04.19. - 21:08:23] [NET__IDENT_TRACE] 127.0.0.1:63227: First opcode 0x4dd0 did not match expected 0x2792
[04.19. - 21:08:23] [NET__IDENT_TRACE] 127.0.0.1:63227: Tried patch 6.2_world, and it did not match.
|
This just means it didn't match the patch it is trying. It checks all of the patches registered to what it is expecting (in this case, it's the enter world opcode) and when it finds it, it stops looping through them. This is normal, and log files aren't always bad things, even if they are filtered under error.
Threaded Mode
