|
Cheat Engine The Official Site of Cheat Engine
|
View previous topic :: View next topic |
Author |
Message |
coffeeAchiever Newbie cheater Reputation: 0
Joined: 27 Dec 2014 Posts: 22
|
Posted: Sun Dec 17, 2017 3:06 pm Post subject: Duke Nukem 3D: Lazy Programmers and Game Crash |
|
|
I was looking for gun bullets in Duke Nukem 3D. After about 20 seconds I found a single green address.
My understanding is that green addresses mean variables pre-allocated in the .data segment. In other words, local static or global variables. But these variables are no relocatable. If gun bullet number is held at green address #0192D89C today, it'll be held at the same place tomorrow. Right?
As a test I killed the game and reloaded. Sure enough, #0188D89C held gun bullets.
Question #1: Is it a general rule of thumb that when I see a green address in the scan section, my work is done?
Just to play around because I like using CE to learn, I tried to find out what writes to this address. When the debugger is attached, whenever I shoot the gun, the game immediately crashes.
Question #2: Does that have anything to do with the address being a global / static local? Is there a way to prevent the crashing? I tried to switch the Preferred breakpoint method to Int3, but the game still crashed. What should be done in a situation like this?
Edit: When I restarted the game, I noticed something really strange.
Question #3: My scanned address is still #0192D89C, but when I attached CE to the game again, the stored address changed to #006DD89C. Why? What's going on here?
Thanks!
|
|
Back to top |
|
|
OldCheatEngineUser Whateven rank Reputation: 20
Joined: 01 Feb 2016 Posts: 1587
|
Posted: Sun Dec 17, 2017 3:37 pm Post subject: |
|
|
coffeeAchiever wrote: | Question #1: Is it a general rule of thumb that when I see a green address in the scan section, my work is done? |
no, not all games will define their variables as static.
coffeeAchiever wrote: | Question #2: Does that have anything to do with the address being a global / static local? Is there a way to prevent the crashing? I tried to switch the Preferred breakpoint method to Int3, but the game still crashed. What should be done in a situation like this? |
switch to another debugger, goto settings -> debugger settings -> VEH debugger.
and make sure you havent attached the debugger yet, otherwise you have to restart CE to change the debugging method.
coffeeAchiever wrote: | Question #3: My scanned address is still #0192D89C, but when I attached CE to the game again, the stored address changed to #006DD89C. Why? What's going on here? |
nothing going on, its normal.
0{000}0000 usually these digits change, but as long as you have the module address you are fine.
module address like:
example when you click on the address:
"duke3d.exe"+12345
simply save the CT (cheat table)
and then whenever you load CE, CT and the game you will get your address.
_________________
About Me;
I Use CE Since Version 1.X, And Still Learning How To Use It Well!
Jul 26, 2020
STN wrote: | i am a sweetheart. |
|
|
Back to top |
|
|
|
|
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
|
|