Quote:
Originally Posted by #HB
That's actually a missing handler in the game server, parties should be removed from matching automatically if they were registered for +an hour.
Shard manager sends the packet to the game server, but for some reason the handler of it is missing and the opcode is unrecognizable by the game server. Which leads us to another question, is the game server really the same version as the shard manager?
Here's the timeout address in shard manager:
Code:
0045055C | 83F8 3C | cmp eax,3C | Party Matching Timeout
I've attached x64dbg patch to skip this part, so parties will last in matching forever. I've thought of disabling the timer itself, but I was scared if it would f*** something up, so I just skipped the timeout interval.
|
I'm sure the game server is same version as shard manager, because this happens in BlackRogue files too. So the problem must in our configuration instead of the module mismatching.