Roadmap

This roadmap uses three states only, and each one means exactly what it says: released (in the package, with tests), in development (someone is working on it and it may ship), planned (wanted, not started). No dates are promised, and nothing in the last two is usable today.

Released#

• Saving and loading — typed values, your own classes, and the collections built from them.
• No-code component with Save and Load chosen per field, and handlers for the Unity components a game moves.
• Slots, metadata, rotating backups and the recovery ladder for a damaged file.
• Protection — AES-256 with HMAC authentication on request, compression when it helps.
• Asset references through the registry, and runtime prefab instances through Persist.Spawn.
• Cloud — a provider contract, a folder provider and a REST provider, conflict detection by content, keep-local / keep-remote / keep-both, and an offline queue.
• Migrations — ordered steps, preview, a copy before writing, and a rollback if the write fails.
• Editor tools — save folder, field discovery, validation, registry, cloud actions, migration preview and apply, and a diagnostics report.

In development#

• More samples. A clicker/idle sample, a physics sandbox and a small multi-scene RPG sample, each importing from Package Manager and playing without setup. Today the package ships one quick-start sample.
• The Addressables seam. A resolver that takes the registry's place when a project stores its content in an Addressables catalog — including the alias support that keeps a save working when an address changes. It is designed and written down, not written into the package yet.

Planned#

• Scene and object persistence for multi-scene games: additive scene loading, objects that must stay destroyed when a scene is revisited, and an explicit lifecycle for restore order.
• More built-in component handlers where a Unity component has state worth remembering.
• A performance section in the documentation backed by measurements, rather than by intuition.

Deliberately not planned#

• A cloud adapter for a service whose SDK cannot be run here (Unity Cloud Save, Steam Cloud, Firebase, Supabase, PlayFab). The contract they would plug into is published, and the page about writing a provider says exactly what each one would take. Shipping an untested adapter and calling it supported is the one thing this roadmap will not do.

How this page is kept honest#

Anything that ships moves to Released with the tests that prove it. Anything that stops being worked on is deleted from this page rather than left to age. The changelog records what actually shipped.