The bug:
Look at the write() function — when it saves a file, it calls updateMeta(...), but that only updates an in-memory record. It does not call flushMeta(...), which is the function that actually writes that metadata to disk. flushMeta only runs when a separate 'flush' message is sent, or during a 'list' operation.
So here’s what’s actually happening to your save:
-
You save in-game.
-
The raw save bytes ARE written to OPFS storage.
-
But the “this file exists” record is only updated in memory — never saved to disk.
-
When the page reloads (or a new session starts), that in-memory record is gone. The worker only knows about files it can find in the persisted metadata file.
-
Look at the
listcase:if (fileMeta) { ... entries[...] = fileMeta; }— if there’s no metadata entry, the file is skipped entirely, even though the actual bytes are sitting right there in OPFS storage.
In short: your save data is very likely actually being written to disk in your browser — it’s just invisible to the game because the bookkeeping that says “this file exists” never gets saved. The game asks “does GTAVCsf1.b exist?”, checks the metadata index, finds nothing, and reports “couldn’t find” — even though the real file may still be sitting there physically.
This is about as concrete as a bug report gets. This isn’t speculation anymore — it’s a specific, identifiable logic gap in their write() function: it should call flushMeta() after writing, or the game should send a 'flush' message after every save, and evidently neither is happening reliably.