Help Index → Working with starships → Use case 28
Review the upgrade field boundary before accepting the picker. The operation uses matched reference data, but non-Corvette equipment replacement is deliberately broader than adding a few missing modules.
Before you start
- Make a full backup before replacing equipment you may want to keep.
- Load the correct context and complete the preserve-all/one-tab preflight. If necessary, inspect the target’s current technology and cargo before starting.
- 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, inspect the intended ship’s Inventory, Inventory_TechOnly and Inventory_Cargo in Raw JSON or the expanded node tree. (control reference)
- Click Upgrade Starships and read the bold warning before checking a ship. (control reference)
- For a non-Corvette, decide whether replacing the entire technology Slots array with the matched reference’s complete item records is acceptable. Cancel if you need to protect the current equipment first. (control reference)
- If acceptable, count ALL ownership-ordered picker rows, including unoccupied rows, to select the preidentified ship slot. Cancel if uncertain; otherwise click OK and inspect the successful or skipped technology outcome. (control reference)
Expected result
- Validated base-stat lists are copied into general and technology inventories. General and cargo inventory class settings are set from the S-class reference. Successful technology processing targets a ten-by-six grid of sixty enabled cells.
- Identity, resource and seeds outside replaced technology records, appearance, linked builds, primary-ship selection and cargo contents/geometry are preserved. Supercharged-cell records are retained when compatible with the target grid.
- Corvettes use missing-only technology additions instead of wholesale equipment replacement.
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
- For non-Corvettes compare the new technology layout with the reference-based result, not with an expectation that original extras survived.
- For a partial result check stats/class separately from unchanged technology items and capacity.
Important details and recovery
- Original technology extras, figurines, trails and module seeds can disappear on non-Corvettes. A malformed reference’s statistics or class causes whole-ship rejection; a technology-only failure does not cancel valid stats/class changes.