Changing Addresses
Changing Addresses
ok so i have a question, but i need to some intro first. Here it is:
Intro:
When Combat Arms updates the memory addresses for certain certain values are changed. This prevents people fro using old hacks after updates.
Question:
So Do the people at Nexon do this intentionally? It seems to me they right their code in whatever High-level language they use, then they save it as a Win32 executable file. The Memory locations are allocated by the Win32 Compiler which is (cl.exe... am i right here?). Anyway so do the memory locations change just because the file has changed and not because Nexon pointed out exactly which memory addresses a value should be stored in?
Intro:
When Combat Arms updates the memory addresses for certain certain values are changed. This prevents people fro using old hacks after updates.
Question:
So Do the people at Nexon do this intentionally? It seems to me they right their code in whatever High-level language they use, then they save it as a Win32 executable file. The Memory locations are allocated by the Win32 Compiler which is (cl.exe... am i right here?). Anyway so do the memory locations change just because the file has changed and not because Nexon pointed out exactly which memory addresses a value should be stored in?
If they were to use a (I believe this is called that) Dynamic address, it would change every time you open Combat Arms to a completely different address.
The ones that are static, may be changed purposefully, but after some updates the hacks still work, meaning it might not be the compiler.
Don't quote me on this, though. I'm pretty stupid.
The ones that are static, may be changed purposefully, but after some updates the hacks still work, meaning it might not be the compiler.
Don't quote me on this, though. I'm pretty stupid.
