CheatTurbine vs chromedp
CheatTurbine
github.comchromedp
github.comSide by side
| Figure | CheatTurbine | chromedp |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | — | Yes |
| Plans published | 0 | 1 |
| Spec score · Game Memory Editors | 6.8 (#18) | 8.5 (#2) |
| License | The repository identifies its license as GPL-2.0. | The repository identifies its license as MIT. |
| Purpose | Cheat Turbine describes itself as a Cheat Engine alternative for Linux. | chromedp is a Go package for driving browsers that support the Chrome DevTools Protocol, without an external driver. |
Plans
In their own words
CheatTurbine
CheatTurbine is a free, GPL-2.0 open-source Linux application described as a Cheat Engine alternative. Its listed tools include a value scanner, memory editor, and structure dissector. A breadth-first pointer scanner is included, but the README calls it extremely unstable. The project is under active development and uses ImGui for its interface. The README recommends building from source with CMake, GCC, G++, and listed Linux graphics dependencies. Recent binary artifacts are available through GitHub Actions, with the non-AppImage build preferred when possible. The documented launch process uses xhost and starts the binary with sudo. CheatTurbine does not list a debugger or scripting support. Project save/open, scanner improvements, scripting, code injection, and a disassembler are identified as planned work rather than current features.
chromedp
chromedp is a Go package for driving browsers that support the Chrome DevTools Protocol without an external driver. It runs Chrome headlessly by default and supports actions such as navigating, clicking, reading page text, running JavaScript, filling forms, and waiting for elements. Its examples also cover cookies, HTTP headers, proxy authentication, request interception, session restoration, and HAR recording. For output, it can capture screenshots, print pages to PDF, and save screencast frames as JPEG files. Separate browser contexts can support parallel work, but sharing one context between goroutines can cause races. A separate remote module connects to an already-running browser over WebSocket, and the project provides a headless-shell Docker image. By default, Chrome communicates over remote-debugging pipes and does not open a debugging port; switching to WebSocket uses one. The package is available under the MIT license at free. The README requires Go 1.27 or newer.