Legacy Sorter captions normally use Storage Container 1 through Storage Container 10 followed by the loaded inventory Name (or No name provided), not Organizer’s Container 1 captions. The legacy list filters missing/falsy inventory records but derives type labels from the unfiltered fixed-path index. With an earlier missing record, a later actual inventory can receive the wrong storage-type caption even though its hidden inventory_id still targets that later object. Do not route solely by the caption; inspect actual Name/Slots and destination contents. Prefer Organizer’s stable-path roster in such contexts.
Before synchronization, formatting or a structured operation, copy EACH pending Raw JSON pane you need into separate external inspection files. Updating one tab can refresh ALL four editors and overwrite other pending text. Reapply, synchronize and verify only understood Bases, Starships or Teleport Endpoints edits, one pane at a time. Keep Inventory text externally: do not synchronize or Pretty Print it because its current update path is defective. Use the documented structured inventory tools from a trustworthy baseline instead. If pending Inventory text blocks a tool, preserve it, deliberately reload a trustworthy saved baseline when ready to abandon the pending app state, then recreate supported changes through structured tools. Never click Sync in every pending tab just to obtain green indicators.
Follow the same branch you see in the application. Select an item below for its definition and behavior.
Check actual inventories from which matching whole slot records may be moved. This is the legacy Sorter roster, not the Organizer roster; do not assume it has Organizer’s empty-slot and invalid-record exclusions.
Check receiving inventories. Each target has its own category dropdown. Existing contents remain but positions are compacted first; the sorter resets each processed target to a 120-cell grid. Identical source/target inventories are skipped.
Select one or more saved InventoryType categories for each target; names alone do not determine routing. The dropdown displays comma-separated selected labels and is not a free-text field.
Inventory Processing → Node View → Inventory Sorter → Categories → Product (Crafted or Special Items)
Inventory Processing → Node View → Inventory Sorter → Use All Unselected Storage Containers For Overflow
Use All Unselected Storage Containers For Overflow
Checked initially. The current implementation scans backward from Storage Container 10 and adds unchecked targets until it meets the first checked container, then stops. Do not assume the label guarantees that every unchecked container is used. Added overflow targets accept all six categories.
Runs immediately against app-model data; there is no Review/Apply stage. Saves sorter choices and normally reports Inventory has been sorted! before closing. Source/target/category choices must be meaningful. The legacy caller can still show its completion notice after an internal validation warning, so inspect the actual result rather than relying only on that notice. File saving remains separate.