paul44 Expert Cheater Reputation: 2
Joined: 20 Jul 2017 Posts: 152
|
Posted: Sat Dec 03, 2022 8:53 am Post subject: Break Condition on 'memory location' |
|
|
I'm currently looking at COD AW...
(bizar engine as i haven't come across a single struct with VFT yet ?! written entirely in "native" C perhaps ?)
The problem: some values (such as cloak, health hover tank and many more) are managed through the use of a (fixed) number of static mem_locations (~ stack-like). That means that the mem_location i'm interested in, is constantly being overwritten by all sorts of values.
Based on some condition for sure, the 'correct' value is then written to my final mem_location; which holds the actual value I've scanned/found.
So, I know which 'static mem_address' updates the health value, but I needed to find the opcode that updates the health value in that 'static mem_location'... (and "of course", that static mem_location is updated constantly by 100+ opcodes, so...)
After all sorts of Trial&Errors, i eventually took this approach: [ https://imgur.com/a/73UEirE ].
The break&trace detail gave me - part of - the proper subroutine. and after some additional tests at the start of that routine, i was able to locate the opcode that actually updated the static_memlocation itself... (which btw is - again - updated by some other 'static mem_location' )
=> still, it allowed me to build a proper cheat for that.
BUT: my question is actually: is there another/better way to apply a 'break condition' on a (changing) value ?
(similar to what one can do in the Mem_viewer with opcodes)
ps: i also tried to save the 'break & trace' but got this stream error ?! (saving to textfile is no problem - 200+GB diskspace) - using v7.2 atm
(i got some very specific Qs related to this feature, but will probably open a new topic on that one)
|
|