Save Compatibility

Specific installed-mod persistence paths are runtime tested, while broad/general SavePersistence is intentionally not advertised.

Dedicated FTK2 1.14.6 runs proved:

• custom ConfigName, stable Thing.Id, and material serialization;
• unequipped inventory save/load across two processes;
• equipped MAIN_HAND save/load across two processes;
• exact Thing adoption/reconstruction without replacement creation;
• active-definition protection while loaded references remain;
• compatible installed-definition load preflight and adoption;
• missing-definition detection before commit;
• blocked-load recovery without save write or graph mutation.

These results do not promise universal persistence for every future content system, migration across arbitrary Toolkit versions, or multiplayer synchronization.

Warning

Do not force-load a save after removing a required custom definition. Restore the owning mod and compatible Toolkit version, then use the missing-content diagnostics to identify the absent namespaced IDs.

Keep published IDs stable and treat removal/renaming of save-referenced content as a migration problem.