Help Index → Working with bases → Use case 25
Remove a visually contiguous group of unwanted base records using right-button range selection. This selects tree nodes, not a special checklist of base identities, so collapse the records before selecting a range.
Before you start
- Keep a full backup and individually export any base you may want to reinsert.
- Synchronize pending text and identify the complete group by labels rather than position alone.
- 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.
- Open Bases, expand the list root, and collapse each individual base so only complete base rows lie between your intended endpoints. (control reference)
- Hold the right mouse button on the first unwanted base and drag to the last. Review all highlighted rows before releasing. (control reference)
- On release, review Delete N Nodes. Choose it only when the highlighted range contains exactly the whole bases you want removed. (control reference)
- Review the Delete Nodes confirmation and cancel if the number or range is wrong. Otherwise confirm and inspect the refreshed list. (control reference)
Expected result
- The generic deletion operation removes the selected nodes and updates loaded app data. Remaining base records are retained in their relative list order and receive new positions.
- The menu count is a count of selected visible nodes, not proof that all selections are complete base records.
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
- Confirm each intended base is absent and each intended survivor remains.
- Compare the decrease in the base count with your intended whole-base selection; inspect Raw JSON if the result is unexpected.
Important details and recovery
- A right-drag range includes visible child nodes of expanded bases. Cancel and collapse them before retrying; do not treat a large node count as a large base count. This generic operation does not validate linked Corvette builds or game-side dependencies.