Company of Heroes 3: Final Stand Defense

Defense in Company of Heroes 3: Final Stand starts with an honest boundary: Steam confirms the purpose of the mode, not a public spreadsheet of every wave. The official description says that you build layered defenses and survive 12 escalating waves, with boss units and dynamic battlefield events. It also offers Endless Mode after the standard run. That is enough to plan a useful defense process: protect the objective, notice which approach becomes dangerous, and pick a next-wave option for a visible weakness rather than for an unverified ranking.

This hub is for players who need a structure for reading pressure. It does not replace a map walkthrough, because the official Store confirms five battlegrounds but does not publish a complete named map list, route diagram, event trigger list, or boss catalogue. The goal is to turn the information visible in your current match into a repeatable decision, then keep any map-specific claim tied to the version and layout where you observed it.

Start from the asset that ends the run

Before you assign a unit, locate the objective whose loss ends the attempt. A released-game review described a base that attackers try to destroy and defensive bunkers on approach routes. That observation can help you look for the right information in the current match, but it is not a guarantee that every battlefield presents the same geometry. The client, not an old screenshot, is the authority for the object you must defend and the lanes that feed it.

Once you know the objective, identify the first place where an attack can be delayed or split. A layered defense is useful only if each layer has a job. One layer might buy time, another might maintain coverage on an approach, and another might protect the point that cannot be abandoned. Do not pile every asset at the outermost contact point merely because it is where combat first appears. If that line is breached, a second readable decision point is more valuable than a perfect-looking but single-use wall.

The public material does not name the available defenses, costs, repair rules, or exact lane mechanics. Read the unit cards and construction menus in the current run before describing one as mandatory. A sound page can tell you how to evaluate a layer without pretending that every faction receives the same tools.

Turn wave breaks into useful decisions

The interval after a wave is the moment where Final Stand becomes more than a real-time firefight. Steam says randomized units or abilities can be chosen after each wave and that these choices persist for the duration of the run. Use that pause to decide which pressure was real, not which option has the most impressive title.

Ask three concrete questions. First, did the previous wave reach the objective or merely force you to move? Second, did the defense fail because a route had no coverage, because the response arrived too slowly, or because the plan could not sustain itself? Third, can the offered option solve that exact failure before the next wave starts? If the answer is vague, choose the option whose purpose you can observe immediately and note what changes.

Read events as changes to the battlefield, not as lore

Steam confirms 18 dynamic in-game events. The useful immediate response is to identify what changed on the current field: an approach, a timing window, a priority target, a defensive asset, or the information available to you. Give the event its exact in-game label in your own notes when visible. Do not assign it a community name, an unseen probability, or a permanent rule from one run.

An event can make a normally stable plan unsafe without making the entire faction or difficulty choice wrong. Treat it as a reason to preserve a recovery layer. If your response depends on moving every unit away from the objective, the plan is fragile. If it leaves an approach uncovered, decide whether the new threat or the old route is more urgent; the right answer can differ by map and current option pool.

For a guide update, a useful event report includes the date, AppID, difficulty, visible name, map name if displayed, what changed, and what the player did next. That is enough to turn a later observation into a testable note. It is not enough to publish a universal trigger table, and it should never be inflated into one.

Treat boss waves as a planning test

The official page states that Final Stand has 36 boss units with special abilities and rewards. It does not disclose their names, spawn schedule, abilities, health values, or rewards. A defense plan should therefore prepare for the category of problem rather than a fictional roster. Keep an answer for concentrated pressure, preserve a route back to the objective, and enter a major wave with enough information to see whether the threat changes the lane, the target priority, or the time you have to react.

When a boss appears, avoid claiming that a single successful response is a strategy. Note the visible action, the position it threatened, and the resource or defensive layer it forced you to spend. If a new ability appears, record its on-screen wording and current version context. This is especially important for co-op: both players should agree on which responsibility remains covered while the other reacts to the major threat.

The absence of a public boss list is not a reason to write empty advice. You can still ask whether your line can absorb a sudden priority change, whether a fallback position exists, and whether your current choice pool has been tested under pressure. Those questions remain useful without inventing enemy behavior.

Use Endless Mode only after you can diagnose a normal run

Endless Mode is a verified mode, but the Store page does not explain its requirements, progression, failure condition, or reward structure. Use it as a longer diagnostic instead of assuming it is the “real” endgame route. A 12-wave run gives a bounded comparison: same faction, same difficulty, one deliberate change, and a clear point where the plan succeeded or failed. Endless is more valuable once that baseline is readable.

Bring a question into an Endless attempt: can the second layer still operate when the outer line is lost, can the current run choices continue to cover the same approach, or does the team need a different division of attention? Stop treating results as comparable when a new event, map layout, or unrecorded option changes the premise. Long survival can be satisfying, but it is poor evidence for a “best” label without context.

Do not infer rankings, scaling formulas, wave caps, or unlocks from the word “Endless.” If the client provides a score, reward, or progression screen, capture its exact wording and date before expanding a guide. Until then, the reliable answer is simply that the mode exists and is intended as the ultimate challenge after the 12 escalating waves.

Build a field note that another player can use

At the end of a defense attempt, write a compact field note: faction, difficulty, map name if shown, selected run choices, the first wave that created an unstable route, and whether an event or boss changed the plan. Add one sentence about the decision you would test next. This produces a guide contribution that another player can reproduce without assuming the same faction unlocks or map position.

If you share a clip, identify it as a current observation rather than evidence of a permanent rule. A useful clip shows the route, the protected objective, the choice immediately before the problem, and the moment the plan changes. A dramatic final kill does not explain the defense.

For targeted pages, continue with the Wave Defense Guide. Endless Mode and Dynamic Events receive separate pages because their questions are different: one is about a long-form mode and the other is about a changing battlefield condition. Boss names and map lists remain deferred until reliable current evidence exists.

Sources

• Company of Heroes 3: Final Stand on Steam — official 12 waves, Endless Mode, dynamic events, boss count, factions, and progression wording; checked 2026-08-13.
• GameReactor review by Patrik Severin — independent released-game observation about base, routes, and bunkers; published 2026-07-30, checked 2026-08-13.