Sinking Ships and Crumbling Ruins: Running Dynamic Maps That Change Mid-Fight

The party boards the pirate ship and initiative begins.

There are enemies on the forecastle, two spellcasters near the stern, a narrow staircase leading below deck, and rigging hanging over both sides. It already looks like a good fight.

Then something explodes below the waterline.

The ship lists hard to starboard. Water begins flooding the lower deck. A mast cracks. Cargo slides across the planks. The staircase everyone planned to use is suddenly half underwater.

Now the party is not fighting on a ship. They are fighting on a ship that is sinking.

That distinction is the foundation of a dynamic map. The battlefield should not simply look damaged. It should change the decisions players make as the encounter progresses.

What makes a changing battle map actually work?

A strong dynamic map changes tactical relationships, not just artwork.

If a wall collapses but everyone can continue using the room exactly as before, the collapse is mostly visual. If that same collapse blocks a doorway, creates rubble, opens a new line of sight, and gives the archer Half Cover behind fallen stone, the battlefield has meaningfully changed.

The easiest way to design these encounters is to think in map states.

You do not always need four states. A simple encounter can work perfectly with an intact map and one dramatic transformation halfway through combat.

What matters is that each state creates a new tactical problem.

How do you build map states without creating too much bookkeeping?

Prepare the changes before the encounter instead of inventing every new square during initiative.

For a physical table, this might mean removable tiles, terrain pieces, transparent overlays, or a second printed version of the map.

For a VTT, prepare separate scene versions, map layers, tiles, overlays, or images that can be swapped when the battlefield reaches the next state.

The DM should be able to say, "The western wall collapses," make one quick map change, and continue the round.

Avoid tracking every cracked plank, loose brick, and puddle individually unless one of those details becomes tactically important.

Change the map in chunks.

How do you run a sinking ship encounter?

A sinking ship gives you a natural progression because the environment already suggests escalating stages.

State 1: The hull is damaged

Start with the ship functioning normally. Players can use stairs, rigging, deck positions, railings, cargo, and elevation without special movement rules.

Then telegraph the damage.

A cannonball punches through the hull. A sea monster tears open the lower deck. A magical explosion blasts below the waterline.

Tell the players immediately that water is entering the ship.

State 2: Lower areas begin flooding

Once water reaches between shin and waist depth, current fifth-edition rules give you a ready-made mechanic: that liquid can count as Difficult Terrain.

A 5-foot square of Difficult Terrain generally costs 10 feet of movement to cross.

Now anyone below deck must decide whether finishing the fight there is worth becoming slower as the water rises.

The stairs back to the main deck become much more valuable.

State 3: The deck begins to fail

The ship lists hard to one side. Broken cargo, loose rope, shattered planks, and fallen rigging transform open deck into hazardous terrain.

You do not need a custom "tilted ship" rules system. Mark the sections where movement has become meaningfully difficult and treat those areas as Difficult Terrain when appropriate.

A mast might fall across the deck, creating an obstacle and possibly Cover. A shattered railing might expose a dangerous drop into the sea.

State 4: The ship is going under

At this point, stop pretending the encounter is still ordinary shipboard combat.

Characters are climbing toward the highest remaining section, swimming through flooded compartments, jumping to lifeboats, grabbing debris, or trying to finish the enemy before the battlefield disappears.

When the map reaches its final state, let the objective change with it. Winning may no longer mean defeating every enemy.

How do you run a crumbling ruin without making collapse feel random?

Show the damage before it becomes dangerous.

Cracked columns, fractured arches, missing ceiling stones, leaning walls, hanging masonry, and piles of existing rubble should all tell the party that the structure is unstable.

Then escalate those visual warnings.

A column cracks further after the ogre hits it. Dust pours from the ceiling after a thunder spell. Stone fragments fall from the bridge one round before the center gives way.

The current DM's Toolbox includes a Collapsing Roof trap that provides a useful baseline for sudden structural failure. Its low-level example calls for a Dexterity saving throw against falling debris, deals Bludgeoning damage, and leaves rubble behind.

The exact numbers do not need to be copied into every ruin encounter. The design principle is more useful: collapse can deal immediate damage and leave a permanent map change afterward.

When should the battlefield change during initiative?

Use predictable timing.

One of the easiest options is changing the map at a fixed initiative count. Another is changing it at the end of each round. A third is tying the transformation to something players or enemies actually do.

Examples:

End of Round 1: Water enters the lower deck.
End of Round 2: Lower-deck water becomes Difficult Terrain.
End of Round 3: The ship lists and one staircase becomes unusable.
End of Round 4: The mast falls and the evacuation phase begins.

That structure gives players time to react.

You can also make changes conditional.

The bridge collapses when the giant crosses it. The tower begins failing when the second support is destroyed. Fire spreads when nobody spends an action containing it. The flood stops if someone closes the gate controlling the water.

Conditional transformations are especially satisfying because players can influence when, or whether, the next map state appears.

How much warning should players get before terrain changes?

Usually at least one clear warning.

If a bridge is going to collapse, describe ropes snapping or stones dropping from underneath it. If a wall will fall, show the crack spreading. If a room is about to flood, describe water surging through the doorway before it becomes waist-deep.

Telegraphing is what turns environmental danger into a tactical decision.

Without warning, the DM is simply changing the rules underneath the characters.

With warning, the players decide whether staying in that dangerous position is worth it.

How do you use existing D&D rules instead of inventing new mechanics?

Use familiar rules as building blocks.

Rubble, shallow flooding, steep surfaces, and similar obstacles can become Difficult Terrain. Current rules make each foot of movement through Difficult Terrain cost one additional foot.

Collapsed walls, fallen masts, overturned carts, and broken stone can create Cover. Current rules support Half Cover, Three-Quarters Cover, and Total Cover depending on how much of the target the obstruction protects.

Open flames can use the Burning hazard when appropriate. A burning creature or object takes 1d4 Fire damage at the start of its turns until the fire is extinguished.

Broken bridges, cliffs, towers, and collapsing floors naturally interact with Falling. Current rules deal 1d6 Bludgeoning damage for every 10 feet fallen, up to 20d6.

Structural supports, ropes, doors, barricades, and similar terrain can be treated as objects when characters try to destroy them. Current rules explicitly support damaging objects and allow the DM to assign properties such as AC, Hit Points, vulnerabilities, resistances, and Damage Thresholds as appropriate.

The more you can express the changing battlefield through rules players already understand, the faster the encounter runs.

For more ideas on making map features mechanically relevant, see our guide to dungeon hazards and environmental detail.

Should players be able to cause map changes themselves?

Yes, whenever the environment reasonably supports it.

A cracked pillar is much more interesting when the barbarian can deliberately destroy it.

A hanging sail can be cut loose. A rope bridge can be severed. A sluice gate can flood the lower chamber. A burning beam can be pushed into an enemy route. A damaged mast can be brought down intentionally instead of waiting for the DM's timer.

This changes the environment from a scripted hazard into a tactical resource.

The moment players realize they can change the battlefield too, they start looking at scenery as equipment.

If you have prepared a later map state, do not be afraid to reveal it early because the players found a clever way to trigger it.

That is not ruining the encounter. That is the encounter working.

Why do dynamic maps become frustrating instead of exciting?

The first problem is changing too much at once.

If ten squares become Difficult Terrain, three walls disappear, four fires spread, the floor tilts, and everyone needs to make a saving throw at the same time, players stop making tactical decisions and start asking what the map currently looks like.

The second problem is changing terrain without updating the visual representation. If a bridge is gone, remove it. If the room is flooded, show the flooded version. If the ceiling has collapsed, place rubble on the map.

The third problem is using transformation only to punish the party. If every new map state removes player options without creating new ones, the encounter becomes progressively less interesting.

A fallen pillar can block one route and create another piece of Cover. A collapsed wall can close a hallway but open a shortcut outside. Rising water can slow everyone but allow characters to swim through an opening that was unreachable earlier.

The fourth problem is letting the transformation continue after the encounter has already reached its dramatic peak.

Once the ship is completely underwater, you probably do not need seven more stages of sinking. Move to the escape, underwater fight, or next scene.

What is a simple template for building a dynamic encounter?

Use five questions.

If you can answer all five questions clearly, you probably have enough information to run the transformation smoothly.

If the change requires a paragraph of explanation every round, simplify it.

And if you want environments that give you room for collapsing routes, spreading hazards, changing cover, alternate paths, and evolving encounter states, explore the Black Lantern Forge battle map collection.

Frequently Asked Questions

Sources