The Difference Between “Deep Combat” and “Delayed Competence”

“Deep combat” is one of the most overused phrases in game writing.

It usually means the systems are complicated, the move list is long, and the skill ceiling looks high on paper. What it often describes in practice is something else: delayed competence. The game withholds the tools, the clarity, or the feedback you need to play well, then calls the resulting struggle depth.

I draw a hard line between the two.

Deep combat gives you readable decisions early and then keeps adding meaningful layers. You understand what you are doing and why it works. New tools change how you approach the same problems. Mastery feels like the natural result of attention and practice, not the result of surviving an unnecessarily opaque tutorial period.

Delayed competence does the opposite. It fronts a kit that feels incomplete, muddy, or punishing, then slowly drips out the missing pieces. For the first five, eight, or twelve hours you are not learning a rich system. You are waiting for the system to become playable. The game treats your early frustration as evidence that the combat is sophisticated rather than evidence that the onboarding or the feedback loops are incomplete.

The difference shows up in a few reliable places.

Readability of cause and effect

In deep combat, you can usually tell why you won or lost a fight within a session or two. The signals are consistent. In delayed competence, outcomes feel noisy for a long time. You die and are not sure whether the problem was positioning, timing, build, or the game simply not having given you the right tool yet.

When the verbs arrive

Deep systems introduce core verbs early and then expand their use. Delayed competence holds back key verbs or upgrades so that early combat feels like a lesser version of the real game. The marketing calls the later version “when the combat opens up.” The player experiences it as “I was playing a weaker game for the first ten hours.”

Skill expression versus system endurance

Real depth rewards reading the situation and executing under pressure. Delayed competence often rewards simply enduring until the next unlock or the next power spike. The player who pushes through is not necessarily more skilled; they are more patient. Those are not the same trait.

How the game talks about its own difficulty

Games with deep combat tend to give you clean information and let the difficulty come from the decisions. Games built on delayed competence often obscure information, bury stats, or lean on long recovery animations and stiff early tuning, then point to the resulting struggle as proof of substance.

I am not against systems that take time to master. I am against systems that take time to stop feeling broken or incomplete. The first is depth. The second is a tax on the only resource many of us cannot refill: focused attention in short windows.

When I write System Breakdowns, this is one of the first distinctions I apply. I will tell you when a combat system is actually adding decisions over time and when it is simply rationing competence. The first earns the hours. The second spends them while asking you to be grateful for the eventual payoff.

A game doesn’t need to be perfect. It needs to earn the hours. If the combat only starts feeling good after you have already paid a long patience tax, it has not earned the early ones.