SoF client issue with MySEQ

seamerc · #1 07-15-2009, 11:45 PM

I dont know if its related to anything, but the date and time sent to the client by the server in SoF (opcode 0x7274) has something weird going on with it inside the client.

I was putting together some memory offsets for MySEQ, to use with the SoF client but when it reads the correct memory location, its blank. I used IDA to go thru eqgame.exe and confirmed the offset is correct. I also confirmed that I had the right memory offset for finding the in game Date/Time too.

I checked it was working as expected with Titanium client and the client used for SoD. But something is not going correct with SoF. I am not sure if anyone else has ideas, or if this may be related to other issues. ShowEQ reads the Date/Time fine, but it does not read from the client, using the 0x7274 opcode. I am still learning to use IDA and to work with the EQEmu server. I plan to look more at what is going on, but I thought I would meantion it to see if anyone has any ideas. I am trying to learn more to contribute as I am new to the EQEmu scene.

Razzle

**trevius** · #2 07-16-2009, 12:14 AM

Well, we have that opcode set in SoF_patch.conf already:

Code:

OP_TimeOfDay=0x7274 			#SEQ 12/04/08

So, as long as the packet size/structure hasn't changed, it should work fine.

seamerc · #3 07-16-2009, 12:28 AM

I checked the opcodes SoF_patch.conf, and confirmed that it was correct. The packet size/struct did not change. I checked that too. That was the issue, everything was where it should be to work correct. I checked with IDA on the executable to find the memory offset. I confirmed this with pattern recognition searches in the executable, and with the offsets found in MQ2 when the version was live too. Everything matched up. I went in and looked at the memory the pointers were going to, and the data was not there. I got SEQ running with, and looked at the packet info, it was going over to the client correctly from the server.

Is anything being done to with the obfusicator opcode? I know when this version of the exe was live, they were doing obfusication with the opcodes. Does this client need possibly a default value, or null value so to speak? Has anything been looked at concerning this before? I am just looking for possibilities, not sure where to look.

Razzle