Reply to thread

Message: <blockquote data-quote="Indaarys" data-source="post: 9507754" data-attributes="member: 7040941">The issue is due to the nature of Moves. If a Move imposes something in the fiction that you didn't actually want to do, the game has to stop to hash that out. Go Aggro as a go-to example doesn't allow for the nuance that a character could be perfectly willing to kill someone and could even go through the motions to do so, but still choose not to for one reason or another. If Go Aggro has been triggered as a result of doing this, and you roll 10+, you're killing somebody, or least maiming them severely, and the game literally tells you can't take it back.To get over the hiccup you have to either ignore the trigger so you can just dictate what happens, or you disrupt the game and have a negotiation over what happens. Neither is particularly ideal, as the latter can be unwelcome and the former makes the Move superflous if we're just going to ignore it like that.A lot of the issue with that specific example could be fixed by just deleting that stupid ass line, but even without it its still the same kind of dynamic being produced, just not as severe, in the other outcomes of the Move.</blockquote>