Help Index → Working with inventories → Use case 41
Use only existing valid inventory cells. The Organizer’s expansion checkbox is the capacity safeguard; the legacy Sorter has no equivalent no-expansion workflow.
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.
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)
- If Inventory Organizer is not already open, choose Inventory Processing → Node View → Inventory Organizer before using the dialog controls below. (control reference)
- Click Clear, then check only Exosuit as a source. Leave all other source boxes unchecked. (control reference)
- Set Resources → Container 1. Set Crafted products, Technology, Consumables, Trade goods and Special items to Leave where they are. (control reference)
- Uncheck Expand all Destination storages to 120 cells. Also uncheck Overflow: if destination is full, overflow to other 'Container' type storages. for this single-destination example. (control reference)
- Click Review Moves and check the proposal. Use Apply to app data only if movement within existing capacity is wanted. (control reference)
Expected result
- The planner uses actual unoccupied ValidSlotIndices, including sparse grids, rather than assuming every destination has 120 usable cells.
- Records fit as whole slot/stack records or remain in Exosuit. Existing amounts are unchanged; the operation does not merge stacks to manufacture room.
What changes, and when to save
Review Moves changes no inventory data. Apply to app data publishes the reviewed candidate in memory, marks it modified and closes the dialog. File → Save is separate and writes the loaded save target. Organizer preferences persist even when Close cancels the proposal; neither a review nor preferences create a save backup. Before a live write, compare every intended edit with its preserved copy; a refreshed pane can hide lost pending work.
Check the result
- Inspect Container 1’s ValidSlotIndices and contents after applying. Compare its valid-cell list with the pre-operation state and inspect Exosuit for retained resource records before saving.
Important details and recovery
- If you deliberately enable overflow, leave expansion unchecked: eligible spare containers must then use their existing free cells too.
- With no sources selected and expansion off, Review Moves is disabled.
- A full destination may produce no positive transfer row. No row is not proof that the source had no matching resources.
- Replace Items from Backup is not this workflow: it can expand a small target independently of Organizer settings.