Skip to main content

System dashboard

Guide

Check the active scene's setup and open the tools for editing and inspecting battles.

Open the window from this menu:

Tools > TinyGiants > GCS > Game Card System

The Game Card System dashboard with setup, tools, changelog, quick-access, and support cards

The dashboard above brings scene setup and tool access into one window. Use Initialize System on the left to prepare the battle scene, then open the authoring and debugging tools through Editor & Monitor. On the right, check the Unity environment in System Information, look up release changes in Changelog, open project folders through Quick Access, or find help under Support & Community. See Installation and initialization for the scene setup steps.

If you use Game Event System, click Initialize GES Events under GES Event Bridge. Once compilation finishes, confirm 48 / 48 Events Synced. See GES integration for setup and mapping repair.

Open authoring and diagnostic tools​

After the system and scene initialize successfully, both Open buttons under Editor & Monitor become available.

The Editor & Monitor card with Game Card Editor and Game Card Monitor entry points

  • Open Game Card Editor to create or edit Cards, Decks, Players, Enemies, Statuses, and Encounters. Its database dropdown lists the active databases on the scene's Manager.
  • Open Game Card Monitor in Play Mode to inspect units, card piles, battle phases, FlowGraph execution, events, and wait state.

Both tools also open directly from Tools > TinyGiants > GCS.

Check the Changelog​

The Changelog card in the Game Card System dashboard

Check the latest entry to confirm the installed version after an upgrade. Click View Full Changelog to see earlier releases.

Locate directories through Quick Access​

Use Quick Access to locate Demo content, runtime scripts, and your custom data in the Project window.

The Quick Access card with links to common package directories and the custom data directory

The first click selects the matching directory in the Project window. When it is already selected, clicking the same entry again opens that directory.

Entry pointActual location and content
Demo DatabasesDemo/Databases/ under the current installation, containing the six Single-Character preset databases and six focused Multi-Character databases
Demo ScenesDemo/Scenes/ under the current installation, containing 13 playable battle scenes
API ScriptsRuntime/ under the current installation, containing GCS.API.cs and the rest of the runtime code
Custom DataThe currently resolved user-data root, which defaults to Assets/TinyGiantsData/GameCardSystem/
tip

  • If a disk path exists but cannot load as a Unity asset, the entry opens the location in the system file manager instead.

  • Custom Data opens after you create content in the user-data directory.

See Project structure for the boundary between installation and user-data directories. Demo content reference and Demo scene reference cover the Demo databases and scenes. GCSApi guide explains the public entry point under Runtime.

Submit a support request​

Open Support & Community to reach the documentation, community, or support email.

The Support & Community card with documentation, community, forum, email, and rating links

Include this information in a support request:

  • All four environment values from System Information.

  • The complete Unity Console error and call stack.

  • The relevant Game Card Monitor tab and current wait state.

  • Reproduction steps, Encounter name, and related content assets.

Check Common symptoms and Runtime errors for the Console message or wait state you found.

On this page