Cheat Engine

[raelharris]

Hi guys, I have noticed something odd about using pointers in Teleglitch,

When I hack this game and try to find base addresses and use pointers to make my codes permanent, I had problems closing the program and entering it again because it interferes with the memory locations of where certain values are held. I thought that pointers are supposed to fix this issue. So now while I can now save my "cheats" to use later, sometimes they will stop working on a value like health etc right in the middle of the game.

And to my second question, I have noticed something really interesting: Teleglitch: Die More Edition seems to reference the exact same base address (found using pointers) for every single ammo type! When you add a new address for what you think will be a new weapon's ammo, it "unlinks" itself from the old weapon ammo and only alters the values of the new weapon ammo. None of these pointers save properly either it would seem. I have no idea why it does this and whether or not I'm doing something wrong.

Can anyone perhaps give some pointers on pointers?

[raelharris]

Bump

[++METHOS]

If pointers aren't working, use injection.

[raelharris]

What is injection?

[Gniarf]

[raelharris]

Hi Gniarf,

Thanks for your detailed answer. I some responses to the things you mentioned below. Sorry that my images are attachments. The forum won't let me paste urls.

[Gniarf]

[AltairPL]

In your case 03E9D314 is current value address - if changing it in CE changes value in game, it's good.
What you get from Find out what writes to this address is info that FC is probably last offset of the pointer, which can speed up search for pointer.
If you have value address entry in list, right-click on it and select Pointer scan for this address. Option Stop traversing... can decrease number of found pointers and in most cases should be sufficient. Since you know that FC is most likely offset, click on Pointers must end with specific offsets and type FC in the field.
When scan is done, do something like changing area, restarting the game or even steam. When you're back in game you have two options:
- find current value address and do pointer rescan using new address or
- do pointer rescan using current value
To do pointer rescan, select Pointer Scanner -> Rescan memory in pointer scan window, select Address/Value to find and enter in the field address/value (respectively) and hit OK.
Do this few times and list of possible pointers should decrease considerably - with luck, to single one, but that doesn't mean that only one pointer is valid. Most likely, valid pointers will have a base address like "teleglitch.exe"+ but that depends on the game.
If you add pointer to the address list, its address will be displayed as P->03E9D314 and should always point to the address where value is stored. If you double-click on this address you will see window similar to Add address window from your Adding base addresses.PNG. 2 represents base pointer address, positions below 3, like FC in your screenshot, are offsets. Close this window without changing anything and you should be good to go.

Have fun!

[raelharris]

Thank you Gniarf and AltairPL for your awesome responses!

I looked up some tutorials on pointer scanning last night and I am trying it out. I did not know that I could use the "Pointers must end with specific offsets" option to speed things up.

Right now I am at work so I'm unable to test it till this evening, but I cannot wait to give it all a try and let you know how it goes!

[raelharris]

Good news! Following your advice and reading the "Pointer Information" tutorial by inuyasha0011, I Managed to find my first base value! It seems stable and it works every time I load the game. (It is infinite health for Teleglitch.)

Ammo still seems to stump me though. When I search for it I always get 3 addresses. The strange thing is that they are all the same address but are of different value types. How can a single address be both 1 byte, 2 bytes and 3 bytes at once? Also when I run a pointer scan for these and filter using offset FC (which I got by checking what writes to the address) as AltairPL suggested, I ultimately end up with 0 results. (I have attached images detailing my process for anyone who wants to try and help me work out what I'm doing wrong.)

(If anyone wants my infinite health base address and my pointer scan files please let me know how I can send them to you.)

[Gniarf]

[raelharris]

Hi Gniarf,

I am trying the pointer scan again.

I doubled the max offset and max level values. I have 3TB HDD space so I think it should be fine... I hope.

Thank you for the lesson on understanding how bytes are written. I'm not sure I understand how the e in ecx tells you that it's 4 bytes though.

As for your question about the multiplied variable *4, I never saw anything like that. However I only pay attention to the line highlighted in red when looking at what writes to my scanned addresses. Should I be looking elsewhere? I do not see anything bigger than 0x800, I think... (Is that the same as writing 00 00 08 00? As in... 2048 when converted to decimal?... Hang on... That is the same number as what my max offset was! Is there a link?

[Gniarf]

[AltairPL]

[Gniarf]