Then if that looks good then just watch individual hooks for stray addresses and values, say during cut scenes or where ever I think that the problem may be. And then if all looks good there I just hook a base address and start the watching over again (having still not modified any values). 1 DS3 Cinders: CE Item IDs 2 Goods 3 Weapons and Catalysts 4 Shields 5 Ammunition 6 Spells 7.
Activate the trainer options by checking boxes or setting. And just watch, not just for stray addresses but play though for a bit and see if I get crashes from just the debugger (adjusting settings as I go). Click the PC icon in Cheat Engine in order to select the game process. Then just attach the debugger to an instruction (one that I might be using in another table already). If I fill confident in this then I just start a new table find a simple, easy to find value, save the address or byte pattern to an instruction that accesses it to the table in a script for just notes.
Well my approach with a situation like that is to step back, in any trouble areas try it with a new save and make sure it's not the game or OS or an update for either.
0 kommentar(er)
