Cheat Engine:Internals - Revision history

Chris314 at 14:51, 23 April 2022

2022-04-23T14:51:21Z

Chris314 at 07:35, 23 April 2022

2022-04-23T07:35:54Z

Llgnll: /* Memory Scanning */

2021-09-28T21:39:19Z

‎Memory Scanning

GodwinStanley: /* Memory Scanning */ 100

2021-03-09T14:17:41Z

‎Memory Scanning: 100

TheyCallMeTim13 at 14:26, 19 March 2017

2017-03-19T14:26:48Z

Dark Byte: Reverted edits by Mohamed (Talk) to last revision by Raijinili

2016-02-08T17:33:12Z

Reverted edits by Mohamed (Talk) to last revision by Raijinili

Mohamed: /* Speedhack */

2016-01-25T18:53:02Z

‎Speedhack

Raijinili: Revert http://wiki.cheatengine.org/index.php?title=Cheat_Engine:Internals&diff=prev&oldid=795

2016-01-22T00:55:04Z

Revert http://wiki.cheatengine.org/index.php?title=Cheat_Engine:Internals&diff=prev&oldid=795

Dark Byte: Reverted edits by 149.3.21.131 (Talk) to last revision by Dark Byte

2012-02-10T13:31:38Z

Reverted edits by 149.3.21.131 (Talk) to last revision by Dark Byte

149.3.21.131: /* Speedhack */

2012-02-09T22:08:15Z

‎Speedhack

@@ Line 15: / Line 15: @@
 The source for this is located in '''speedhack2.pas''' in the main program, and the separate speedhack project.
-The '''speedhack.dll''' gets injected into the target process and the dll itself has some exports, like speed, addresses of original functions, and an initialize speedhack routine.
+The '''speedhack-i386.dll''' or '''speedhack-x86_64.dll''' gets injected into the target process and the dll itself has some exports, like speed, addresses of original functions, and an initialize speedhack routine.
 Here the hooking and controlling takes place from CE's side and its auto assembler functions.
@@ Line 22: / Line 22: @@
 After it's hooked, the export "speed" of the dll is modified to the wanted speed and '''CreateRemoteThread''' API is called with the address of the Initialize function to start the speedhack and set a base of reference (the current time).
-When a timer function is called it will calculate the new time based on the initial time the speedhack got started, the current time, and the speed. So: returned time = basetime+((currenttime-basetime)*speed) .
+When a timer function is called it will calculate the new time based on the initial time the speedhack got started, the current time, and the speed. So: '''returned_time = base_time + ((current_time - base_time) * speed)''' .
 When the speed is modified, the basetime itself is modified as well to make sure the time doesn't go backwards.

@@ Line 1: / Line 1: @@
 [[Category:Help]]
 == Speedhack ==
-CE has 2 different types of speedhack.
+CE has 2 different types of speedhack: the old one and the new one.
-The old one is located in speedhack.pas of the cehook project (cehook.dll)
+The old one is located in '''speedhack.pas''' of the cehook project ('''cehook.dll''').
-When it gets activated it uses a simple hook on those functions (just place with a hook and never even bother calling the original function)
+When it gets activated, it uses a simple hook on those functions (just place with a hook and never even bother calling the original function).
-It then starts a very high priority thread in the game which will increase time counters for itself using timed sleeping. The speed the time increments with is determined by the speed variable
+Then it injects and starts a very high priority thread in the open process (game) which will increase time counters for itself using timed sleeping. The speed the time increments with is determined by the speed variable.
-When the game then calls those functions, it just fetches the emulated timer functions and passes it to the caller.
+When the open (target) process calls those functions, it just fetches the emulated timer functions and passes it to the caller.
@@ Line 15: / Line 14: @@
 The new one is a bit more complex, but less prone to bugs because of a too low sleeptime, or too high, and no thread that counts time for you.
-The source for this is located in speedhack2.pas in the main program, and the separate speedhack project
+The source for this is located in '''speedhack2.pas''' in the main program, and the separate speedhack project.
-The speedhack.dll gets injected into the target process and the dll itself has some exports, like speed, addresses of original functions, and an initialize speedhack routine
+The '''speedhack.dll''' gets injected into the target process and the dll itself has some exports, like speed, addresses of original functions, and an initialize speedhack routine.
-Here the hooking and controlling takes place from CE's side and it's auto assembler functions.
+Here the hooking and controlling takes place from CE's side and its auto assembler functions.
-What it does is it first uses the API hook template script on the to hook functions. This results in a script that can be used to hook the functions and fills in some predetermined addresses with the location to call if you want to call the original function (thats what the exports for the original functions are for)
+What it does is it first uses the API hook template script on the to hook functions. This results in a script that can be used to hook the functions and fills in some predetermined addresses with the location to call if you want to call the original function (thats what the exports for the original functions are for).
-After it's hooked the export "speed" of the dll is modified to the wanted speed and CreateRemoteThread is called with the address of the Initialize function to start start the speedhack and set a base of reference (the current time)
+After it's hooked, the export "speed" of the dll is modified to the wanted speed and '''CreateRemoteThread''' API is called with the address of the Initialize function to start the speedhack and set a base of reference (the current time).
-Then when a timer function is called it will calculate the new time based on the initial time the speedhack got started , the current time, and the speed. returned time = basetime+((currenttime-basetime)*speed)
+When a timer function is called it will calculate the new time based on the initial time the speedhack got started, the current time, and the speed. So: returned time = basetime+((currenttime-basetime)*speed) .
-When speed is modified the basetime itself is modified as well to make sure the time doesn't go backwards
+When the speed is modified, the basetime itself is modified as well to make sure the time doesn't go backwards.
 == Memory Scanning ==

← Older revision		Revision as of 21:39, 28 September 2021
Line 28:		Line 28:

	== Memory Scanning ==		== Memory Scanning ==
−	~~...~~

← Older revision		Revision as of 14:26, 19 March 2017
Line 1:		Line 1:
		+	[[Category:Help]]
	== Speedhack ==		== Speedhack ==
	CE has 2 different types of speedhack.		CE has 2 different types of speedhack.

← Older revision		Revision as of 17:33, 8 February 2016
Line 10:		Line 10:


−	----~~modern combat 5 blackout~~	+	----

	The new one is a bit more complex, but less prone to bugs because of a too low sleeptime, or too high, and no thread that counts time for you.		The new one is a bit more complex, but less prone to bugs because of a too low sleeptime, or too high, and no thread that counts time for you.

← Older revision	Revision as of 14:17, 9 March 2021
(No difference)

← Older revision		Revision as of 18:53, 25 January 2016
Line 10:		Line 10:


−	----	+	----modern combat 5 blackout

	The new one is a bit more complex, but less prone to bugs because of a too low sleeptime, or too high, and no thread that counts time for you.		The new one is a bit more complex, but less prone to bugs because of a too low sleeptime, or too high, and no thread that counts time for you.

@@ Line 25: / Line 25: @@
 When speed is modified the basetime itself is modified as well to make sure the time doesn't go backwards
-yy
 vhbvWIUEF[[Media:WEF]]
 ...