Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Coverage

Honest status

There is no implementation yet.

MetricValue
Curated tools designed81
Curated tools implemented0
Curated tools tested0
Documented Lua functions585
Lua functions mapped to a curated tool0 verified
Lua functions implemented as generated tools0

“Designed” means a contract exists in spec/. It does not mean the tool works. This page must never report design as coverage.

Curated tools

GroupDesignedMappedGapImplementedTested
Meta44000
Process76100
Memory1010000
Scan88000
AOB/symbols55000
Table1010000
Pointer scan60600
Disassembly/assembly44000
Debugger1211100
Structures44000
Lua33000
UI/application54100
Misc31200
Total81701100

A “mapped” tool has an identified Lua or native strategy. A “gap” has no reliable mapping yet. Gaps are documented, not hidden.

The 11 gaps

ToolWhy it is a gap
process_closeNo closeProcess in celua.txt; openProcess(0) behavior is unverified
pointer_scan_startNo direct Lua pointer-scan API
pointer_scan_statusDepends on pointer scan
pointer_scan_resultsDepends on pointer scan
pointer_scan_rescanDepends on pointer scan
pointer_scan_cancelDepends on pointer scan
pointermap_generateNo direct Lua API; pointer-map callbacks exist, but orchestration is form-driven
stacktraceDepends on the debugger backend and symbolication
ui_open_toolForm automation is possible but fragile; not designed yet
snapshot_restoreRestoring memory and table state needs a conflict and safety model
trainer_generateWindows/PE-centric; out of scope for macOS

The disposition and closure criterion for each gap is recorded in Gap deferrals. A gap is not an implementation promise.

Lua API

FamilyFunctionsStatus on macOSNotes
dbvm_*39Unsupported on macOSWindows/DBVM kernel features
dbk_*19Unsupported on macOSWindows kernel features
debug_*22UnverifiedSome functions are Windows-only; arm64 support is uncertain
Other505UnmappedCross-platform or unknown; mapping not started
Total585

The exact names and statuses are in spec/lua-api.yaml. celua.txt has 585 unique names and 613 signatures because some functions are overloaded. An initial count of 586 included ModuleLoader(Inheritance: -), a class heading rather than a function.

The lua profile will generate one tool per documented function. Generated tools are designed, not implemented. The all profile is the union of the curated catalog and the generated tools.

Bundled Lua code outside the count

Cheat Engine ships Lua code that is not part of celua.txt:

  • Contents/Lua/Autorun/: speedhack, Mono/.NET, Java, pseudocode and symbol scripts loaded at startup;
  • Contents/Lua/Extensions/AITools/: an MIT-licensed AI assistant extension;
  • Contents/Lua/Extensions/UETools/: MIT-licensed Unreal Engine inspection tools.

These scripts are not in the 585-function count, are not generated as tools and are not exposed by default. They are shipped application assets, not copied into this repository. Adopting one later would require an explicit tool contract and a license review.

Platform coverage

PlatformCurated designBridgeNative gaps
macOS arm64YesPlanned; first targetPointer scan, arm64 debugger context, interactive structure dissect, arm64 speedhack path unverified
macOS x86_64YesPlannedSame, plus x86-specific debugger behavior
WindowsYesFutureDBVM/kernel features excluded
LinuxYesFutureBridge needs validation

No platform is implemented yet.

How coverage will be measured

  1. Extract function names from celua.txt.
  2. Compare with spec/lua-api.yaml.
  3. Fail on missing, duplicate or status-less names.
  4. Compare spec/tools/*.yaml with generated server registration.
  5. Fail on a documented tool that is not registered, or a registered tool that is not documented.
  6. Run contract tests against a real Cheat Engine 7.7 instance.
  7. Publish the result here.

A function is only “covered” when:

  • a curated tool implements it and has a contract test, or
  • a generated tool is registered and tested, or
  • it is explicitly excluded with a platform reason.

How to update this page

  • Do not edit the counts by hand once the coverage generator exists.
  • Until then, update the table when a tool moves from gap to mapped, implemented or tested.
  • Keep the gaps list current.
  • Add a journal entry when a gap is closed or a new one is found.