Click to view comment #144

Cheat Tool Set

Cheat tool set (CTS) is a tool like CE written in #C .NET

Current version: 1.11 Changelog:


Memory scanner
Memory viewer / editor (Pro)
Pointer scanner (Pro)
IAT (Import Address Table) tool
Debug viewer (Pro)
Windows debugger: Read, Write, and instruction execute (Find out what addresses this instruction accessess) (Pro)
Disassembler (Pro)
Dump strings tool



What is the difference compared to Cheat Engine (CE)?

- One of a kind memory viewer/editor
- The software has unique functionality that you cannot currently do with other similar programs.
- Debug viewer is a lot more advanced vs CE's pointer scanner memory rescan feature "Value to find"
- Pointer scanner has new functionality such as "Custom pointer path scan" and is more user-friendly
- The main view has "A sequence of values" scan type.
- Currently not as fast because of (4) static threads. The scanning speed is still reasonably fast.
- The core functionality is pretty much the same.

Memory viewer itself in the tool makes the distinction to the competition.

To cut a long story short: Previously unfound values can be found with the tool. The tool is a work in progress.

The purpose of the program is to enhance the functionality of the CE. That's why the software has only the most important CE equivalent features
and new features that are not available in other similar programs.

To mention one enhanced functionality: Pointer scanner level one scan takes less than five seconds and memory consumption is almost non-existent.







How do I get the tool?

To get the updated version of the software. You must register an account and "order" the software via the system. All this is free of charge.
Once your "order" has been approved, the download will be activated to your account.


The first review: Thanks.


Runs on: Windows 7/10 64-bit
Requires .NET Framework 4.7.2 or newer

The software is a portable application. No installation is required. The software does not modify your computer registry.
The tool supports only x64 (64-bit) processes.
Offsets are mainly entered as hex values.

No personal data is sent upon checking for an update.

When you use the "Include the result if the value has changed ...", you can no longer press the next scan button because the number of times the value has changed
is not saved in the result files.

By default the disassembler disassembles the current function.

"Array of bytes" scan supports the following formats:


83 E0 01
\x83 \xE0 \x01
0x83 0xE0 0x01

"Exact value" float scan: "Value to find" is automatically truncated to four decimal places double value. No rounding is done to that value.

Pointer scanner

"Generate a pointer map" feature is almost mandatory for scans larger than a level 3 and 0x0400. You do not have generate a pointer map for a custom path scan.
"The first element of pointer must point to virtual function table" enables "Class pointer rule check". Pros: Those pointers paths are more likely valid after game has been restarted.


Currently only one HWBP (hardware breakpoint) is supported.



Data types

Byte: 0 - 255
2 Bytes: -32768 - 32767
4 Bytes: -2147483648 - 2147483647

If you like the software, you can donate via PayPal

The source code

The source code is not available to maintain the uniqueness of the software. Therefore the executable is heavily obfuscated. This may result in false positives in AV's.

CREDITS: See the about box.

If you find a bug or a logic issue. Always mention which CTS version and briefly describe the issue.
08/19/2018 20:56 - 218 days 19 hours 40 minutes
#144 #144
#140 Originally posted by A visitor :

It's 2018 ... Are not major games only x64? I never designed the tool for both. After thinking about this. It would be simpler to write a separate version that is x32 only.

However I've no time for that. Unless someone hire me for that. I won't be bothering with anything less than $2499 for that version. Otherwise it is very unlikely to happen that I come with a version that supports 32-bit processes.

There are various features to be added and fixes to be done in the current x64 version. I add each features/fix in an order I need most.

Adding support for 32-bit processes in the current version would just make the software a way too complicated and even more prone to bugs.

I try to provide as soon as possible the source code of the software as a commercial source.

I never realized until now that coding a software like this is a full day job. What I mean by this? A software like this is not an ordinary software that is easy to code.

It requires experience from reverse engineering community. I say this so you know that adding a support for 32-bit processes does not happen by snapping a fingers especially when the software was never designed this way.

Post a comment

Registered users do not have to enter captcha. A line in the code tag is currently limited to maxium of 160 characters.
Posting guidelines: You may not post any personal information. If you report a crash or any other issue: Always mention which Overlay Hack version and operating system and briefly describe the issue. Any support request post that does not include this information will be removed as spam without a reply.
Tags You may use the following tags: [QUOTE] [/QUOTE] [B] [/B] [URL] [/URL] [CODE] [/CODE]
Captcha Please enter the text you see (case insensitive). The listed characters must be entered clockwise starting from twelve o'clock.
Comments are moderated Y