Help Index → Working with bases → Use case 19
Reorder complete base records manually in Bases Node View when the automatic grouping is not the order you want. Work at the base-list level, not inside an individual base’s fields or construction objects.
Before you start
- Keep a full backup and load the correct Main or Expedition context.
- Synchronize pending Raw JSON edits before moving nodes.
- 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.
- Expand the base-list root enough to see each base label, then collapse the individual bases so their child fields are out of the way. (control reference)
- Use the left mouse button to drag one complete base onto another complete base under the same list root. Do not use right-drag, which selects a deletion range. (control reference)
- Release, let the tree and Raw JSON refresh, and inspect the actual resulting position. Repeat small moves until the order is correct. (control reference)
- Leave Sort By Gal, Sys, Name alone once your custom order is finished; another automatic sort will replace that order. (control reference)
Expected result
- Accepted drops remove and reinsert the complete record and publish the revised list to app memory. Positions and labels are refreshed.
- The generic drop handler requires compatible array/dictionary parents and refuses to drag a node whose parent has only one child.
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 the entire resulting base sequence, not just the dragged label.
- Check base count, addresses and part counts against the records you intended to preserve.
Important details and recovery
- Parent-type checks are structural checks, not game-side validation. Do not drag nested fields between records or apply this workflow to starships: safe ship reorder associations are not established.