The Consuming Aspect of the Megalo-Dungeon
As dungeon masters, we have all done it. We have spent hours and hours (and hours) writing histories and stories for our campaigns only for our players to ignore them. It can be frustrating. It can feel defeating. But it is never a waste. The act of creating those histories is an exercise in itself. As we do things over and over, we get better at it. The first adventure you ever wrote is probably far different than one you write today. And we learn as we create, and we do not make the same mistakes. Or do we?
Writing the dwarven dungeon project has become much more than designing a dungeon. Something of this magnitude has spurred myriad other creative undertakings in its orbit. Obviously, its history, from its rise to fall, and its pantheon of deities are important because they help me understand what was there then and what is there now. It allows me to create the ecosystems and political environments within the dungeon. Historical information also helps develop potential patrons and the quests they offer.
Speaking of patrons, they have become another enterprise entirely. From lowly farmers or magistrates to nobles, wizards, clerics, governors, alchemists, and sages, the dungeon needs dozens (and dozens) of interested benefactors. I have found myself developing quests and quest chains, interesting personalities, and quirky situations that enable players to choose patrons, political sides, and allies. As the village grows into a town and then into a city, new personalities arrive, opening up new opportunities.
Which then brings me to the village. The village, itself, is a living environment. As money is dredged from the dungeon, the village grows, offering new buildings, equipment, patrons, and supplies. This tiered effect enables the characters to feel its growth and benefit from it. It also opens up potential quests outside the dungeon (e.g., bandits on the road that will limit trade until defeated or goblin war parties that threaten the village's ultimate safety). And who knows that kind of greedy, treasure-hoarding monster might arrive if too much wealth is brought out of the mountain?
And since I did not have enough on my plate, I created a list of potion ingredients (and recipes) for the alchemist. These ingredients are spread throughout the dungeon. Resourceful characters can hunt them down to unlock new potions or commission the alchemist to mix potions with found ingredients for their journeys.
The list goes on. Poisons that can be fashioned from things in the dungeon. A list of goods (with weights and values) that linger in the dwarven storerooms and warehouses. Ancient books that provide beneficial knowledge. Lost shrines to forgotten deities that might provide boons. Parlaying situations with monsters that can result in quests or knowledge. A host of minor puzzles and complicated mysteries to keep players thinking. And I have not even scratched the surface.
So, did I learn from all those times I spent hours and hours (and hours) creating stories and histories? I like to think I have. I do not spend a lot of time creating intricate narratives for small adventures I run. I start with a map, some basic notes on the people and places the characters might interact with, and the adventure itself. If it becomes something larger, I build as I go. But I have also learned how to develop something far more complex, and I know that complexity requires a great deal of time, effort, and attention. The dwarven dungeon project was scheduled to consume 7 years of my life. It is not just a megalo-dungeon. It is an entity in its own right, and it requires the myriad complexities that shape it.
This is my largest project so far, but I have written many adventures over the decades. Each one has its own challenges. What approaches do you take when writing a dungeon? What have you learned, and what mistakes have you made? What stories do you have to tell?