Skip to content

Unity and Game Creator compatibility

Use official Game Creator Core and module releases that support your chosen Unity version and each other. Install and compile those packages before importing ActionFlow 2. Check the Game Creator release notes and each installed module's release notes when upgrading.

ActionFlow 2 is currently tested on Unity 6000.3.22f1 and 6000.6.0f1 with the corresponding compatible Game Creator Core 2.19.61 uploads. These are specific tested combinations, not a guarantee for every later vendor update.

Install or upgrade

  1. Back up or commit the project before changing Unity or Game Creator versions.
  2. Select official Core and module releases compatible with the target Unity version. Follow the vendor's installation and upgrade instructions.
  3. Let Game Creator finish importing and compiling, then import ActionFlow 2.
  4. Check that the Console contains no compilation errors before editing graphs.

Core 2.19.61 has existed in different Asset Store uploads with the same visible version number. If an old cached download fails to compile, download and import the appropriate official package again. If compilation still fails, retain the first error and contact the affected package's developer.

ActionFlow 2 no longer includes the older GC2 Unity API migration patch or its external preflight scripts. GC2 compatibility with Unity comes from the official vendor packages. Existing vendor files are not reverted when updating ActionFlow.

Updating from an earlier ActionFlow beta

Unity package imports can leave files from an earlier release in the project. If these retired files remain under Assets/Plugins/bionic/ActionFlow2, remove those exact assets through Unity's Project window after importing the update:

  • Editor/GC2GameCreatorPatchManifest.cs
  • Editor/GC2GameCreatorUnity65PatchManifest.json
  • Tools/Apply-GC2Unity65Patch.ps1
  • Tools/ApplyGC2Unity65Patch.py
  • Tools/apply-gc2-unity65-patch.sh
  • Documentation/Unity65GC2Preflight.md

Keep Editor/GC2GameCreatorPatch.cs; it contains the retained scene-dirtying fix. This cleanup removes ActionFlow's retired tools, without reverting Game Creator source changes already present in the project.

Keep Unity 6.3 and 6.6 projects separate

Maintain separate project copies with Game Creator packages appropriate to each Unity version. Do not copy vendor source files from the Unity 6.6 project into Unity 6.3 merely because their visible GC2 version numbers match.

ActionFlow's own version-specific Unity API handling remains active, including Unity 6.6 field support. Removing the vendor migration tools does not change graph serialization, Undo/Redo, or prefab handling.

Scene-dirtying fix

ActionFlow 2 retains one separate, narrowly scoped Game Creator source fix: SerializationUtils.ApplyUnregisteredSerialization should mark a scene dirty only when serialized values actually changed. This prevents unchanged Inspector refreshes from producing unnecessary save prompts.

The fix checks at editor startup and when that exact source asset is imported. It leaves an already-patched method untouched and refuses unfamiliar method contents with a diagnostic warning. It is independent of the Unity API migration and does not create Undo records or change prefab override handling.