Skip to content

LogicBlock integration

When a compatible LogicBlock version is installed, ActionFlow 2 can open a LogicBlock Block asset as one graph document. LogicBlock remains the owner of the asset; ActionFlow 2 provides the visual editing, navigation, search, Undo, and runtime-debugging surface.

LogicBlock is optional. ActionFlow 2 does not require NodeFlow and has no compile-time dependency on LogicBlock.

The Enemy Encounter Block opened as a LogicBlock overview with Start Encounter, Resolve Encounter, and Can Engage Player list roots
The overview places every supported list in one document. Named references remain visible at the roots while connections reveal the contained flow.

Open a Block asset

Use either workflow:

  1. double-click a compatible LogicBlock Block asset; or
  2. select it and choose Assets › Open in ActionFlow 2.

The ScriptableObject context menu also offers Open in ActionFlow 2 for a compatible selected asset.

The Block opens as a unified document with two levels:

  • Overview shows the Block and its instruction and condition lists;
  • a focused list view opens one instruction or condition list for editing.

List roots display their signature and reference information. You can create and navigate lists without losing the context of the parent Block. Use the Overview as a visual map instead of relying on memory to relate isolated, nested Inspector lists.

Edit LogicBlock flow

Compatible lists use the same ActionFlow tools as native graphs:

  • node search and creation;
  • serialized value editing inside nodes;
  • structural connection editing;
  • copy, paste, delete, layout, and view state;
  • Unity Undo and Redo;
  • refresh when the asset changes outside the graph.

Use Edit Mode for structural changes. ActionFlow 2 treats the LogicBlock asset as authoritative and writes back to its supported serialized schema.

Find usages

Open the document menu and choose Find Usages to search for references to the current LogicBlock content. The search covers usages in open scenes and in serialized project assets.

This is especially useful before changing a list signature or removing a list from a shared Block.

Debug in Play Mode

Keep the Block document open while entering Play Mode. ActionFlow 2 can highlight execution through direct LogicBlock calls and compatible LogicBlock instance-list calls, including continuations after asynchronous instructions.

As with other graph surfaces, Play Mode is for observation and value testing; structural editing remains locked.

Compatibility safeguards

LogicBlock integration uses a compatibility bridge so ActionFlow 2 can remain independent of a specific LogicBlock assembly at compile time. Before exposing editing, it validates that the installed asset schema is understood.

If validation fails, ActionFlow 2 fails closed: it reports the incompatibility and does not modify the asset. See Troubleshooting if a Block asset will not open.

Keep a checkpoint before package updates

After updating LogicBlock, let Unity finish compiling and open a copy or a representative Block first. Confirm that its lists and values appear as expected before editing production assets.