Demos

The Demos sample is a set of small playable scenes. Each scene shows one part of Vantage and explains itself on screen. The pages in this section describe every scene exactly: the assets it uses with their field values, where every object stands, and the steps to build it yourself.

Import the scenes

1. Open Window → Package Manager and select Vantage.
2. Open Samples and press Import next to Demos. Unity copies the sample to Assets/Samples/Vantage/<version>/Demos.
3. Accept the TextMeshPro essentials import if Unity offers it. The labels above units need it.
4. Open Vantage → Demos. The window lists every scene; press Play next to one.

The scenes need the Universal Render Pipeline and the Input System set as the active input handling.

The scenes

Controls

• Right-click the ground to walk, a hostile unit to attack, an item or gold to pick it up.
• Left-click a unit to select it, Shift-click to add or remove one, drag a box to select several, double-click to select every unit of that kind on screen, and press Esc to clear.
• In 23 · Selection and Orders there is no hero. Right-click gives the selected units orders, A and a left-click attack-moves, S stops and H holds. Ctrl and a number saves a control group, the number selects it. Move the mouse to the screen edge to scroll.
• Number keys cast the abilities on the hotbar. Clicking a slot casts too.
• Scroll to zoom, hold the middle mouse button to pan, press Space to re-centre on your unit.

Every panel on screen can be hidden:

The unit frames, the action bar, the stat list, the resource bars, the buff bars and cast bars, the currency readout, the quest tracker, the threat list, the selection panel and the interaction prompt are the sample’s HUD panels and hide with F10. The inventory, talent, quest log, crafting and dialogue windows are the sample’s windows: a key opens one through VtDemoWindowKey, Esc closes the topmost, and the conversation window opens by itself when someone speaks. Messages such as a refused cast or a level gained are toasts from the sample’s notifications.

The lesson card is split into pages: Overview, Look at, Try, and Panels with the keys of the panels in the current scene. The name of the page shown sits under the title. Look at lists each asset or object as a small tag above its explanation, Try numbers the steps, and Panels shows each key as a key cap. Back, a bar per page and Next sit under a divider at the bottom of the card; click a bar to jump to its page.

Every unit with health has a nameplate over its head: its name, level and a health bar, red for enemies, green for allies and amber for neutral units, with the unit’s hint and its active buffs underneath. A unit’s hint is the Subtitle of its VtNameplateInfo. Resource nodes and crafting stations have VtNameplateInfo with Hidden on and keep their world labels. See UI. When the Game view is too short for a page, the page scrolls with the mouse wheel and the panels below it stay in view.

What the sample contains

The layout every scene shares

Every scene has these root objects. The scene pages only list what differs.

Units and items are instances of the kit prefabs. Each instance sets its own Definition, or item, and every unit gets VtDemoReviveAfterDeath so the scene stays playable. On the player instance, the label’s Show Health is off.

Build the shared layout

1. Create a new scene with a Directional Light, or start from an empty scene and add one.
2. GameObject → Create Empty, name it Level, at (0, 0, 0).
3. Add a 3D Object → Cube as a child of Level, name it Ground, set Position (0, -0.5, 0) and Scale to the scene’s size with a height of 1, for example (30, 1, 30).
4. Add four more cubes under Level as walls, 1.5 high, along the edges of the ground.
5. Select Level, Add Component → Navigation → NavMesh Surface, set Collect Objects to Current Object Hierarchy, and press Bake. Units are placed outside Level so they are not baked into the NavMesh.
6. Select Main Camera, check that its tag is MainCamera, and Add Component → Vantage → Camera → VtTopDownCamera. Set its Initial Target once the player is in the scene.
7. GameObject → UI → Event System. In its inspector, press Replace with InputSystemUIInputModule.

Kit prefabs

Unit.prefab is every unit in every scene.

Player.prefab is a prefab variant of Unit with VtTopDownClickInput, VtAbilityHotkeys, VtGroundTargetIndicator, VtUnitSelection, and VtSelectionIndicator with Style set to the package preset SoftRing, added.

Kit/Vfx holds the effects: particle prefabs named after what they show, such as FireSparks, FireBurst, FrostRing, SnowFall, MeteorImpact and DeathPuff, all using one additive particle material, Particle, with a soft round texture. Burst and spark prefabs keep their particles at the unit’s chest or feet through a child offset. Area prefabs are authored for a radius of 1 and are used by cues with Scale To Area on.

WorldItem.prefab is an item on the ground: a gold Box cube 0.5 wide turned 45 degrees, a Box Collider set to Is Trigger with Center (0, 0.4, 0) and Size (1, 0.8, 1), VtWorldItem with Item and Count set per instance, and a Label at (0, 1.2, 0). The collider is a trigger so units walk over items while clicks still find them.

GoldPile.prefab is a flat gold cylinder with a trigger Box Collider, VtDemoGoldPile with Currency set to Gold and Amount set per instance, and a Label.

FireProjectile.prefab and ArcaneProjectile.prefab are glowing spheres 0.35 across without shadows, used as projectile prefabs by damage effects.

The materials in Kit/Materials use the URP Lit shader. Kit/UI/VtDemoPanelSettings uses Scale Mode Constant Pixel Size at Scale 1, so the panels stay readable in a small Game view, with the theme VtDemoTheme. That theme imports the Vantage default theme and adds three rules for the demo cards: 10 px below each card, 6 px below its header, and a 20 px title. See UI.

Build the prefabs

Unit, the prefab every unit uses:

1. GameObject → Create Empty, name it Unit, at (0, 0, 0). Its pivot is the unit’s feet.
2. Add Component → Physics → Character Controller. Set Center (0, 1, 0), Height 2, Radius 0.45. Center Y is half the height, so the capsule stands on the pivot instead of floating above it.
3. Add Component → Vantage → Units → VtUnit. Unity adds the unit’s other components with it: modifiers, stats, traits, buffs, combat engagement, abilities, combat text and equipment.
4. Add Component → Vantage → Movement → VtLocalMovementExecutor. It moves the Character Controller.
5. Add Component → Vantage → Movement → VtTopDownClickToMove. It follows paths, turns the unit and applies gravity.
6. Add Component → Vantage → Movement → VtNavMeshPathProvider. It finds paths on the baked NavMesh.
7. Add Component → Vantage → Presentation → VtUnitPresenter. It plays the effects authored on abilities, buffs and unit definitions.
8. GameObject → 3D Object → Capsule as a child named Body, at (0, 1, 0). Remove its Capsule Collider; the Character Controller is the unit’s collider.
9. Optional, as in the table above: the Facing cube, and VtDemoFactionTint on the root with Body assigned.
10. Drag Unit from the Hierarchy into the Project window to save it as a prefab.

Player, the unit you control:

1. Right-click Unit.prefab in the Project window, Create → Prefab Variant, and name it Player.
2. Open it and Add Component → Vantage → Movement → VtTopDownClickInput. It turns right-clicks into orders: walk to the ground, attack a hostile unit, pick up an item.
3. Add Component → Vantage → Movement → VtAbilityHotkeys. It casts abilities from keys; scenes without abilities leave its slots empty.
4. Add Component → Vantage → Visuals → VtGroundTargetIndicator. It draws the ring while a ground ability is aimed.
5. Add Component → Vantage → Selection → VtUnitSelection. It turns left-clicks and drags into selection.
6. Add Component → Vantage → Selection → VtSelectionIndicator, and drag SoftRing from Packages/Vantage/Runtime/Core/Selection/Presets into Style. It draws the markers under selected and hovered units.

WorldItem, an item on the ground:

1. GameObject → Create Empty, name it WorldItem.
2. Add a 3D Object → Cube child named Box at (0, 0.3, 0), Rotation (0, 45, 0), Scale (0.5, 0.5, 0.5), and remove its Box Collider.
3. On the root, Add Component → Physics → Box Collider: Is Trigger on, Center (0, 0.4, 0), Size (1, 0.8, 1).
4. Add Component → Vantage → Items → VtWorldItem, and save it as a prefab. Each placed copy sets its own Item and Count.

GoldPile, gold on the ground:

1. GameObject → Create Empty, name it GoldPile.
2. Add a 3D Object → Cylinder child named Coins at (0, 0.08, 0), Scale (0.7, 0.08, 0.7), and remove its collider.
3. On the root, add a Box Collider with Is Trigger on, Center (0, 0.3, 0), Size (1, 0.6, 1).
4. Add Component → Vantage → Demos → VtDemoGoldPile, set Currency to Gold, and save it as a prefab.

FireProjectile and ArcaneProjectile:

1. GameObject → Create Empty, name it after the projectile.
2. Add a 3D Object → Sphere child named Ball with Scale (0.35, 0.35, 0.35), remove its collider, set Cast Shadows to Off, and give it the Fire or Arcane material.
3. Save it as a prefab. A damage effect with this prefab under Projectile adds the flight behaviour when it launches.

Shared content

Content/Shared holds what several scenes use.

Every unit definition in the sample sets Damage Channel Melee, Damage Type Physical, Attack Range 2, Attack Interval 1 and Basic Attack BasicAttack unless its page says otherwise. Fields a page does not mention keep their defaults.

Demo-only components

These exist to make the scenes readable. A game does not need them.