Company of Heroes 3: Final Stand has eight difficulty levels, according to the official Steam listing. That is enough to make difficulty a useful experiment setting; it is not enough to publish a modifier table, a reward chart, a recommended order, or a claim about which level a particular faction should play. The visible client is the source for current names and rules. Treat difficulty as a way to hold conditions steady while you learn a decision, then raise it only when you can explain the previous run.
Start from the level the client displays
Open the difficulty selector and write down the exact label shown there. Steam describes a range from newcomer to veteran but does not provide the full label list, numerical modifiers, unlock order, or completion rewards. Those missing details matter: a guide cannot safely replace them with older Company of Heroes settings or an unverified screenshot. If a setting is locked or has a tooltip, read its current text before making a plan around it.
Use the first selected level as a baseline. Pick a faction and one question about the defense, such as whether a particular approach becomes difficult to cover or whether a between-wave choice provides a visible answer. Keep the map display, faction, and goal in your notes. A baseline is valuable because it lets you identify a changed condition instead of treating every loss as proof that the setting is wrong.
Raise the test only after you can name the failure
Do not increase difficulty simply because a run ended early. First identify the first unstable moment: which wave changed the defense, which route forced a rotation, and whether the problem was time, coverage, or loss of a fallback. Then decide whether a new setting would test that same problem or hide it behind several new variables. A higher level is useful only if you can observe how the same decision behaves under the new pressure.
Run a short comparison with one change. Keep the faction and goal, choose the next displayed setting, and record the first wave where the field differs. If an event appears, include its exact on-screen name instead of assuming it is part of the difficulty rule. Final Stand has confirmed dynamic events and boss units, but the Store listing does not connect a named event or boss to a particular level.
Separate difficulty from progression
Final Stand has faction-specific progression trees and persistent upgrades between runs. That means two attempts at the same displayed difficulty can still start from different long-term states. Before calling one setting too easy or too hard, record whether the faction progression screen shows a different persistent state than during your last comparison. The official product page establishes that persistent upgrades exist; the current client must establish their exact effects and requirements.
The same caution applies to within-run choices. Steam says randomized units or abilities can be chosen after waves and persist for the current run. A result may reflect the chosen response, not an intrinsic difficulty threshold. Save the option’s exact name and the wave where it was taken. If you cannot repeat the option, do not use a single run as a universal ranking.
Same setting, different run
Compare progression state and post-wave choices before blaming the difficulty label.
Next setting, same goal
Change only the displayed level when the previous failure is clearly described.
New event or boss
Log the on-screen name and wave; do not infer a hidden difficulty rule from one encounter.
Use co-op as a separate condition
Final Stand supports solo play and online two-player co-op. Player count is a separate condition from difficulty. Do not claim that a specific level becomes easier, has more rewards, or changes enemy rules in co-op unless the live client or an attributable official source confirms it. A duo can still use the same observation method: one player records the earliest pressure point while the other records the displayed setting and post-wave choice.
If the lobby exposes additional difficulty-related controls, capture their exact wording and date. This site’s published scope is Steam Windows PC AppID 4836540; it does not assume console, Steam Deck, Proton, controller, cross-play, or parent-game behavior. Keeping the context with the observation makes a later update useful instead of misleading.
Finish with a repeatable next run
After a run, write five items: displayed difficulty, faction, first unstable wave, first unstable route, and one post-wave selection that you tested. That short record makes it possible to choose whether to repeat, simplify, or move to the next available level. It also reveals when the right next step is not a harder setting but a clearer defensive question.
For the actual wave loop, read the Wave Defense Guide. For run choices and long-term state, continue to Progression. Recheck the official Store page after a patch or update before treating this page’s version boundary as current.
Sources
- Company of Heroes 3: Final Stand on Steam — official eight-level count and product scope; checked 2026-08-13.
- Company of Heroes 3: Final Stand review by Patrik Severin — independent PC review observing the published level range; checked 2026-08-13.