DOSBox Cheat Engine vs MemDBG

DOSBox Cheat Engine is a single-page web application for scanning, editing, and freezing emulated memory in DOSBox Staging. Search for values, narrow the results, and add memory addresses to a Cheat Table; values in the table can be changed by double-clicking or frozen so they do not decrease. Live memory polling can be paused during CPU-heavy game segments. Cheat tables can be exported and loaded as JSON files, and Shift-click or Ctrl-click supports range selection. The application connects to DOSBox Staging through its Web Server API, which must be enabled in the emulator configuration. It requires DOSBox Staging 0.83 or newer; the API web server's default local address is http://127.0.0.1:8086. Precompiled executables are offered for Windows and Linux, and the Python source can be run directly using only the standard library, without a pip installation. The project is MIT licensed and free. Closing the browser tab sends a signal for the Python server to shut down gracefully.

MemDBG is a console payload and native frontend for memory inspection, scanning, debugging, trainer creation and research on PS4, PS5 and host machines. Its stated uses include offline homebrew development, reverse-engineering education, preservation and authorized security research. Scan workflows include exact values, process-wide searches, AOB patterns, pointer chains, unknown values and heuristic Smart Auto-Search. Debugging tools cover thread control, stepping, registers, breakpoints, watchpoints, stack walking and disassembly. Trainer workflows support .cht save and load, batchcode import, ON/OFF values, lock intervals and patch-to-trainer export. The frontend supports desktop-side Lua and Python plugins from repository manifests, with a public MemDBG plugin repository as its default source. It documents a GDB remote bridge for IDA Pro and an optional x64dbg plugin bridge. MemDBG is free and licensed GPL-3.0-or-later; it is in active pre-release development. Host builds bind to loopback by default, and the project recommends an allowlisted frontend IP for LAN sessions. Some macOS debugger actions may need SIP or code-signing changes; the iOS/iPadOS release artifact is unsigned.