Help Index → When something does not behave as expected → Use case 54
Highlight unavailable means the app cannot prove a reliable structural match between that node and the displayed JSON. It refuses rather than jumping to an arbitrary repeated word or silently repairing data.
Before you start
- Read and retain the complete refusal message. Do not save or edit values simply to dismiss a navigation problem.
- 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. Copying a node label is not a JSON backup.
- A parse error can leave the old tree with a green light; [] is ignored, and Pretty Print can overwrite invalid pending text from the old model. Preserve text and verify actual values, not lights.
- Do not sync or Pretty Print Inventory Raw JSON: its current dictionary-assignment defect is not reliable inventory replacement. Use Organizer for supported moves or Replace Items from Backup for supported replacement.
Steps
- Dismiss Highlight unavailable and check whether Raw JSON was edited after the current Node View was built. Compare the intended change with the existing record; the previous cursor selection remains unchanged on refusal. (control reference)
- After preserving ALL pending panes, reapply understood edits in bases, starships or teleport endpoints one tab at a time; correct syntax, Sync to Node View, wait for Processing to dismiss, and verify the exact value in both panes before the next tab. After a parse error, do not trust a green light or old tree; [] is ignored and Pretty Print may overwrite invalid text. For inventory edits, do not sync/Pretty Print: use supported structured tools instead. (control reference)
- Select the node again in the freshly built tree, then retry Highlight In Text Box. Do not rely on an earlier selection after deletion, reordering or another tree change. (control reference)
- If refusal persists, inspect the message for unsupported, duplicate-key or unmapped structure. Use Search Text only as a manual inspection aid and check the surrounding record yourself; do not assume the first matching value identifies the node. (control reference)
Expected result
- Successful navigation uses the exact structural key/value location and selects its line, including when text formatting differs.
- On refusal, text, tree and save data remain unchanged. The app does not automatically synchronize, regenerate text or choose a guessed match.
What changes, and when to save
Highlighting itself is read-only. A deliberate synchronization can publish your text edits into app memory, but neither navigation nor synchronization writes the live save.
Check the result
- On success, check the selected field within the correct record, especially for repeated names and values. If a warning remains, preserve the text and seek help with the exact message rather than making speculative structural edits.
Important details and recovery
- A green sync indicator alone does not prove a reliable mapping or game-valid data.
- The same navigation refusal rules apply in bases, starships and inventories, but Inventory Raw JSON sync is defective and is not a repair path. Preserve text and use Organizer or supported replacement; do not use Pretty Print to repair ambiguity.