Dungeon World has the following instruction regarding the game world:

The campaign map is updated between sessions or whenever the players spend significant downtime in a safe place. Updates are both prescriptive and descriptive: if an event transpires that, say, gathers a larger fighting force to a village, update the tags to reflect that. Likewise if a change in tags mean that a village has a bigger fighting force you’ll likely see more armored men in the street.

Between each session check each of the conditions below. Go down the list and check each condition for all steadings before moving to the next. If a condition applies, apply its effects.

I have a small campaign map with 6 steadings currently (and one I'll probably have to add in-session because a character spouted lore that defined it nearby.) This is a manageable size for updating between sessions. However, I am a distributed systems engineer. I immediately look to the case of a long campaign with 10-100x as many points of interest, many of them steadings. Do you seriously mechanically update all of the tags (and then address the fiction) for every one of these between sessions or between significant fiction-based downtimes? If that is a crucial part of Dungeon World, I'm probably going to write a program that automates the non-creative half of this process, but that seems a little silly here.

Do you really need to update all steadings according to the given rules?


1 Answer 1


Yes. But maybe not the way you think.

This section is designed to provide the GM with a tool to enable their overarching responsibilities. Yes, technically, you should follow the rules (and that means checking all your steadings) but the rules of Dungeon World aren't meant to be hard to follow. Keep in mind that you are only checking whether or not the steadings need to be updated based on what is going on in your game world. This rule forces you to think offscreen too in a way that allows you to exploit your prep. It just gives you a list of things to consider before deciding that nothing has happened so you don't ignore consequences that aren't obvious. If nothing that is going on would have affected it, it should be pretty obvious just from glancing at the checklist and campaign fronts.

If you're worried about how much work this going represent, you should consider using a tool such as the campaign map and wiki features of Obsidian Portal to make it easier to update and track. However, also bear in mind that new steadings are added only as the fiction demands it. If you're adding new steadings because you're moving to new territory, that's good. It also means whatever is going on is less likely to have a session-to-session impact on the other territories farther away. However, if the map starts to become over-saturated you have a few approaches you can try.

  1. Give the players incentives not to create new steadings. This can be anything from the benefits of dealing with NPCs who remember them to running entire Adventure Fronts within a city. Give them a reason to want to return.
  2. Not every steading needs to be city. Or even a proper village. Something as a small as a lumber camp or well-established farm (homestead) could qualify. The less there is going on, the less you have to worry about when it comes time for the checklist.
  3. Not every update has to be positive. A natural consequence of over-saturation is a strain on resources. This can cause all sorts of problems, from people leaving for more prosperous locations to war and bandits. This can be fodder for adventures (see point 1) or it can simply mean that a village becomes a ghost town. At that point, you probably don't need to worry about updating it as a Steading. You should absolutely still think offscreen too.
  4. Dungeon World's mechanics are heavily integrated around a core philosophy that makes it difficult to change rules without unintended consequences. However, it is permissible. Once you've had some experience you may see ways to simplify things without extensive adverse affects. For instance, you might decide that it makes more sense to keep a distinct campaign map for each "region" and only update other regions after a Front resolves or when players are returning to them.†

On a side note, if you're interested in programming something to make this process easier, you might consider mapping the steading relationships so when you change the tags on one the related steadings show up as needing reviewed (in case that change affected them).

† Disclaimer: I haven't tried this before and so it is an example, not a suggestion.

  • \$\begingroup\$ If there is a need for such a tool, and a demand, I'll write one. However, it looks like there are plenty of ways to limit the scope of the map via incentives and optimizations that should obviate the need for one. I'll keep this in mind and come back to this question (or one like it) if necessary. Thank you. \$\endgroup\$ Jan 27, 2017 at 21:20

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .