Troubleshooting and Safety

Use at your own risk

CheatSpecter changes the memory of a running game. That can crash the game, corrupt a save, or have other effects nobody intended. It has only been tested on one jailbroken PS5, on firmware 13.60 with ps5debug-NG 1.3.2. What you do with it, and any consequences, are your responsibility. The software comes with no warranty; see the license.

Sensible habits:

• Back up your saves before experimenting, and save in the game before switching on something new.
• Switch code cheats and hooks on at a quiet moment, not in the middle of the action.
• If the game misbehaves, press Restore everything first.

Common problems

The page does not open. Check that the device is on the same network as the PS5, that the payload's notification appeared, and that you typed http:// and the port: http://<PS5 IP>:8744. The payload must be loaded again after every reboot, and the console's address can change between reboots.

"ps5debug is not running" or no game is found. Start ps5debug-NG before the CheatSpecter payload and wait for its "loaded" notification. Then start a game.

No cheats are listed for my game. Nobody has published a table for that title, or the device you are browsing from has no internet access (tables are downloaded by the browser). Make your own: Your First Cheat.

A cheat says it does not match this version of the game. The table was made for another version. The app is protecting you from writing into the wrong place. Look for a table for your version, or re-make the cheat.

A search for the right number finds nothing. The game stores it differently. Try Type Auto, then About (shown rounded), then Unknown. See Finding Values.

Searches are slow. Big games have gigabytes of memory. Use Where to search to leave out the largest blocks.

My cheat worked, then stopped after restarting the game. It pointed at a raw address. Use "find what writes to this" and disable the code, or the pointer finder. See Making and Managing Cheats.

My cheats stopped working after a game update. Use Save → Re-find my cheats after a game update….

"Something else is using the debugger." Only one debugging session exists at a time. Stop the trace, the Debug tab's session, or the guide, whichever the message names. Another tool on your network using ps5debug's debugger has the same effect.

The Learn page says the lessons could not be loaded. The device needs internet access to reach GitHub.

Running from a computer: "what writes to this" finds nothing. The console connects back to the computer on port 755. Allow it through the firewall.

Things that can crash a game

These come from how debugging a live process works.

• Tracing ("what writes to this") attaches a debugger. If the page is closed mid-trace, the watchpoint may be left armed and the game can die at the next hit. Press Stop first.
• Breakpoints and stepping freeze the game. Some games do not survive being frozen for long.
• Injected code is written while the game keeps running. A hook replaces at least five bytes; if that spans several instructions and the game jumps into the middle of them, it crashes.
• Function calls borrow a game thread. The function must return within about two seconds.
• Scripts and imported cheats that run code are held for review before first use. Read them.

Your network

ps5debug-NG listens on the console with no password, so anyone on the same network can reach it, with or without CheatSpecter. Use a network you trust.

Reporting a bug

Open an issue with the CheatSpecter version, firmware, ps5debug-NG version, the game's title ID and version, and what you did. Security problems go through the private form described in SECURITY.md.