gum-tool-save-classes

Gum's save/load data model serializes types like ElementSave, StateSave, and VariableSave to XML using ShouldSerialize patterns to minimize empty elements. This reference guide documents the exact file structures and serialization behavior for these core data types.

When renaming instances or variables in Gum, cross-element references are maintained through propagation rules documented in this guide. It explains how runtime and save data interact so that renaming an object updates all dependent references across the project.

Two-phase loading is Gum's deserialization approach for resolving complex cross-references between saved objects like ComponentSave and BehaviorSave. You need to understand it when modifying Gum's load behavior or troubleshooting reference resolution during project initialization.

GumProjectSave is the root object containing ScreenSave, ComponentSave, and StandardElementSave types, all of which derive from ElementSave. ElementSave objects contain StateSave and VariableSave collections, defining the hierarchical structure documented in this guide.

Gum uses ShouldSerialize patterns on properties within VariableSave and other save objects to prevent empty XML tags. This guide details how these patterns minimize file size by omitting default or empty values during serialization.

Yes, this guide covers exposed variables and BehaviorSave types alongside InstanceSave and VariableSave. It documents their relationships within the save/load hierarchy and explains their specific serialization and deserialization behaviors.