Roadmap
This roadmap uses three states only, and each one means exactly what it says:
Available Released — in the package today, documented and covered by tests · Roadmap Planned — agreed on, not started · nothing in the planned column is available today
0.1.0 — the framework
ReleasedOptions, diagnostics and the result model; the document model and serializer abstraction; local storage with atomic writes and recovery; the save container and slots; versioning and migration; the operation coordinator; persistent object identity; autosave and checkpoints; security — integrity, authentication, encryption and bounded compression.
0.2.0 — cloud, tooling and verification
ReleasedVendor-neutral cloud synchronisation with conflict policies, conflict-copy preservation and an offline queue; the guided Editor setup with presets; validation with remedies; the support matrix as data; the storage probe; generated code; fuzz, corruption, culture and performance tests; and an IL2CPP player probe that found — and fixed — a real culture defect.
In development#
| Item | Status | Notes |
|---|---|---|
| Documentation portal | Available | This site: versioned content, search, breadcrumbs and previous/next navigation generated from one content tree. |
| Adapter authoring guide | Roadmap | A worked transport implementation, so the cloud seam is not the only thing standing between a game and its provider. |
| More Editor diagnostics | Roadmap | Extending the existing finding format rather than adding a second one. |
Planned#
| Item | Status | Notes |
|---|---|---|
| Generic REST adapter | Roadmap | The most likely first adapter: no vendor SDK, and the failure-injection doubles are already HTTP-shaped. |
| Firebase adapter | Roadmap | A transport over Firestore or Cloud Storage, with honest conditional-write capabilities. |
| PlayFab adapter | Roadmap | A transport over the entity and title data APIs. |
| Steam Cloud adapter | Roadmap | If a shipped project needs it; the same seam applies. |
| Visual Scripting integration | Roadmap | Nodes over the existing facade, for projects that do not write C#. |
| PlayMaker integration | Roadmap | The same idea for a different authoring workflow. |
| Mobile platform verification | Roadmap | Running the existing suite and probe on Android and iOS, and reporting what it finds. |
| Console platform verification | Roadmap | Requires an SDK; the most likely outcome is an ISaveStorage or IPathProvider adapter per platform. |
| Additional Unity type support | Roadmap | Driven by what shipping projects ask for, not by filling a list. |
Deliberately not planned#
| Item | Status | Why |
|---|---|---|
| A bundled cloud service | Not supported | The seam is ICloudTransport; bundling a provider would be a vendor lock-in and a support liability. |
| Key storage or rotation policy | Not supported | Hiding a key is a platform decision. The framework asks for keys and clears its copies. |
| Accounts, leaderboards, telemetry | Not supported | Not persistence. A framework that grows these stops being reusable. |
| Server authority | Not supported | Client-side protection raises the cost of tampering; it does not establish trust. |
| Rollback (replay) protection | Not supported | Detecting a restored older save needs a server-side sequence. |
| Save-file editing tools | Not supported | Player data is not a toy; the Editor inspects and reports, and never rewrites a save. |
Where to check what exists today#
The documentation describes only what is released, and the changelog records what each release contained. Anything on this page that is not in those two places is a plan, not a feature.