[Unity] Game Creator 2 Visual Scripting — Triggers, Actions, Conditions & Events

Thank you for visiting this site.

In this article, we will provide a detailed explanation of “Visual Scripting”, the core system of Game Creator 2.

Unlike node graph systems like Playmaker or Unity’s built-in Visual Scripting, it adopts a task list approach (a list that executes instructions from top to bottom) — this is its defining feature.

Official documentation: Game Creator 2 Documentation

You can find a list of all articles in this series below.

Complete Article List — Game Creator 2 Complete Guide Series Indexen.senkohome.com/gamecreator2-series-index/

---

What Is Visual Scripting?

Game Creator’s Visual Scripting consists of 3 components + 1 (Hotspot):

Naming Conventions

• Actions contain multiple Instructions
• Conditions contain multiple Branches, each Branch holding Conditions and Instructions
• Trigger listens for a single Event

High-Level Scripting Philosophy

Designed so you can write using vocabulary closer to human intuition than programming languages. Operations like “make this character follow that object” can be written as a single instruction without breaking them down into low-level vector calculations.

Coexists with Graph-Based Systems

You can combine it with Playmaker or Unity Visual Scripting without issues. GC2 excels at “quickly assembling common patterns”, while graph-based systems excel at “writing detailed control logic” — they complement each other.

Game Creator Hub

A community hub site (officially recommended) where Instructions / Conditions / Events are distributed for free. You can expand your vocabulary without any programming.

---

Actions (Instruction Lists)

Creation

• Right-click in Hierarchy → Game Creator > Visual Scripting > Actions
• Or add via Inspector → Add Component > Actions on an existing object
• Delete via the gear icon → Remove Component

Adding Instructions

• Click Add Instruction for a dropdown → select from categories or use the search bar to filter directly
• Right-click an existing instruction → Insert Above / Insert Below to insert at any position

Fuzzy Search

GC2 has its own index search that matches semantically similar results even with typos. For example, searching move will find not only Move Character but also Change Position.

Built-in Help

Right-click an instruction → Help to open a floating window with descriptions and parameter lists.

Execution Order

Instructions are executed sequentially from top to bottom. The next instruction does not run until the current one completes (instructions like Wait to Complete inherently wait). When the end of the list is reached, the Actions component finishes.

Debug Features

Right-clicking an instruction reveals the following toggles:

• Disable Instruction: Disables the instruction (shown grayed out). Click again to re-enable
• Breakpoint: Pauses the editor just before that instruction (editor only, does not affect builds)

---

Triggers (Event Listeners)

Creation

• Right-click in Hierarchy → Game Creator > Visual Scripting > Trigger
• Or Add Component > Trigger on an existing object

Basic Structure

A Trigger monitors a single Event and executes its internal Instructions list the moment it fires. The Instructions portion operates the same as Actions.

Changing the Event

Click the current Event name → select a different Event from the dropdown (Fuzzy Search enabled).

Representative Event Categories

• Audio: Monitor volume changes
• Cameras: Shot transitions
• Characters: Input / combat / death / ragdoll, etc.
• Input: Buttons, cursor, flick, touch
• Interactive: On Interact / On Focus / On Blur
• Lifecycle: On Start / On Update / On Interval, etc.
• Logic: Hotspot activation, On Receive Signal
• Physics: Collider Enter/Exit, collisions
• Storage: Save, load, delete
• UI: Selection, hover
• Variables: Variable change monitoring

---

Conditions (Conditional Branching)

Conditions Component Structure

• Evaluates Branches from top to bottom
• Each Branch holds a “Conditions (condition list)” and an “Instructions (instruction list)”
• If all conditions in the list are true, that Branch’s instructions execute and processing ends
• If any condition returns false, it moves to the next Branch
• An empty condition list always succeeds (can be used as a default branch)

Adding and Reordering Branches

• Add Branch adds to the end
• Drag the = on the right to reorder
• Use the Description field for memo-style labels (does not affect logic)

Condition Negation

The green toggle on the left of each Condition applies NOT. For example: NOT on Is Player Moving returns true when the player is stationary.

Creation

• Right-click in Hierarchy → Game Creator > Visual Scripting > Conditions
• Or Add Component > Conditions

---

Hotspots (Interaction Visualization)

Overview

Hotspots are presentation components that do not directly affect gameplay. They provide mechanisms to indicate interactable objects to the player through visuals, sound, and character attention.

For example, you can highlight an object when the player approaches, or make a character’s head turn toward an important object.

Generally, Triggers and Hotspots are placed together. The Trigger handles the actual interaction logic, while the Hotspot signals to the player that the object is interactable.

Components

The Hotspot component consists of a Target field and a Mode. Target is the object to track, and Mode determines when the Hotspot responds.

Mode (4 Types)

On Interaction Focus and On Interaction Reach require the Target to have a Character component.

Gizmos and Debug

• Editor: Selecting a Radius mode Hotspot displays a red gizmo in the scene showing the response distance
• Runtime: The gizmo is displayed in a lighter color, turning green when the Target activates the Hotspot

Distance Check Mechanism

Hotspot distance checks do not use Unity’s physics engine. It uses a simple distance calculation between the Hotspot’s center and the Target’s position, so a Collider component is not required.

How to Create

• Right-click in Hierarchy → Game Creator > Visual Scripting > Hotspot to create as a scene object
• Or add Add Component > Hotspot to an existing GameObject

Spots (Presentation Elements)

Spots are individual presentation units that define what happens when a Hotspot is activated/deactivated. Add them via the Add Spot button dropdown.

• Evaluated from top to bottom
• Multiple Spots of the same type can be placed, but when effects overlap, the later one overrides

Audio > Play Sound

Plays a UI sound effect when the Hotspot is activated/deactivated.

Characters > Look At

When the Hotspot is activated, the Character looks at the Hotspot’s center, and smoothly looks away when deactivated. Works with the Character’s IK (Look at Target rig) to rotate head, neck, chest, and spine.

Game Objects > Activate Object

When the Hotspot is activated, it enables an existing GameObject instance in the scene, and hides it when deactivated.

Game Objects > Instantiate Prefab

When the Hotspot is activated, it instantiates (or enables) a Prefab GameObject, and hides it when deactivated.

Materials > Change Material

Switches materials based on whether the Hotspot is active or inactive. Useful for object highlighting effects.

UI > Change Text

Overwrites the value of a specified Text component.

UI > Cursor

Changes the cursor image when hovering over the Hotspot.

UI > Show Floating Text

When the Hotspot is activated, displays text on a world-space canvas, and hides it when deactivated. Uses a default UI if no Prefab is specified.

Related Visual Scripting Nodes

Instruction:

• Activate Hotspots (Visual Scripting category): Toggles Hotspot activation/deactivation by type

Event:

• On Hotspot Activate (Logic category): Fires when the associated Hotspot is activated
• On Hotspot Deactivate (Logic category): Fires when the associated Hotspot is deactivated

---

Properties (Common Dynamic Value System)

Many instructions, conditions, and events support dynamic selection of field values via dropdowns. This is the Property feature.

• Example: PropertyGetPosition can dynamically select from “constant Vector3”, “Player position”, “Main Camera position”, “Local Variable”, “Nested Access”, etc.
• Provided as PropertyGetXXX classes from scripts
• This allows switching between “hardcoded coordinates” and “runtime-determined coordinates” in the UI

---

Debug Support Summary

---

Creating Custom Instructions / Conditions / Events with Scripts

Programmers can write custom nodes in C#. Generate templates via Project right-click → Create > Game Creator > Developer > C# Event (or Instruction / Condition).

Event Example (Custom Event)

using System;
using GameCreator.Runtime.VisualScripting;

[Serializable]
public class MyEvent : Event
{
    protected override void OnStart(Trigger trigger)
    {
        base.OnStart(trigger);
        _ = trigger.Execute(this.Self);
    }
}

• The parent class Event has many virtual methods similar to MonoBehaviour (OnAwake / OnStart / OnEnable, etc.). See Event.cs for details
• Triggers fire via trigger.Execute(target). The return value is an async Task
  • Fire-and-forget: _ = trigger.Execute(this.Self);
  • Await completion: await trigger.Execute(this.Self);
• target is the GameObject treated as the “Target” for the executed Instructions

Decoration Attributes

C# attributes to make nodes easier to work with in Visual Scripting.

Prerequisites for Sharing Custom Events on the Hub

When publishing to the Hub, properly setting Title / Version / Description / Keywords / Dependency is essential to avoid searchability and compatibility issues for users.

---

Instructions — Full List: 312 Core Types

Categories match the Visual Scripting dropdown hierarchy as-is. Module-specific instructions (Inventory, Dialogue, Stats, Quests, Behavior, Perception, Shooter, Melee) are covered in their respective asset articles — only core instructions are listed here.

Animations (8)

Application (2 + Cursor 3)

Audio (21)

Cameras (3 + Sub 35)

Root: Change To Shot / Revert To Previous Shot / Set Main Shot. See the Camera System article for details.

Characters (Core 67)

See the Character System article for details.

Debug (8 + Console 5 + Gizmos 1)

Game Objects (8 + Components 8 + Pooling 2)

Input (6)

Lights (2)

Math > Arithmetic (13)

Math > Boolean (6)

Math > Geometry (23)

Math > Shading (4)

Math > Text (4)

Physics 2D (6)

Physics 3D (11)

Renderer (5)

Scenes (2)

Storage (5)

Time (3)

Transforms (6)

UI (16)

Variables (16)

See the Variables article for details.

Visual Scripting (12)

Module-specific additional instructions (reference): Inventory (36) / Dialogue (4) / Stats (12) / Quests (9) / Behavior (3) / Perception (13) / Shooter (17) / Melee (19). See each asset’s article for details.

---

Conditions — Full List: 80 Core Types

Audio (6)

Cameras (1)

Characters (29)

See the Character System article for details.

Game Objects (7)

Input (9)

Math > Arithmetic (2)

Math > Boolean (3)

Math > Geometry (5)

Physics (9)

Platforms (5)

Scenes (1)

Storage (2)

Text (2)

Transforms (3)

Variables (1)

Visual Scripting (2)

---

Events — Full List: 50 Core Types

Audio (6)

Cameras (3)

Characters (17)

See the Character System article for details.

Input (4)

Interactive (3)

Lifecycle (13)

Logic (3)

Physics (7)

Storage (3)

UI (4)

Variables (4)

---

Hotspot Spots — Full List

Presentation units that activate when a Hotspot is enabled/disabled. Add via the Add Spot button. Evaluated from top to bottom — when the same type of Spot overlaps, the later one overrides.

---

Practical Usage — Configuration Guide by Use Case

Key Press → Display Message

1. Create a Trigger → set Event to On Input Button
2. Set the Button to an InputAction equivalent to “Space”
3. Add Log Text or Play UI Sound to Instructions

Player Approaches → NPC Turns to Face

1. Add a Hotspot (Mode=Radius) to the NPC, Target=Player
2. Add Characters > Look At as a Spot on the Hotspot
3. When within radius, the character’s head turns toward the NPC

Branch by Gold (Classic RPG)

1. Place a Conditions component
2. Branch 1: Compare Wealth >= 500 → Instruction: Purchase processing
3. Branch 2: Empty condition → Instruction: "You can't afford this" message

Periodic Event to Reduce Enemy HP

1. Create a Trigger → Event=On Interval, Interval=1
2. Add a Stats module instruction to Change Stat HP by -1

Loose Coupling with Signals

• Sender: Use the Emit Signal instruction to broadcast "boss-defeated"
• Receiver: A separate Trigger with Event=On Receive Signal, ID="boss-defeated"
• Since neither side holds a reference to the other, this design is easy to prefab and reuse

---

Tips and Notes

• Make use of Properties: Instead of fixed values, selecting “Player position”, “Local Variable”, etc. makes prefabbing and reuse dramatically easier
• Empty Conditions always return true: When you want a “default branch” in a Conditions component, leave the last Branch’s conditions empty
• Disable and Breakpoint are editor-only: Breakpoints are ignored in builds. Use Log Text / Log Number for logs
• Signal vs. direct reference: Use Signals for loose coupling. Use direct references when two objects are reliably linked during their lifetime
• Run Actions / Run Conditions / Run Trigger: Since these can call other components, you can prefab common logic and call it from anywhere

---

Official Links

• Game Creator 2 Official Documentation
• Game Creator 2 — Unity Asset Store

---

Summary

In this article, we covered Visual Scripting in Game Creator 2.

Visual Scripting is a system that lets you build game logic with 4 components — Actions, Triggers, Conditions, and Hotspots — using a task list approach different from node graph systems.

The core alone provides 312 Instructions, 80 Conditions, and 50 Events, and adding modules further expands your vocabulary. With debug support features like Fuzzy Search, built-in help, and breakpoints, efficient development is possible.

Complete Article List — Game Creator 2 Complete Guide Series Indexen.senkohome.com/gamecreator2-series-index/

We hope you’ll check out our other articles as well.