🧰 Zion Tools

Unity Editor Asset Tools

Overview Zion Scene Backup Zion Save Inspector

Overview Installation Quick Start Concepts Window Reference Editing Tree Search Save Diff Schema & Reports Built-in Providers PlayerPrefs Custom Source Custom Format Tutorial API Surface Save Safety Troubleshooting

Editing

The tree editor exposes every value in the save as a foldout or inline field. Editing rules by node kind:

Editing rules

Strings edit inline.
Numbers edit as double. If your format needs int/float, cast back in Serialize.
Booleans edit as toggles.
Null is read-only as a value - use Change Type from the right-click menu to convert it to something editable.
Object/Array structure is fully editable.

Right-click context menu

On an Object: Add Child ▸ (kind) appends a new key and immediately drops you into rename mode for the key.
On an Array: Append Item ▸ (kind) appends a new element; indices are kept in sync automatically when items are added, removed, or moved.
On any child of a container: Rename Key… (Object only), Duplicate, Delete, Move Up / Move Down, and Change Type ▸ (kind) for primitive nodes.
On any node 1.1: Copy ▸ As JSON and Copy ▸ Path. On containers: Paste JSON as Child. On any child of a container: Paste JSON Replacing This Node.

Press Enter to commit a rename, Escape to cancel.

Clipboard - copy and paste as JSON 1.1

JSON is the clipboard interchange format regardless of the save's own on-disk format, so subtrees move cleanly between saves, between formats, and between Unity instances.

Copy ▸ As JSON copies the node and all children as pretty-printed JSON.
Copy ▸ Path copies the node's dotted path (e.g. inventory[2].id) - handy for bug reports.
Paste JSON as Child parses the clipboard and appends it to the container. Object keys are made unique automatically; array indices stay in sync.
Paste JSON Replacing This Node replaces the node's value while keeping its key or index.

Invalid clipboard JSON is rejected with a clear error - nothing in the tree changes.

Adding new fields

Right-click the root node and choose Add Child ▸ Number. A new new_field key appears and the inspector drops you straight into rename mode for the key - type the name you want, press Enter, then edit the value. Save again and your save now carries a field that wasn't in the original schema. The same pattern works for nested structures: right-click an array and Append Item ▸ String to add an element, with indices kept in sync automatically.

Continue to Tree Search.