US Forces is one of the four playable factions named on the official Company of Heroes 3: Final Stand Steam page. That is the durable public fact this page starts from. The product page also confirms that each faction has a progression tree and that runs include randomized unit or ability choices after waves. It does not publish a Final Stand US Forces roster, starting units, costs, doctrine, tech-tree node list, or a best-build ranking. The parent Company of Heroes 3 product is a separate AppID, so its familiar unit guides are not safe substitutes for this standalone mode.
Begin with the displayed US Forces state
Select US Forces in the current client and make a short field record before wave one. Include the exact faction label, displayed difficulty, map label if shown, and anything the starting interface names. This is not busywork. It gives a later run a way to distinguish a change in the game from a change in memory. If a starting unit, ability, resource, or menu is not visibly confirmed, leave it out of the record.
Choose one observation goal. You might track the first approach that demands an answer, the moment a defensive layer stops buying time, or the result of one post-wave offer. Do not begin by trying to prove that US Forces should use a particular opening. Final Stand’s Store page establishes the wave-defense loop; it does not validate a fixed opener or a parent-game tactical prescription for this faction.
Read a post-wave offer as a response, not a label
Steam says that players choose between randomized units or abilities after waves and that the chosen option persists for that run. When a US Forces offer appears, first name the problem from the preceding wave. Was a route ignored too long? Did the objective become exposed? Was there no fallback after a breach? Then record the offer’s exact name and what you expect it to change on the next relevant wave.
This turns a choice into a test. If the following pressure point is easier to cover, the result is useful for that faction, difficulty, map, and run. If it is not, the note still says what was attempted. Avoid calling an option a mandatory US Forces pick after one run. The public sources do not establish its rarity, availability, numerical effect, or interaction with every map and difficulty.
Keep between-run progression on its own page
The official description confirms faction-specific progression trees with persistent upgrades between runs. Use the current US Forces progression screen to record only what it displays: exact node or perk name, visible requirement, level, and date. A persistent element belongs in the between-run record; a randomized choice belongs in the current-run record. Mixing those two systems produces misleading advice even before a patch changes them.
If the client exposes a prerequisite or says an upgrade is unavailable, copy that text rather than guessing a grind route. The Gamereactor PC review observed long-term faction progression but did not publish a verified US Forces node catalogue. It can support the existence of a progression loop, not an unlisted unlock path. Recheck the actual client after each update.
Current-run note
Save the exact post-wave choice, wave, and defensive problem it was meant to solve.
Persistent note
Save the US Forces progression-screen wording separately, including any visible requirement.
Comparison note
Change one condition between attempts so a result remains understandable rather than anecdotal.
Evaluate a line by what it protects
The useful US Forces question is not “which name is strongest?” It is “what part of the current field did this choice protect?” Start with the protected objective, then identify the first route that forces a late rotation. A response can be judged by whether it buys time, retains coverage, or creates a place to recover after the outer defense gives way. These are observations a player can make without claiming unpublished damage values, target priorities, or unit counters.
Bosses and dynamic events can change a run. Steam confirms their existence and counts, but not a US Forces-specific counter list. When one appears, write the exact name if visible and the defensive symptom it created. Do not transform a memorable answer into a fixed faction guide until it is repeatable and scoped to the current product version.
Avoid the wrong product boundary
Company of Heroes 3 uses AppID 1677280. Its campaigns, multiplayer balance, DLC, patch notes, factions, and unit stats do not automatically apply to Final Stand. A Store bundle that includes both products is a commercial offer, not evidence that their rules are shared. This page also makes no claim about Steam Deck, Linux, controller mappings, or co-op resource rules because those are not confirmed by the public Final Stand sources used here.
Continue with Faction Overview to compare the confirmed roster, Wave Defense to frame an in-run response, and Faction Progression Trees to keep long-term state readable. The next reliable US Forces guide improvement should come from a named official source or repeatable, version-recorded live evidence, not inherited Company of Heroes advice.
Sources
- Company of Heroes 3: Final Stand on Steam — official faction roster, run choices, and faction progression; 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.