Tutorials:Cheat Engine Tutorial Guide x64 - Revision history

Lxb007981 at 04:00, 17 November 2024

2024-11-17T04:00:09Z

3rA: /* Step 9: Shared code */

2022-03-14T14:07:05Z

‎Step 9: Shared code

Edisecrinorthi: /* Step 9: Shared code - small spelling fixes */

2019-01-05T04:53:26Z

‎Step 9: Shared code - small spelling fixes

Edisecrinorthi: /* Step 8: Multilevel pointers - added pointer scan section */

2018-12-31T05:08:01Z

‎Step 8: Multilevel pointers - added pointer scan section

Toemik: Formatting fixes/improvements

2018-10-12T19:59:42Z

Formatting fixes/improvements

Dave11674: /* Step 6 */

2018-04-11T15:22:53Z

‎Step 6

TheyCallMeTim13 at 13:58, 19 March 2017

2017-03-19T13:58:15Z

TheyCallMeTim13 at 12:52, 19 March 2017

2017-03-19T12:52:52Z

TheyCallMeTim13: Created page with '

@@ Line 222: / Line 222: @@
 When choosing the code to find the base address for the pointer, try to select an instruction that doesn't write to the same register as the base address.
 Here we're interested in the value between the square brackets ('[' and ']'), so here we want the value of RDX.
 [[File:Tutorials.CETutorialx64.step06.02.png|border]]
@@ Line 233: / Line 237: @@
 Then the offset would be '12C' (0x12C), note that this is in hex.
-Now '''set the scanner for ''8 bytes'', ''exact value'', check the ''hex'' check box, then take the value found and put that as the value to scan for'''.
+Now we want to find out which pointer points to the interested address 012348D0 we found before. '''Set the scanner for ''8 bytes'', ''exact value'', check the ''hex'' check box, then take the value found and put that as the value to scan for'''.
 When ready '''click the ''first scan'' button'''.
@@ Line 241: / Line 245: @@
 [[File:Tutorials.CETutorialx64.step06.03.png|border]]
-'''Add one to the cheat table''', '''double click the ''address'' of the memory record''' that was added to the address list, copy the address then check the pointer check box, and paste the address in the pointers base address.
+Now we want to trace this pointer, so that whenever its content changes (which means it points to a different memory location), we will be able to modify the new memory address. '''Add the pointer we just found to the cheat table''', '''double click the ''address'' of the memory record''' that was added to the address list, copy the address then check the pointer check box, and paste the address in the pointers base address.
 :If you are unsure how to do this look here: [[Tutorials:Add_address_to_list|How to add addresses to the address list]]

@@ Line 549: / Line 549: @@
 [[File:Tutorials.CETutorialx64.step09.06.png|border]]
-So here we can see that the team variable is at offset 0x10 of the structure.
+So here we can see that the team variable is at offset 0x14 of the structure.
 Now we need to '''add some injection code to a script''', then '''add some code that checks the team variable of the structure''', to determine which actors are allies and which are combatants.

@@ Line 473: / Line 473: @@
 [[File:Tutorials.CETutorialx32.step09.01.png|border]]
-So here like the help text says there is far more then one solution.
+So here like the help text says there is far more than one solution.
 First we need to '''find one of the addresses and add it to the table'''.
@@ Line 485: / Line 485: @@
 So here it's good to understand what we're actually looking for to tell allies and combatants apart.
-When the game or engine is written, actors and players mite be written like this.
+When the game or engine is written, actors and players might be written like this.
 <!-- <pre>//// Actor, base for all actors
 class Actor(object){
@@ Line 620: / Line 620: @@
 Then you should see a form telling you that you have completed the tutorial.
 = See also =
 * [[Tutorials]]
 * [http://pinetools.com/syntax-highlighter Syntax Highlighter]

@@ Line 331: / Line 331: @@
 [[File:Tutorials.CETutorialx32.step08.01.png|border]]
 So here we will '''follow the same steps as step 6, except we'll see what accesses the base address we find''', and we'll '''keep repeating this until a static base is found'''.
@@ Line 455: / Line 457: @@
 [[File:Tutorials.CETutorialx64.step08.02.png|border]]
 '''After you have found the pointer, freeze it at 5000, then click the ''change pointer'' button'''.
 If you found the right base the next button should become enabled after about 2 seconds.
 So '''click the ''next'' button''' to go to the next step.
 = Step 9: Shared code =

@@ Line 19: / Line 19: @@
-== Step 1 ==
+= Step 1: Welcome =
 When the tutorial launches you should see some thing like this, you can just '''click the ''next'' button after reading the help text'''.
@@ Line 27: / Line 27: @@
-== Step 2 ==
+= Step 2: Exact Value scanning =
 So for step 2 you will see some thing like this.
@@ Line 65: / Line 65: @@
-== Step 3 ==
+= Step 3: Unknown initial value =
 When you start step 3 you should see the form looking like this.
@@ Line 112: / Line 112: @@
-== Step 4 ==
+= Step 4: Floating points =
 When you start step 4 you should see the form looking like this.
@@ Line 140: / Line 140: @@
-== Step 5 ==
+= Step 5: Code finder =
 When you start step 5 you should see the form looking like this.
@@ Line 207: / Line 207: @@
-== Step 6 ==
+= Step 6: Pointers =
 When you start step 6 you should see the form looking like this.
@@ Line 261: / Line 261: @@
 '''Click the ''next'' button''' to advance to the next step.
-== Step 7 ==
+= Step 7: Code Injection =
 When you start step 7 you should see the form looking like this.
@@ Line 327: / Line 327: @@
-== Step 8 ==
+= Step 8: Multilevel pointers =
 When you start step 8 you should see the form looking like this.
@@ Line 461: / Line 461: @@
-== Step 9 ==
+= Step 9: Shared code =
 When you start step 9 you should see the form looking like this.
@@ Line 512: / Line 512: @@
 So one way we could do this is to find the team id or team structure in the player structure.
-=== Find the team id in the player structure ===
+== Find the team id in the player structure ==
 After you have found the function that decreases health.
@@ Line 570: / Line 570: @@
-=== Find a difference in the registers ===
+== Find a difference in the registers ==
 After you have found the function that decreases health.
@@ Line 615: / Line 615: @@
-== See also ==
+= See also =
 * [[Tutorials]]
+* [http://pinetools.com/syntax-highlighter Syntax Highlighter]

@@ Line 7: / Line 7: @@
 -->
 [[Category:Tutorial]]
-<!-- == Cheat Engine Tutorial Guide (x64) == -->
+{{DISPLAYTITLE:Cheat Engine Tutorial Guide (x64)}}
 So let's go through the Cheat Engine Tutorial (x64).