System Dashboard
Check scene setup, open the event editor and monitor, and run project maintenance tools from Game Event System.
Unity developers setting up GES or managing an existing installation.Open the dashboard from the Unity menu.
Tools > TinyGiants > GES > Game Event System
Interface Overviewβ
The dashboard groups scene setup and editing on the left, with environment and project information on the right.

The screenshot shows the setup controls beneath the version header. In GES 2.3.0, the main window shows one preview image and adds a Changelog panel. Use Initialize System to check the active scene before opening the editor.
Initialize Systemβ
A green System Initialized button indicates that the manager, database, and generated code are ready. When Initialize Event System is available, click it to set up the scene, then save the scene. See Installation for the setup and hierarchy checks.
Editor & Monitorβ
After initialization, use the Open button beside the tool you need.

| Tool | What you can do |
|---|---|
| Game Event Editor | Create, search, filter, and edit events in the selected database |
| Game Event Monitor | Follow event execution, listeners, and FlowGraph activity during Play Mode |
Tools & Utilitiesβ
Open a tool to generate code, remove generated custom types, bake conditions, or move event data between projects.

| Tool | Result |
|---|---|
| Generate Game Event Code | Opens the type picker to generate event classes and bindings |
| Clean Game Event Code | Opens the cleanup window to select generated custom code to remove |
| Clean All Game Event Code | Deletes generated custom code after confirmation and keeps the basic types and bindings |
| Bake AOT Conditions | Regenerates the condition registry and linker file before a build |
| Import Event Data / Export Event Data | Restores a compatible archive or saves event assets, code, and recorded references to an archive |
System Informationβ
Read the Unity version, render pipeline, editor platform, and scripting backend of the selected build target. The panel displays the environment settings. See Automatic Environment Check for the supported Unity versions.
Quick Accessβ
Select a shortcut to locate the corresponding folder in the Project window.
| Shortcut | Folder |
|---|---|
| Documentation | The installed documentation folder |
| Demo Scenes | The scenes included with GES |
| API Scripts | The runtime scripts |
| Custom Databases | Project databases |
| Custom Flow Graphs | Project FlowGraph assets |
| Custom CodeGen | Project-generated event classes and bindings |
Support & Communityβ
Open Documentation, Discord Community, Video Tutorials, Asset Store, or Support Email to find help with your installed version.

When reporting a problem, include the GES and Unity versions, the render pipeline, and the first relevant Console error. See Community & Support for the support channels.
Changelogβ
Changelog reads the release notes from the installed package. Click View Full Changelog to see the complete version history.

- 2.3.0 adds Receiver Action Conditions and updates editor layout, event selection, and scene-condition validation. The Event Action card uses Unity's native UnityEvent controls. Run Bake AOT Conditions again after upgrading.
- 2.2.0 supports Unity 6000.6.0f1. Press Esc or click outside a FlowGraph event selector to cancel, including when the database has no matching events. The selector also closes on editor exit or script reload.
- 2.1.1 fixes Game Event Editor scrolling, duplicate Odin Inspector headers, and event selection for arrays, lists, and multi-object editing. It also fixes the optional Addressables assembly reference.
- 2.1.0 aligns the shared files with GCS 1.5.0 and keeps the GES editor and runtime APIs used by the optional GCS event bridge.
Troubleshootingβ
| Symptom | Check |
|---|---|
| The menu or dashboard is unavailable | Fix compilation errors in the Unity Console and confirm that the GES package scripts are present |
| Initialize Event System remains available after setup | Check the Console, then verify the manager and database in the active scene |
| An IL2CPP build reports stale conditions | Run Bake AOT Conditions and rebuild |