you also talk about sending the correct checksum to be able to loot corpses
Id like to address this first.
the checksum has nothing to do with looting corpses, what I do, is just intercept the opcode for looting and then call the correct function for it.
so does this mean eqgame.exe and eqgame.dll are now interacting and matching correctly, thus no longer sending the wrong checksum to the server every 2 seconds like the Secrets client did?
From what I can tell by looking at his eqgame.dll it does two things, 1. same thing as I explained above regarding to loot.
2. detour getmodulefilename.
now I do the EXACT same thing in my eqgame.dll, with only one minor difference, his dll needs a static c:\eqmac path, mine doesn't.
There is NO WAY his version of eqgame.dll (or mine) have anything to do with the wrong checksum being sent.
Let me explain:
So the client (eqgame.exe) wants to tell the server a few "checksums" during the course of you playing.
One of those is its own, another is the one for spells_en.txt and there is one for guilds as well, and a couple others, I don't want to go into all of them here, but those are the main ones.
Ok, so lets talk about the eqgame.exe one first:
eqgame.exe calls getmodulefilename to get its own path (this is where we return the path to "eqmac.exe" instead)
then it does a crc32 on the whole file and the result is a hash which is sent to the server.
Same thing goes for spells_en.txt and so on, but since we never make any changes to those files, there is no reason to circumvent those checks in any way.
IF a user edits his spells file for example, THEN the checksum will be wrong, BUT THAT... that is not my (or secrets) fault.
If the user replaces the eqmac.exe with another version, well then the wrong checksum will obviously be sent, again, that's not our problem either.
IF there was a scenario where the wrong checksum was sent, it just meant the user has the wrong eqmac.exe or wrong spells_en.txt or some other file that's checked which does not match the latest mac patch. Im pretty sure one of the secret zips out there like the 1.0 one had an old version of eqmac.exe and if people used that one, yes absolutely they would be playing with a client that sent wrong checksums... Im not so sure about the 1.1 zip, but I think that too had an outdated eqmac.exe in it, I see that as a userproblem though, they could have just updated their version by taking the everquest file in the macos directory and renamed it eqmac.exe and they should have been fine. (Of course this is not easy for ordinary users to keep track of, let alone understand, so I don't blame anyone for not knowing that, in any case, use my zips from now on and I will update them when needed if there is another patch)
