Preferably it would be an instruction that doesn't also access other addresses, but you could do something like step 9 of the CE tutorial to fix that. What exactly did you mean by "dig deeper" in your first post? If you just want to automatically find the address, try the pointer scanner (use multiple pointer maps - tutorial) or make a code injection to copy the address ("injection copy") on any access to that address. (this is getting a little advanced - I can't explain what to do both sufficiently and succinctly, and beginners would have a hard time doing this on their own) In that little amount of code, "inc ecx" makes me think that instruction is being run in a loop. Where Opt.01 points to the option count from the ingame hotkey. Now in the hotkeys dialogbox you will see this hotkey as Opt.01. You could look at the callstack and compare/contrast the callers and arguments of different invocations of that function, but I'm not sure how much that would help in this case. on one hotkey from the ingame hotkeys section below: 1 NUMPAD1 Toggle Infinite Health. A trace can only look at where it started and go from there.
0 kommentar(er)
