Help Index → Working with teleport endpoints → Use case 51
Stage a player-location change using one endpoint already stored in the active context. This edits saved-location data in the app; it does not teleport a running game.
Before you start
- Keep NMS closed, load the intended live save and confirm its active Main or Expedition context. Make a full backup before changing the location.
- Inspect the endpoint’s address and coordinates; do not proceed if the destination is uncertain.
- Before sync, formatting or structured refresh, copy EACH pending Raw JSON pane to its own external file: one sync can overwrite all others. Reapply non-inventory edits one pane at a time, syncing and comparing exact values before the next. Parse errors can leave an old tree with green status; [] is ignored, and Pretty Print can erase invalid text.
- Do not sync/Pretty Print Inventory Raw JSON: dictionary assignment is defective. Use Organizer for supported moves or Replace Items from Backup for supported replacement.
Steps
- Preserve EACH pending pane externally before refresh: one sync can overwrite the others. Reapply non-inventory edits one pane at a time, syncing and verifying exact values. Stop after parse errors even if green; [] is ignored and Pretty Print may erase invalid text. Use structured tools, never defective Inventory Raw JSON sync/Pretty Print. (control reference)
- Open Teleport Endpoints. Expand the outer array and identify the complete endpoint record you intend to use, checking its label, UniverseAddress and Position rather than selecting a similarly named entry. (control reference)
- Right-click that complete record directly beneath the array, not the array root or a child field. Choose Set Player Location to this Endpoint. This command immediately changes the in-memory location; it is not a preview dialog. (control reference)
- Read and dismiss the Set Player Location message. Treat Player has been moved as an app-data result, not confirmation of disk saving or a safe in-game spawn. (control reference)
- Review the intended change before choosing File → Save. Check the confirmation’s slot and Main or Expedition context; cancel if wrong. The later Live save written result reports the exact verified data and metadata paths. (control reference)
Expected result
- The active context receives the endpoint’s UniverseAddress and its three Position coordinates in the player/spawn location fields. LastKnownPlayerState becomes OnFoot.
- The endpoint list itself is not a new in-game teleport service. The command does not add a terrain-clearance offset.
What changes, and when to save
The context-menu command stages changes in app memory. Only a separately confirmed File → Save writes the loaded live target; keep the independent backup until the result is checked.
Check the result
- Confirm the endpoint you selected still has the address and three coordinates you intended. For a full-context comparison, inspect an exported context separately; the endpoint pane alone does not display all changed player/spawn fields.
Important details and recovery
- The app does not validate terrain or promise a safe arrival. Do not save an untrusted location.
- If the result is unwanted, preserve any other work you need and deliberately reload the disk save instead of assuming text Undo reverses this action.