Decompiled Engine

Thanks. But most of us decompile the engine anyway to see what type of coding we're dealing with. And are you sure YOU decompiled it? Because it's not supposed to be in a .txt file, instead a .dll and another application:

_$dir.exe

oh, nvm, you just opened the .dll with notepad. I see. Thanks anyway!

Win Win for you!

This is very interesting... but i'm not sure what i could use it for...

Very useful! This can be very helpfull!

yAY NOW I DONT HAVVE TO LOOK FOR THE ADDIES FOR HACKS

It looks like just a bunch of calls to windows internal functions. It is not a decompilation. It is as the .txt file says: "Module Dependency Tree" which shows which Windows modules it is accessing. Some of it may be important, I would need to know a lilttle more about how Windows works and what method you used to get this data, otherwise its gibberish.

There's no order. It doesn't even show any of the Engine's own function so there's this huge list of function calls and we don't even know why they were called or in what instance. All applications usually end up calling a bunch of Windows internal functions. I would have to look through the whole damn list and cross reference it with the hacksheild components stated here: http://www.mpgh.net/forum/207-combat...-analysis.html See this list contains only the specific modules used by Hackshield. We don't need to know all the Windows components.

But it's already known that Hacksheild uses these methods. The important thing is how they are called and in what order, what is returned, etc.

hmm ill try to take out the code that checks for hack shield -_- this gonna b hard, anyway good thread!

its not a decompile, it's just asm... but weird asm... what program did you use to get this?

I can't remember what program I decompiled it with.
LOL
FML