The current narrative systems prototype Shakespeare has been somewhat disappointing so far: the director switches, seemingly erratically, between 5-6 different plot threads, and nothing seems coherent. I need a way of (a) allowing the player to influence story pacing / scope, and (b) a way for the system to push back, to try to force some story pacing / scope.
For this, I'm looking at how improvisational comedy generates and upholds structure. You might've heard that improv is about "always saying yes," but there's a lot more to it, apparently.
Specifically, longform improv comedy involves actors cooperating to "find the game" -- to find the core of a joke. Each actor makes "offers" to expand upon a premise and move action forward, hopefully toward a funny destination, and usually, actors err on always accepting offers ("saying yes") and building upon it since "blocking" offers frustrates your scene partners. However, it's very possible to "say yes" to a premise while still "blocking" the "game."
Here's an explanation from an NYC improv comedy personality, Will Hines:
What if we frame interactive narrative as the process of negotiation about a shared reality AND the significance of that reality?
We now need a structure for this negotiation. Longform improv comedy provides us with "The Harold," which on a high-level, is about giving space to explore a scene and "find the game." It is basically a series of improvised interspersed with "group games" that discourage plot continuity and encourage thematic continuity instead. Some situations will live throughout the entire act as a recurring motif / pattern, while others will prove to be dead ends and they'll be dropped within the first few minutes when no one can find anything really funny about it. Plot holes are frequent because plot isn't really the point if no one cares about it. (If ludonarrative dissonance is utterly pervasive in a game, does that mean it's no longer dissonant?)
... which is sort of at odds with Shakespeare's design goals, that precisely emphasize plot as a governing principle of narrative. But I think I can make it work anyway.
So now I'm planning to design / implement these general changes to Shakespeare:
- There will be periodic lulls when less will happen, but the player can freely stage characters and interact with things.
- All throughout, Shakespeare will watch which story concepts get invoked most often, and then run plot threads that focus on those concepts more. Sometimes Shakespeare will "push back" and offer totally random threads too.
- Only 2-3 plot threads can run at a time. Each plot thread is "sustained" for a short period before focus can change to another plot thread. Sometimes the focus won't change, if the player is really fascinated by the offers.
- Condense the plot thread / stage / concept hierarchy into singular plot thread assets.
- Blocked plot threads will be dropped, but get a brief callback in the end.