BBB NMS Save File Manipulator — Help

Reference arranged like the application

Inventory Processing

Important limitations before using these controls

  1. Before synchronization, formatting or a structured operation, copy EACH pending Raw JSON pane you need into separate external inspection files. Updating one tab can refresh ALL four editors and overwrite other pending text. Reapply, synchronize and verify only understood Bases, Starships or Teleport Endpoints edits, one pane at a time. Keep Inventory text externally: do not synchronize or Pretty Print it because its current update path is defective. Use the documented structured inventory tools from a trustworthy baseline instead. If pending Inventory text blocks a tool, preserve it, deliberately reload a trustworthy saved baseline when ready to abandon the pending app state, then recreate supported changes through structured tools. Never click Sync in every pending tab just to obtain green indicators.
  2. Legacy Sorter captions normally use Storage Container 1 through Storage Container 10 followed by the loaded inventory Name (or No name provided), not Organizer’s Container 1 captions. The legacy list filters missing/falsy inventory records but derives type labels from the unfiltered fixed-path index. With an earlier missing record, a later actual inventory can receive the wrong storage-type caption even though its hidden inventory_id still targets that later object. Do not route solely by the caption; inspect actual Name/Slots and destination contents. Prefer Organizer’s stable-path roster in such contexts.
  3. An import error does not guarantee an unchanged destination. The helper can expand ValidSlotIndices before it reads the backup’s Slots, so a backup missing Slots can fail after capacity already changed; there is no rollback around this helper. Do not retry or save blindly. Inspect target capacity and items, preserve needed work, and deliberately reload from the saved baseline if abandoning the failed replacement. A filename extension does not validate structure; use a known complete inventory export.
  4. Current Inventory Processing Raw JSON synchronization is defective: it assigns an integer-keyed entry into each existing inventory dictionary instead of replacing that inventory record. Intended fields may remain unchanged and unexpected fields may be introduced. Do not use this path as a reliable inventory edit/save workflow or save merely because the panes refresh. Prefer the structured Inventory Organizer or the supported inventory-replacement tool for their documented scopes, and inspect actual fields before saving.

Follow the same branch you see in the application. Select an item below for its definition and behavior.

Inventory Processing → Node View

Node View

Shows inventory data from the loaded context.

Inventory Processing → Node View → Inventory Sorter

Inventory Sorter

Opens the legacy immediate-execution Sorter, which has no Review/Apply stage. Organizer is a distinct structured operation. Legacy filtered-row captions can misidentify storage types when earlier inventories are absent; inspect actual data rather than routing solely by the caption.

Before using Inventory Sorter, read the shared safety limitations for this page.

Open Inventory Sorter help →

Inventory Processing → Node View → Inventory Sorter → Source Inventories

Source Inventories

Check actual inventories from which matching whole slot records may be moved. This is the legacy Sorter roster, not the Organizer roster; do not assume it has Organizer’s empty-slot and invalid-record exclusions.

Before using Source Inventories, read the shared safety limitations for this page.

Before using Source Inventories, read the shared safety limitations for this page.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Sorter → Target Inventories

Target Inventories

Check receiving inventories. Each target has its own category dropdown. Existing contents remain but positions are compacted first; the sorter resets each processed target to a 120-cell grid. Identical source/target inventories are skipped.

Before using Target Inventories, read the shared safety limitations for this page.

Before using Target Inventories, read the shared safety limitations for this page.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Sorter → Categories

Categories

Select one or more saved InventoryType categories for each target; names alone do not determine routing. The dropdown displays comma-separated selected labels and is not a free-text field.

Inventory Processing → Node View → Inventory Sorter → Categories → Product (Crafted or Special Items)

Product (Crafted or Special Items)

Product: crafted or special products.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Sorter → Categories → Substance (Organic Resources)

Substance (Organic Resources)

Substance: resources and materials.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Sorter → Categories → Technology (Tech Upgrades)

Technology (Tech Upgrades)

Technology: technology-upgrade records.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Sorter → Categories → Consumable (Food and One Use Items)

Consumable (Food and One Use Items)

Consumable: food and other one-use items.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Sorter → Categories → Trade (Commodities)

Trade (Commodities)

Trade: trading commodity records.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Sorter → Categories → Special (Specialty Items)

Special (Specialty Items)

Special: unique, specialty or quest-related records.

↑ This page’s hierarchy
↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Sorter → Use All Unselected Storage Containers For Overflow

Use All Unselected Storage Containers For Overflow

Checked initially. The current implementation scans backward from Storage Container 10 and adds unchecked targets until it meets the first checked container, then stops. Do not assume the label guarantees that every unchecked container is used. Added overflow targets accept all six categories.

Before using Use All Unselected Storage Containers For Overflow, read the shared safety limitations for this page.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Sorter → Execute Sort

Execute Sort

Runs immediately against app-model data; there is no Review/Apply stage. Saves sorter choices and normally reports Inventory has been sorted! before closing. Source/target/category choices must be meaningful. The legacy caller can still show its completion notice after an internal validation warning, so inspect the actual result rather than relying only on that notice. File saving remains separate.

Before using Execute Sort, read the shared safety limitations for this page.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Sorter → Cancel

Cancel

Closes without executing the sort.

↑ This page’s hierarchy
↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Organizer

Inventory Organizer

Opens the separate review-then-apply organizer.

Open Inventory Organizer help →

Before using Inventory Organizer, read the shared safety limitations for this page.

Open Inventory Organizer help →

Inventory Processing → Node View → Inventory Organizer → Gather from these sources

Gather from these sources

Choose inventories whose whole saved slot/stack records may be gathered. Parts means records, not individual quantity units: the organizer does not split/merge stacks or change amounts. Available rows follow the loaded inventory roster: Exosuit, Container 1–10, Freighter, Fish Platform, Fish Bait Box, Cooking Ingredients, then starships. Names come from loaded data; missing names use No name provided. The organizer omits identifiable empty ship slots and invalid inventory entries.

Inventory Processing → Node View → Inventory Organizer → Gather from these sources → Select all

Select all

Checks every available source inventory.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Organizer → Gather from these sources → Mobile Storages

Mobile Storages

Replaces the source selection with Exosuit, Freighter, Fish Platform and available starships.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Organizer → Gather from these sources → Stationary Storages

Stationary Storages

Replaces the source selection with Containers, Fish Bait Box and Cooking Ingredients.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Organizer → Gather from these sources → Clear

Clear

Unchecks all source inventories.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Organizer → Gather from these sources → Inventory checkboxes

Inventory checkboxes

Check each inventory that can supply records. Initial defaults use mobile storages; saved preferences override defaults. A destination does not need to be checked as a source.

↑ This page’s hierarchy
↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Organizer → One destination per category

One destination per category

Choose one receiving inventory for each category; multiple categories may share a destination. Routes use the saved InventoryType. Defaults route the six categories to Containers 1–6 when available; preferences override them.

Inventory Processing → Node View → Inventory Organizer → One destination per category → Resources

Resources

Routes records whose InventoryType is Substance. Choose an available inventory or Leave where they are.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Organizer → One destination per category → Crafted products

Crafted products

Routes records whose InventoryType is Product. Choose an available inventory or Leave where they are.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Organizer → One destination per category → Technology

Technology

Routes records whose InventoryType is Technology. Choose an available inventory or Leave where they are.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Organizer → One destination per category → Consumables

Consumables

Routes records whose InventoryType is Consumable. Choose an available inventory or Leave where they are.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Organizer → One destination per category → Trade goods

Trade goods

Routes records whose InventoryType is Trade. Choose an available inventory or Leave where they are.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Organizer → One destination per category → Special items

Special items

Routes records whose InventoryType is Special. Choose an available inventory or Leave where they are.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Organizer → One destination per category → Leave where they are

Leave where they are

No routing for that category. Unknown categories also remain in place. A source-equals-destination route retains the record and does not overflow.

↑ This page’s hierarchy
↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Organizer → Optional

Optional

Two independent settings control overflow and destination expansion.

Inventory Processing → Node View → Inventory Organizer → Optional → Overflow: if destination is full, overflow to other 'Container' type storages.

Overflow: if destination is full, overflow to other 'Container' type storages.

Uses available containers unassigned to every category, working backward from Container 10 and excluding the record’s source. With no suitable space the record stays where it started. Checked by default unless saved preferences say otherwise.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Organizer → Optional → Expand all Destination storages to 120 cells.

Expand all Destination storages to 120 cells.

Expands every assigned destination, even if no record moves to it. With expansion enabled, an overflow container also expands when it receives records. With expansion off, existing unoccupied valid cells determine capacity and no destination is automatically expanded. Checked by default unless saved preferences say otherwise.

↑ This page’s hierarchy
↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Organizer → Review Summary

Review Summary

Read-only proposal display. Before review it shows current source/category routes without move counts. After review it summarizes the proposal; the current renderer may omit overflow-only or retained-only rows, so absence of a row is not a complete inventory audit.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Organizer → Review Moves

Review Moves

Creates a private proposal without publishing inventory changes. Disabled when no sources are selected and expansion is off. Requires synchronized Raw JSON in every tab and valid loaded context. Any source, route or option change invalidates this review.

Before using Review Moves, read the shared safety limitations for this page.

Inventory Processing → Node View → Inventory Organizer → Review Moves → Reviewing inventory moves, please wait…

Reviewing inventory moves, please wait…

The text-only notice reads exactly: Reviewing inventory moves, please wait…

Review Moves owns this non-cancellable modal while constructing the private proposal. It dismisses progress in cleanup after planning returns or fails, restores interaction, then renders the review or reports an error. No inventory change is published by Review.

There are no Cancel or Close buttons in this notice. Wait for the owning operation to finish; no separate user-dismissal or cancellation control is provided here.

↑ This page’s hierarchy
↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Organizer → Apply to app data

Apply to app data

Enabled only after review proposes a change. Applies the exact candidate, refreshes app views, marks modified data and closes. Rejects changed source identity or data since review. This is not File Save.

Before using Apply to app data, read the shared safety limitations for this page.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory Organizer → Close

Close

Closes without applying inventory changes; Escape/window-close have the same cancellation boundary. Preferences still persist, including choices changed without applying.

↑ This page’s hierarchy
↑ This page’s hierarchy

Inventory Processing → Node View → Inventory tree

Inventory tree

Expand an inventory to inspect its fields and stored slot records. Inventory drag/drop is not enabled by the initial tree configuration.

Inventory Processing → Node View → Inventory tree → Right-button drag selection → Delete N Nodes

Right-button drag selection → Delete N Nodes

The shared right-button range-selection handler can expose Delete N Nodes even on this tab, although its ordinary right-click menu has no Delete Node item. Confirmation removes the selected structure through the generic handler. This is structural deletion, not the category-based Organizer; do not use it casually on inventory fields.

Before using Right-button drag selection → Delete N Nodes, read the shared safety limitations for this page.

This generic tree-to-model path also reaches the defective inventory set_json branch; it is not a reliable supported inventory-edit workflow. Prefer the documented Organizer/replacement controls and inspect actual model data before saving.

Inventory Processing → Node View → Right-button drag selection → Delete N Nodes → Delete Nodes — confirmation

Delete Nodes — confirmation

Review Delete (N) nodes from the Tree? before acting. For a base or generic tree deletion the selected visible-node count can include expanded child fields. The starship-specific controller instead deduplicates complete occupied ship slots and validates the complete request.

Before using Delete Nodes — confirmation, read the shared safety limitations for this page.

↑ This page’s hierarchy

Inventory Processing → Node View → Right-button drag selection → Delete N Nodes → Delete Nodes — confirmation → OK

OK

Confirms this deletion request. Generic deletion removes the chosen tree nodes in app memory; starship deletion uses its guarded fixed-slot transaction instead. There is no automatic live save.

↑ This page’s hierarchy

Inventory Processing → Node View → Right-button drag selection → Delete N Nodes → Delete Nodes — confirmation → Cancel

Cancel

Rejects the confirmation without performing the requested deletion. Closing this dialog also rejects it.

↑ This page’s hierarchy
↑ This page’s hierarchy

Inventory Processing → Divider between Node View and Raw JSON

Node View / Raw JSON pane divider

Inventory Processing sets Node View/Raw JSON stretch weights to 5:7; it does not explicitly set equal initial sizes.

Drag the vertical handle of the horizontal QSplitter between the two pane containers to change their widths. This changes layout only: Raw JSON text, shared model values and disk save data remain unchanged. It is not record drag/drop, node movement, synchronization or Pretty Print.

↑ This page’s hierarchy
↑ This page’s hierarchy

Inventory Processing → Node View → Right-click menu

Right-click menu

Inventory-specific commands appear on eligible inventory records.

Inventory Processing → Node View → Right-click menu → Backup this Inventory

Backup this Inventory

Writes the selected inventory’s Node View JSON to a chosen *.nms_inventory.json file. Its Name supplies the proposed filename, or default if unnamed. This exports one inventory record, not the whole save.

Inventory Processing → Node View → Inventory tree → Right-click menu → Backup this Inventory → File selection — Save File

File selection — Save File

Choose the output folder and filename for the selected record, using .nms_inventory.json. The suggested name may be default for an unnamed record. Review an existing filename before replacing that separate backup file.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory tree → Right-click menu → Backup this Inventory → File selection — Save File → Save

Save

Writes a separate record-backup JSON file, not the loaded live NMS save. A file-save success message reports this export only.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory tree → Right-click menu → Backup this Inventory → File selection — Save File → Cancel

Cancel

Leaves this file-selection request without writing a backup or applying its selected input.

↑ This page’s hierarchy
↑ This page’s hierarchy

Inventory Processing → Node View → Right-click menu → Replace Items from Backup

Replace Items from Backup

Opens Replace Inventory Contents and reads a selected *.nms_inventory.json file. Replaces only the selected inventory’s Slots from the backup, not its whole record. If its ValidSlotIndices has fewer than 120 entries, the helper expands it to the 120-cell grid first. This edits app data and is not a full-save restore. Review the selected target and replacement contents before saving.

Before using Replace Items from Backup, read the shared safety limitations for this page.

Before using Replace Items from Backup, read the shared safety limitations for this page.

Existing occupied item slots are replaced, not merged; destination name and other metadata are not wholesale restored. Compare actual target Slots and ValidSlotIndices, including after a failed attempt, before any live save.

Inventory Processing → Node View → Inventory tree → Right-click menu → Replace Items from Backup → File selection — Replace Inventory Contents

File selection — Replace Inventory Contents

Select an appropriate .nms_inventory.json backup file. These filters help locate a record backup; choosing All Files does not make an arbitrary file compatible. Native file-dialog layout and labels are supplied by your operating system.

Before using File selection — Replace Inventory Contents, read the shared safety limitations for this page.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory tree → Right-click menu → Replace Items from Backup → File selection — Replace Inventory Contents → Open

Open

Reads the selected record-backup file and attempts the requested import into app memory. Review the resulting data before File → Save NMS Save File; this is not an automatic disk save or game-compatibility check.

Before using Open, read the shared safety limitations for this page.

Before using Open, read the shared safety limitations for this page.

↑ This page’s hierarchy

Inventory Processing → Node View → Inventory tree → Right-click menu → Replace Items from Backup → File selection — Replace Inventory Contents → Cancel

Cancel

Cancels this file-selection request before reading/applying its selected input. This does not undo an earlier failed replacement or its possible capacity change; inspect or deliberately reload if abandoning an earlier attempt.

↑ This page’s hierarchy
↑ This page’s hierarchy

Inventory Processing → Node View → Right-click menu → Toggle Expansion 2 Levels

Toggle Expansion 2 Levels

Collapses an expanded node or expands a collapsed node through the configured two-level helper. This changes only what is visible.

↑ This page’s hierarchy

Inventory Processing → Node View → Right-click menu → Highlight In Text Box

Highlight In Text Box

Selects the corresponding line in Raw JSON without changing data. It refuses if the captured node structure and current text cannot be matched reliably; it does not silently synchronize them.

↑ This page’s hierarchy

Inventory Processing → Node View → Right-click menu → Copy This Node's Text

Copy This Node's Text

Copies the selected node’s displayed label to the clipboard. It does not serialize that node’s full JSON or export the complete record.

This command copies the visible label of the clicked node, not the node’s complete JSON subtree. To copy JSON, select the desired text in Raw JSON and use Copy; use the whole-context clipboard export only when that larger scope is intended.

↑ This page’s hierarchy
↑ This page’s hierarchy
↑ This page’s hierarchy

Inventory Processing → Raw JSON

Raw JSON

Contains the inventory data exposed by this tab.

Inventory Processing → Raw JSON → Synched to Node View — status indicator

Synched to Node View — status indicator

Reports the app’s synchronization flag, not independent JSON validity. Red means the app has marked this editor unsynchronized. Green can also follow a failed parse with invalid text beside an old tree, or ignored [] input; it does not prove the intended edit reached the model, that another editor’s pending work survived, or that a live save was written.

A parse error is not a safe synchronization: the current handler ignores the failure return, can rebuild the previous model’s tree and turn the synchronization light green while invalid text remains. An empty array ([]) is silently ignored by this path; it is not a reliable way to delete all records. After any error or ignored input, do not trust a green light or proceed to Save: preserve the text, compare both panes and the intended field values, correct and retry, or deliberately reload a known saved baseline.

For Synched to Node View — status indicator: do not synchronize or Pretty Print Inventory Raw JSON as an editing workflow. Use supported structured tools from a trustworthy baseline; see the inventory limitation above.

↑ This page’s hierarchy

Inventory Processing → Raw JSON → Sync to Node View

Sync to Node View

For Sync to Node View: do not synchronize or Pretty Print Inventory Raw JSON as an editing workflow. Use supported structured tools from a trustworthy baseline; see the inventory limitation above.

Attempts to parse this tab’s Raw JSON into the shared in-memory model and rebuild Node View; no live-save write is performed.

Before using Sync to Node View, read the shared safety limitations for this page.

A parse error is not a safe synchronization: the current handler ignores the failure return, can rebuild the previous model’s tree and turn the synchronization light green while invalid text remains. An empty array ([]) is silently ignored by this path; it is not a reliable way to delete all records. After any error or ignored input, do not trust a green light or proceed to Save: preserve the text, compare both panes and the intended field values, For understood non-inventory text only, correct and retry; for Inventory text, do not retry synchronization—preserve it externally and deliberately reload a trustworthy saved baseline when abandoning the attempt.

A Processing notice can remain visible after the Node View appears to update. Wait for owner-controlled dismissal; it reports synchronization work, not successful validation or a live save.

Inventory Processing → Raw JSON → Sync to Node View → Processing — Node View synch

Processing — Node View synch

The text-only notice reads: Processing the Node View synch. This can take a few seconds after the Node View appears to update...

This window-modal notice has no Close or Cancel button; Escape does not cancel the operation. The app dismisses it when the enclosing synchronization completes or raises an error. It may also cover the work that follows a confirmed generic node deletion.

↑ This page’s hierarchy
↑ This page’s hierarchy

Inventory Processing → Raw JSON → Pretty Print

Pretty Print

For Pretty Print: do not synchronize or Pretty Print Inventory Raw JSON as an editing workflow. Use supported structured tools from a trustworthy baseline; see the inventory limitation above.

Pretty Print is not display-only: it attempts a model update from the editor, reloads indented text from the model and rebuilds Node View.

Before using Pretty Print, read the shared safety limitations for this page.

The current formatting handler reloads the previous model text even after a parse failure or ignored empty array. This can discard pending invalid text; copy it out before formatting. Formatting or a refreshed tree does not prove the intended edit was applied. Compare actual values before saving.

↑ This page’s hierarchy

Inventory Processing → Raw JSON → JSON text editor

JSON text editor

Displays this tab’s inventory-view data. You can edit the JSON directly. Line numbers identify text lines; the current line is highlighted. Text is not line-wrapped, so long lines scroll horizontally.

Keep a separate copy of pending text before Sync, Pretty Print or structured changes: a model refresh can replace editor contents in other tabs. Work and verify one tab at a time. Text editing is not an automatic model update or disk write.

For JSON text editor: do not synchronize or Pretty Print Inventory Raw JSON as an editing workflow. Use supported structured tools from a trustworthy baseline; see the inventory limitation above.

The editor displays line numbers and does not wrap long JSON lines. Use the editor’s own horizontal scrollbar to inspect a long value. Selecting or copying text does not edit the save; typing, cutting, deleting or pasting does. A text edit is not automatically a successful synchronization or a disk save.

↑ This page’s hierarchy

Inventory Processing → Raw JSON → Right-click menu

Right-click menu

The editor supplies its standard editing commands plus Search Text.

Inventory Processing → Raw JSON → Right-click menu → Standard editing commands

Standard editing commands

Undo, Redo, Cut, Copy, Paste, Delete and Select All operate on the text editor, subject to its current selection and available edit history. These are text operations, not a general undo facility for tree operations.

Inventory Processing → Raw JSON → Right-click menu → Standard editing commands → Undo

Undo

Reverses the most recent text-editor edit when an undo step is available. It is not an application-wide undo for sorting, upgrades, node deletion or inventory organization.

↑ This page’s hierarchy

Inventory Processing → Raw JSON → Right-click menu → Standard editing commands → Redo

Redo

Reapplies a text-editor change that was undone, when redo history is available.

↑ This page’s hierarchy

Inventory Processing → Raw JSON → Right-click menu → Standard editing commands → Cut

Cut

Removes selected text and places it on the clipboard. This marks the Raw JSON changed.

↑ This page’s hierarchy

Inventory Processing → Raw JSON → Right-click menu → Standard editing commands → Copy

Copy

Copies selected text to the clipboard without changing JSON.

↑ This page’s hierarchy

Inventory Processing → Raw JSON → Right-click menu → Standard editing commands → Paste

Paste

Inserts clipboard text at the cursor, replacing any selected text. It does not automatically synchronize the Node View.

↑ This page’s hierarchy

Inventory Processing → Raw JSON → Right-click menu → Standard editing commands → Delete

Delete

Removes selected text. This is different from Node View → Delete Node.

↑ This page’s hierarchy

Inventory Processing → Raw JSON → Right-click menu → Standard editing commands → Select All

Select All

Selects the complete text of this tab’s Raw JSON editor.

↑ This page’s hierarchy
↑ This page’s hierarchy

Inventory Processing → Raw JSON → Right-click menu → Search Text

Search Text

Opens Search Dialog for this tab’s Raw JSON.

Inventory Processing → Raw JSON → Right-click menu → Search Text → Enter search term

Enter search term

Text to locate in the current Raw JSON document.

↑ This page’s hierarchy

Inventory Processing → Raw JSON → Right-click menu → Search Text → Search Backward

Search Backward

Finds the preceding occurrence from the current cursor. No more occurrences produces End of Search; the implementation does not wrap to the opposite end.

↑ This page’s hierarchy

Inventory Processing → Raw JSON → Right-click menu → Search Text → Search Forward

Search Forward

Finds the next occurrence from the current cursor. The match is selected and brought into view.

↑ This page’s hierarchy

Inventory Processing → Raw JSON → Right-click menu → Search Text → Close

Close

Closes the Search Dialog without changing JSON.

↑ This page’s hierarchy

Searching follows the current text cursor in the chosen direction. No more occurrences found. means the search reached its end; it does not automatically wrap to the other end. To search again from the beginning or end, close the dialog, reposition the Raw JSON cursor and reopen Search Text.

↑ This page’s hierarchy
↑ This page’s hierarchy
↑ This page’s hierarchy