waywardstrategy.com

Wayward Strategy approaches Company of Heroes 3 faction design through two contributor articles by Felipe Eduardo Gonzalez Argañaras: one arguing that factions are built in "layers," and one tracing the Deutsches Afrika Korps (DAK) as a faction shaped across three games. Both are design analysis rather than news or reviews, and both are attributed to a contributor rather than to site founder Brandon "Wayward" Casteel. If you want a single-sentence answer: the site's angle is that CoH3 faction identity is a layered construction, and that the DAK is the clearest case of a faction whose identity accumulated over the series rather than being designed from scratch.

The two CoH3 faction articles on the site

The titles themselves carry the site's framing. "Layers" implies faction identity is assembled from multiple interacting systems rather than expressed through one signature mechanic. "Three games in the making" implies the DAK is not a fresh CoH3 invention but the endpoint of a longer design lineage.

What "layers" means as an analytical lens

The site's own description of its RTT/RTS article gives a sense of how it separates design concerns: it distinguishes games that emphasize "troop positioning and immediate engagements" from those emphasizing "economic growth and broader strategic planning." Applied to factions, that habit of separating concerns is what a layered reading looks like — faction identity is treated as the sum of several distinct design decisions, not a single trait.

For CoH3 specifically, the article title asserts that the game "builds" faction identities, which points to construction over inheritance. The excerpt does not enumerate the layers, so treat the specific layer list as something to read in the article itself rather than something the site summarizes elsewhere.

The DAK as the worked example

The DAK article is the concrete case study. Its framing — a faction "three games in the making" — suggests the analysis traces how the Afrika Korps concept evolved across earlier Company of Heroes titles before arriving in CoH3. That makes it the more useful of the two articles if you want a single faction examined in depth rather than a general framework.

Where this sits in the site's broader design writing

Wayward Strategy's CoH3 faction pieces are part of a wider design-analysis section that includes:

• "An Exploration and Definition of the Real-Time Tactics Game Genre" — the RTT vs. RTS distinction
• "Mind Control, Stun, and Fire, Oh My! A Discussion about Status Effects in Real Time Strategy Games"
• "RNG Discourse is a Disaster" — an argument to move past "RNG vs Skill" framing
• "Age of Sigmar: Realms of Ruin Beta impressions"
• A re-shared Tempest Rising interview

The through-line is design-space argument rather than review scoring. The RNG piece is explicit about this: it rejects the standard framing and proposes exploring the design space instead. Expect the same posture in the faction articles — analytical and occasionally critical, not a buyer's guide.

How to use these articles

Read "Factions have layers!" first if you want the general model for how CoH3 faction identity is assembled. Read the DAK piece second if you want that model applied to one faction with a multi-game history. Both are by the same contributor, so the two read as a pair rather than as independent takes.

Two caveats worth stating plainly:

• The site's excerpt does not reproduce the actual layer breakdown or the DAK's specific mechanics. The titles and framing are what the page evidence supports; the substance is in the articles.
• Attribution matters here. These are contributor articles by Felipe Eduardo Gonzalez Argañaras, distinct from Casteel's own writing on RTT/RTS definition and historical RTS. If you are citing "Wayward Strategy's view," cite the contributor.

The site also signals subscription options ("subscribe," "subscription" appear in its pricing signals), but the page evidence does not state what is gated versus free, so check the article pages directly before assuming access.

Wayward Strategy is an English-language games criticism and design analysis site focused on real-time strategy (RTS) and real-time tactics (RTT) games. It publishes long-form articles, faction and design breakdowns, beta impressions, interviews, and video content, written primarily by Brandon "Wayward" Casteel with additional contributors. If you want design-level discussion of games like Company of Heroes, Command & Conquer-style titles, or historical RTS, this is the kind of site to read; if you need news, patch notes, or a general gaming database, it is not that.

What the site covers

The published work clusters around a few recurring subjects:

• Genre definition and theory — for example, an article distinguishing RTT from RTS, arguing that RTT centers on troop positioning and immediate engagements while RTS emphasizes economic growth and broader strategic planning. It uses games such as Wargame and World in Conflict as illustrations and asks what RTS can learn from RTT.
• Faction design — pieces on how Company of Heroes 3 builds faction identities, including a dedicated article on the Deutsches Afrika Korps faction.
• Systems and mechanics — a discussion of status effects (mind control, stun, fire) in real-time strategy games, and a piece arguing that "RNG vs Skill" framing limits design discussion.
• Impressions and interviews — beta impressions of Age of Sigmar: Realms of Ruin, a re-shared Tempest Rising interview, and a historical RTS overview of War Wind.
• Video and commentary — including a piece titled "The RTS Masterminds Are Back!"

Who writes it

Brandon "Wayward" Casteel is the main author and the name behind the site. Other contributors also publish there, such as Felipe Eduardo Gonzalez Argañaras (Company of Heroes faction articles) and Johaggis (the RNG design piece). Articles carry both author names and publication dates.

How to use it

• If you are studying RTS/RTT design, start with the RTT-vs-RTS definition article and the status-effects discussion; they are the most conceptual entries.
• If you follow Company of Heroes 3, the faction-identity and Afrika Korps articles are the relevant cluster.
• If you want broader genre context, the historical RTS piece on War Wind and the Tempest Rising interview cover older and upcoming titles respectively.
• If you prefer watching over reading, the site also lists video content.

What to expect and what not to

Expect opinionated, design-oriented writing with named authors and dates, organized into categories such as Games, Game Design, Contributors, Overviews, Technology, and Videos. The site's own navigation shows pagination ("Older posts"), so the archive extends beyond the front page.

The available site information does not specify a publication schedule, editorial policy, or full staff list, and it does not state whether any content sits behind a subscription. Terms like "subscribe" and "subscription" appear as signals on the site, but no pricing links or payment platforms are listed in the material reviewed here, so treat access terms as unconfirmed and check the site directly before assuming anything is free or gated.

Wayward Strategy argues that the usual "RNG vs. skill" framing is a dead end. In the article "RNG Discourse is a Disaster," contributor Johaggis writes that RNG discussions "suck" precisely because they get stuck in that binary, and proposes stepping away from it to "explore the design space" instead. So the site's position is not that randomness is good or bad, but that the question itself is usually asked the wrong way.

The core argument: stop asking "RNG or skill?"

The article's title and framing make the stance explicit. Rather than treating randomness and player skill as opposing forces to be weighed against each other, Wayward Strategy treats randomness as one design tool among many. The productive question is not how much randomness exists, but what kind of randomness, where it sits in the decision chain, and what it does to the player's experience.

This matters because "RNG vs. skill" collapses very different mechanics into one bucket. A damage roll, a spawn location, a fog-of-war reveal, and a matchmaking draw are all "random," but they affect skill expression in completely different ways.

What the "RNG vs. skill" framing gets wrong

The site's critique implies several recurring problems with how players and designers talk about randomness:

• It treats randomness as a single quantity. Two games with "the same amount" of RNG can feel completely different depending on when and how it applies.
• It assumes skill and randomness are zero-sum. In practice, randomness can create skill expression (adapting to an unexpected situation) rather than only diluting it.
• It skips the design intent. Whether a random element is acceptable depends on what the designer wanted it to accomplish — tension, replayability, comeback potential, or something else.
• It produces heat, not light. Framing the debate as a fight makes it hard to reach useful conclusions, which is why the article calls the discourse a "disaster."

A more useful way to think about it

Wayward Strategy's suggested move — "explore the design space" — points toward asking concrete design questions instead of taking sides. Useful angles include:

For players, this reframes complaints: instead of "this game has too much RNG," the sharper question is "which random elements can I actually play around, and which ones just decide outcomes for me?" For designers, it means treating randomness as something to place deliberately rather than something to minimize or maximize.

Where this fits in the site's broader coverage

The RNG article sits alongside Wayward Strategy's other design-focused writing, including its exploration of Real-Time Tactics versus Real-Time Strategy and its breakdowns of Company of Heroes 3 faction identity. The through-line is design analysis: the site tends to examine how mechanics shape play rather than ranking games or settling fan arguments. The RNG piece follows that pattern — it is less a verdict on randomness than a call to argue about it more precisely.

Wayward Strategy treats status effects—mind control, stun, fire, and similar mechanics—as a core design lens for real-time strategy games, not just a list of abilities. The site's article "Mind Control, Stun, and Fire, Oh My! A Discussion about Status Effects in Real Time Strategy Games" sits alongside its broader writing on RTT vs. RTS, faction identity, and randomness, which together frame status effects as a question of how much control a player actually has over their units. If you want to understand the site's position, the useful move is to read that status-effect piece together with its RTT/RTS definition and its RNG discussion, because the three overlap.

The core distinction the site draws

Wayward Strategy's RTT/RTS article separates the genres by where player attention goes:

• Real-Time Tactics (RTT) centers on troop positioning and immediate engagements—examples the site cites include Wargame and World in Conflict.
• Real-Time Strategy (RTS) emphasizes economic growth and broader strategic planning.

That split matters for status effects. In an RTT, a stun or mind-control effect lands inside an engagement you are already micromanaging, so its cost is measured in seconds of positioning. In an RTS, the same effect competes with economy and production decisions, so its cost is measured in attention and tempo across a wider map. The site's framing suggests status effects are not inherently "good" or "bad" design—their value depends on which layer of the game they interrupt.

Why mind control, stun, and fire are different problems

The article groups these three because they remove player agency in different ways:

The through-line is agency. A stun that lasts long enough removes the player from the fight; a fire effect that ticks slowly gives them time to react. Mind control is the sharpest case because it flips the unit's allegiance, which changes both the tactical math and the emotional read of the engagement.

How this connects to the site's RNG argument

Wayward Strategy's "RNG Discourse is a Disaster" post argues for moving past the framing of "RNG vs. skill" and exploring the design space instead. Status effects are a close cousin of that argument. A stun with a random duration, or a fire effect with a random tick, is an RNG question wearing a different hat. The site's consistent position is that the interesting question is not whether randomness or control-removal exists, but what it does to the decisions available to the player. That is why the status-effect discussion belongs with the RNG piece rather than standing alone.

What the site does not claim

The available page evidence shows the article exists and is grouped under Games, but it does not include the full text, specific game comparisons, or a stated verdict on which implementations work best. So the honest summary is: Wayward Strategy opens the topic as a design discussion and ties it to its wider writing on genre definition and randomness, but the detailed per-game analysis is in the article itself, not in the site's summary. If you want the specific examples and conclusions, read the piece directly.

How to use this if you are designing or studying RTS

A practical way to apply the site's framing:

1. Identify which layer your game prioritizes—tactical positioning or economic planning.
2. For each status effect, ask what the player loses: a unit, time, or predictability.
3. Check whether the player has a response window. If not, the effect is closer to a cutscene than a mechanic.
4. Treat random durations or ticks as an RNG design choice, and evaluate them the same way the site evaluates RNG generally—by what decisions remain.

That sequence turns the site's discussion into a checklist rather than a verdict, which matches how Wayward Strategy tends to approach these topics.

Wayward Strategy draws the line between RTT and RTS at where the player's attention and decisions are concentrated. In its article "An Exploration and Definition of the Real-Time Tactics Game Genre," the site argues that Real-Time Tactics focuses primarily on troop positioning and immediate engagements, while Real-Time Strategy emphasizes economic growth and broader strategic planning. That distinction is the site's working definition, and it uses games like Wargame and World in Conflict as RTT examples to show how the two design priorities produce different play experiences.

The core distinction

Wayward Strategy frames the split as a question of what the game asks you to manage in real time:

• RTT (Real-Time Tactics): the primary challenge is where your units are, what they can see, and how an engagement resolves once contact happens. Positioning and timing of individual fights carry the weight.
• RTS (Real-Time Strategy): the primary challenge is building and sustaining an economy while converting that economic advantage into military pressure. Broader planning across the match matters more than any single engagement.

This is a matter of emphasis, not a hard binary. The site's point is that games cluster around one priority or the other, and that clustering shapes everything from unit design to match length.

What the RTT examples show

Wayward Strategy cites Wargame and World in Conflict to illustrate the RTT side. In both, the article's framing suggests the interesting decisions are tactical: how you array forces, what terrain or line of sight you exploit, and how a specific engagement unfolds. Economic management is either absent or heavily abstracted, so the player's real-time attention stays on the battlefield rather than on a base or production queue.

That contrasts with the Command & Conquer-style lineage the site also covers, where expansion, income, and production are live concerns running alongside combat.

What RTS might borrow from RTT

Beyond defining the genres, the article discusses potential lessons RTS could take from RTT design. The implication is that RTS games can lose clarity when economic and strategic layers crowd out the tactical decision-making that makes individual engagements readable. RTT's tighter focus offers a model for making positioning and engagement outcomes matter more legibly.

Which one you might prefer

The useful takeaway is to look at where a game puts its real-time pressure. If most of your attention goes to unit placement and the resolution of contact, you are playing something closer to Wayward Strategy's RTT definition; if it goes to economy and long-range planning, it sits on the RTS side.