It is xored, but it isn't just a simply XOR byte,0xED.
There are 3 xors.
Printable View
It is xored, but it isn't just a simply XOR byte,0xED.
There are 3 xors.
Okay... enough with the OT please.
It's fair enough when people are trying to figure out why the OP doesn't explain how the DLL is used for packets and SQL and files and whatever else. A: because it's isn't ever!
But now we know that, and I've updated the OP so that I hope that is now blatantly clear without having to go down the pages of OT posts to get that clear in your head right from the start.
Let's not go into how those things are achieved here please. Except, maybe to say, if you where hoping to find out blah... this isn't the place, you want... [link to appropriate guide]
Right now, I think the protocol.dll guide / release is the best there is... though there are some high level implementations of "bits" of that floating around. I'm hoping someone who could make more sense of protocol.dll (or the same routines in GFantasy section) could explain how they work; what parameters they take, and how they use those to modify the packet buffers. (I've never quite got my head around it, or I'd have re-released a C version of the DLL source)