TINT Cheats

← All tables

Contribute a cheat table

tint-cheats is open source and community-driven. If you make Cheat Engine tables for single-player games, add them here so people get a trustworthy, checksummed, no-gate download. Here is the whole process.

Full CONTRIBUTING.md Just request one instead

Steps 6

  1. Fork and set up

    Fork the repo on GitHub, clone your fork, and run just setup (installs the pinned Node via asdf and the dependencies).

  2. Scaffold a table

    Run just new-table "". This copies the template into tables// with an index.md, a media/ folder, and a starter .CT.

  3. Add your .CT and media

    Drop your Cheat Engine table file in the folder and add a cover plus any screenshots under media/. Name the file using the convention below.

  4. Fill in index.md

    Set the frontmatter (game, status, table_version, author, game_versions you tested, cheats with hotkeys, tags) and write the documentation sections. Keep it honest about what was tested.

  5. Validate locally

    Run just verify (validate + type check + build). It enforces the schema, checks the file naming convention, and generates checksums. Fix anything it flags.

  6. Open a pull request

    Push to your fork and open a PR. Fill in the template (which game, what version you tested on). Checksums and the download copy are generated automatically.

Rules and conventions

  • File naming. Table files must be named tint-<game-slug>-<table_version>.ct, lowercase. Example: tint-20-minutes-till-dawn-1.7.0.ct. The build fails if a file does not follow this.
  • Single-player only. No online or multiplayer tables. They will be rejected.
  • No piracy or DRM circumvention. Tables are for cheats in games people own.
  • Be honest. List the exact game version/build you tested on, and mark untested versions as such.
  • Credit your sources. If you built on someone else's pointers or scripts, say so.
  • No gates. Never add surveys, shorteners, ads, or redirects. The whole point is trust.