Ver 5.3

Summary

Flow Core 5.3 updates Graph and Inspector authoring, adds focused entry editing and consistent access to commands and reference information, and separates personal editor preferences from team configuration. Review the settings scope before changing shared behavior, then choose the editing surface and expansion mode that suit the current task.

Graph and Inspector authoring

• The main Graph, built-in Flow Inspector, and dedicated Node Editor share a clearer hierarchy for node identity, functional sections, Instruction and Condition entries, and fields.
• Node titles use an explicit Rename command. The title toolbar keeps node commands separate from authored content.
• The Flow Inspector can follow selection or remain pinned to a node. Switching its side moves the existing pane while preserving its target, pinned state, active controls, width, zoom, and scroll position.
• Main-graph Control Inputs are grouped under their disclosure header. Compatible connection drags can reveal applicable hidden ports without changing the authored connection rules.
• Long Instruction and Condition captions stay on one line, while their complete text remains available in the tooltip and Rename field.

See Graph Editor and Node Inspector & Entry Editing.

Focused entry editing and commands

• Single Focus is the default entry expansion mode. Each node in each editing surface keeps one active leaf path and the ancestors required to edit it.
• Continuous permits multiple open entries and keeps its own remembered expansion set. Expand All Items is temporary; Return to Entry Expansion Mode resumes the selected default.
• New or duplicated entries receive focus. Reordering follows the entry, deletion clears its state, and unconfirmed identities after Undo or reload do not reopen stale details.
• Entry command groups expose Rename, Open Editor, Information, and More. More retains applicable insertion, movement, clipboard, removal, and Flow Knowledge actions when inline shortcuts are hidden or space is narrow.
• Rename commits on Enter or normal focus loss; Escape cancels an uncommitted draft. Dedicated Instruction and Condition editors use the same caption and field presentation while keeping their own expansion behavior.

Field Information and Flow Knowledge

Field Information and Flow Knowledge share Main, Fields, and Technical reference views where applicable. Field groups, nested field descriptions, local field search, and member paths help explain configuration without editing a graph. Flow Knowledge adds capability search and type filtering, while the Flow Knowledge command connects a selected node or entry to its reference.

These windows describe types and supported configuration; runtime values still need the intended process and Debug Context. Follow Field Information & Flow Knowledge.

Personal preferences and shared settings

• Personal stores editor appearance, interaction, search, name suggestions, and editor diagnostics in project-scoped EditorPrefs.
• Project Shared keeps build and runtime settings in the existing FlowCoreSettings asset, including save/load rules, runtime scanning, Context Shortcuts, character defaults, and runtime diagnostics.
• Tools keeps generator and maintenance launchers separate from both configuration groups.
• Missing personal fields initialize once from the legacy asset, or built-in defaults when no asset exists. Existing stored values and intentionally empty suggestion lists are preserved.
• Personal changes, including name-management and add-to-whitelist actions, no longer modify the shared settings asset. Undo/Redo and open editor views follow those personal changes.
• Log Persistent GUID Collisions is off by default in Personal > Diagnostics > Editor Registry Logging. It is stored in personal, project-scoped EditorPrefs and controls only the persistent GUID collision warning in Editor Play Mode. Duplicate cleanup, GUID identity, and built-player logging keep their existing behavior.

See Personal & Project Settings for migration, reset, and reimport steps.

Reflection editing and conditional fields

• Ordinary reflected field edits update dependent visibility and summaries while retaining the editing controls, focus, foldout state, and scroll position.
• Source, Target, and list-related fields follow the selected value route. Hiding a field with a Show rule does not itself clear its stored value.
• Reflection Show expressions support boolean and enum comparisons, nested member paths, negation, conjunction, disjunction, and parentheses. Invalid conditions leave the affected field visible and report a bounded Console warning.
• Routine reflection fallback messages and lightning suffixes are removed. Missing data and other actionable drawing errors remain visible.
• Other open views refresh to show the edited data. List structure changes, Undo/Redo, and an explicit custom-drawer rebuild can still rebuild controls.

See Graph Editor for the editing workflow, and Authoring Custom Instructions for the Show and Generator boundaries.

Details built when expanded

Instruction and Condition rows, FSM sections and transitions, Guard and Wait conditions, Stack instruction sections, and supported branch rows now build their detailed controls when expanded. This also covers If/Else condition groups, Enum outputs, Gather branches, weighted Combiner branches, and BT child rows.

Collapsing a supported row releases its detail controls while preserving authored data and the row’s available header and ports. Expanding it again draws the current data. This is an editor behavior change: collapse does not disable a row, remove a branch, or change runtime execution order. Reordering and removal continue to keep the associated data and ports aligned.

Upgrade notes

1. Open Edit > Project Settings > Flow Core and review Personal and Project Shared.
2. Confirm personal suggestions and display choices after the initial migration. Use Restore Built-in Defaults or Reimport from Existing Asset only when you intend to replace those choices.
3. Keep the existing settings asset in version control for shared configuration. Its identity and legacy serialized personal fields remain compatible; existing public asset properties still expose asset values.
4. Expect a fresh personal preference scope after moving the project or opening another checkout.
5. The package includes updated generated Drawers for its built-in types. If your project maintains separately generated editor Drawers, regenerate the affected outputs and their editor registration files with the current Generator to adopt the updated field layout. Keep their existing output roots and review the generated changes; do not hand-edit generated files. A handwritten custom Drawer keeps control of its own UI.
6. New or changed extension types still follow their normal generation and registration workflow. Changing a presentation preference, opening an editor, or expanding an entry does not require running Generator.

No graph-data migration is required for these editor presentation changes. Verify gameplay through the same runtime checks used before the update.

Related

• Personal & Project Settings
• Graph Editor
• Node Inspector & Entry Editing
• Field Information & Flow Knowledge
• Authoring Custom Conditions
• Ver 5.2