A save system that survives a crash mid-write - and proves it. Atomic writes with backup, checksummed files, versioned sections with migrations, and a Save Browser showing what is inside every save.Quick Save Pro is a save system whose crash-safety is not a promise but a test result. Every write goes temp file, then backup, then promote - so at no moment does the disk hold zero good copies. The test suite proves it by tearing save files in half at every stage of the write and loading anyway.CRASH-SAFE BY CONSTRUCTIONA crash mid-save leaves either the new save or the previous one on disk - never a corrupt file and nothing else. If the main file is torn, the load falls back to the backup automatically and tells you it did.NOTHING FAILS SILENTLYEvery file starts with a QSAVE header carrying a SHA-256 checksum of the payload. A truncated or edited file is caught on load. Every load returns an outcome in words - Loaded, LoadedFromBackup, Missing, CorruptWithoutBackup - plus a sentence explaining what happened, so your load screen can tell the player the truth.VERSIONED SECTIONS WITH MIGRATIONSEach serializable class you bind is stored as its own named section with its own version number. When a section's shape changes, register one pure migration step per version bump. Old saves walk the chain on load; a missing step is refused with its exact position named, and the bound object is left untouched. One section's problem never touches another, and sections your build does not know about - DLC, mods, a newer build's data - survive a save/load cycle untouched.SAVE BROWSERTools > Quick Save Pro > Save Browser lists every save file with its outcome, its sections with versions and sizes, and the exact JSON inside. "Why does my save not load" is answered by looking, not guessing.LOAD MENUS THAT NEVER LIESaveCatalog scans the save folder and actually decodes every file - checksum, backup fallback and all - so a load menu built from it never offers a slot that would then fail to load.A DEMO WITH A SELF-DESTRUCT BUTTONBuild the demo scene from the menu, press Play: walk with WASD, collect coins, save with F5 - then press F8 to tear the save file in half, as if the game crashed mid-write, and press F9 to load anyway and watch the backup restore your exact position and coins.HONEST LIMITSSections are serialized with Unity's JsonUtility: fields only, no dictionaries or polymorphism inside a section. Files are plain text and not encrypted - the checksum is integrity, not secrecy. These limits are stated in the documentation rather than discovered in production.WHAT IS IN THE PACKAGEFull C# source. Runtime with zero dependencies, editor window, buildable demo scene, README and CHANGELOG. Works with the Built-in Render Pipeline, URP and HDRP - the runtime never touches rendering.- Atomic write order: temp file -> previous save becomes .bak -> temp promoted. At no moment does the disk hold zero good copies; verified by tests that tear files at every stage.- File format: "QSAVE 1 " header, SHA-256 first 8 bytes over the payload, UTF-8 plain text.- Load outcomes: Loaded, LoadedFromBackup, Missing, CorruptWithoutBackup - each with a worded explanation.- Sections: named, versioned, serialized with JsonUtility; one section's failure never touches another; unknown sections are preserved across save/load cycles.- Migrations: pure string-to-string steps registered per section and version; a broken chain is refused with the missing step named; the bound object is left untouched.- SaveCatalog: scans a folder and fully decodes every file before a menu offers it.- Save Browser editor window: outcomes, sections, versions, sizes, pretty-printed JSON.- Files live in Application.persistentDataPath/saves with .bak alongside.- Runtime has zero dependencies and never touches rendering; works on all render pipelines.- Requires Unity 2021.3 or newer. Full source included.AI assistance was used while making this package, and here is exactly where.Code: an AI coding assistant helped write and review the C#. The safety claim was proven rather than asserted: the tests tear save files in half at every stage of the write and load anyway, and the invariant that the disk never holds zero good copies is checked step by step. Twenty of twenty storage checks pass, each with a negative control - removing the checksum check makes three of them fail, which is how we know the checks are real.Text: the README, the documentation and this store description were drafted with AI assistance and then edited by hand for accuracy.Images: no image content is AI generated. The screenshot is a real capture of the sample scene running in the Unity Editor. The other pages are diagrams of the write order and the file format, plus the package's own API - illustrations and real code, not pictures of the product.Nothing in the package generates content at runtime. It writes and reads plain text files; there are no dependencies, no accounts and no network access.
