Help Index → Working with starships → Use case 27
Choose several ships in one Upgrade Starships operation and review each result independently. A successful ship does not make another selected ship’s rejection or skipped technology step a success.
Before you start
- Make a full backup and verify the active loaded context.
- Complete the preserve-all/one-tab preflight before opening the picker; the operation will not silently synchronize text for you.
- Before any sync, Pretty Print or structured refresh, copy EACH pending Raw JSON pane’s complete text to a separate external file. Successful tab sync refreshes ALL Raw JSON panes and can erase pending text elsewhere.
- Before opening Upgrade Starships, record each intended zero-based ownership index in the tree. Named picker checkboxes show no visible index: count ALL ownership-ordered rows from one, including unoccupied rows; tree index 0 is picker row 1. Cancel if you cannot identify the row confidently.
Steps
- If several panes contain wanted pending work, preserve ALL before any refresh. If applying it, reapply and verify one non-inventory tab at a time; never simply sync each changed tab. Keep inventory text externally and reproduce supported changes with structured tools instead.
- In Starships, click Upgrade Starships and read the replacement/preservation warning. (control reference)
- Check the intended ownership-ordered rows by counting ALL rows from one, including unoccupied rows, against the zero-based tree indices recorded before opening. Named labels have no visible slot number; cancel if any row identity is uncertain. (control reference)
- Review the complete checked set, especially duplicate names and unnamed or unoccupied labels. Click Cancel if you need to inspect the roster first. (control reference)
- Click OK to apply the selection. After progress, read every row and the Upgrade notes section in the results, then close the report with OK. (control reference)
Expected result
- Selected ships are planned independently with matched reference families; rejected ships and unoccupied slots do not prevent other selected ships from receiving their permitted changes.
- Non-Corvette technology Slots are replaced wholesale on technology success. Corvettes retain existing equipment and builds and add only missing reference technology. Stats/class may still apply when technology is skipped.
What changes, and when to save
Changes stay in the loaded app data until File > Save NMS Save File writes the retained live slot and Main or Expedition context. Close No Man’s Sky and confirm that destination before saving; a green synchronization light alone does not mean the game file was saved. A refreshed pane is not proof that pending text survived; compare the intended values with your external copies before authorizing a live write.
Check the result
- Account for each selected slot as Upgraded, Already up to date, stats/class applied with tech skipped, Rejected, or unoccupied.
- Inspect unexpected outcomes and check unselected ships remain unchanged before deciding to save the combined result.
Important details and recovery
- The batch is not a promise of uniform success. Do not blindly repeat upgrades to cure a reference or layout error; read the per-ship reason first. A batch containing no actual changes does not create a new model edit.