Help Index → Working with teleport endpoints → Use case 50
Inspect a destination already recorded in the loaded context without changing the player’s location. An endpoint entry is saved data, not a live connection to that place.
Before you start
- Load the intended save and confirm whether its active context is Main or Expedition. Endpoints belong to that loaded context.
- Before any synchronization, Pretty Print or structured refresh, copy EACH pending Raw JSON pane to its own external file; syncing one tab can overwrite pending text in all others. If the tree does not reflect intended edits, use the deliberate recovery in cases54–56 rather than automatically rebuilding it.
Steps
- Open Teleport Endpoints and inspect the endpoint records beneath the outer array in Node View. Use the numbered record labels to distinguish entries, rather than treating a repeated name as unique. (control reference)
- Expand the intended record. Right-click it and use Toggle Expansion 2 Levels if needed; inspect its UniverseAddress and Position fields before deciding it is the destination you want. (control reference)
- Right-click the record or a particular field and choose Highlight In Text Box to inspect its corresponding Raw JSON line. Navigation selects a line; it does not rewrite the endpoint. (control reference)
- For a text search, right-click Raw JSON and choose Search Text. Search for a known name or value and inspect the surrounding record. At End of Search, acknowledge it, Close Search Dialog, reposition the editor cursor, then reopen Search Text; search does not automatically wrap. (control reference)
Expected result
- The selected record’s stored address and coordinates are available for inspection. Expanding, searching and highlighting do not relocate the player.
- Copy This Node’s Text copies its visible label only; select actual Raw JSON text if you need the recorded values.
What changes, and when to save
Inspection needs no File → Save. Typing or pasting in Raw JSON is an edit and creates a separate synchronization and saving decision.
Check the result
- Match both the endpoint label and its address/position, particularly when names repeat. Confirm you have not chosen Set Player Location to this Endpoint while merely inspecting.
Important details and recovery
- A familiar label does not establish that the stored position is safe or current in the game.
- If highlighting refuses, follow its message and reconcile tree/text deliberately; do not change coordinates just to make navigation succeed.