Why Your D&D Towns Feel Dead

Summary

The video argues that D&D towns feel “dead” when a DM creates data (shop lists, NPC bios) instead of playable content. The creator proposes designing towns as “toys” and a “playground”—places that generate situations, problems, quests, and town-specific adventures so players have reasons to interact, return, spend money, and explore.

---

Core artistic/creative approach: “Make toys, not data”

Start from creative scaffolding rather than exhaustive documentation:

1. Theme / situation first What kind of town is this, and what’s going wrong?

2. Create adventures that resolve those situations

3. Add establishments/shops that reinforce the loop: earn money adventuring → spend money in town

Towns should be designed to produce situations, not merely store information.

---

Step-by-step design process shown

1) “Don’t make a world—make a town”

Use a real-world-inspired frontier settlement as a reference model (e.g., Icelandic towns as inspiration).

Treat geography as the constraint that makes the town feel natural.

2) Lead with geography and map constraints

Build the map by placing:

• Hills/mountains along edges or dominating views
• Perimeter trees/forest
• A gorge/river/impassable terrain to force layout compromises
• Key infrastructure implied by terrain Example: a bridge suggests where a train station goes

Creative principle: the town should compromise with its surroundings so its shape doesn’t feel arbitrary.

3) Choose an identity “settlement focus” (one main economic thread)

Pick a single dominant thing the town is known for, such as:

• fishing
• lead export
• logging
• mining
• farming

When inventing NPCs you haven’t detailed yet, assign roles that connect to that focus (e.g., fisherman, ship repairer, butcher who serves local industry, fisherman’s accountant).

4) Limit the number of meaningful places (to avoid overwhelm)

Cap labeled/icon locations to around 15.

Ensure variety without creating “15 dungeons”:

• some locations are establishments
• others are short questlike activities or exploration hooks

5) Add “human necessities” to increase believability

Ensure the town can get fresh water—via a well, spring, river, or lake.

Even small additions improve verisimilitude.

6) Build the content loop: situation → adventure → rewards → town feels alive

Create situations (problems affecting everyday life) and tie each to a town adventure that resolves it.

Example problems and resolutions from the running example town:

• No trains for 2 weeks → goods/services cost 2×
  • Resolution: players run an adventure at the railway station (“Railway Thugs”)
• Lumber mill strikes → town cannot be a safe haven for long rests
  • Resolution: players run an adventure involving a union-related outpost (“Union Trouble”)

Gameplay loop logic described:

• Problems create questions and dissatisfaction
• Players go on adventures to fix them
• Fixing them provides rewards (cheaper goods, safe rests, etc.)
• The town becomes more attractive to engage with again

7) Make town adventures “complete experiences,” not static facts

Use two sets of five-room dungeons (one per major situation) so there’s always “something to do.”

Include standard dungeon play elements:

• monsters/bad guys
• initiative, exploration, negotiation
• maps and set-piece locations

8) Convert labeled locations into quest hooks

For establishments/locations, make most non-shop points either:

• mini-quests that relocate the party, or
• short tasks that reveal lore/history and point to bigger threats

Example mini-quests:

• A shopkeeper (“frog man” Gibby) offers a delivery job that rewards gold and sends the party to another location.
• A bank contact (“Rain Price”) shares a backstory about a bear owl attack and offers a gem/treasure recovery quest into the forest.
• “Cookie’s house” serves as a lore hub that directs players toward the final boss dungeon.

9) Populate shops with “money sinks” and progression

Shops act as return points that convert adventure rewards into character upgrades.

Emphasize:

• visible goods in shop windows that cost money
• purchase options that motivate players to come back after adventuring
• underused concept: money sinks (players need reasons to spend)

10) Write prep notes so others can run your town

Keep notes in tools like:

• Obsidian
• World Anvil
• Word Docs
• even Post-its

Use shorthand instead of long prose. For example: “Church, Sister Francesca sells spellcasting services.”

Also: don’t overwork towns that aren’t central to the story—use “background towns” as travel montage filler.

---

Artistic techniques, concepts, or creative processes highlighted

• Constraint-based worldbuilding: geography forces a natural town layout
• Thematic compression: one settlement focus anchors NPCs and details
• Mechanics-driven narrative: town “situations” change gameplay economy/rest rules

• Loop design: iterative cycle of town problem → town adventure → improved town → player engagement

• Playground framing: towns act like toy boxes full of quests and experiences

• Modular enemy design: shared stat blocks with different action sets (e.g., “railrunner variations”)
• Quest routing: mini-quests function as navigation between town and larger regions (e.g., a forest)

---

Creators / contributors featured (mentioned at the end)

• Dalia (host; professional writer and director)
• Maknus (writing partner; credited with map creation in the described Civ 5 editor context)
• Pocket Bard (sponsor mentioned in the video)