![]() |
OPCodes addresses in ASM keeps changing!
I haven't worked on trainers for awhile and I have a really bad memory.
The problem is, usually the memory dump addresses keeps changing which is why (from what I know) most people make trainers by poking addresses in the ASM code and changing the flow of the code (jumping into a code cave and back when done) because those usually doesn't move.. But what do you do when even this keeps changing : Code:
(First run)The value i'm modifying is the "panic bar" which goes from 0(gameover) to 100(fullbar) in decimal. The question in short, what am I doing wrong? Okay so I finally finished the trainer, I'll upload the source code and link it once I actually release it. I have no idea why the memory is shifting but doing a pattern scan solves the problem. Basically you read a large portion of the process memory and compare it with the opcodes of the commands you're looking for. When found, you then know exactly where to inject the code. This is where I learned about it And here's the trainer's source code |
| All times are GMT -7. The time now is 02:40. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
FileForums @ https://fileforums.com