- Joined
- Aug 5, 2010
- Messages
- 316
- Reaction score
- 87
If you try to use speed hack, it works. but CE crash.
Alright it only had speed hacks blocked.
And cheat engine 6.1 is what i used to test speed hacks with ...
"CheatEngine Speed hack wont work at all. -> Cheatengine crash"
Addres scanning in Flyff is pretty much useless lol.
But i will try blocking that too...
She means cheat engine x64. Address scanning is not useless, I can spawn items on eFlyff(along with a full packet editor) thanks to being able to use memory scanning of cheat engine x64.
Remember, any experienced windows hacker can tear apart something like gameguard in a couple hours. You're best off with obfuscation and cutting off easy access points for hackers.
Alright then I will try blocking it.She means cheat engine x64. Address scanning is not useless, I can spawn items on eFlyff(along with a full packet editor) thanks to being able to use memory scanning of cheat engine x64.
Remember, any experienced windows hacker can tear apart something like gameguard in a couple hours. You're best off with obfuscation and cutting off easy access points for hackers.
She means cheat engine x64. Address scanning is not useless, I can spawn items on eFlyff(along with a full packet editor) thanks to being able to use memory scanning of cheat engine x64.
Remember, any experienced windows hacker can tear apart something like gameguard in a couple hours. You're best off with obfuscation and cutting off easy access points for hackers.
Wow, is that true? :?:
No bro, he actually just buys Gpots with his donation money from Demon.Wow, is that true? :?:
No bro, he actually just buys Gpots with his donation money from Demon.
seems that cheat engine x64 speed hack stil works I will figure out why
Alright then I will try blocking it.
Most packet editor shouldn't be working anymore.(The released ones).
Lol I'm kinda curious how you do that :/
Basically I detoured the CClientSock::Send() function after I found the pointer to the function in memory. Of course, Gameguard interfered when I detoured a function within neuz's address space. However, Gameguard uses mostly x86 winapi calls, so it was quite simple to detour the memory modification checks it used.
Once I had CClientSock::Send() detoured, it was all too simple to exploit eFlyff's lax serversided security. I also have a few other holes in their security that may be useful in the future.
Now, if Gameguard was a proper antihack that actually blocked x64 kernel calls, it still would've been simple to defeat once you were able to get the client to run in a VM. Clientsided security is only meant to stop kids from messing around with the client.
Basically I detoured the CClientSock::Send() function after I found the pointer to the function in memory. Of course, Gameguard interfered when I detoured a function within neuz's address space. However, Gameguard uses mostly x86 winapi calls, so it was quite simple to detour the memory modification checks it used.
Once I had CClientSock::Send() detoured, it was all too simple to exploit eFlyff's lax serversided security. I also have a few other holes in their security that may be useful in the future.
Now, if Gameguard was a proper antihack that actually blocked x64 kernel calls, it still would've been simple to defeat once you were able to get the client to run in a VM. Clientsided security is only meant to stop kids from messing around with the client.
lethal = smart and alot of time on his hands to figure that out all that out
Nice! By the way, I have some question about xor guard. It's really blocked the memory modification or what..? 'Cause I tried to modify the old version of CE x86 version, speedhack was works. :?: