Help Index → Working with bases → Use case 24
Remove one unwanted base record from the loaded Bases list. Select the complete base rather than deleting one of its fields; the command acts on the node you actually right-click.
Before you start
- Keep a full backup; optionally export the individual base for later reinsertion.
- Load the correct context and synchronize pending text before working in Node View.
- 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.
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.
- Find the base using its name, galaxy, system and Parts label. Expand or highlight its JSON if the name is ambiguous. (control reference)
- Collapse its children and right-click the complete labeled base directly beneath the array root. (control reference)
- Choose Delete Node and review the Delete Nodes confirmation. Cancel if the selection is not the intended single base. (control reference)
- Confirm only when ready, then inspect the refreshed list and Raw JSON before saving. (control reference)
Expected result
- The chosen base node is removed from the list and the app refreshes its model and text. Later base positions shift and the base count decreases.
- The generic base deletion command does not perform ship-specific ownership, appearance or primary-ship cleanup.
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
- Check that exactly the intended base disappeared and nearby same-name bases remain.
- Check the remaining base count and review the full-save backup path before committing the edit.
Important details and recovery
- Deleting a nested Name, Objects or address node can damage a surviving record instead of deleting the whole base. Do not remove a Corvette’s linked PlayerShipBase here as a substitute for ship deletion; use the ship-specific safeguard workflow.