Company of Heroes 3: Final Stand uses faction-specific progression trees for persistent upgrades between runs. The official Steam listing establishes that system and identifies four playable factions: US Forces, Wehrmacht, British Forces, and Deutsches Afrikakorps. It does not publish a complete tree map, node names, prerequisites, effects, currency costs, rank limits, reset controls, or recommended order. The safe player workflow is to make a live lookup record from the faction screen, then connect an option only to a failure you have actually observed in a matching run.
Pick the faction before opening the tree
Start at the exact faction progression screen. Its label is the first field in your record, because a tree shown for one faction should not be assumed to exist for another. Then transcribe only what the current client makes clear: a node or perk name, a visible requirement, displayed level, path relation, and the date. If an icon has no accessible text or a value is unclear, leave the field unknown rather than assigning it a guessed effect.
This turns the screen into a useful database without pretending it is static. Keep the record local to Final Stand’s Steam AppID 4836540 and the current Windows client. A Company of Heroes 3 AppID 1677280 doctrine, DLC screen, or balance guide may use similar vocabulary, but it describes a different product scope and cannot fill an undocumented Final Stand node.
Build an honest screen inventory
Read the tree in a consistent order that matches its visible arrangement: start node, connected choice, and any prerequisite the client reveals. A simple entry can contain the faction, displayed node name, visible connection, requirement, and whether the item remains visible between runs. Do not turn the entry into an index of inferred bonuses. The goal is to make an available decision easy to find, not to create a fake detailed tree from labels alone.
If the client changes the arrangement after an update, preserve the old check date and make a new record. The independent Gamereactor PC review reported that the mode’s faction progression had persistent elements and that its reviewer saw multiple upgrade levels. That supports the value of looking at the screen, but it does not prove every current node, connection, or level for each faction. Treat review detail as a dated observation, never as a substitute for the displayed tree.
Connect a tree choice to a specific run question
Open a progression tree after writing the failure from a completed run. Was the defense short on time at one route, unable to cover two demands, or unable to recover after a first breach? Read the available node wording and decide whether it is clearly relevant to that question. Then change as little else as possible on the next attempt. The next run is where a player can check whether the decision affected the observed problem.
This method avoids a deceptive tier list. An upgrade that helps a new condition may not be the right choice for the one you recorded, and a random post-wave offer can alter the run independently. Steam confirms those within-run choices persist only for the run, so list them beside the wave rather than inside the progression-tree record.
Screen record
Capture the current faction, exact node text, visible path, requirement, and date.
Run record
Capture the first unstable route, wave, difficulty, and temporary choice separately.
Test record
Repeat a narrow question before saying the tree choice changed a final outcome.
Watch for version and context changes
Final Stand is a released Steam product with no public semantic version label on the Store information checked for this page. Do not present a SteamDB change number, a review date, or a community screenshot as the game’s public version. If the client displays a branch or version, write it beside the screen record. If not, retain the check date and the official source URL.
Dynamic events, boss units, five battlegrounds, eight difficulty levels, solo play, and two-player co-op can all change the context of a run. The official product page confirms their broad existence, not their exact interaction with a faction node. Record events by their current on-screen name and do not publish a counter or a fixed unlock relationship without stronger evidence.
Choose a useful next lookup
After recording one tree, move to the page that answers the next question rather than duplicating it. Use Persistent Upgrades to separate long-term choices from temporary offers, Battlegroup Guide for the in-run loop, and the individual Factions pages for faction-specific field notes. The missing official data here is not an invitation to invent; it is a checklist for future versioned observation.
This page intentionally has no universal tree diagram or “best route”. A future diagram should be built only from a current, attributable Final Stand source or repeatable live client capture, with exact faction and version boundaries recorded for each node.
Sources
- Company of Heroes 3: Final Stand on Steam — official faction-specific progression and product scope; checked 2026-08-13.
- Company of Heroes 3: Final Stand review by Patrik Severin — independent PC observation of persistent faction progression; checked 2026-08-13.