Ascension, Mastery, and Evolutions Explained

New players see the recruiting screen and think Command An Army is a gacha. It is not — it is a development game wearing a gacha’s clothes. The three upgrade tracks (Ascension, Mastery, evolution) mean the unit you recruit on day one can be your strongest unit on day thirty, and the four-slot army cap concentrates your whole economy onto just four stories. This guide explains each track and how to spend between them.

What is Ascension?

Ascension fuses duplicate copies of a unit into a stronger version of that unit. Pull (or otherwise obtain) the same troop again, and that copy becomes fuel instead of clutter.

The strategic consequence is the single most important economy fact in the game: availability is a stat. A common unit whose duplicates arrive constantly ascends fast and cheap; a rare unit you have pulled once may sit at its base version for weeks. The game says this out loud — rarer does not always mean stronger — and the rarity guide unpacks why. When you pick your four slots in the army building guide, duplicate availability belongs in the decision.

What is Mastery?

Mastery is the long track: a unit levels toward 20 through use. There is no clever shortcut documented at launch — you play with a unit, and it grows. Two implications worth planning around:

1. Mastery rewards commitment. In a four-unit army, your mastery levels concentrate naturally on your core lineup. Players who rotate slots every match have four half-leveled units; players who commit have four near-cap units.
2. Mastery precedes endgame planning. Before deciding whether a flex slot is permanent, check its mastery trajectory. A unit you enjoy at level 8 is a unit you will love at level 20; a unit that already bores you is a dead slot no matter its ceiling.

What are evolutions?

Evolutions are promotions along defined paths — a unit transforms into a stronger, usually more specialized form. Two chains are documented at launch:

• Mercenary → Squire → Knight
• Archer → Longbowman

The pattern those two chains establish — a modest base unit growing into an advanced battlefield role — is exactly why the recruiting question in this game is “what does this unit become?” rather than “what is this unit now?” The evolution paths page tracks known chains and will grow as the community maps the full set.

Planning note: evolutions interact with your other two tracks. A unit you have already ascended and mastered carries that investment into its evolved form (that is the documented design intent of a promotion system), which makes your day-one common pulls legitimate long-term slots, not placeholders.

How do the three tracks interact?

The healthy loop: pick four complementary roles → play them until mastery climbs → feed duplicates to whichever ascends cheapest → plan evolutions around whichever core unit has a documented chain. When a new tempting pull appears, the test is whether it replaces a role in your four — not whether its rarity is shinier. If it does not replace a role, it is fuel for an Ascension you already own.

What happens to your investment when a patch lands?

Balance patches re-price everything — and this developer patches actively (a balance update shipped inside launch week; the codes page tracks the trail). The calm way to absorb a patch:

1. Change nothing for a day. Patch-day impressions are the least reliable data in any game; let the lobby’s hot takes cancel out.
2. Re-check roles, not ranks. If your holder still holds and your breaker still breaks, a number tweak does not unmake your four. Replacements are for role failures, not stat drift.
3. Redirect new duplicates first. The cheapest way to test a buffed unit is feeding it the copies you were going to spend anyway — before committing Mastery time.

The mirror-image risk is FOMO-rebuilding your whole army every patch. In a four-unit system, a full rebuild resets three upgrade tracks at once; the players who climb fastest patch after patch are the ones who changed the least.

What mistakes waste upgrade investment?

1. Ascending flavor-of-the-week units. Every duplicate spent on a unit outside your core four is budget taken from your core four.
2. Evolving into redundancy. If your Knight already holds the frontline, evolving a second unit into another frontline does not add a role — it adds a benchwarmer to a four-seat roster.
3. Ignoring the base-unit economy. The Mercenary → Knight chain means even freebie pulls are long-term assets. Delete nothing, dismiss nothing as trash.

Still assembling the core four? Start with the unit type overview, fund it with the launch codes, and the beginner guide sequences the rest.