Stop Counting Squares: The Zone Trick That Keeps Combat Moving Without Losing the Tactics

Stop Counting Squares: The Zone Trick That Keeps Combat Moving Without Losing the Tactics

A middle-ground technique for running combat when a full battle grid is overkill but pure theater of the mind starts losing the tactics — plus a concrete way to run it at your next session.

Here's the fight that made me rethink my whole approach: six PCs, a collapsing bridge, and a pack of kobolds with slings on the far bank. I pulled out the grid map because "ranged combat" screamed grid to me, and then spent the next twenty minutes converting every "I want to close the distance" into square-by-square movement math while four players checked their phones. The fight itself was great. Getting there was not.

I'd been running everything as either full grid or pure theater of the mind, like those were the only two settings on the dial. Grid gives you precision — reach, cover, exact range — but it costs setup time and turns movement into an accounting exercise. Theater of the mind is fast and cinematic, but the second a player asks "can I reach him from here," you're eyeballing it, and eyeballing it inconsistently is how you end up arguing about whether a hasted rogue can cross forty feet of open ground.

Zones split the difference, and once I started using them I stopped reaching for the grid unless the fight actually needed it.

Here's how it works. Instead of a battle map, you carve the scene into a handful of loose areas — the bridge, the far bank, the collapsed section, the riverbank below — and describe roughly what's in each one. You don't need minis or a poster map, just index cards, sticky notes, or honestly just naming them out loud and keeping track on a scrap of paper. Most PCs move about 30 feet a turn, which conveniently lines up with "cross one zone" for most reasonable zone sizes, so a normal move gets you to an adjacent zone, and a Dash gets you two. Ranged attacks work fine within a zone or into an adjacent one; anything farther needs a real reason and probably disadvantage.

The trick that makes this actually playable is being upfront about the conversion the moment someone asks. When my rogue asked if she could reach the kobolds from the bridge, I didn't measure anything — I just said "they're one zone over, so you'd need to Dash or use a ranged attack this turn," and she made her call in about two seconds. That's the whole value proposition: questions get answered fast enough that combat doesn't stall out on logistics, but there's still a real spatial answer instead of DM vibes.

Where this actually breaks down is dense tactical fights — anything with reach weapons mattering foot-by-foot, opportunity attacks along a precise path, or a boss with an aura that cares about exact range. That's when I still pull out the grid, because zones get mushy exactly where grid combat earns its keep. The reverse is also true: chase scenes, skirmishes with lots of open ground, or fights where the terrain itself is the interesting part (that collapsing bridge) run better in zones than they ever did on a 5-foot grid.

One thing I got wrong early on: don't let zones become invisible. Players need to see the boundaries as clearly as they'd see grid lines, or "which zone am I in" turns into its own argument. Cards on the table, a quick sketch, or just narrating positions every time someone's turn comes up all work — the format matters less than making sure everyone's tracking the same mental map you are.

If you're already running combat on something grid-aware — I use Virtual Combat Simulator for anything that needs real reach checks and token tracking — you don't have to pick one system forever. I'll drop into a loose zone map for a chase or an ambush and switch back to the full grid the moment somebody pulls out a reach weapon or a fight gets dense enough that "which zone" stops being a good enough answer. The tool should bend to the fight, not the other way around.

Try it on your next fight that doesn't need foot-by-foot precision — a chase, an ambush, anything with more open ground than choke points — and see how much faster your table gets through it. I'd genuinely like to know if this holds up for horror or stealth-heavy games too, where exact positioning usually matters more. Drop your results in the comments, good or bad.

Comments (0)

More from the Blog

Ready to create something?

Subscribe to an individual app or get the full GameMaster Studio.