Cheat Engine

[DrNOP]

I've made a German translation.

I decided not to translate the CE program strings, because that would lead to misapprehension in forum questions etc.
So I've translated only the tutorial (and added a translation of the lclstrconsts.po made by someone else.

Note: I have changed some text in Tutorial step 8, because the original text described the procedure only suboptimally

Here's what I changed (translated back to English)

_______________________________________________________

This step will explain how to use multi-level pointers (chained pointers, traversing multiple levels).
In step 6 you had a simple level-1 pointer, with the first address found already being the real base address.
This step however is a level-4 pointer. It has a pointer to a pointer to a pointer to a pointer to a pointer to the health.

You basically do the same as in step 6. Find out what accesses the value, look at the instruction and what probably is
the base pointer value, and what is the offset, and already fill that in (Add address manually) or write it down. But in this case the address
you'll find will also be a pointer. You just have to find out the pointer to that pointer exactly the same way as you did
with the value. Find out what accesses that address you found, look at the assembler instruction, note the probable
instruction and offset, and use that for [New Scan] (Hex).
and continue till you can't get any further (usually when the base address is a static address, shown up as green)


OLD:
Click Change Value to let the tutorial access the health.
If you think you've found the pointer path click Change Register. The pointers and value will then change and you'll have 3 seconds to freeze the address to 5000

Extra: This problem can also be solved using a auto assembler script, or using the pointer scanner
Extra2: In some situations it is recommended to change ce's codefinder settings to Access violations when encountering instructions like mov eax,[eax] since debugregisters show it AFTER it was changed, making it hard to find out the the value of the pointer


NEW:
Detailed description:
Scan for the address of the Health value.
Find out what accesses this address, look at the assembler instruction, and read the probable base pointer and the offset.
Enter the base pointer as [X] Hex for a [New Scan].
Close the code finder window with [Stop] and then [Close], because there is only a restricted number of breakpoints available.
[Add Address Manually], [X] Pointer - add the address found AND the offset found in the previous code finder scan.. (Check: the value in the 'Value' column has to be the Health value).
(LOOP:) Now find what accesses this pointer again. Enter the address found as a new pointer, along qwith the offset. Now we are at level 2, so click [Add Offset] to add a new offset field. Here you enter the offset found in the first scan. So now there is a pointer field and TWO offset fields.
Continue (from LOOP:), until the scan result shows a green (static) Address.
Always make sure that the value (column 'Value') equals the Health value.
(In case it's displayed as hexadecimal, right-click | Show as decimal)
If you find multiple addresses, you must try them; the code finder will not find a correct result when used with a bogus address.

Once to think you found the pointer, enter 5000 as the value and check 'Active' (=freeze). Click [Change pointer]. After a few seconds, the [Next] button should be activated.


Extra: This problem can also be solved using an auto assembler script, or using the pointer scanner.

Extra2: In some situations it is recommended to change ce's codefinder settings to Access violations when encountering instructions like mov eax,[eax] since debugregisters show it AFTER it was changed, making it hard to find out the the value of the pointer

Extra 2: sometimes you'll need to get the correct register values from a breakpoint, because in code finder, you see the register values AFTER the the instruction's execution. An instruction like MOV ESI,[ESI] will possibly show the wrong value then.


"Extra3: If you're still reading: you might notice that when looking at the assembler instructions, that a pointer is being read and written within the same routine. This doesn't always happen, but can be really useful for finding a pointer when debugging is troublesome.
_______________________________________________________

I hope you agree with this, DarkByte

Download the translation files here: datendienst . com/users/DrNOP/languages.zip