Quick Start

🚀

GES · Examples

Run the one-time setup that activates the Game Event System in your project, then confirm the manager, database, and generated code are in place.

For anyone opening the Game Event System for the first time, before running any other example scene.

Overview

Open the Quick Start scene to initialize GES from Game Event System and check the manager and default assets before you open another demo.

🔈 Hover for sound

---

Demo Scene

Assets/TinyGiants/GameEventSystem/Demo/00_QuickStart/00_QuickStart.unity

Open this scene to begin the initialization process.

---

Why Initialize?

The Game Event System relies on a persistent manager (GameEventManager) to coordinate all event operations. The manager supplies the database and Inspector bindings used by this demo.

The initialization process automatically sets up:

Component	Description
🎮 GameEventManager	Singleton manager (marked as DontDestroyOnLoad)
📚 Event Database	Default asset to store your event definitions
🔗 Flow Container	Visual logic graph for event orchestration
⚙️ Generated Code	C# classes for built-in event types (void, int, float, etc.)

---

Step-by-Step Setup

1. Open the Dashboard

From Unity's top menu, navigate to:

Tools > TinyGiants > GES > Game Event System

This opens the Game Event System window, your central hub for managing events, databases, and flow graphs.

---

2. Check System Status

Locate the "Initialize System" section in the window:

Before Initialization

• The blue button "Initialize Event System" is visible
• ⚠️ Warning: "Please initialize the system first"

3. Click Initialize

Press the "Initialize Event System" button. The plugin will automatically perform the following:

Action	Result
Create Managers	Adds GameEventManager GameObject to the scene (persistent)
Generate Database	Creates GameEventDatabase_Default.asset in your project
Setup Flow Graph	Creates GameEventFlow_Default.asset for visual logic
Compile Code	Generates type-safe C# event classes

The Console will display: 🎉 GameEvent initialization complete

After Initialization

• The status bar turns green with "✅System Initialized"
• ✅Confirmation: "Core managers, database and codes are ready"

---

Verification

After initialization completes, verify the setup:

1. Hierarchy Check 🔍

   A GameEventManager GameObject should appear at the root level

2. Inspector Check 👀

   Select the manager to see assigned Database and Flow Container references

3. Console Check 📝

   Look for the success message confirming initialization

In Play Mode, the root GameEventManager persists across scene loads and keeps its registered databases and FlowGraphs. If a later scene contains another manager, its event bindings merge into the persistent instance. Register any additional databases on the persistent manager. If you start Play Mode directly in a different scene, that scene needs a root manager configured with its databases and FlowGraphs.