dsh-cheatengine

When reverse-engineering a standalone game, toggling between Cheat Engine and your Agent session to scan memory, trace pointers, and lock values is both tedious and error-prone. dsh-cheatengine lets a DSH Agent drive Cheat Engine directly for the full debugging pipeline: memory scanning, filtering, read/write, disassembly, breakpoints, register inspection, writer tracing, pointer scanning with base-address verification, address locking, AOB search, and module dumping—all within a single conversation, no window switching.

The plugin uses an on-demand unlock model. By default only a handful of tools (status, connect, tool search, playbook, mission) are registered to keep token overhead low. You progressively open packs such as scan, memory, or pointer via ce_tool_search, so the tool surface grows only as your task requires. An optional floating status panel in the bottom-right corner shows the current phase, call count, scans, and locks; it reads a local API endpoint and adds zero LLM token cost.

dsh-cheatengine is designed for single-user, local, low-concurrency debugging: one target process, one DSH session at a time. It suits game-reverse hobbyists, indie developers, or security researchers working on Windows standalone titles for memory analysis, resource locking, and anti-cheat detection. It is not intended for multi-agent high-concurrency workflows or untrusted remote networks.