Regardless of a compression check, or a CRC, the easiest thing to do would be to eliminate the problem. Since he is able to bypass HS and use an assembly analyzer (Olly, CE, etc), I'm pretty sure he could step through the loading process until it catches the function that kicks you. Buttttt, doing just that is probably a pain in the ass. But you know what? Be happy this is something that can be literally NOP'd on the client-side of things.
I'm sort of wondering if Trion has AA utilize Hackshield to the point of detecting memory modifications done directly to the libraries initialized. While I could very well check, I'm assuming Plox has checked this himself. o:
At the moment, HS looks like plain ol' wrapper for this game.
-----------------
On a side note, it might be in someone's best interest to go find the switch which enables folder data load -- I mean who enjoys packing this shit? It'd make on-the-fly tests easier too. I won't ask for it though, I'm just a player! :)
I'm sort of wondering if Trion has AA utilize Hackshield to the point of detecting memory modifications done directly to the libraries initialized. While I could very well check, I'm assuming Plox has checked this himself. o:
At the moment, HS looks like plain ol' wrapper for this game.
-----------------
On a side note, it might be in someone's best interest to go find the switch which enables folder data load -- I mean who enjoys packing this shit? It'd make on-the-fly tests easier too. I won't ask for it though, I'm just a player! :)