Help Index → Working with bases → Use case 20
Use a base’s summary label to distinguish similar names before backing it up, moving it, or deleting it. The label combines identity clues and a count of saved construction records; it is not a guarantee that the base is valid in the game.
Before you start
- Load the intended save and active context.
- If you edited Bases Raw JSON, synchronize it before relying on the Node View labels.
- 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 and expand the list root to expose the complete base records. (control reference)
- Read the bracketed position, Gal name, Sys, Parts and Base portions of the candidate label. Compare all of them when names repeat. (control reference)
- Right-click that complete record and choose Highlight In Text Box to locate its corresponding Raw JSON. (control reference)
- Inspect Name, GalacticAddress and Objects in the record. Return to the complete base label before choosing a base-level command. (control reference)
Expected result
- Gal name is derived from GalacticAddress; Sys is the system component of that address, shown in hexadecimal. Parts is the length of Objects, or zero when Objects is absent.
- The bracketed number is a zero-based list position and can change after sorting, insertion or deletion. The other parenthesized count describes dictionary fields, not build parts.
What changes, and when to save
Inspection and highlighting do not write a backup or save file. Any subsequent record edits remain in app memory until you explicitly save the loaded NMS context. 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 the highlighted record has the intended name and address, especially if two bases share a name.
- Treat Unnamed Freighter Base as the app’s empty-name fallback, not independent proof of base type.
Important details and recovery
- Parts counts saved object records, not an independently measured in-game construction limit. If highlighting refuses, synchronize or rebuild the view rather than guessing a nearby JSON block.