A castle is not one map. It is three different jobs wearing the same stonework. A siege map needs wide engagement lines, wall access, and room for mass combat. An infiltration map needs multiple real routes, patrol logic, and sightlines a rogue can exploit. An intrigue map needs an open social space where positioning, sightlines, and who is standing near whom matter more than movement speed. Design each map for its specific encounter, then keep the maps visually unified as one fortress. A good castle pack should let a DM run a siege, a heist, and a throne room negotiation without any scene feeling like it is using the wrong map.
A DM builds one castle map, a detailed courtyard with a single gate and a straight hallway to the throne room, and tries to run three different sessions on it: a siege where the party defends the gate, an infiltration where a rogue sneaks in through that same gate at night, and a throne room negotiation where the party finally meets the baron. All three sessions play the same because the map was built for none of them specifically. The siege has nowhere for a second front to open. The infiltration has no alternate route, so sneaking in just means walking toward the same door more slowly. The throne room has no meaningful sightlines, so the intrigue scene becomes dialogue happening near furniture.
Castles get treated as a single map type more than almost any other location in D&D, and it weakens the encounters inside them. A siege, an infiltration, and a court intrigue scene each revolve around a different core mechanic: mass combat lines, route choices under stealth, and social positioning. This guide explains how to design each map type deliberately, size and elevate it correctly, and connect the maps into one coherent fortress pack.
Why Does One Castle Map Break the Pacing of Different Encounters?
Every encounter type inside a castle asks a different tactical question. A siege asks where the enemy will break through and how the defenders can hold multiple positions at once. An infiltration asks which route gets the party past the fewest eyes. An intrigue scene asks who can overhear a conversation and where a character should be standing when an accusation lands.
A generic layout with one gate, one hallway, and one throne room cannot answer all three questions well. Each encounter needs different structural features built into the map from the start. In our map design work, the castle packs that hold up across a campaign arc are the ones created with the encounter type decided first. Structure comes before decoration.
What Makes a Siege Map Support Mass Combat?
A siege map needs engagement to happen in more than one place at once. There might be a breach at the gate, defenders fighting on the wall, and a secondary assault against a weaker section of curtain wall. Supporting those events requires wide engagement zones instead of the tight chokepoints that work well for corridor ambushes.
The walls must also function as playable spaces rather than painted borders. Archers, defenders, and siege crews need enough room to move, take cover, and contest access points. If the battlements cannot comfortably hold tokens and movement paths, their tactical value disappears.
The gatehouse is usually the most important feature on a siege map. It should read clearly as the primary point of failure: reinforced and defensible, but visibly the place both sides are fighting to control. If the gate does not look or function like the objective, players may spend the encounter guessing where the real pressure point is.
How Do You Create Real Stealth Routes on a Fortress Infiltration Map?
An infiltration map lives or dies on route count. If there is only one way from the outer wall to the objective, sneaking in becomes a series of Stealth checks along a predetermined path. A workable infiltration map needs at least two, and ideally three, genuinely different routes.
Those routes could include a servants' passage, a climbable section of wall, or a sewer grate that receives less attention from the guards. Each route should have a different risk profile. One might be physically difficult but lightly guarded. Another could be easy to enter but heavily patrolled. A third might create a longer path that provides better cover.
Patrol logic matters as much as route count. A guard following a predictable loop gives players something they can study and exploit. They can time a crossing, lure the patrol away, or use a blind spot in a specific corridor. Static guards remove that planning layer and reduce the infiltration to a chain of checks.
How Much Elevation Should a Castle Map Include?
The right amount of elevation depends on the encounter. Siege maps benefit heavily from playable wall elevation because archers, defenders, and siege engines need to occupy those positions meaningfully. Infiltration maps benefit from at least one vertical route, such as a low wall, drainpipe, roofline, or servants' stair.
Intrigue maps generally need less verticality and more horizontal social space. Alcoves, side rooms, doorways, and a raised dais matter because they establish social distance and control sightlines. The elevation is symbolic and positional rather than primarily tactical.
| Map Type | Elevation Use | Route Count | Best For |
|---|---|---|---|
| Siege courtyard | High, with fully playable walls | 1 to 2 breach points | Large-scale defense or assault |
| Infiltration wing | Moderate, with one climbable route | 2 to 3 distinct paths | Stealth-focused parties |
| Barracks skirmish | Low, mostly ground level | 1 to 2 tight routes | Mid-fortress combat |
| Throne room intrigue | Low, with a single dais | Open floor without funneling | Social and political scenes |
In our experience, three genuinely distinct routes are enough to make an infiltration feel like a tactical choice. Two routes can work, but three give players a real decision to debate before they enter the fortress.
How Should You Size Each Type of Castle Map?
Assume a standard 5-foot grid and a party of four. A siege courtyard with wall access on two sides could cover roughly 50 by 60 squares, or 250 by 300 feet. An infiltration wing with three parallel routes might span approximately 40 by 40 squares. A throne room built for social positioning could use an open footprint of about 25 by 25 squares. These are starting points, not fixed rules. Party size, creature count, encounter objectives, and VTT display size should determine the final dimensions.
Siege maps require enough space for multiple fronts without becoming so large that turns are spent only on movement. Infiltration maps can use narrower corridors, but the total footprint increases when the map includes several parallel routes. Throne rooms need enough open space for proximity and sightlines to matter without spreading every participant so far apart that the social geography loses meaning.
Why Do Most Castle Map Packs Fall Flat?
Four failure modes appear repeatedly. The first is asking one layout to do three jobs. A single courtyard-and-hallway map gets reused for siege, infiltration, and intrigue, but none of those encounters plays particularly well.
The second is missing patrol logic. Guards exist as static obstacles instead of forming patterns the players can study. The third is using decorative-only walls on siege maps. The battlements look impressive, but they are not wide enough or connected well enough to support combat. The fourth is giving throne rooms no social geography. A flat room with a chair at one end provides no meaningful near and far positions, private conversation areas, or useful sightlines.
Strong castle maps establish breach points, route choices, or social geography before adding tapestries and heraldry. Our guide to designing encounters in crumbling cities and fallen empires applies the same structure-first approach to ruined fortifications and fallen strongholds.
A castle map should make the party defend, sneak, or negotiate differently. If changing the encounter type does not change how the space is used, the map is only scenery.
How Do You Know Whether a Castle Map Is Working at the Table?
Track signals specific to each encounter. On a siege map, determine whether combat occurred in more than one location or whether everyone clustered around a single chokepoint. On an infiltration map, note whether the players seriously considered multiple routes. On an intrigue map, watch whether anyone changes position to overhear a conversation, remain near an exit, avoid a noble's sightline, or approach the dais.
If every siege stays in one spot, alternate infiltration routes are ignored, or the throne room geography never enters the conversation, the map is not doing enough mechanical work. Tracking those outcomes across sessions makes it easier to distinguish functional encounter maps from attractive backdrops.
Should a Castle Map Pack Progress From the Outer Walls to the Throne Room?
Yes. A single map only needs to support one scene, but a fortress pack needs to tell a spatial story. The outer walls and gatehouse support the siege or initial approach. The courtyard and barracks wings support infiltration and smaller skirmishes. The inner keep and throne room provide the political or combat climax.
This progression makes the fortress feel like one coherent building instead of a stack of unrelated rooms with matching stone textures. When evaluating a castle set, check whether it supports changes between siege, stealth, exploration, and social play as the party moves deeper into the location. Our battle map packs are designed around this type of encounter progression.
Frequently Asked Questions
How big should a siege battle map be for a castle courtyard fight?
Roughly 50 by 60 squares, or 250 by 300 feet, is a reasonable starting point for a courtyard supporting mass combat and wall access on multiple sides. A smaller siege focused on one breach can use a tighter map.
Do infiltration maps need multiple routes to feel real?
Yes. A single path reduces the infiltration to walking down one corridor and rolling Stealth. At least two, and ideally three, routes with different risks give players a real planning decision.
Should castle maps include playable walls and battlements?
Siege maps should include playable walls whenever defenders or ranged combatants are expected to use them. The battlements need enough room for tokens, movement, cover, and access points rather than functioning as decorative borders.
What is the difference between a siege map and an infiltration map?
A siege map supports simultaneous combat at multiple positions and needs wide engagement zones, breach points, and playable walls. An infiltration map revolves around route choice, patrol patterns, blind spots, and paths with different risk levels.
How do you design a throne room map for intrigue instead of combat?
Prioritize social geography. Include a dais, alcoves for private conversations, recognizable entrances, and sightlines that make eavesdropping or dramatic arrivals possible. Players should have social reasons to change positions.
Do castle battle maps need a grid for VTT play?
A grid is useful for siege and infiltration encounters because movement, range, cover, and dynamic lighting depend on consistent scale. Gridless maps can also work when the VTT applies its own grid or the group uses zone-based movement.
How many castle maps are needed for a full fortress campaign arc?
A self-contained fortress arc can often use 10 to 20 maps covering the outer walls, gatehouse, courtyard, barracks, infiltration routes, inner keep, and throne room. The exact count matters less than giving each major encounter a map built for its specific purpose.
Explore battle map packs built as coherent locations, with layouts designed for combat, infiltration, exploration, and dangerous negotiations.
Browse Battle Map PacksSources
| Kobold Press | One-Shot Builder: Siege Mentality |
| Kobold Press | Castles & Crowns: Design Diary |
| D&D Beyond | How to Make Social Encounters More Than a Charisma Check |
| Sly Flourish | Build Single-Encounter Situations |
| Foundry Virtual Tabletop | Levels: Multi-Elevation Module |
| Roll20 Help Center | Page Settings for Dynamic Lighting |
