Cheat Engine alternative for Mac — Dave the Diver

Cheat Engine is Windows-only. There is no Mac build, and the workarounds people suggest mostly don't work on modern macOS. For a single-player game like Dave the Diver, though, you probably don't want a memory trainer at all — you want a save editor. Here's the honest difference.

The short answer

Cheat Engine does not run on macOS. Its native replacement for Dave the Diver is a save editor: it changes values in the save file on disk while the game is closed, instead of scanning and patching a running game's memory. For a single-player game that's simpler, safer, reversible — and it doesn't need any of the privileges memory editing requires.

DiveSaveEd is a free, open-source, native macOS save editor for exactly that. macOS 14+, Apple Silicon and Intel.

Why Cheat Engine doesn't work on a Mac

Cheat Engine is a Windows application built around Windows APIs for attaching to another process and reading and writing its memory. Several things stand in the way on macOS:

The projects usually named as "Cheat Engine for Mac" — Bit Slicer, iGG and friends — are genuine memory scanners, but they're general-purpose, they require granting an app debugger-level access to your machine, and they only work while the game is running. That's a lot of exposure for something you can accomplish by editing a file.

Memory trainer vs. save editor

They solve the same problem from opposite ends:

Memory trainer (Cheat Engine) Save editor (DiveSaveEd)
What it edits The game's RAM while it runs The save file on disk while the game is closed
Game must be running Yes — it attaches to the process No — it refuses to write if the game is open
How you find a value Scan, change it in-game, re-scan, narrow down, guess at addresses Pick the field by name from a list
Survives a game update Often not — addresses and offsets move Generally yes — it works on the save format, not on code layout
Undo Restart the game and hope you didn't save In-app undo, plus a timestamped backup of every write
Privileges needed Debugger-level access to another process Read/write on one file in your own home folder
Live effects (godmode, speed) Possible — that's its advantage Not possible, by design
Runs on macOS No Yes — native, universal, signed and notarized

To be straight about the trade-off: a save editor genuinely cannot do everything a trainer can. Real-time effects — freezing oxygen, infinite ammo, movement speed — live in memory and vanish when you close the game, so they're out of scope. What a save editor can do is everything that's persisted: currencies, inventory, ingredients, item counts, staff levels. In Dave the Diver, that covers virtually every reason people reach for a trainer in the first place, since the grind is in the resources, not in the combat.

What DiveSaveEd does instead

It opens your save, decodes it, shows you the values, writes them back, and closes. It never attaches to the game process, never reads or writes game memory, never touches the game executable, and makes no network calls of any kind — no account, no telemetry, no update pings.

DiveSaveEd editing Dave the Diver currencies on macOS DiveSaveEd in dark mode editing Dave the Diver currencies on macOS
Values by name, with exact entry, step buttons and per-field reset — no address scanning.

There's a raw inspector, but it's read-only

If what you liked about Cheat Engine was poking at the guts, the raw inspector lets you search the entire decoded save as formatted JSON. It's deliberately read-only: hand-editing raw values can set progression flags out of order and soft-lock a run. Looking is free; editing goes through the fields that are known to be safe.

The read-only raw JSON inspector in DiveSaveEd, showing a decoded Dave the Diver save
The whole save, decoded and searchable — read-only on purpose.

Will this get me banned?

No. Dave the Diver is a single-player game with no multiplayer, no leaderboards, and no anti-cheat software. This tool edits a file on your own computer while the game is closed. It never attaches to the game process, never reads or writes game memory, and never touches the game executable — which is, incidentally, precisely the set of behaviours anti-cheat systems in other games look for.

The realistic risk isn't a ban; it's a broken save. That's why every write is backed up first, every bulk action is undoable, and the raw editor is locked. See the FAQ for the specifics.

⚠️ One thing that will make edits “not work” Steam Cloud restores the old cloud save over your edit at launch. Quit the game, turn Cloud off for Dave the Diver in its Steam properties, then edit — the full order is here.

Get it

Download DiveSaveEd — free Read the source

macOS 14+, Apple Silicon and Intel. Signed and notarized by Apple. MIT licensed, no ads, no network.


Related