Company of Heroes 3: Final Stand Progression

Progression in Company of Heroes 3: Final Stand has two time scales. The official Steam description says that players build a custom battlegroup during a run, choose randomized units or abilities after waves, and keep those choices for the duration of that run. It separately says that powerful perks and unique abilities unlock between runs through faction-specific progression trees. The most useful way to read a choice is therefore to ask one question first: is this meant to solve the current defense or change what the faction can do on later runs?

That distinction is the foundation for this section. It prevents a player from treating a temporary selection as a permanent unlock, or a persistent upgrade as an immediate answer to a route that is already collapsing. Steam confirms that both layers exist; it does not publish every node, requirement, cost, rarity, reset rule, probability, or optimal order. Any guide that fills those gaps with exact numbers without an attributable current source is guessing.

Name the time scale before choosing

At the post-wave choice screen, solve the immediate problem first. If an approach lacks coverage, a temporary choice that makes that route easier to defend can be evaluated in the next wave. If the choice instead affects what you unlock between runs, write down its exact label and inspect it after the attempt; do not expect it to repair the line in front of you.

This is more than vocabulary. A player who mixes the two scales may spend an entire run trying to demonstrate a permanent improvement that has not been acquired, or blame a faction for a temporary option that was never intended to last. Separate notes make the result legible: “run choice, taken after wave X, tested on the next pressure” and “between-run upgrade, visible on the faction tree after the match” are different claims.

The official page does not state how often an option appears, whether choices can be rerolled, whether upgrades stack, or whether currency is shared. Do not let a familiar roguelite convention answer those questions. Read the current UI and retain its wording alongside the faction and date.

Build a battlegroup around the next wave you can see

Steam calls the run-specific construction a custom battlegroup. The safest useful advice is to make every selection answer a visible defensive need. If the last wave forced a late rotation, choose for coverage. If the objective was threatened, choose for the layer that lets the team regain control. If the last choice was difficult to evaluate, choose something whose effect you can observe rather than stacking another unknown interaction on top of it.

The objective is not to create an artificial “best battlegroup” list. Randomized offers mean two runs may not present the same comparison. A meaningful guide entry therefore includes the selected faction, difficulty, map name if the client shows it, the visible option wording, the run stage, the immediate need, and what happened when that need returned. Without this context, an option name is a rumor rather than a recommendation.

Treat persistent upgrades as a long-term experiment

Between runs, inspect the faction-specific progression tree. Steam confirms that persistent upgrades include powerful perks and unique abilities, and that they can meaningfully change faction play. That does not authorize a page to invent a node catalogue. Start with the visible tree and document one choice at a time: its exact name, stated requirement, effect text, faction, date, and whether the effect was observed in the released Windows Steam product.

Before selecting a persistent upgrade, decide what you expect it to change on the next run. It might affect a particular defensive need, make a formerly weak option worth testing, or simply reveal a new route for experimentation. If you cannot name the expected change, delay the choice until the current client explains it more clearly. This is not wasted progression; it protects you from turning an unfamiliar requirement into a fictional guide claim.

When an upgrade changes a run, compare it with the same faction and a similar goal where possible. Do not compare a new persistent unlock on one difficulty to an unrelated attempt with a different event, map, co-op partner, and temporary option pool. Progression is a source of variation; clean notes prevent it from hiding every other variable.

Keep faction trees separate

The Store says progress trees are faction-specific. That is a direct reason to keep the four factions separated in the site architecture. An upgrade observed for US Forces is not automatically a Wehrmacht, British Forces, or Deutsches Afrikakorps feature. Copying it across a generic “builds” page would make a reader think a shared system has been verified when the public description says the opposite.

For each faction, use a compact record rather than a promise of completion. The record can show the faction, current AppID, platform, visible upgrade name, whether it is in-run or persistent, its stated effect, source date, verification status, and a link to the exact faction page. Unknown effects stay empty. This lets players find trustworthy data without pretending that every tree is documented on launch week.

The same rule applies to cosmetic packs. Steam lists one premium cosmetic skin pack per faction. A cosmetic unlock may be relevant to a purchase page, but it is not evidence of a gameplay perk, and it should never be merged into a progression recommendation.

Avoid base-game battlegroup leakage

Company of Heroes 3 has older public battlegroup guides, videos, and discussions. They are valuable only as historical context unless they identify Final Stand’s AppID and current mode. The words “battlegroup,” “faction,” and “upgrade” are not enough to establish compatibility. A different game mode can change the timing, available pool, objectives, and incentive for the same name.

If a search result makes a specific claim, check two things before bringing it here: does it name Company of Heroes 3: Final Stand or AppID 4836540, and can the claim be found in the current Final Stand client or a current official source? If either answer is no, keep it out of the player page. This protects the reader from a polished but wrong meta recommendation.

Turn each run into a progression record

After a match, make two lists rather than one. The run list contains choices that lasted only for that attempt, ordered by when they were selected. The progression list contains only the faction-tree upgrades that remained visible after the attempt. Add the problem each choice addressed and one observation that could prove or disprove it next time.

This separation helps both solo and co-op play. A partner can tell you what changed in the field while you track a temporary option; after the run, compare the persistent screen together. Steam confirms two-player online co-op but does not describe shared progression, reward ownership, or unlock rules, so do not assume those systems work one way until the product itself or an official support source confirms them.

The Battlegroup Guide is the next page for a current-run selection routine. Persistent Upgrades and Faction Progression Trees remain separate approved pages because their player questions are long-term and faction-specific. None of these pages should publish a numerical tier list until the entries can be tied to a current source and stated conditions.

Sources

• Company of Heroes 3: Final Stand on Steam — official custom battlegroup, after-wave randomized-choice, persistent-upgrade, and faction-tree wording; checked 2026-08-13.
• GameReactor review by Patrik Severin — independent evidence that the released game has a wave-defense play loop; published 2026-07-30, checked 2026-08-13.