Guides
How to Run D&D Bastions and Strongholds
Learn how to run D&D Bastions and strongholds: pick facilities and hirelings, handle upkeep and downtime check-ins, and add story hooks without slowing play.
By Mythical AtlasLast updated
Giving your party a home base is one of the easiest ways to make a campaign feel lived-in. The trouble is bookkeeping: who works at the stronghold, what does it cost each week, and what did the party come home to after a month away? This guide shows how to run D&D Bastions and strongholds without letting them swallow your sessions, whether you use the Bastion rules from the 2024 Dungeon Master's Guide, an older stronghold system, or something homebrew.
The short version: treat the base as a downtime layer. Keep a short list of facilities and hirelings, settle the numbers in one quick check-in each time the party returns, and spend your table time on the story hooks the base creates.
Decide what the base is for
Before you track a single coin, pick the job your stronghold does in your campaign. Common answers:
- A reward and a resource. The party earns income, crafted gear or favors, which makes returning home feel good.
- A story engine. Visitors, rumors, sabotage and festivals give you ready-made hooks.
- A sink for treasure. Players who are swimming in gold finally have something to spend it on.
Most write-ups on the 2024 Bastion rules make the same point: bases work best in campaigns with real downtime, and they can overshadow the adventure if you let them. If your game is non-stop travel and dungeon crawling, keep the base small and the check-ins short.
Keep the cast of the base small
A stronghold with forty named staff members is a spreadsheet, not a game. Start with:
- Two to four facilities. An inn, a forge, an apothecary, a workshop, a farm. Each should do one clear thing.
- A handful of hirelings. Give the important ones a name and a personality. The rest can be "the kitchen staff."
- One recurring problem. Something the base needs that the party can solve on an adventure.
Facilities are where the numbers live. For each one, write down what it costs per week, what it earns per week, and whether it makes anything over time. Hirelings work the same way: a weekly salary, and sometimes income from their services.
One-off projects vs. steady production
Two kinds of output cover almost everything:
- One-time projects, like a custom weapon, a suit of armor or a magic item the party commissions. These take a set number of weeks.
- Recurring production, like potions every few weeks or a batch of arrows each cycle. Leftover progress carries into the next cycle.
Here's a worked example. An apothecary produces 2 healing potions every 3 weeks. The party is away for 7 weeks. That's 2 full cycles (6 weeks), so 4 potions, with 1 week of progress carried forward.
Run downtime as a quick check-in
The simplest rhythm is a check-in each time the party returns. Ask one question: how long were they away? Then multiply.
- Total weekly profit minus weekly upkeep and salaries, times the weeks away, gives the net gold.
- Reduce the weeks remaining on every commissioned project.
- Work out how many production cycles finished.
That takes a couple of minutes, which is the point. If your table follows the 2024 Bastion rules, which break the base into turns with orders for each facility, you can use the same idea: do the turn between sessions or in a short block at the start, not as a main event. Check the book for the exact turn length and the orders your facilities can take.
Add a story beat, not just a number
After the math, roll or choose one event. Ideas that need no rules at all:
- A traveling merchant wants to rent a stall.
- A rival sends someone to sniff around the forge.
- A hireling asks for a favor tied to the party's last quest.
- The town wants the base to host a festival.
One event per return is plenty. It turns "you made 4 gold" into a reason to care.
Make the money coherent
Strongholds fall apart when the economy is fuzzy. Two habits help:
- Use the same currencies everywhere. If your region trades in something other than gold, price the base's income and costs in it, and sell the same things in the local market. That's where a shop and merchants setup helps: custom currencies are defined once and reused.
- Let the base be a net cost sometimes. A keep that always profits isn't interesting. Occasional losses (a bad harvest, a pricey hire) make the party's choices matter.
For more on running markets, the same ideas apply to any merchant the party visits.
Share the base with your players
A base only matters if players remember it exists. Give them a place to see what's built, who works there, and what they came home to. Posting a short "while you were away" note after each return, in your session updates, keeps the base in the story. For general campaign housekeeping, our guide on how to organize a D&D campaign covers a routine that fits well, and the session zero checklist is the right place to agree on how much downtime and base play your group wants.
How the Player Keep tracks this
If you'd rather not do the arithmetic by hand, the Player Keep in Mythical Atlas, the campaign manager we build, handles exactly this loop:
- One keep per campaign. It's created the first time anyone opens the Player Keep page. The GM sets a description and an icon.
- Facilities and hirelings. Each facility has a weekly upkeep and weekly profit, plus GM-only notes. Hirelings have a weekly salary and optional weekly profit. A summary at the top shows net income or expenses per currency, in green for profit and red for loss.
- Crafting. Add one-time projects with a number of weeks, or recurring items with a quantity and a cycle length.
- Record Return. Enter how many weeks the party was away and review the report: income and costs line by line, finished projects and completed production cycles. Confirm, and all progress updates automatically.
- History. Past check-ins are saved and every member can read them. The keep holds up to 50 records and drops the oldest after that.
Currencies come from the same list the Shop uses, so homebrew money works on both sides. Players can browse the keep, its facilities, hirelings and history, while the GM manages everything. Note that it's a general weekly-income-and-production tracker: it doesn't implement any particular edition's Bastion turn, orders or events, so you'll still run those at the table.
A simple routine to keep
- Agree on the role of the base at session zero.
- Keep facilities and hirelings few and distinct.
- Ask "how long were you away?" each time the party returns.
- Settle the numbers, then add one event.
- Tell the players what happened.
Do those five things and the stronghold stays a source of fun instead of homework.
