Demo Overview

🎮

Guide

The demo is a playable card battler and an inspectable reference project built with the same GCS tools available to your game

Included content

Content	Count	Owning location
Battle scenes	12	Demo/Scenes/<Class>/
Encounters	12	PresetEncounterDatabase
Players	12	PresetPlayerUnitDatabase
Enemies	16	PresetEnemyUnitDatabase
Decks	16	PresetDeckDatabase
Cards	80	PresetCardDatabase
Statuses	30	PresetStatusDatabase

The four class lines are Warrior, Mage, Hunter, and Priest; each one has Normal, Elite, and Boss scenes, three player tiers with starting decks, a reward deck, and a four-enemy roster; the demo supports Unity 2021.3 or newer, including Unity 6, and uses one content set for the Built-in Render Pipeline and URP

Choose the reference that matches the asset or scene you need:

Need	Open
Scene names, tiers, lineups, and Play Mode captures	Demo Battle Scenes
Database ownership for cards, decks, statuses, units, and encounters	Demo Content Reference
Asset ownership and folder placement	Demo Asset Layout

Six preset databases

All demo definitions are registered through six assets under Demo/Databases/: card, deck, encounter, enemy, player, and status databases; a demo scene reads from those preset databases and does not copy entries into another database

The Demo Content Reference maps each content family to its database and shows how to reuse a graph or rule block on project-owned content

Read mechanics before presentation

When inspecting a demo effect, separate the mechanic from its presentation:

• the card, status, enemy, or encounter definition owns authored data
• FlowGraph owns the behavior sequence
• prefabs, art, VFX, SFX, and animation own presentation
• the scene and bootstrap connect the runtime view

If the card resolves, resources change, enemies act, and the battle reaches an outcome, the mechanical chain is healthy; A missing sound or unfinished effect belongs to the presentation layer, not the encounter definition