Help Index → Working with starships → Use case 32
Use Delete Node on the complete Starships ownership record to invoke ship-specific deletion. Unlike generic base removal, this preserves fixed slot positions and performs the cleanup required by the selected ship category.
Before you start
- Keep a full-save backup; deleting a Corvette also removes its linked build.
- Load the correct context and identify at least one other occupied ship that must remain.
- 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)
- In Starships, identify the unwanted complete slot node using its position and resource identity; collapse its children to avoid selecting a nested field. (control reference)
- Right-click the whole slot and choose Delete Node. The request is validated before confirmation; a nested node alone is refused. (control reference)
- Review the Delete Nodes confirmation. Cancel if this is not the intended occupied ship, otherwise confirm. (control reference)
- Inspect the resulting empty slot, surviving roster, and any affected Bases records before saving. (control reference)
Expected result
- Ownership remains a twelve-entry array. The deleted position receives the appropriate empty ownership template and its legacy-colour flag resets; surviving ships keep their original positions.
- Custom-built ships also have their mapped appearance reset. Corvettes use their own empty template, reset mapped appearance, and lose their entire uniquely linked PlayerShipBase build. Ordinary ships do not have their appearance entry reset.
- If the deleted ship was PrimaryShip, selection moves to the lowest remaining occupied index. A CorvetteEditAssociatedShipIndex pointing at the deleted slot becomes -1; unrelated editor data remains.
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. Before a live write, compare every intended edit with its preserved copy; a refreshed pane can hide lost pending work.
Check the result
- Check the intended resource filename is now empty and every survivor remains at the same index.
- For a Corvette, confirm only its linked build disappeared; inspect the new primary selection when relevant.
Important details and recovery
- Deleting the last occupied ship is blocked. Missing or ambiguous Corvette builds, malformed linked data or stale selection refuse the request rather than falling back to generic removal. Deletion discards that ship’s equipment and cargo, not just its displayed name.