Company of Heroes 3: Final Stand has persistent upgrades between runs across faction-specific progression trees. That is an official product fact. The public Steam page does not provide the tree names, node descriptions, currency requirements, upgrade levels, reset options, unlock order, or a best path. The most useful guide at this stage is a method for reading the live progression screen accurately and separating a long-term choice from the temporary choices that only last for one wave-defense run.
Start on the between-run screen
Open the progression screen for the faction you actually played. Record the exact label of the upgrade or perk, its visible requirement, any displayed level, and the date. If the client names a currency, write that name rather than converting it into a familiar resource from another Company of Heroes title. If the screen does not explain a cost, unlock, or reset, mark it unknown instead of filling the gap with a community assumption.
This small record gives you a reliable comparison later. Final Stand has four playable factions, and the official description says their progression trees are faction-specific. A change on one faction screen does not prove the same option exists on another. Keep every note tied to the faction label and Steam AppID 4836540 so a parent-game guide or an old screenshot cannot quietly become a false source.
Do not confuse a permanent choice with a run choice
Steam also says that after waves, players choose randomized units or abilities that persist for the duration of the run. Those are different from persistent upgrades. A run choice should be recorded with the wave, the defensive problem it answered, and the next pressure where it was tested. A persistent upgrade should be recorded on the progression screen with its exact visible requirement. Mixing the two creates bad advice: it can make a temporary selection sound permanent or make a long-term unlock sound available during every fresh attempt.
Before spending or selecting anything, ask which time horizon you are looking at. Does the client show it only after a wave, or does it remain on the faction screen after a match? Then read the current tooltip or description. A familiar word such as ability, perk, or upgrade is not enough to establish behavior. The current product UI is the source for its own distinction.
Make a progression decision serve a recorded failure
Persistent progression is most useful when it answers a failure you can describe. After a run, note the first place where the defense lost time, coverage, or recovery. Then look at the relevant faction screen and compare the wording of an available upgrade with that observed problem. Do not select an item just because it sounds more powerful or because another game used the same label. A clear reason lets the next run test a claim instead of hiding several changes inside a vague sense of improvement.
The Gamereactor PC review reports that long-term faction progression can affect a starting state and that its reviewer saw repeatable upgrade levels. That is a useful independent observation, not an official catalogue of current values. Check the live client before treating any level count, bonus, or currency claim as reliable. A patch can revise the screen, and one review cannot establish every faction’s rules.
Observed failure
Write the first route, wave, or recovery point that made the run collapse.
Visible upgrade text
Match only the wording the current faction screen shows to that concrete problem.
Next-run test
Keep the displayed difficulty and observation goal stable enough to see whether the state changed the result.
Compare runs without hiding changed conditions
Two runs can differ because of faction, difficulty, map, dynamic event, post-wave offer, a persistent upgrade, or player count. Do not call an upgrade the reason for success unless the other major conditions are recorded. Use a compact comparison line: faction, difficulty label, map label if visible, progression state, first unstable wave, and one temporary choice. This does not require a spreadsheet or unproven stat formula; it gives a player enough context to repeat a useful test.
For two-player co-op, add the faction pair and describe what each player observed. Final Stand supports online two-player co-op, but public sources do not establish shared progression, ownership, resource, or matchmaking rules. Do not turn a teammate’s experience into a general unlock rule without visible client evidence.
Protect the product boundary
Company of Heroes 3 AppID 1677280 is a different Steam base game. Its campaigns, DLC, balance patches, faction doctrines, resources, and progression systems are not this page’s evidence. A bundle that lists both products does not merge their technical systems. Final Stand’s official Store page says it is standalone and does not require a previous Company of Heroes title, which is a purchase boundary rather than a license to transfer mechanics.
Continue with Faction Progression Trees for a clear screen inventory method and Battlegroup Guide for current-run choices. The next safe improvement to this page needs an official Final Stand update or a repeatable client record with its date and displayed version, not a borrowed tier list.
Sources
- Company of Heroes 3: Final Stand on Steam — official persistent-upgrade and faction-progression description; checked 2026-08-13.
- Company of Heroes 3: Final Stand review by Patrik Severin — independent PC observation of between-run progression; checked 2026-08-13.