Community Cheat Tables

Where they come from

When a game is running, the app looks for cheat tables for its title ID in three community collections:

• etaHEN PS5 Cheats
• GoldHEN Cheat Repository
• HEN Cheats Collection

Your browser downloads them, straight from those repositories. The console never needs internet access, and nothing from the collections is stored in the CheatSpecter repository. Tables you have used before are cached in the browser and still work offline.

It also lists cheat files that are already on your PS5 (see "On this PS5" below), and tables saved in the game's own cheat file.

If no table exists for your game, the list is empty. Make your own: Your First Cheat. Frame-rate and resolution patches are a separate collection: see Game Patches.

Saved on your PS5 for your exact version

Beta. New in 0.4.3. Passes the automated tests against the simulated console; not yet tried on a real PS5.

When a table is made for exactly your game's title ID and version, it is converted and saved into the game's cheat file on your PS5 the first time it is opened, next to your own cheats. From then on:

• It opens from the PS5 straight away, with no download and no internet. The line under the table's name says "Saved on your PS5" and when.
• It looks and works exactly like the downloaded table: same switches, same checks before anything is written.
• Check for updates reads the table's source again. If cheats were added, changed or removed, a window lists them, and Update replaces the saved copy. Your own cheats are never touched. The app also checks quietly in the background and shows Review update under the table when something changed.

This happens once per game version. It does not happen again after you delete the file during the same visit, and not when the cheats showing came from another version's file: then a Save it into button, followed by the file name, is offered instead, so you can check your cheats first. A table for another version is never saved by itself.

The cheats from a saved table can be part of the game's start set; see Making and Managing Cheats.

On this PS5

Beta. New in 0.4.3; not yet tried on a real PS5.

Cheat files that other tools keep on the console are listed as a source named On this PS5:

• /data/etaHEN/cheats
• /data/elf-arsenal/cheats
• /data/GoldHEN/cheats

Each folder is looked through itself and in its json, shn and mc4 folders, for files whose names start with the game's title ID and end in .json, .shn or .mc4. CheatSpecter only reads them; it never changes or deletes them. One for exactly your version is saved into the game's cheat file like an online table, and Check for updates then compares it with the file on the console.

Formats

Format	Read	Written
.cspector (CheatSpecter's own)	Yes	Yes
JSON (GoldHEN / etaHEN)	Yes	Yes, simple patches
SHN (trainer XML)	Yes	Yes, simple patches
MC4 (encrypted trainer)	Yes	Yes, simple patches

When a collection has the same table in several formats, the JSON one is used.

Versions

A table is made for one version of a game. The picker shows each table's version and source, and marks the one that matches your game and those saved on your PS5. When none is for your version, the page says so; you can still try one, and nothing is saved on your PS5 unless you choose to.

Whatever the label says, every cheat is checked before it is switched on: the bytes in the game are compared with what the table expects. A cheat that does not match is left off, with Apply anyway if you are sure.

"Master code" cheats

Some community cheats change memory outside the game's main program and name a memory "section" instead of an offset. CheatSpecter places these by finding the cheat's own original bytes in the running game, and leaves the cheat alone, with the reason shown, when that does not give a single answer. Only the page can place them, so the PS5 never applies them by itself. This is new in 0.4.0 and has not been tried on a real console yet.

Importing a file

Drop a .cspector, .json, .shn or .mc4 file on the import area at the bottom of the Cheats tab, or click it to choose one.

A .cspector file's cheats join Your cheats. If it was made with Save, the tables saved in it come along too, unless the game's file already has them. Anything in an imported .cspector file that runs code (code cheats, function calls, scripts) is held for review before first use.

Exporting yours

See "The game's cheat file" in Making and Managing Cheats. Exports are named the way the collections name them: <TITLEID>_<version>.json, .shn or .mc4.