Sure. This is no different from any other action declaration, at least where the GM is obliged to honour the outcome.
I mean besides the obvious difference that you just agreed to right?
For what it's worth, I agree the GM is bound to honor it. I don't see the relevance of that point in relation to what we are disucssing but if it may help move the conversation forward if you can clearly see my agreement to that point. I think it's been a while since this was stated, but I'm not saying fail forward doesn't work in general. The point of saying fail forward is different than regular resolution is only so that I can explain what I dislike about it and discuss how it conflicts with many D&D playstyles. And yes, there are many differences I would count as pros in the fail forward column. I can understand why someone would look at that list of pros and decide it's a better way for themselves. But there are differences about it in the con column as well and maybe for you those things bear little weight, but for others they bear significant weight.
Part of what it seems is typical of these discussions is 1) talk up the differences where fail forward is a pro and 2) deny any differences where fail forward is a con. 3) Another framing of the same thing might be 'fail forward is objectively better since it has a bunch of pros and no cons'. 4) and if that's really the position, then you objectively aren't leaving room for others preferences as preferences 5) which is why IMO there is always such intense pushback on this topic.
Yes they did! They decided to try and kill the Orc, and the corresponding action resolution system was employed to find out if they achieve their goal.
They did not make the decision that on a success they would kill the orc, they didn't even make the decision that on a success they would hit the orc and harm it (taking away some hp). The failure stake in this orc example is also system decided, on a failure you miss. The system, independent of the player decided all of these stakes.
What the player did was decide to attack the Orc because they knew the stakes the system set. Their 'hope' for a specific outcome didn't factor into the resolution process at all.
(If you want to go back to first cause the players deciding to play a game where the system has these stakes could be framed as the players deciding those stakes by virtue of deciding to play this game, but even that's ultimately different than deciding to play a game where they get to decide the stakes [or the success part of the stakes] on the fly).
Contrast to the runes, the player did decide that on a success what the runes would be. The GM decided or will decide (depends on specific system implementation) on a failure what the runes will be (with the constraints that whatever they decide must be negative for the PC's, related to the PC's and also push the game forward). Thus the players 'hope' for a specific outcome factors into the resolution process as the result on a success, whereas in the orc example, the 'hope' has no effect on resolution process. (Similar could be said about the failure state involving the constraint that it must be 'related to the PC's' and the failure states independence in the Orc example).
This is the part that conflicts with simulation play, something i think you've readily admitted even very recently in this very thread.
For some reason, some posters - maybe you among them? - seem to me to not be able to identify the difference between the
rune reading and the
Orc killing case.
Here it is again:
*In the Orc-killing case, (i) the player's roll causes everyone to agree the Orc is dead, and (ii) in the fiction the PC kills the Orc;
*In the rune-reading case, (i) the player's roll causes everyone to agree that the runes reveal a way out, but (ii) in the fiction, the PC does not cause the runes to say what they say.
I don't disagree with those assessments. But that doesn't make the scenarios the same. There are important details you are eliding in this framing that I and others keep on pointing out.
Those details are specifically around how the stakes of the roll are determined and ultimately how players setting those stakes impacts the simulation.
It's not a quibble. As per what I just posted, you can't follow what is going on if you don't separate the two things.
IMO there's a 1 to 1 mapping between the players action declaration and the characters action. Because that 1 to 1 mapping exists, then saying the players action declaration does X is the same thing as saying the characters action does X. Since you cannot have 1 without the other then either can be accurately described as the cause if one is.
And the point is in fact bigger than that, and goes to something that I and moreso
@Campbell have been posting about for some time now: the failure of some other posters - including you? - to take other sorts of play on their own terms. In your play, which assumes the correlation of (a) and (b) above, the distinction can be ignored. But in the play I'm describing, it can't be - because it is ignored, nonsense conclusions will be drawn, like
the runes are quantum runes until read or that
the PC causes the runes to say what they say.
Again, I have no problem with you playing the way you play. There's plenty of pros to it. All I'm saying is that there are cons as well. Can you admit there are some non-trivial cons to it? I even agree the principles rule out quite a few of the hypothetical examples (but that's because we are exploring the general technique of fail forward and not the specific implementations). But I'm also fairly certain that with a full understanding of the principles that there would be hypothetical example that could be constructed to illustrate similar points in less outlandish ways. So focusing on 'bad hypotheticals' without offering the information needed to correct them isn't great for the discussion either.
Like the most egregious example of what we mean is the rune example from actual play. Your point is that well the player cannot actually put success stakes for anything imaginable due to the principles of the game. Awesome! But that doesn't rule out them potentially establishing a diverse variety of success stakes. Like your runes revealed a way out. What if instead the player hoped the runes would teleport them to another location. Or that the runes were a spell of such power that they would blow a hole out of their current location. Or etc. So yea, it cannot literally be anything, but from my perspective that kind of misses the point.
Yes, I know. That's my point: you are like a go player looking at a game of draughts, and complaining that the pieces are on the squares rather than on the points; or a canasta player looking at a game of bridge and complaining about the way hands are dealt and played.
Right, so why would a narratvist player like yourself ever complain about the way a game of D&D is played?
This repeated insistence that everyone's RPGing must make sense through the lens of a rather narrow approach to play, that you know is not applicable to the episode of play that you're trying to comment on, is just bizarre.
Again, this thread turned sharply toward 'fail forward' in D&D. The lens of the narrow approach to D&D play is certainly applicable here. What's bizarre is trying to treat this conversation as one about 'narrativist games on their own terms'.