Help Index → Working with Node View and Raw JSON → Use case 15
Tools > Export 'BaseContext' JSON to Clipboard copies the whole loaded context model for inspection elsewhere. The menu label is fixed: if the loaded save selected ExpeditionContext, the exported model is that expedition context, not the inactive Main context.
Before you start
- Load the intended live save and verify its slot and recognizable data. Otherwise you may export startup or other current model data instead.
- Decide whether pending Raw JSON edits belong in the export. This command does not automatically synchronize them.
- 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.
- To include pending edits in the export, preserve all panes first and reapply/verify one non-inventory tab at a time. Use structured tools for wanted inventory changes. Inspect actual values before exporting; otherwise export contains only the current model, not the preserved pending text. (control reference)
- Choose Tools > Export 'BaseContext' JSON to Clipboard. (control reference)
- Acknowledge the Copied notice, then paste into a separate JSON-capable inspection tool or plain-text document. (control reference)
- Inspect recognizable records and the top-level context contents. The export contains the loaded context, not the full outer save with both context branches. (control reference)
- If you save the pasted text elsewhere, use a separate inspection file. Do not overwrite a live game data or metadata file with this plain JSON. (control reference)
Expected result
- Clipboard text is an indented serialization of the current whole-context model, including its sections beyond the currently visible tab.
- Unsynchronized text is not included merely because it is visible in an editor. Export reads the model without performing a synchronization step.
What changes, and when to save
The export action replaces clipboard text only. It does not write a file, create a full backup, change preferences, or save live game data. Any earlier synchronization updates app memory separately. 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 expected records and any deliberately synchronized edits in the pasted result.
- Do not treat the Copied notice as a game-save or backup completion notice. Modified Data Saved is not cleared by exporting.
Important details and recovery
- This is not the compressed game-save format or a full-live-tree backup.
- There is no visible corresponding whole-context clipboard import command in the current UI.
- JSON inspection does not validate edited data against game behavior.
- Inventory Raw JSON synchronization is currently defective: it adds index-keyed data inside inventory dictionaries instead of replacing the intended records. Do not sync or Pretty Print inventory text as an editing workflow; keep it externally, use supported structured inventory tools, and inspect actual Name, Slots and unexpected fields before saving.