Help Index → Working with bases → Use case 21
Export one complete base as a reusable base-backup file without exporting the entire save. The backup captures that record from the current tree, including any synchronized edits already made in the app.
Before you start
- Identify the intended base by name, galaxy, system and part count.
- Synchronize pending Bases Raw JSON edits first if you want those edits included. A full-save backup is still separate protection.
- 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 locate the complete labeled base record directly under the list root. (control reference)
- Right-click that base label and choose Backup a Base. If the command is missing, click the whole base rather than a nested field or the list root. (control reference)
- Choose a distinct filename and folder in Save File. Use the NMS Base Files format, normally ending in .nms_base.json, and avoid overwriting your only earlier copy. (control reference)
- Complete the file dialog and check for File saved successfully. Retain the chosen path for a later restore. (control reference)
Expected result
- The app writes one JSON object representing the selected base to the chosen file. It does not export the full PersistentPlayerBases array or the whole loaded context.
- An empty base name uses default as the proposed filename stem; that stem does not identify the base for you.
What changes, and when to save
Backup a Base writes the separate backup file immediately. It neither saves your current app edits into the live game file nor creates a complete live-save recovery backup. 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 destination and filename you chose, especially for unnamed or identically named bases.
- Confirm the source base is still present with the same position and Parts value.
Important details and recovery
- The export includes the saved record as it stands; it does not sanitize ownership, coordinates or linked relationships for another account. A write error is not a completed backup.