Tutorials:Auto Assembler:Injection full - Revision history

TheyCallMeTim13 at 20:26, 22 April 2018

2018-04-22T20:26:19Z

TheyCallMeTim13 at 20:23, 22 April 2018

2018-04-22T20:23:08Z

TheyCallMeTim13 at 20:16, 22 April 2018

2018-04-22T20:16:55Z

TheyCallMeTim13: /* Writing the injection code */

2018-04-22T18:55:24Z

‎Writing the injection code

TheyCallMeTim13: /* Step 3 */

2017-12-30T03:53:04Z

‎Step 3

TheyCallMeTim13 at 14:01, 19 March 2017

2017-03-19T14:01:22Z

TheyCallMeTim13 at 12:50, 19 March 2017

2017-03-19T12:50:46Z

TheyCallMeTim13 at 08:20, 15 March 2017

2017-03-15T08:20:34Z

TheyCallMeTim13 at 08:18, 15 March 2017

2017-03-15T08:18:17Z

TheyCallMeTim13 at 18:47, 12 March 2017

2017-03-12T18:47:17Z

@@ Line 1: / Line 1: @@
 [[Category:Tutorial]]
 [[Category:Auto Assembler]]
 {{DISPLAYTITLE:Code Injection - Full}}
 So in most games to really do any thing cool, you will want or need to use code injection.

@@ Line 148: / Line 148: @@
 And that's that basics of assembly injection with Cheat Engine.
+{{Template:CodeInjectionSeeAlso}}
 == External links ==

@@ Line 1: / Line 1: @@
 [[Category:Tutorial]]
-[[Category:Assembler]]
+[[Category:Auto Assembler]]
 {{DISPLAYTITLE:Code Injection - Full}}
 So in most games to really do any thing cool, you will want or need to use code injection.

@@ Line 78: / Line 78: @@
 == Writing the injection code ==
-Will setup a script to enable and disable the injection.
+We'll setup a script to enable and disable the injection.
 === Step 1 ===
@@ Line 120: / Line 120: @@
 [[File:Tutorials.AddScriptToTable.AssignToTable.CTScript.01.png|border]]
 == Testing the injection code ==

@@ Line 108: / Line 108: @@
 :Note the ''yellow'' lines, these mark code changes on that line.
-::so here line 26 is showing that it have changed.
+::so here line 26 is showing that it has changed.
 [[File:CEForm.AutoAssembler.CodeInjection.autoAssembler.2.01.png|border]]

← Older revision		Revision as of 12:50, 19 March 2017
Line 1:		Line 1:
		+	[[Category:Tutorial]]
		+	[[Category:Assembler]]
	So in most games to really do any thing cool, you will want or need to use code injection.		So in most games to really do any thing cool, you will want or need to use code injection.

@@ Line 81: / Line 81: @@
 so on the form's menu '''click ''template'' then click ''cheat table framework code'''''.
-[[File:CEForm.AutoAssembler.CodeInjection.autoAssembler.01.png|border]]
+[[File:Tutorials.AddScriptToTable.AssignToTable.Template-CTFramework.01.png|border]]
 This will give you the base code needed to add a script to the table.

@@ Line 23: / Line 23: @@
 '''right-click and select ''find out what writes to this address'''''.
-[[File:CEForm.AutoAssembler.CodeInjection.01.png]]
+[[File:CEForm.AutoAssembler.CodeInjection.01.png|border]]
 A message window will tell you ''this will attach the debugger of Cheat Engine to the current process. Continue?''.
@@ Line 35: / Line 35: @@
   FF8396CC - 41 83 43 14 FE - add dword ptr [r11+14],-02
-[[File:CEForm.AutoAssembler.CodeInjection.02.png]]
+[[File:CEForm.AutoAssembler.CodeInjection.02.png|border]]
 Once some code comes up you can '''click the ''stop'' button'''.
-[[File:CEForm.AutoAssembler.CodeInjection.03.png]]
+[[File:CEForm.AutoAssembler.CodeInjection.03.png|border]]
 Then '''click on the line of code''', this should enable the buttons,
 now '''click the ''show disassembler'' button'''.
-[[File:CEForm.AutoAssembler.CodeInjection.04.png]]
+[[File:CEForm.AutoAssembler.CodeInjection.04.png|border]]
 This will bring up the disassembler / memory view form.
-[[File:CEForm.AutoAssembler.CodeInjection.disassembler.01.png]]
+[[File:CEForm.AutoAssembler.CodeInjection.disassembler.01.png|border]]
 === Step 3 ===
@@ Line 54: / Line 54: @@
 '''right-click and select ''find out what addresses this instruction accesses'''''.
-[[File:CEForm.AutoAssembler.CodeInjection.disassembler.02.png]]
+[[File:CEForm.AutoAssembler.CodeInjection.disassembler.02.png|border]]
 === Step 4 ===
@@ Line 62: / Line 62: @@
 So we are '''looking to see that this only accesses the score address'''.
-[[File:CEForm.AutoAssembler.CodeInjection.disassembler.03.png]]
+[[File:CEForm.AutoAssembler.CodeInjection.disassembler.03.png|border]]
 So if only the address we want (the score) comes up then we can '''close the window''',
@@ Line 71: / Line 71: @@
 or just press ''Ctrl+A''.
-[[File:CEForm.AutoAssembler.CodeInjection.disassembler.04.png]]
+[[File:CEForm.AutoAssembler.CodeInjection.disassembler.04.png|border]]
@@ Line 81: / Line 81: @@
 so on the form's menu '''click ''template'' then click ''cheat table framework code'''''.
-[[File:CEForm.AutoAssembler.CodeInjection.autoAssembler.01.png]]
+[[File:CEForm.AutoAssembler.CodeInjection.autoAssembler.01.png|border]]
 This will give you the base code needed to add a script to the table.
-[[File:CEForm.AutoAssembler.CodeInjection.autoAssembler.02.png]]
+[[File:CEForm.AutoAssembler.CodeInjection.autoAssembler.02.png|border]]
 === Step 2 ===
 So now on the form's menu '''click ''template'' then click ''full injection'''''.
-[[File:CEForm.AutoAssembler.CodeInjection.autoAssembler.03.png]]
+[[File:CEForm.AutoAssembler.CodeInjection.autoAssembler.03.png|border]]
 You will be prompted for the address if you haven't changed the selected code in the memory view form,
 then '''click the ''ok'' button'''.
-[[File:CEForm.AutoAssembler.CodeInjection.autoAssembler.04.png]]
+[[File:CEForm.AutoAssembler.CodeInjection.autoAssembler.04.png|border]]
 This will give you the base code needed for a full injection.
-[[File:CEForm.AutoAssembler.CodeInjection.autoAssembler.05.png]]
+[[File:CEForm.AutoAssembler.CodeInjection.autoAssembler.05.png|border]]
 === Step 3 ===
@@ Line 107: / Line 107: @@
 ::so here line 26 is showing that it have changed.
-[[File:CEForm.AutoAssembler.CodeInjection.autoAssembler.2.01.png]]
+[[File:CEForm.AutoAssembler.CodeInjection.autoAssembler.2.01.png|border]]
 === Step 3 ===
 Now we can add this to the table, so on the form's menu '''click ''file'' then click ''assign to current cheat table'''''.
-[[File:CEForm.AutoAssembler.CodeInjection.autoAssembler.08.png]]
+[[File:Tutorials.AddScriptToTable.AssignToTable.01.png|border]]
 This should create a memory record in the tables address list.
-[[File:CEForm.AutoAssembler.CodeInjection.addrLst.script.01.png]]
+[[File:Tutorials.AddScriptToTable.AssignToTable.CTScript.01.png|border]]
@@ Line 126: / Line 126: @@
 '''enable the script''' (click the box or with it selected press the space bar).
-[[File:CEForm.AutoAssembler.CodeInjection.addrLst.script.02.png]]
+[[File:CEForm.AutoAssembler.CodeInjection.addrLst.script.02.png|border]]
 You should see a red X in the enabler box, a jump command, and the same code as before the injection on the next line,
 if all went as planed.
-[[File:CEForm.AutoAssembler.CodeInjection.autoAssembler.2.02.png]]
+[[File:CEForm.AutoAssembler.CodeInjection.autoAssembler.2.02.png|border]]
 Now '''check that the score gets increased'''.
@@ Line 139: / Line 139: @@
 and the red X should be gone and the original code should be injected back.
-[[File:CEForm.AutoAssembler.CodeInjection.addrLst.script.04.png]]
+[[File:CEForm.AutoAssembler.CodeInjection.addrLst.script.04.png|border]]
 Now '''check that the score gets decreased'''.
@@ Line 150: / Line 150: @@
 * [[Code_injection]]
 * [[Tutorials]]
 == External links ==

@@ Line 1: / Line 1: @@
-So in most game to really do any thing cool, you will want or need to use code injection.
+So in most games to really do any thing cool, you will want or need to use code injection.
 Now there are different types of injection, the most common methods are DLL injection and assembly injection.
@@ Line 15: / Line 15: @@
 == Finding the injection point ==
-After you have found the addresses of the score and time then we can find the injection point.
+After you have found the address of the score then we can find the injection point.
 Where this is depends on what we want to do so in ''Windows Solitaire'' the score decreases over timer,
 lets make it increase the score.