Cheat Engine Built From Source Tutorial | Driver | DBVM | VEH Debugger | Renaming | Error Correction

Summary

This video guides viewers through the process of building Cheat Engine from source. The tutorial covers everything from downloading and setting up necessary tools like Lazarus, Visual Studio 2019, and HxD, to renaming and modifying Cheat Engine to bypass basic detection mechanisms in games. The video also walks through building the DBK driver and customizing Cheat Engine using scripts for enhanced functionality. By the end of the tutorial, viewers will have a fully functional and renamed version of Cheat Engine ready for use.

Takeaways

• 😀 The video provides a tutorial on how to build Cheat Engine from source, including how to fully rename it and bypass string detection in games.
• 😀 A variety of tools and programs are required for the process, including Lazarus IDE, Visual Studio 2019, HxD, and the Windows SDK.
• 😀 The specific version of Lazarus IDE needed is version 2.2.2, and it should be installed with certain components for a smooth build process.
• 😀 The video uses Visual Studio 2019 due to fewer errors compared to the newer 2022 version when building Cheat Engine.
• 😀 Users should install the Windows 10 SDK version 2004 and Windows Driver Kit for Windows 10 to avoid build issues during the process.
• 😀 Renaming Cheat Engine requires hex editing the executable and modifying its internal string values without exceeding the original character limits.
• 😀 The tutorial includes instructions on changing the name of the Cheat Engine driver (DBK) to a custom name, such as 'game exploit'.
• 😀 The steps show how to bypass errors related to header files during driver compilation by adding the necessary Windows Driver Kit headers.
• 😀 Building the driver involves using the 'release without signature' setting to avoid issues when compiling the driver.
• 😀 After building the driver, additional changes to Lua scripts are necessary to ensure the renamed Cheat Engine runs without errors.
• 😀 A small script for bypassing string detection is provided, which uses homoglyphs to maintain readability while bypassing basic game protections.

Q & A

What is the main objective of the video tutorial?

The main objective of the video is to guide viewers on how to build Cheat Engine from source, including renaming it and bypassing basic string detection used in games.

What tools and software are required to follow the tutorial?

The required tools include Lazarus IDE, Visual Studio 2019, HxD (for hex editing), Windows 10 SDK, Windows Driver Kit (WDK), and DBK driver files.

Why is Visual Studio 2019 specifically recommended for this tutorial?

Visual Studio 2019 is recommended because it avoids build errors and complications that can occur with Visual Studio 2022, particularly with issues related to driver code and redacted components.

What is the purpose of the HxD program in this process?

HxD is used for hex editing to rename Cheat Engine's executable and to avoid basic string detection by modifying specific hex values.

How does the user change the service name and driver files in the tutorial?

The user changes the service name and driver files by opening specific files in a text editor or Lazarus, searching for 'Cheat Engine', and replacing it with a custom name (e.g., 'Game Exploit').

What is the significance of using a virtual machine (VM) in this tutorial?

The use of a virtual machine helps keep the main PC clean and prevents unnecessary programs from being installed. It also provides a controlled environment for building Cheat Engine.

Why is it important to use the 'release without signature' build configuration for the driver?

Using the 'release without signature' configuration avoids errors that occur with unsigned drivers and is necessary when building the driver in Visual Studio 2019.

What steps are involved in renaming Cheat Engine using hex editing?

To rename Cheat Engine, the user searches for specific strings like 'Cheat Engine' and '7.5' in the hex editor, replacing them with the new name (e.g., 'Game Exploit'). Care must be taken to ensure the length of the replacement text matches the original.

What is DBVM, and why is it used in this process?

DBVM (Debugging Virtual Machine) is a tool used for debugging and memory manipulation in Cheat Engine. It allows for more advanced functionality, but it can cause frequent blue screens if not handled properly.

What should be done if errors occur related to missing inclusions during the build?

If errors related to missing inclusions occur, the user should go to the 'Header Files' section in the Windows Driver Kit, locate the missing files, and add them to the project manually.