I recently read a book that's been on my shelf for a long time. Backwards and Forwards: A Technical Manual for Reading Plays by David Ball is a step by step approach to script analysis. As I've stated before, script analysis is a useful tool when looking at board game design. Crafting a good story is important not just in the lore of a game, but also within the emergent narrative of gameplay itself. Today, I'm summarizing some of the main points in Backwards and Forwards and applying them to board game design. Quotes in italics are excerpts from the book.
On Actions
"Action occurs when something happens that makes or permits something else to happen." (p.9)
Backwards and Forwards begins with an analysis of what constitutes an action. Actions are caused by triggers (the first event) and result in heaps (the second event; the result of the action). An action requires two events in order to be an action: a cause and a result. In board games, we can use this definition to cover game actions and narrative actions. Mechanically, each action has to have a reason to occur (the trigger) and an effect (the heap). Players should feel that the mechanics are connected and do not simply occur unconnected from the rest of gameplay. Narratively, actions should feel motivated by the story. Players should understand why two characters are trying to kill each other (the trigger) and what the result will be if one succeeds (the heap).
"Each trigger leads to a new heap. (Each event causes or permits a second event.) ...But now the heap, the second event, becomes a trigger: a new first event of a new action." (p.12)
Each action must make sense and progress to future actions. Players should be able to see a clear line of their choices during gameplay that leads to their success or failure. In themed games, mechanics must progress the story as well as the game. A mechanism might work well but still feel out of place due to the theme.
"Only when we look at events in reverse order can we see, with certainty, how the dominoes fell, which fell against which." (p.15)
Once there is an end to your game, narratively or mechanically, work backwards to ensure every action serves that end. This prevents parts of the game not directly connected to the win condition from proliferating. Additionally, you can avoid having the early parts of gameplay feel rote or unnecessary by working backwards through your game and stopping where the actions stop being meaningful.
On Narrative
"First the playwright presents the world in stasis....And for a play to begin, there must be an intrusion....Stasis comes about at the close of the play when the major forces of the play either get what they want or are forced to stop trying." (pp.19, 20, 21)
Each action has a cause, a reason for that action to be taken. Which means the first action in a game must have a reason for occurring. The story must have a reason to begin. Any lore before the game starts must make sense within the context of the beginning of gameplay. If the lore feels unrelated to the beginning stage of gameplay, players will not understand why they are playing. Ideally, exposition should describe the state of the world just before the first action in a game. Similarly, a game's ending should make sense. Victory points are fine, as long as there is a reason the game ended when it did (such as a time track, etc). Ideally, the intrusion that starts the narrative rolling should be related to when and how the story ends. Note: if the lore of what happens before or after the game sounds more fun that the actual gameplay, players will feel cheated. The most interesting parts of the story should occur during gameplay. Otherwise, you are including a companion short story/novel not lore related to the game.
"Dramatic conflict...is the force that drives the play from action to action." (p. 31)
"[A] play's conflict is between what someone wants and what hinders the want: the obstacle." (p. 28)
Any game with a goal and an obstacle has conflict. This is different from violence or aggression. If a game causes players to overcome obstacles, even if it is non-competitive/non-scoring, it has conflict.
There are four types of conflict:
"1. Me against myself. 2. Me against other individuals. 3. Me against society. 4. Me against fate, or the universe, or natural forces, or God or the gods." (pp. 30, 31)
Conflict in games looks like player vs. player, one vs. all, player(s) vs. game, etc. Other types of conflict could include players vs. time, or even players vs. having to be creative under pressure. Make sure that the conflict present in your game is the conflict you intended. Do this by examining the goals and obstacles in your game. There will be many different types of conflict, varying by the variety of mechanical and thematic actions in the game. Some of the types of conflict present may not feel right in the overall context of the game. By examining your conflicts, you can identify which are outside the intended experience of the game.
"A forward is anything that arouses an audience's interest in things yet to come." (p. 45)
"A forward is any of a myriad of devices, techniques, tricks, maneuvers, manipulations, appetizers, tantalizers, teasers, that make an audience eager for what's coming up." (p. 46)
"Sometimes the promise of the forward is not fulfilled.... [T]he effect of the forward is the same: the audience has been maneuvered into paying close attention." (p. 57)
Any action, event, phase, or resource not available at the beginning of the game should be used to increase player engagement by keeping them excited for what's to come. Space Base's multi-tier market is a great example of this. Players can see expensive items long before they can buy them. These elements can help build tension through to the end of the game. A good game should tell an interesting story (even if it's an abstract game).
"Not only do forwards keep us interested, but forwards focus attention where the playwright wants it." (p. 47)
By holding some things back, designers can redirect the attention of the players to certain strategies or narrative events. Timing is important not just from a balance standpoint but from an emergent narrative one.
"[C]haracter in drama is revealed in one way: action, that which a person does—deeds." (p. 60)
"Action results from what a character does to get what he or she wants (motivation) in spite of obstacles." (p. 62)
"Description must be validated by examination of action." (p. 63)
I don't care how much you insist on a particular narrative in your lore, if it's not born out in gameplay it's not the actual story of your game. For instance, I am a big fan of Scorpius Freighter. The lore states that the players are smugglers. The game plays like 'trading in the Mediterranean in space.' The 'bribes' could easily be taxes. Other than flavor text, no part of the gameplay indicates that what you are doing is illegal. Perhaps the smuggler theme is more desirable from a marketing standpoint, but from an artistic view, it feels pasted-on. Honestly, most games are guilty of this on some level. In which case, any game that bucks the trend and matches a lore description to gameplay experience will automatically be ahead of the curve.
Honestly, there's more I could go into, but that's enough for this post. Check out the book if any of this intrigues you.
Backwards and Forward by David Ball is available here.
On Actions
"Action occurs when something happens that makes or permits something else to happen." (p.9)
Backwards and Forwards begins with an analysis of what constitutes an action. Actions are caused by triggers (the first event) and result in heaps (the second event; the result of the action). An action requires two events in order to be an action: a cause and a result. In board games, we can use this definition to cover game actions and narrative actions. Mechanically, each action has to have a reason to occur (the trigger) and an effect (the heap). Players should feel that the mechanics are connected and do not simply occur unconnected from the rest of gameplay. Narratively, actions should feel motivated by the story. Players should understand why two characters are trying to kill each other (the trigger) and what the result will be if one succeeds (the heap).
"Each trigger leads to a new heap. (Each event causes or permits a second event.) ...But now the heap, the second event, becomes a trigger: a new first event of a new action." (p.12)
Each action must make sense and progress to future actions. Players should be able to see a clear line of their choices during gameplay that leads to their success or failure. In themed games, mechanics must progress the story as well as the game. A mechanism might work well but still feel out of place due to the theme.
"Only when we look at events in reverse order can we see, with certainty, how the dominoes fell, which fell against which." (p.15)
Once there is an end to your game, narratively or mechanically, work backwards to ensure every action serves that end. This prevents parts of the game not directly connected to the win condition from proliferating. Additionally, you can avoid having the early parts of gameplay feel rote or unnecessary by working backwards through your game and stopping where the actions stop being meaningful.
On Narrative
"First the playwright presents the world in stasis....And for a play to begin, there must be an intrusion....Stasis comes about at the close of the play when the major forces of the play either get what they want or are forced to stop trying." (pp.19, 20, 21)
Each action has a cause, a reason for that action to be taken. Which means the first action in a game must have a reason for occurring. The story must have a reason to begin. Any lore before the game starts must make sense within the context of the beginning of gameplay. If the lore feels unrelated to the beginning stage of gameplay, players will not understand why they are playing. Ideally, exposition should describe the state of the world just before the first action in a game. Similarly, a game's ending should make sense. Victory points are fine, as long as there is a reason the game ended when it did (such as a time track, etc). Ideally, the intrusion that starts the narrative rolling should be related to when and how the story ends. Note: if the lore of what happens before or after the game sounds more fun that the actual gameplay, players will feel cheated. The most interesting parts of the story should occur during gameplay. Otherwise, you are including a companion short story/novel not lore related to the game.
"Dramatic conflict...is the force that drives the play from action to action." (p. 31)
"[A] play's conflict is between what someone wants and what hinders the want: the obstacle." (p. 28)
Any game with a goal and an obstacle has conflict. This is different from violence or aggression. If a game causes players to overcome obstacles, even if it is non-competitive/non-scoring, it has conflict.
There are four types of conflict:
"1. Me against myself. 2. Me against other individuals. 3. Me against society. 4. Me against fate, or the universe, or natural forces, or God or the gods." (pp. 30, 31)
Conflict in games looks like player vs. player, one vs. all, player(s) vs. game, etc. Other types of conflict could include players vs. time, or even players vs. having to be creative under pressure. Make sure that the conflict present in your game is the conflict you intended. Do this by examining the goals and obstacles in your game. There will be many different types of conflict, varying by the variety of mechanical and thematic actions in the game. Some of the types of conflict present may not feel right in the overall context of the game. By examining your conflicts, you can identify which are outside the intended experience of the game.
"A forward is anything that arouses an audience's interest in things yet to come." (p. 45)
"A forward is any of a myriad of devices, techniques, tricks, maneuvers, manipulations, appetizers, tantalizers, teasers, that make an audience eager for what's coming up." (p. 46)
"Sometimes the promise of the forward is not fulfilled.... [T]he effect of the forward is the same: the audience has been maneuvered into paying close attention." (p. 57)
Any action, event, phase, or resource not available at the beginning of the game should be used to increase player engagement by keeping them excited for what's to come. Space Base's multi-tier market is a great example of this. Players can see expensive items long before they can buy them. These elements can help build tension through to the end of the game. A good game should tell an interesting story (even if it's an abstract game).
"Not only do forwards keep us interested, but forwards focus attention where the playwright wants it." (p. 47)
By holding some things back, designers can redirect the attention of the players to certain strategies or narrative events. Timing is important not just from a balance standpoint but from an emergent narrative one.
"[C]haracter in drama is revealed in one way: action, that which a person does—deeds." (p. 60)
"Action results from what a character does to get what he or she wants (motivation) in spite of obstacles." (p. 62)
"Description must be validated by examination of action." (p. 63)
I don't care how much you insist on a particular narrative in your lore, if it's not born out in gameplay it's not the actual story of your game. For instance, I am a big fan of Scorpius Freighter. The lore states that the players are smugglers. The game plays like 'trading in the Mediterranean in space.' The 'bribes' could easily be taxes. Other than flavor text, no part of the gameplay indicates that what you are doing is illegal. Perhaps the smuggler theme is more desirable from a marketing standpoint, but from an artistic view, it feels pasted-on. Honestly, most games are guilty of this on some level. In which case, any game that bucks the trend and matches a lore description to gameplay experience will automatically be ahead of the curve.
Honestly, there's more I could go into, but that's enough for this post. Check out the book if any of this intrigues you.
Backwards and Forward by David Ball is available here.
No comments:
Post a Comment