Maybe that it's not the correct address but if it is, I would find a pointer that is using that address or look few address up or down since you using float maybe 4 addresses up or down to find the correct one.
Another way is set the freezing interval with less milliseconds.
CE -> "Edit" menu -> "Senttings" -> "General Settings" section -> Change Freeze interval to 1 (ms) _________________
C,C++ and Vb6 programming
Assembly basics
DirectX 8,9 libraries knowledge
Reverse engineering with games & applications
Network structure's knowledge
Specialized in CPU/GPU overclocking
When I freeze the energy to...say 15000, the variable starts to flicker between a changing var (the real var) and the frozen var.
You have found the displayed value only which is frequently updated with the real value. This is why it flickers between the frozen value and the real value. Values like this can be useful in some cases if you know ASM (because you can backtrace the code and see where is the real value stored) but for beginners, they are pretty much useless. Maybe it is stored in another value type (try float and 4 bytes) or the real value could be stored in a completely different way. Try to scan again to find the real value. _________________
GrawCube!
Could you upload your current perimeter cheat table?
Please.
I'm sorry, but I don't have it anymore. I don't think I even have the game installed anymore
Anyways, the reason it was flickering was because I found the wrong variable, I changed the variable which only shows the text, not the energy value itself, as explained by Geri above.
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