The Hero Run template: runs, rage cards and bosses

What is inside

• Runs. The campaign is islands of six levels, each island with its own world theme. A level is one run: waves of enemies, a camp, fountains, a chest on the road and a boss at the end. A death ends the run.
• Rage and cards. Kills fill the rage; at every threshold the run pauses and the player takes one of three cards. There are 58 cards: a trigger and an effect ("on kill", "on crit", "every 3rd attack" - lightning, axes, spears, healing, stuns, charges) or a passive bonus. One "Refresh" a run.
• Attack and armor types. The weapon has an attack type, every enemy an armor type, and the damage table decides how hard a blow lands: green numbers - strong, grey - weak. The types come in island by island; the first island is casual, and from the second one a scouting screen shows the enemies' armor before the run.
• Gear. A weapon, armor and a shield: the shield is a blue pool that takes the blows first. A two-handed weapon leaves no room for a shield.
• Ultimate and potions. One ultimate a run (a meteor or a frenzy); only a card brings it back. Potions are taken along and drunk by a tap, or on their own at low health with "Auto" on.
• Energy and the reward chest. A run costs energy, which refills by itself. At the end the ticket of the run opens a chest by the result: defeat, victory or a run without losses.
• The hero's sheet under the road: every number with what the cards added, the cards taken and their effects.
• A 2D hero with its own skeleton, swappable parts and animations; gear changes how it looks.

Systems already connected

Besides the six systems of every project, the template brings its own:

In a new project all of this is already filled with a sample: GOLD, GEMS, ENERGY (30 at most, one back every 6 minutes, 5 a run), RUN_TICKET, POTION and XP currencies, heroes, gear with attack and armor types, reward chests (the first three always hold a potion), a gear summon, a store and quests.

For developers

• The game module is hero-run (Phaser plus a React screen). The game sits inside the lobby: balances above it, the system tabs below it. It brings the character, lootboxes, store and inventory systems with it.
• The fight uses the hero's server-side stats; the cards act only inside a run. Progress is stored in the player's private data (hero_run_progress).
• The game reports the level_cleared and run_finished counters to quests: build your own tasks on them.
• Module events for other modules: hero-run:level-cleared@1 (a level was cleared) and hero-run:character-upgraded@1 (a hero ranked up).

How projects and modules are built is in the TypeScript SDK overview.