Help Index → Working with inventories → Use case 45
Choose the tool by its commit and capacity behavior, not by similar names. Inventory Sorter and Inventory Organizer are separate side-by-side buttons in Inventory Processing → Node View.
Before you start
- Load the intended save and confirm its active Main or Expedition context. Make a full backup before changing data.
- Before sync, formatting or structured refresh, copy EACH pending Raw JSON pane to its own external file: one sync can overwrite all others. Reapply non-inventory edits one pane at a time, syncing and comparing exact values before the next. Parse errors can leave an old tree with green status; [] is ignored, and Pretty Print can erase invalid text.
- Do not sync/Pretty Print Inventory Raw JSON: dictionary assignment is defective. Use Organizer for supported moves or Replace Items from Backup for supported replacement.
- If an earlier inventory record is missing, legacy Sorter captions can shift and misidentify storage types. Prefer Organizer’s stable-path roster; verify the actual inventory Name/Slots and destination contents, not the legacy caption alone.
Steps
- Preserve EACH pending pane externally before refresh: one sync can overwrite the others. Reapply non-inventory edits one pane at a time, syncing and verifying exact values. Stop after parse errors even if green; [] is ignored and Pretty Print may erase invalid text. Use structured tools, never defective Inventory Raw JSON sync/Pretty Print. (control reference)
- Open Inventory Organizer when you need a private review, one destination per category, or control over automatic capacity expansion. (control reference)
- For a constrained Organizer example, click Clear, check Exosuit only, set Resources → Container 1 and all other categories to Leave where they are. Uncheck both Optional boxes. (control reference)
- Use Review Moves before Apply to app data, or Close to reject the data proposal while retaining preferences. (control reference)
- Choose Inventory Sorter instead only when immediate execution is intended and source/target identity is certain. Check Exosuit only under Source Inventories, Storage Container 1 (followed by the loaded inventory name) only under Target Inventories, and Substance only for that target. Verify actual Name/Slots; if missing records make captions uncertain, cancel and use Organizer. Uncheck overflow before Execute Sort. (control reference)
Expected result
- Organizer stages a private candidate and applies only after explicit review. Sorter changes app-model inventories directly when Execute Sort runs.
- Sorter reindexes targets and resets their valid cells to its 120-cell grid. Organizer can leave capacities unchanged when expansion is unchecked.
What changes, and when to save
Organizer Review is private; Apply and Sorter Execute change app memory, not the live save. File → Save is separate. Organizer preferences persist on changes/Close; Sorter stores source, target and category choices on Execute. Neither tool creates a backup. Compare every intended edit with its preserved copy before any live write; refreshed panes alone cannot prove preservation.
Check the result
- Inspect actual source and destination contents after either tool. Treat File → Save as a separate decision affecting the loaded save target.
Important details and recovery
- Do not execute both example routes expecting the second to be a preview of the first.
- Sorter overflow scans backward only until the first checked container; Organizer uses available containers unassigned to every category.
- Sorter may show a completion message after a validation warning. Inspect results instead of taking that message as proof.