Demo asset layout
Locate Demo assets by their owning card, unit, status, intent, deck, or encounter, and organize project presentation assets by the same rule
Root folders
📦 Demo/Content/ # All shipped presentation assets, grouped by owner
├── 🎨 Art/ # Cross-object shared assets only
├── 🃏 Cards/ # Card-family frames, prefabs, and per-card artwork
├── 🗂️ Decks/ # Starting/reward deck cover icons for each class
├── 🌄 Encounters/ # Class backgrounds, parallax layers, and encounter UI
├── 🎯 Intents/ # Enemy-intent icons and the widgets that display them
├── ✨ Statuses/ # Status icons, status widgets, and status-owned VFX
└── 🧙 Units/ # Player/enemy artwork, prefabs, and shared unit widgets
Cards
🃏 Content/Cards/ # Five card families plus their one shared glow sprite
├── ⚔️ Basic/ # Basic-family frame, prefab, and card artwork
│ ├── 🖼️ Artwork/ # Art for Basic cards such as Strike and Defend
│ ├── 🎨 Basic.png # Basic card-frame sprite
│ └── 🧩 Basic.prefab # Basic card-view prefab
├── 💥 Burst/ # Burst-family frame, prefab, and artwork
├── 🕯️ Curse/ # Curse-family frame, prefab, and artwork
├── 🛠️ Skill/ # Skill-family frame, prefab, and artwork
├── 🤝 Support/ # Support-family frame, prefab, and artwork
└── ✨ CardGlow.png # Glow sprite shared by every card family
The five folders correspond to the five card template families. Each owns its frame sprite, card Prefab, and Artwork/, which stores the art for cards using that frame. The CardGlow.png shared by every template stays at the Cards/ root
When a card later gains dedicated VFX, audio, or animation, place those assets under the card family that uses them and add a VFX/, Audio/, or Animation/ subfolder. Avoid asset-type roots such as Content/VFX/Cards/
Units
🧙 Content/Units/ # Unit-owned art/prefabs plus unit-wide shared assets
├── 👹 Enemy/ # Enemy folders grouped first by class, then by unit
│ ├── 🏹 Enemy_Hunter/ # Hunter enemy roster
│ │ ├── 🐍 Enemy_PlagueStalker_Normal/ # Normal enemy artwork and prefab
│ │ ├── 🍄 Enemy_SporeBrute_Elite/ # Elite enemy artwork and prefab
│ │ ├── 💀 Enemy_MireReaper_Boss/ # Boss artwork and prefab
│ │ └── 🌱 Enemy_BogPolyp_Summon/ # Summoned-unit artwork and prefab
│ ├── 🪄 Enemy_Mage/ # Mage enemies, each in its own tier-suffixed folder
│ ├── ✨ Enemy_Priest/ # Priest enemies, each in its own tier-suffixed folder
│ └── ⚔️ Enemy_Warrior/ # Warrior enemies, each in its own tier-suffixed folder
├── 🦸 Player/ # Player-unit assets grouped by class
│ ├── 🏹 Hunter/ # Avatar, full-body art, and player prefab
│ ├── 🪄 Mage/ # Avatar, full-body art, and player prefab
│ ├── ✨ Priest/ # Avatar, full-body art, and player prefab
│ ├── ⚔️ Warrior/ # Avatar, full-body art, and player prefab
│ └── 🌟 Shine.png # Highlight sprite shared by player units
├── 🧩 Prefabs/ # Unit-wide widgets such as HpWidget.prefab
└── 🌑 Shadow.png # Ground shadow shared by every unit
Each enemy uses its own Enemy_<Name>_<Tier> folder under the owning class, with art and Prefab stored together. Player assets store the avatar, full-body art, and unit Prefab by class. Components shared by multiple units, such as HP bars, belong in Units/Prefabs/
Encounters
🌄 Content/Encounters/ # Presentation assets owned by each encounter class
├── 🏹 Hunter/ # Hunter encounter presentation
│ ├── 🖼️ Background.png # Full-screen class background
│ ├── 🏞️ Layer/ # Foreground/background parallax layers
│ └── 🧭 UI/ # Hunter-specific encounter UI art
├── 🪄 Mage/ # Mage background, parallax layers, and UI art
├── ✨ Priest/ # Priest background, parallax layers, and UI art
└── ⚔️ Warrior/ # Warrior background, parallax layers, and UI art
Encounter backgrounds and their parallax layers belong to the class folder; the scene files themselves are not content; they live under Demo/Scenes/<Class>/
Statuses and intents
✨ Content/Statuses/ # Status-owned icons, widgets, and presentation effects
├── 🧩 Prefabs/ # StatusWidget.prefab and StatusIconEntry.prefab
├── 💫 VFX/ # 25 status apply/expire effect prefabs
└── 🖼️ Status_<Name>.png # 30 status icons selected in the Game Card Editor
🎯 Content/Intents/ # Assets used to telegraph enemy actions
├── 🧩 Prefabs/ # IntentWidget.prefab and IntentEntry.prefab
└── 🖼️ Intent_<Kind>.png # Eight icons: Attack through Unknown
Each status definition references its icon through the Icon field in Game Card Editor Status mode. Status-specific effects live in Statuses/VFX/, with apply and expiration presentation configured through Status Apply FX and Status Expire FX nodes in the status FlowGraph. Intent icons match the action types shown above enemies, while the two Prefabs/ folders store the status and Intent controls used by Demo UI
Put shared assets in Art
Content/Art/ is reserved for assets used by multiple owning objects:
🎨 Content/Art/ # Shared presentation infrastructure used across owners
├── 🔊 Audio/ # Mixer, BGM, ambience, gameplay SFX, UI, stingers, and voices
├── 🔤 Fonts/ # Runtime fonts and TextMesh Pro font assets
├── 🧪 Materials/ # Shared UI, environment, and VFX materials
├── 🧩 Prefabs/ # Cross-object widgets and reusable presentation prefabs
├── 📦 Resources/ # TinyGiants assets loaded through Unity Resources
├── 🧬 Shaders/ # Shared UI, sprite, environment, and particle shaders
├── 🖼️ Sprites/ # Shared cursor, UI, and VFX textures
└── 💥 VFX/ # Shared combat and class-ambience effect prefabs
The audio tree illustrates the shared boundary. A Mixer, BGM, ambience, general card sounds, combat hits, Intent telegraphs, status sounds, stingers, UI, and enemy voices can serve multiple battles. Audio dedicated to one card family belongs under that family instead
Place object-specific assets directly under their owner and reserve Art/ for cross-object content. Establishing ownership before saving the file avoids changing unrelated references when assets move later
Placement rules for audio, VFX, and animation
When a production pass adds final presentation assets, choose the directory by ownership
| The asset belongs to | Put it under |
|---|---|
| One card family | Content/Cards/<Family>/VFX/ (or Audio/, Animation/) |
| One enemy | its Content/Units/Enemy/Enemy_<Class>/Enemy_<Name>_<Tier>/ folder |
| One player class | Content/Units/Player/<Class>/VFX/ (or Audio/, Animation/) |
| One encounter class | Content/Encounters/<Class>/VFX/ (or Audio/, Animation/) |
| Many unrelated objects | Content/Art/VFX/ (or Audio/, Animations/) |
Create per-object subfolders when the first matching asset appears. There is no need to add an empty Audio/ directory to every card family in advance
Apply the same rule in a project
Demo content always uses this layout. Project-owned assets can apply the same ownership rule in this order:
- Decide which object owns the asset before importing it
- Put the asset in that object's folder, creating the subfolder if needed
- Use a shared folder only when the asset has no single owning object
- Keep databases separate from presentation assets
- Keep Demo and production content under separate roots so removing the Demo does not affect project assets