hawkeyefan
Legend
The cook could be there. But it was clear from the example that the sole reason she was there was because of a failed lockpicking attempt. That may not matter to you, it matters to me. It would matter if this kind of thing happened on a regular basis.
What can I say, the GM adding in a complication completely unrelated to the action attempted isn't something I want. I should have probably said "random-ass-stuff" but there have been so many veiled and not-so-veiled negative comments about people who don't use fail forward that it gets a tad annoying after a while.
And none of the comments made here since pointing out why the example you sited was incomplete or how it could be made to work have done anything? I mean, maybe they haven't changed your mind, but you can at least onboard the information and stop describing things as "unconnected" and "random" and so on.
And "random-ass stuff" wouldn't really be any better. Know why? Because... again... a cook in a kitchen isn't really random.
I think we're in broad agreement here, though the devil is in the details.
Where I prefer the granular approach, within reason, as it helps keep things that should be unrelated (e.g. the pick-locks attempt vs whether the cook is awake or asleep) separate.
Again, those need not be unrelated. If you're picking a lock in the real world, what are some of the possible consequences?
I would think that they would include any number of the following:
- failing to open the lock
- damaging the lock in some way
- damaging the lock pick in some way
- being discovered while picking the lock
These are all things that when someone decides to pick a lock, they're going to be worried about in some capacity.
None of those consequences, if they're realized, are unrelated to the lock picking.
If the GM doesn't roll for the NPCs then who does?
In some games, the players make all the rolls. The ones I've had the most experience with recently are Blades in the Dark, Stonetop, and Spire. Each of them allows for degrees of success depending on the outcome of a roll. Critical Failure, Failure, Success With Complication, Success, Critical Success.
So depending on the outcome of the roll, the GM has NPCs act accordingly. Sometimes this is dictated in specific ways. When you "Clash" in Stonetop, for example, you roll 2d6 and add your Strength stat (ranging from -1 to +3). If you roll a 6 or less, you're taking your enemy's damage. On a 7-9, you hit your enemy, but they also hit you. On a 10+ you hit them, and you can either avoid their attack or choose to do some extra damage.
In Spire, you roll a dice pool of d10s based on applicable stats and situational factors. You'll roll anywhere from 1 to 4 dice, and keep the highest roll. If it's a 1, you suffer your enemy's attack and take twice the normal damage. On a 2 to 5 you fail and suffer your enemy's attack and take damage. On a 6-7 you succeed and inflict damage to the enemy, but also take theirs. On an 8-9 you succeed, inflicting damage and taking none. On a 10 you inflict double damage.
In these kinds of games, it is expected and required that a dice roll does more than mitigate just the task of the PC. The game won't function if that's not the case since the GM never rolls. This is why some folks, notably @Campbell , have cited how poorly the thief/cook situation works as an example. It assumes so much about the way the scenario is constructed and presented.
Not everything an NPC does is going to be known to a PC or even relatable - and here the cook is a fine example: if the thief never gets into the kitchen then he has no way of knowing whether the cook was awake or asleep; relevant in that if she was awake and heard someone trying to break in she might report this to someone in the morning, where if she slept through it then everyone's none the wiser.
Personally, I'd have hinted at the presence of the cook (or someone) beyond the door before the roll was made. Part of making Fail Forward and similar techniques work is telegraphing things... establishing stakes before the roll is made. A flickering firelight seen beneath the door, the sound of footsteps, or someone humming while they work... anything like that, and then the cook is just "offstage" but ready to be introduced.
Instead, it seems to be with failed rolls adding new information which was unrelated to the check to the narrative. For example, the lockpick fails, and now there is a cook. What's-his-names song doesn't make him feel better and therefore a guard shows up. That sort of thing.
Again, you're failing to acknowledge everything that has been said about that example since it was first shared.
The consequences here are logical--a cook could be in the kitchen, a guard could hear a song--but they aren't part of the check.
Why not? According to what game?
For me, they easily can be... even if I'm playing D&D.