Let the easy fight live

Put one ordinary combat room in a design review and somebody will ask for the twist. Add a balcony, an armored enemy, a floor hazard, a timer, and a secondary objective. Now the encounter has earned its salary, apparently. Do this to every room and the game begins to feel like a meeting where each person arrived with a new agenda item.

A simple encounter is not unfinished design. It is the low note that lets the next complication register. Games need rooms where you recognize the situation, perform the skill you already learned, and win without being handed another system to keep in working memory.

This follows In defense of long hallways, which gave quiet traversal a job between action peaks. The same pacing problem exists inside combat. Bullets can still be moving while the encounter gives the player a lower, clearer demand.

The review asks for another problem#

“Never one problem” sounds like a useful rule because it catches rooms where the player repeats a solved input without reading anything new. Then the rule escapes its enclosure. Every pack needs mixed ranges, every traversal needs a threat, and every puzzle needs a second constraint before the first one has had time to become legible.

Once a game has been judged shallow, its quieter encounters start serving as evidence for the verdict. Nisbett and Wilson's classic halo-effect experiment found that a global impression altered how people rated individual traits they had enough information to assess separately. Their study concerns a lecturer rather than a combat arena, so I am borrowing the mechanism cautiously. The review pattern is familiar anyway: “simple game” becomes “simple encounter,” and the encounter's actual job disappears from the conversation.

Ordinary encounters teach the verb#

Nintendo's designers describe building the fun, difficult courses first and then moving easier features toward the beginning when beginners could not use them. In the official New Super Mario Bros. Wii interview, World 1-1 appears late in development and receives adjustment until the end because it has to teach the world without a person standing beside the player.

That first Goomba poses one problem. Good. The player needs a clean reading of movement, collision, jump timing, and consequence before a later level combines those facts with moving platforms or a collapsing route. Complexity placed earlier would make the lesson harder to identify, while complexity placed later can ask whether the player understood it.

Combat uses the same grammar. Three familiar enemies on open ground can confirm that a new weapon works, give the player a stretch of competence after a difficult fight, or establish the normal behavior that a special enemy will violate. For fuck's sake, the player is allowed to solve the thing they learned. Mastery needs a place to become visible before the game changes the exam paper again.

Valve lowers the frequency#

Valve made this relationship executable in Left 4 Dead. Michael Booth's official AI Director presentation calls constant combat fatiguing and long inactivity boring, then uses build-up, a sustained peak, fade, and a relax period. During that relax state the Director maintains a minimal threat population for roughly half a minute before beginning another climb.

The closing observation in that presentation is easy to miss: the Director adjusts frequency rather than amplitude. Enemy difficulty remains available. The game changes how often full pressure arrives. A review that demands another problem from every encounter reaches for amplitude because amplitude is visible in a room diagram, while frequency only appears when several rooms are played in order.

Complexity behaves like suspense here. A blackout matters after you have learned what the lit room permits. Crossfire matters after a frontal fight establishes the safe-looking cover. If every encounter begins with flanking enemies, breakable floors, and a resource clock, the player may still succeed, but the later encounter has nowhere obvious to escalate except more simultaneous administration.

Spice still has to appear#

Some games really are too flat. When the same enemies arrive in the same geometry and ask for the same answer, an additional problem can wake the system up. The mistake is promoting that repair into a minimum standard for every room instead of deciding where the new demand changes the rhythm.

I cannot give you the correct ratio of plain fights to elaborate ones. Player skill, session length, control complexity, and genre move it around. I trust one test more than a slogan: remove the modifier from an encounter and ask what the simpler version contributes to the sequence. Keep it when the player gains recognition, recovery, confidence, or a baseline the next room intends to break.

On the encounter sheet, room twelve says three soldiers on an open floor. Room thirteen adds the balcony, and room fourteen cuts the lights halfway through. Delete room twelve and the balcony becomes setup work. Keep it, and the first shot from above changes how the player reads the whole room.