Some Addies
You cant find Engine.exe in olly cause HS hooks OpenProcess sooo tobad and i just said all these YOU GOT TO NOP WILL YOU READ YOU CAN NOT JUST SET THE ADDIES. and another thing you cant make a trainer unless u make a kernel driver cause HS also hooks ReadProcessMemory and WriteProcessMemory
Hey before you go making big words and such you mind explaining to us How many bytes to NOP. If we can't view Engine.exe like you said, then how do you expect us to know the size of the instructions.
Well buddy u seem smarter than most of these people that posted in this thread its not going to you as u understand what is say anyways. I shall not post how many nops or the bytes cause i already know what would happen,people will just copy and paste and release hacks with no credits. I do not release full source codes ever due to that im sorry but to find out is bypass + CE=win.
and another thing you cant make a trainer unless u make a kernel driver cause HS also hooks ReadProcessMemory and WriteProcessMemory
Haha. Oh lol, that made me laugh. 
Still though I thought you couldn't code a kernel driver in VB. Has to be C, or asm, because you don't have access to .NET, unless you go with a .dll which is a better approach anyway. ( I figure that's what you meant)
Oh and BigBoy, I appreciate you giving out the addies and everything, but kind of defeats the point, well let me correct that. Make it a bit harder to do without a bypass or telling us the number of bytes to write. In any case your right. People are gonna leach your code all over the place, but I figured you expected that before you released the addies. In anycase I don't know how to code a kernel driver, but thx for the headstart with the addies anyhow. Can't blame you for not releasing everything.

Still though I thought you couldn't code a kernel driver in VB. Has to be C, or asm, because you don't have access to .NET, unless you go with a .dll which is a better approach anyway. ( I figure that's what you meant)
Oh and BigBoy, I appreciate you giving out the addies and everything, but kind of defeats the point, well let me correct that. Make it a bit harder to do without a bypass or telling us the number of bytes to write. In any case your right. People are gonna leach your code all over the place, but I figured you expected that before you released the addies. In anycase I don't know how to code a kernel driver, but thx for the headstart with the addies anyhow. Can't blame you for not releasing everything.

i might release a bypass just wait
I think nop is 144... my friend looked it up awhile ago and i think thats what i was... (Can't remember)
NOP is 0x90.
Also the size to write could be of variable length depending on the instructions.
EDIT:.... hmmm 0x90 is 144 in decimal I think.., my bad. just no one does it in decimal like that =/
Also the size to write could be of variable length depending on the instructions.
EDIT:.... hmmm 0x90 is 144 in decimal I think.., my bad. just no one does it in decimal like that =/
xD im different :P
This thread is closed for replies.

