Game Event System (GES)
Stop Fighting Spaghetti. Start Building with Clarity.
Website (
https://tinygiants.tech/) | Documentation (
https://tinygiants.tech/docs/ges) | Discord (
https://tinygiants.tech/discord) | YouTube (
https://tinygiants.tech/youtube/ges) | Unity Forum (
https://tinygiants.tech/forum/ges)
Game Event System (GES) is a visual, type-safe event architecture for Unity. It turns scattered event calls and hidden dependencies into searchable event assets, maintainable flow graphs, and direct C# APIs.
Create events as ScriptableObject assets, connect gameplay through the Inspector or code, organize content across multiple databases, and inspect execution from one centralized toolchain.
GES supports Mono, IL2CPP, and Enter Play Mode Options with Domain Reload disabled.
π’ Important Notice for Legacy Users
I'm back! Due to regional policy adjustments, GES was migrated to this new listing. If you purchased the previous listing and need migration assistance or want to claim your community activation code, please join the TinyGiants Discord Community.
A dedicated migration workflow is included for legacy projects. It exports databases, event sub-assets, generated code, FlowGraphs, scenes, Prefabs, ScriptableObjects, and recorded references into a checksum-verified archive. The importer performs conflict and GUID checks before restoring data and supports rollback if migration cannot be completed safely.
π Core Features
Asset-Driven Event Architecture
Events are ScriptableObject sub-assets stored inside a GameEventDatabase. Persistent event GUIDs replace magic strings, while normal asset renames and folder moves preserve Unity references.
Split large projects into multiple databases for Core, Combat, UI, DLC, or other modules. Databases can be registered, queried, activated, loaded, and released at runtime.
Type-Safe Events and Automatic CodeGen
GES supports:
- GameEvent β parameterless signals
- GameEvent<T> β strongly typed payloads
- GameEvent<TSender, TArgs> β sender-aware events
Use 32 built-in C# and Unity types immediately. The integrated CodeGen workflow creates concrete event types and matching Raiser/Receiver components for custom payloads and sender combinations, solving Unity's generic serialization limitations without giving up type safety.
AOT-Safe Runtime for Mobile and IL2CPP
GES uses strongly typed event actions instead of generating Expression Tree delegates at runtime.
- Built-in and generated event actions invoke typed code directly.
- FlowGraph event dispatch does not generate runtime expression delegates.
- Generated event and bridge classes work with IL2CPP/AOT targets.
- Suitable for mobile, console, desktop, and WebGL projects using Mono or IL2CPP.
AOT Condition Baking
Build nested visual conditions for IL2CPP projects through a defined bake-and-validate pipeline.
- Assigns deterministic identities to serialized condition trees.
- Generates the runtime evaluator registry.
- Detects missing or stale conditions before a build.
- Reports the exact asset and property that must be baked again.
- Stops invalid builds instead of silently changing condition behavior.
Optional Addressables Integration
Load event databases only when their content is needed.
- Load a GameEventDatabase asynchronously by Addressables address or GUID.
- Resolve loaded events through their internal GUIDs.
- Share concurrent loads of the same database.
- Register loaded databases automatically.
- Release databases through owned leases.
- Detect duplicate event GUIDs before registration.
- Cancel one pending request without interrupting other consumers.
Addressables support is optional. Core GES does not require the Addressables package.
Visual Flow Orchestration
Design event relationships in a zoomable node graph.
- Parallel fan-out triggers
- Sequential blocking chains
- Mixed parallel and sequential flows
- Delays, loops, repeat counts, coroutine/async waits, and conditional gates
- Argument transformation b
Description sourced from the Unity Asset Store listing.