Integrates Pixel Crushers Dialogue System with Game Creator 2, enabling GC2 Conditions and Instructions directly in dialogue entries for faster, visual storytelling.
For more details about this asset: Click Here
This package is provided solely for evaluation, learning, or testing purposes before purchase and is not permitted for commercial use.
Integration of Pixel Crushers Dialogue System into Game Creator 2 v1.0.3 (Latest version)
Integration of Pixel Crushers Dialogue System into Game Creator 2 v1.0.2
“If possible, please buy the package to support the developer”
Description
Bring Pixel Crushers Dialogue System and Game Creator 2 together with a seamless editor‑level bridge. Dialogue System For Game Creator 2 adds native support for GC2 Conditions, Instructions, and Sequences directly inside Dialogue System entries, so you can author gameplay logic visually while keeping your narrative workflow intact. No more bouncing between inspectors or maintaining parallel logic, everything lives where your dialogue is built.
This integration optionally patches and extends the Dialogue Editor with inline GC2 lists for each entry. You can use GC2 logic alongside (or instead of) Lua, preserve existing Dialogue System pipelines, and keep your narrative data structured while still leveraging Game Creator 2’s powerful visual scripting ecosystem.
Key highlights:
Inline GC2 Conditions and Instructions per dialogue entry
Visual authoring directly in the Dialogue Editor
Works with existing Dialogue System databases and workflows
Designed to feel native to both Pixel Crushers and GC2
Faster iteration with fewer context switches
Ideal for story‑driven games, quests, and branching conversations where you want the robustness of Dialogue System combined with the speed and clarity of Game Creator 2’s visual tools.
Technical details
Dependencies: Pixel Crushers Dialogue System, Game Creator 2
Installation: Import this package after DS and GC2; run the patcher once
Editor integration: extends Dialogue Editor with inline GC2 Condition/Instruction/Sequence lists
Runtime impact: editor‑only patching; no additional runtime components required
Compatibility: works with existing Dialogue System databases and entries
Platforms: all Unity‑supported platforms (editor tooling only)
Render pipelines: Built‑in/URP/HDRP (editor‑only)
