 |
Cheat Engine
The Official Site of Cheat Engine
|
| View previous topic :: View next topic |
| Author |
Message |
atom0s
Moderator
 Reputation: 205
Joined: 25 Jan 2006
Posts: 8587
Location: 127.0.0.1
|
 Posted: Fri Feb 15, 2013 9:33 pm Post subject: |
 |
|
How are you writing them in your trainer? If you are writing one byte at a time, it'll have the potential of crashing. If you write the entire change at once you'll have a lesser chance of crashing.
If you still want to pause the game, obtain the main thread handle of the application and suspend it with SuspendThread. Afterward, do your edit and resume with ResumeThread.
_________________
- Retired. |
|
| Back to top |
|
 |
justa_dude
Grandmaster Cheater
 Reputation: 23
Joined: 29 Jun 2010
Posts: 893
|
| Posted: Mon Feb 18, 2013 8:52 am Post subject: |
|
|
| Tarek701 wrote: | Well, when I press the Hotkey F, it shall write the byte: "144" to all opcodes. With G you can toggle it back. (It writes the correct bytes to the opcodes) This worked 3-4 times. It varies. However, when I pressed F again, it didn't write the opcodes fastly enough. The client reacted faster than the trainer and the client crashed.
Also, good idea with the suspendthread. I might try that. |
I'm thinking that CE wraps those memory writes inside critical sections, so something like:
RobloxPlayer.exe+57F31A:
db 90 90 90 90 90
nop
would work.
Show us what you're doing. Are you only nopping out the first line in the excerpt you're posting?
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
