How to Run Vertical Combat: Climbing, Falling, and Flying on Tactical Maps

The dragon is forty feet above the courtyard. The fighter is standing on a fifteen-foot balcony. The rogue is climbing a tower wall. The wizard is thirty feet back from the balcony and wants to know whether a sixty-foot spell can reach the dragon.

Everyone looks at the battle map.

The map shows a courtyard.

This is where vertical combat starts to fall apart at a lot of tables. The rules can handle climbing, falling, jumping, and flying. The problem is that most tactical maps are flat. The moment creatures occupy different heights, the DM is suddenly tracking a second battlefield that exists entirely in notes and memory.

The solution is not to turn every encounter into a three-dimensional geometry exercise. It is to make elevation visible, use a few consistent markers, and build maps where vertical movement creates obvious choices. Once players can tell who is above them, how high that ledge is, and what it costs to reach it, vertical combat becomes much easier to run.

What makes vertical combat difficult on a flat battle map?

A normal square grid answers two questions immediately: where is the creature, and how far is it from another creature?

Elevation adds a third coordinate.

Two tokens can occupy what appears to be the same part of the map while actually being thirty feet apart vertically. A monster can stand directly beneath a flying character. A bridge can pass over a lower hallway. A character on a rooftop can be only ten horizontal feet from an enemy but forty feet above them.

That means the map needs to communicate more than horizontal position.

You do not need to label every three-foot step or decorative slope. Track the elevation changes that alter movement, range, cover, line of sight, or fall danger.

How does climbing work during D&D combat?

Under the current fifth-edition Climbing rule, each foot of movement while climbing costs one additional foot. In practical terms, a creature without a Climb Speed normally spends 10 feet of movement to climb 5 vertical feet.

A character with 30 feet of Speed can therefore normally climb about 15 feet before exhausting that movement.

If the climbing surface is also Difficult Terrain, the cost becomes even steeper. Current rules state that each foot of climbing in Difficult Terrain costs two additional feet.

A creature with a Climb Speed can use that special speed to move vertically without paying the normal extra climbing cost.

Do you roll Athletics every time someone climbs?

No. Ordinary climbing does not automatically require an ability check.

The current rules let the DM call for a DC 15 Strength (Athletics) check when the surface is slippery or offers few handholds. That distinction is useful for encounter design.

A stone staircase does not need a check. A normal ladder probably does not need a check. A rough dungeon wall with obvious handholds might simply cost additional movement.

A rain-covered cliff face during a storm is different.

Use climbing checks when failure is genuinely possible, not every time a character moves vertically.

How should ladders, ropes, and climbable walls appear on the map?

Show the route clearly before combat begins.

If a balcony is twenty feet above the main floor, players should be able to look at the map and identify the staircase, ladder, rope, broken wall, or other way to reach it.

This creates an important tactical difference between height and access.

A twenty-foot platform with stairs is relatively easy to reach. The same platform with a vertical rope requires much more movement. Remove the rope entirely and climbing the actual wall might involve an Athletics check.

The destination is identical. The route changes the fight.

How much damage does falling deal?

Current fifth-edition rules keep falling damage straightforward. A falling creature takes 1d6 Bludgeoning damage for every 10 feet it falls, up to a maximum of 20d6.

If the fall deals any damage, the creature also lands Prone.

This makes even moderate elevation tactically important. A twenty-foot balcony is not automatically lethal, but 2d6 damage plus landing Prone can completely change a turn.

That is enough consequence to make ledges matter without turning every rooftop into an instant-death zone.

What happens when someone falls into water?

Current rules give a falling creature a chance to reduce damage when falling into water or another liquid. The creature can use its Reaction to attempt a DC 15 Strength (Athletics) or Dexterity (Acrobatics) check to enter the liquid effectively. On a success, the fall damage is halved.

That makes cliffs above water tactically different from cliffs above stone even when the drop is identical.

How do you make falling matter without constantly pushing characters off cliffs?

Make the threat visible first.

A narrow bridge over a pit creates tension before anyone falls. A crumbling balcony matters because players know the edge exists. A fight on rooftop walkways changes positioning because every square near the boundary has consequences.

The most interesting version lets both sides exploit that danger.

Put an enemy beside the ledge. Give the ogre a reason to charge onto the bridge. Let the party cut a rope, collapse a walkway, shove an enemy from a platform, or retreat up a ladder before destroying it.

Once players realize elevation is usable, not just dangerous, vertical details become part of their planning.

That same philosophy applies to other dungeon terrain. Our Black Lantern Forge battle map collection is built around encounter spaces where terrain and positioning can influence what happens instead of serving as background decoration.

How does flying work in tactical combat?

A creature with a Fly Speed can use that speed to move through the air. The challenge for the map is simply recording how high the creature currently is.

Do not move the token to a random empty part of the map because it is flying. Keep it above its actual horizontal position and mark the altitude separately.

A token standing over square G12 at forty feet of altitude should still be represented over G12. Add a visible "+40" marker, token ring, die, counter, status value, or VTT elevation field to show the third coordinate.

Do flying creatures automatically stay in the air?

Usually, as long as they retain their ability to fly.

Under the current Flying rule, a flying creature falls if it becomes Incapacitated, gains the Prone condition, or has its Fly Speed reduced to 0.

Hover changes that. A creature capable of hovering can remain aloft in those circumstances.

That creates a tactical weakness that is easy to forget when flying is treated as nothing more than extra movement.

The dangerous part of flying is not getting into the air. It is what happens when something takes your ability to stay there away.

How do walking and flying speeds interact in the same turn?

Creatures can switch between different movement speeds during a move, but switching does not give them a completely fresh movement pool.

Current rules tell you to subtract the distance already moved from the new speed.

For example, assume a creature has a Speed of 30 feet and a Fly Speed of 40 feet.

It could fly 10 feet, walk 10 feet, and then use the remaining portion of its Fly Speed to fly another 20 feet. It does not get 30 feet of walking plus another full 40 feet of flight just because it switched movement modes.

That matters on maps with towers, rooftops, pits, balconies, and flying mounts because characters may change movement mode several times in one turn.

How should you handle range when creatures are at different heights?

Do not hide the vertical distance from the players.

If a creature is forty feet in the air, that forty feet is part of the tactical relationship between the attacker and target. The exact method your table or VTT uses to resolve diagonal three-dimensional distance should remain consistent throughout the encounter.

The cleanest practical approach is to track horizontal grid position and elevation separately, then use the same measurement convention every time a ranged attack, spell, aura, or movement effect crosses both.

Do not switch between precise geometric measurement for one spell and simplified grid counting for the next because one answer happens to be more convenient.

Consistency matters more than squeezing perfect real-world geometry out of every square.

How should high jumps and long jumps appear on tactical maps?

Jumps work best when the map shows a clear gap and a clear landing zone.

Under current rules, a running Long Jump can cover a horizontal distance up to the creature's Strength score when it moves at least 10 feet immediately before the jump. A standing Long Jump covers half that distance.

Every foot jumped still costs a foot of movement.

A running High Jump reaches a number of feet equal to 3 plus the creature's Strength modifier, with a standing High Jump reaching half that amount. Characters can also extend their arms above themselves when determining what they can reach.

You do not need to memorize those values while designing every room. You do need to create gaps where the difference matters.

Why do most vertical encounters become confusing?

The first problem is invisible elevation.

The DM knows that the balcony is thirty feet high because it was written in the adventure notes. The players see a rectangle on a map. If height affects the fight, communicate it.

The second problem is tracking every creature's elevation mentally. That works until the wizard flies, the dragon climbs another twenty feet, two gargoyles leave their statues, and the rogue jumps onto a lower roof.

Use markers.

The third problem is adding verticality without adding routes. A sixty-foot tower is visually dramatic, but if the only way to interact with the enemy on top is to spend six rounds climbing one rope, the encounter may be less tactical rather than more tactical.

Good vertical maps provide competing routes: stairs, ladders, jumpable gaps, ramps, flying access, balconies, ropes, elevators, broken walls, and risky shortcuts.

The fourth problem is making every elevation difference enormous. Verticality does not require a 200-foot cliff.

A fifteen-foot balcony can change a fight more effectively than a hundred-foot tower if players can actually interact with it.

What is the easiest way to track elevation at the table?

Use the smallest system that always answers the same question: how high is this creature relative to the battlefield's baseline?

Use feet rather than abstract levels unless every elevation in the encounter uses the same increment.

A "+3" marker is meaningless unless everyone remembers that each level represents ten feet. A "+30 ft." marker answers the question immediately.

How do you design a vertical encounter that players actually enjoy?

Start with a reason to change elevation.

Put archers on a raised platform. Put the objective above the main floor. Give the monster a climbing route the party can cut off. Place a bridge control on a lower level. Let the boss fly between balconies. Make a dangerous shortcut cross a narrow rooftop.

Then provide at least two ways to respond.

Players can climb the wall or use the staircase. They can shoot the flying creature or reach the tower controls that force it lower. They can cross the bridge or jump the collapsed section. They can chase the enemy up the ladder or destroy the platform supports.

Verticality works when height creates decisions. It fails when height simply makes one character unreachable.

If you are building encounters on a standard grid, our 30x30 grid scaling guide covers the underlying 5-foot movement scale so horizontal and vertical measurements stay consistent.

Frequently Asked Questions

Sources