Skip to content

Install ActionFlow 2 | Game Creator 2

Requirements

Before installing ActionFlow 2:

  • install and activate Game Creator 2;
  • make a version-control checkpoint or project backup.

ActionFlow 2 extends Game Creator 2 and is not useful without it.

ActionFlow 2 is currently tested on Unity 6000.3.22f1 and 6000.6.0f1 with their compatible Game Creator Core 2.19.61 uploads. Earlier validation covered Unity 6000.4.12f1/Core 2.18.60 and 6000.5.8f1/the revised official Core 2.19.61 upload.

Install official Game Creator Core and module releases compatible with your chosen Unity version and each other. Let them compile before importing ActionFlow 2. See Unity and Game Creator compatibility for upgrade guidance and the retained scene-dirtying fix. Keep Unity 6.3 and 6.6 projects and their vendor packages separate.

LogicBlock is optional. NodeFlow is not required by ActionFlow 2.

Import the package

  1. Open the Unity project in the Unity Editor.
  2. Import the distributed ActionFlow 2 package using the installation method supplied with your purchase.
  3. Wait for Unity to finish importing and compiling.
  4. Confirm that the Console contains no compilation errors.
  5. Select a GameObject with a Game Creator component and verify that Open Graph is available.

During compilation, ActionFlow 2 discovers compatible Events, Instructions, and property providers supplied by installed modules in a supported Game Creator Core source lane. No separate ActionFlow integration package is needed for each module.

The node picker listing instructions discovered from the installed Game Creator Inventory module
A quick module check: search for one installed module after compilation and confirm that its instructions appear.

Optional LogicBlock integration

Install LogicBlock before or after ActionFlow 2. When Unity finishes compiling, select a compatible LogicBlock Block asset and choose Assets › Open in ActionFlow 2.

The integration is detected at runtime. If the installed LogicBlock version has an unsupported serialized schema, ActionFlow 2 reports the incompatibility and leaves the asset unchanged.

Do not edit the installed package while Unity is importing

Let compilation and any package-update work finish before opening a graph. Interrupting an import can leave Unity with stale editor assemblies.

Verify the installation

Select a GameObject with a Game Creator Trigger, Actions, or Conditions component and choose Open Graph in the Inspector.

If the graph opens and shows the component's contents, the editor integration is ready.

A successfully opened ActionFlow 2 component graph showing a quest encounter flow
A successful component check shows the same Trigger, Actions, and Conditions data as connected nodes.

You can also verify the asset workflow:

  1. Create Game Creator › ActionFlow 2 › Instruction Asset from the Project window Create menu.
  2. Double-click the new asset.
  3. Confirm that its rooted graph opens and its parameter signature is visible.
A successfully opened Instruction Asset with a visible typed parameter signature
The reusable-asset check is complete when the permanent root and typed parameter signature are visible.

Update ActionFlow 2

  1. Close open ActionFlow 2 windows.
  2. Save the project and create a version-control checkpoint.
  3. Install the update using the same distribution channel as the original package.
  4. Let Unity recompile.
  5. Open a representative scene and prefab graph.
  6. Check the Console before continuing production work.

See Troubleshooting if the graph does not open or a component cannot be displayed.