CoCoFlow 0.4.4 release notes
CoCoFlow 0.4.4 was released on October 18, 2026.
- Release tag:
v0.4.4, commit2b61e3eb3912762195fa1266c0763e8374146705. - Package history:
CHANGELOG.md.
Typed Containers and Inspector workflow
Section titled “Typed Containers and Inspector workflow”PersistenceContainerHost stores [Serializable, PersistenceData] business structs
in typed tables. Type + ID identifies a row; matching Containers share data and
existing rows take precedence over initial candidates. Same-object business scripts
prepare candidates in Awake, obtain handles in Start after Container OnEnable registration,
and modify data through ref handle.Value. Gameplay remains in business code.
PersistenceHost exposes ContainerHost wiring, slots, the initial slot, directories,
absolute path previews and folder actions. Container Inspectors provide searchable
short type names and nested initial-data editing; ContainerHost shows runtime table
and binding statistics.
Editor Debug Mode saves and loads in the host’s Assets/DebugSaves/. Files are
created on an actual save; old files are not moved automatically. Player uses normal
directory configuration. Host and static APIs use the same save/load flow.
Fixes and compatibility boundaries
Section titled “Fixes and compatibility boundaries”- Re-enabling the same ContainerHost preserves changes made after its last load.
- Type selection excludes Editor-only/test assemblies absent from a normal Player.
- Removed Store/Catalog/Bridge and Container gameplay templates/commands; old Container gameplay data is not migrated.
- StateGraph persistence APIs and lifecycle stay unchanged; Graph-only projects need no new component. Saves remain schema v2, with Container section format v1.
Known limitations
Section titled “Known limitations”Player save/load and stripping compatibility have not been validated. Editor verification and generated linker metadata do not establish Player compatibility.
These issues were accepted in PR #71 and remain unfixed in 0.4.4:
| Issue | Current limitation |
|---|---|
| BUG-111 | Failed loading may leave a pending snapshot for later registrations to consume. |
| BUG-112 | ../ can resolve outside the default directory; save paths are not a directory sandbox. |
| BUG-113 | Closed generic root structs fail when saving; use ordinary non-generic roots. |
| BUG-114 | Precompiled business DLL types may be omitted from the picker and stripping metadata. |