I appreciate the standard procedure in a game. I think we have all fallen into it at one time or another. But what I find, is there are players that always seem to want to break from the procedure. Maybe it's not thorough enough or they feel like they are missing something? Maybe they don't like the repetitiveness of it? Maybe they are antsy because in the procedure set up the bard is the one always rolling? Or a combination of all three. I really don't know, but as much as I have seen standard procedures start, I have seen almost all fall apart. Then it becomes a huge time sink.
Which, if the players are the ones who can't stick to an SOP, the DM kinda just has to live with. And if the players then complain that things are going too slow, show them where the solution lies by holding up a mirror.
For my part, in the end it doesn't matter to me-as-DM whether they finish the adventure in two sessions or thirty...with one exception, that being if I'm running multiple potentially-interacting parties side-along and I have to worry about lining them up in game time, a slow group can cause headaches. (as can a particularly efficient group)
I do appreciate this. A good dungeon crawl, survival, dungeon roleplay. (That sounds naughty, but not intended.) Mapping and random encounters awesome. Field testing magic items - hilarious! All good stuff. But I have two buts to this:
- For most dungeons, the story lies elsewhere. The dungeon may help tell it, but it is hard to have an entire storyline take place in a dungeon. I get it, there are exceptions. But, for the most part, it is a piece of a setting that helps tell the story. So if it just that, I don't understand the need to spend six months on it (if you played twice a month). I feel like the same thing could be accomplished in two sessions.
- I understand that the dungeon is the actual story. But if the characters are travelling through a forest, is that the actual story? If they are finding a pass through the mountains, is that the actual story? If they are hanging out in a city, is that the actual story? Or make it even smaller, if they visit a huge tavern, is the tavern the actual story? Or are these things accomplished in a few sessions?
In order:
1 - Most dungeons are, in one way or another, part of a larger story. An analogy is that a single game is part of a sports team's season, if each game was of an uncertain length and perhaps involving different elements. While the team is playing a game it is, in theory, focused on the game at hand; and only afterwards pays attention to how the game affected their place in the standings and-or their season.
Same for an adventure. In the here-and-now the focus is on the adventure at hand, for as long as that may take. Afterwards, you can worry about how it lines up with other story elements.
2 - A forest, or a mountain pass, or a city - each can be every bit as much the actual story as a dungeon, as each can be (or be part of) an adventure. Put another way, for these purposes I'm defining a "dungeon" as anything done in significant detail, usually because it involves significant risk. A dungeon crawl is almost always done in detail. An adventure in a forest or mountain pass* or city, ditto; as opposed to just passing through or hanging around in one.
* - in the game I play in we had an adventure once that consisted pretty much of just trying to travel through a mountain pass and clear out some dangers. Something like 8 sessions, three PC deaths, and a whole lot of blood-and-guts later we finally made it, only to realize we'd rather missed what we were there for and had to go back. A few more sessions later we'd figured it out, helped immensely by having already dealt with 95% of the risk. Which makes me think - I've no idea now, five years later, what if anything that adventure had to do with any ongoing story; and I'm fine with that. What I remember more clearly (and a bit fondly, even though my PCs spent the trip getting whaled on!) are some key elements and events that happened in the adventure.
I appreciate a DM that just lets the players choose whatever path they want. To let one arc drop and be replaced by another. It takes skill and a lot of work to do it well.
IME the trick is to have more than one in the hopper, and drop hooks for several. Then, if for some reason one story falters, the groundwork's already been done for a few others.
(Side Note: The ones making stuff up off the top of their head always seems to become a cluster after a few months.)
Agreed.
Winging it is fine for a while of one has to, but unless one is far better at on-the-fly notetaking than I am it's a recipe for disaster in the long run.
I have a DM right now that is the best I have ever seen at this style of play. But what I see from the players' side is restlessness. There may be infinite objectives out there for our characters, but if all of them are going to play out with or without us, and our choices only influences one or two, then it always feels like a losing battle or we always feel like we are behind.
It can feel that way, and I'm guilty of this too.
Comes from having too many ideas and not enough nights in the week to play them all out, I guess.
Not saying this is your table, it is just my experiences with this style of play. In the end, it is the reason the thousands of published adventures exist - to complete a story arc.
Published adventure paths, you mean? If so, yes, though they both assume and promote a somewhat different style of play than I'm seeking.
Published individual adventures may or may not have anything to do with a story arc, or may help it, or may hinder it. One example is an adventure-path-like series I embedded into my current campaign. Was going to be five adventures but a sixth got tacked on; the first, second, fourth and sixth were homebrew modules, the third and fifth were published TSR-era classics that just happened to really fit well with what I had in mind.