DnD Ship Battle Map Guide: How to Run Naval Combat and Seafaring Encounters

A party charters a ship out of a coastal town to chase down smugglers, and the DM pulls out a single top-down image of a galleon. It looks great. Then combat starts, and nobody knows how far apart the two ships actually are, whether the rogue can make a ranged shot across the gap, or what happens when the fighter tries to jump the rail mid-round. The fight stalls into a debate about geometry instead of a tense boarding action, and the table's energy drains out of the room.

This happens because most ship encounters get treated as reskinned dungeon fights instead of what they actually are: a combination of vehicle movement, ranged combat, environmental hazard, and boarding action happening at once. Running it well takes a map built for that specific job, not a pretty picture of a boat. This guide breaks down what a functional dnd ship battle map needs, how to structure the encounter around it, and where naval combat in 5e most often goes wrong at the table.

What Makes Ship Combat Different From a Normal D&D Battle Map?

A standard battle map answers one question: where is everyone standing right now. A ship combat map has to answer that question twice, once for the vessels and once for the people on them, and the two answers change independently. A ship can be moving 60 feet per round while a character standing on its deck is not moving relative to the ship at all. If your map only tracks character position and ignores vessel position, half of the tactical decisions in the encounter become invisible to the players.

Verticality is the second big difference. A dungeon room is mostly flat. A ship is not. There is a main deck, there is usually a lower deck or hold, there may be a raised quarterdeck or a crow's nest, and boarding actions move characters between all of them mid-fight. A single flat map cannot represent that without becoming cluttered or confusing, which is why most naval encounters actually need a small set of connected maps rather than one master image.

Finally, the environment itself is an active participant. Wind direction affects sailing speed. Waves and storms affect footing and visibility. Water itself is a hazard the moment someone goes over the rail. None of this exists in a typical dungeon corridor, and a map that does not visually account for it forces the DM to explain all of it verbally, which is exactly the kind of friction that slows an encounter down.

What Should a DnD Ship Battle Map Actually Include?

A usable naval map earns its keep by making decisions legible at a glance. That means a clear deck layout with named zones (bow, stern, main deck, quarterdeck, hold), a visible scale reference so players can estimate range for spells and ranged attacks without asking, and enough open water bordering the ship that a chase or maneuvering phase does not run off the edge of the map on round two.

It also means hazard zones are drawn in, not just described. Rigging that could entangle a falling combatant, a hatch that drops straight to the hold, a section of rail low enough to be vaulted, a cannon position with a fixed firing arc. These are the details that turn a map from scenery into a tool the players actually use to make choices, which is the entire point of building one in the first place.

In our map design work on coastal and naval map packs, the packs that get used at the table most are the ones where every deck level reads clearly on its own, since most groups will only ever look at one level of the ship at a time during actual play.

How Do You Set Up a Ship-to-Ship Combat Encounter?

Start with three numbers before initiative is rolled: the starting distance between the two vessels, each vessel's speed per round, and wind direction if it matters to your rules set. Everything else in a ship-to-ship phase flows from those three facts, and putting them on the map (or next to it) up front saves the DM from re-explaining the situation every round.

Once the ships are close enough for ranged attacks, treat each round as two overlapping decisions: what does the vessel do (hold course, turn, ram, close for boarding) and what does each character do (fire, brace, prepare to board). Most DMs run these as a single combined initiative order, which works fine as long as the map makes it obvious which zone of the ship each character is standing in when the vessel itself moves.

What Rules Should You Use for Naval Combat in 5e?

Fifth edition's core rulebooks give you the pieces but not a full framework. Vehicle statistics and running battles largely came together in Ghosts of Saltmarsh, which handles ship AC, hit points, and damage thresholds for the vessels themselves, while chase mechanics from the Dungeon Master's Guide cover the tension of one ship trying to outrun or overtake another.

In our experience, tables that try to run every rule at once on the first naval session get overwhelmed fast. A workable starting point is to run the vessel as a single actor in initiative with its own simple move-and-attack turn, resolve character actions normally on their own turns, and only bring in full chase or grappling-hook rules once the group has run one or two simpler ship encounters and knows what the map is showing them. The map should carry the complexity that the rules skip: exact positions, hazard zones, and boarding points, so the ruleset itself can stay lean.

How Do You Handle Boarding Actions and Multi-Level Ship Maps?

Boarding is the moment most naval encounters actually get memorable, and it is also the moment a single flat map falls apart. The fix is to treat a ship not as one map but as a small connected set: a main deck map for the bulk of the fight, a below-deck or hold map for anyone who goes through a hatch, and optionally a raised quarterdeck or crow's nest inset for vertical positioning.

Mark the connection points clearly on every level, hatches, ladders, rope lines, so a player who says "I'm heading below deck" has an obvious, visible path to follow rather than a DM ruling made up on the spot. Keep the visual style consistent across all the levels of the same ship (same wood tones, same wear patterns, same lighting) so the set reads as one vessel rather than three unrelated maps stitched together.

Why Do Most DMs Get Naval Combat Wrong?

The most common failure is running the encounter like a regular dungeon fight that happens to be on a boat, which ignores vessel movement entirely and turns a naval battle into a stationary brawl with a nautical paint job. A close second is inconsistent scale: if the map does not make distance obvious, the DM ends up adjudicating range calls by feel, and sharp players will notice and start arguing about it.

The third failure mode is trying to run full vehicle rules, full chase rules, and full boarding rules simultaneously in the group's very first naval session. High-performing tables scale complexity up over two or three sessions instead of front-loading it all into one, and they lean on the map to communicate hazards and layout so the spoken rules can stay simple.

A ship map that only shows the boat is a diorama. A ship map built for combat shows every reason two crews might want to kill each other in the next six seconds.

How Do You Track and Measure a Good Naval Encounter?

You can translate encounter quality into a few simple things worth watching at the table, the same way you would track any other recurring session element. How many rounds pass before the first meaningful positioning decision, whether every player at the table takes at least one action tied to the ship's layout rather than just attacking the nearest target, and how long the boarding transition takes once it starts.

If your table is consistently taking six or more rounds to get to a meaningful decision, the map or the setup is usually the bottleneck, not the players. Tightening starting distance, simplifying the initial rules explanation, or laying hazards out more visibly on the map will usually fix it faster than adding new mechanics will.

Frequently Asked Questions

Sources