Not long ago, our gaming group tried out Wilderness of Mirrors for the first time. This was also one of our first sessions with improvisational, narrative roleplaying. The premise was the following: In our long going Star Wars Dawn of Defiance-campaign, one of the players have a subplot which includes a long lost sister.
To further that plot, we decided to play out a rescue mission. Not with our regular characters, but with a group called the Antarian Rangers. Also, since we like to try out new games at times (and have talked about some more narrative gaming for a while), we decided to use the Wilderness of Mirrors game by John Wick. This game can be found here: Wilderness of Mirrors [PDF] and a there is also a lengthy discussion about it on rpg.net on this thread
To sum it up, WoM is an agent-style game where you play your Jason Bournes and James Bonds. It is also a narrative, low-preparation game. Basically, the GM gives you a basic premise (Break in and rescue the diplomat, for instance) and then the players start to plan that rescue. When planning, the players can add things like "in order to take out those guards, we need a stun grenade" or "and when we enter that corridor, we have to hack the computer to shut down the weapon turrets". This way, the players build the adventure themselves. For each fact, the group get's a bonus die to add to their rolls when needed.
When the planning is done, the game starts, and together the GM and the players have the plan and the obstacles to use as the adventure. One important point is that skill-rolls don't actually decide if you succeed with an action or not, but rather, it decided who has narrative control. Even if you fail a roll, you might still succeed with the skill-check but the GM has the right to narrate what happens (which might include both good or bad things).
There is also an option in the game to add in negative stuff for other players (since betrayal and trust are major issues in agent movies), and this let's you get more dice. We didn't use that rule since we felt it didn't fit with the setting. However, in retrospect I have some thoughts on that. More on that later.
It should also be said that while all the players are experienced roleplayers, there is a varying degree of experience with more indie-type games.
When the GM told us to start planning, it did take a while for us to get into it. I'm guessing this is a matter of us being unused to the premise. However, after a while ideas where coming from all over the place. If there was one tendency it was to identify problems and then try to solve them in a fairly linear fashion. There wasn't so many ideas that introduced major obstacles or detours from the from-A-to-B-plot. I'm not saying this is a bad thing, but rather that it's a leftover from years of problem solving gaming.
The game itself went rather smoothly. As before, it felt a bit odd at times, and to some extent it was kept in the problem solving tradition. Basically, roll the dice, and if you roll good, you succeed with what you wanna do with no extra details around it. Now, it wasn't dull or plain, but I think that with some more experience in these kinds of games, we could have added more details and excitement to it ourselves.
There you have the next key-word: Excitement! Somehow, it didn't feel exciting, or as exciting as other games can do. To some extent I think it is a result of us as a group covering all bases with maxed attributes, but I also think that playing this kind of game with a problem-solving mindset is sub-optimal. It is to easy to "win".
So, you have to add that excitement yourself in one way or the other. We could have been better at this (again, I think it comes down to lack of experience) and added small tidbits ourselves. For instance, when we as players succeed with a roll, we have full narrative freedom. We can choose to make it easy for us (just say that we manage to do what we want) or to make it hard for us ("Yes, I shoot the masked Sith Inquisitor. However, when he falls to the ground his mask falls of, and I see that it's only a droid. It's a trap!!").
This is where I think the betrayal mechanic could come in handy. Perhaps not as betrayal as such, since that would be a bit out of genre, but as "Dark Side"-temptation-dice or something like that. There should perhaps be a limit to this, but basically, when I have narrative control, I should be able to add in something that makes it worse for me, another character or the group as such, and then get another bonus die. This way, another element of uncertainty is added to the game.
So, to sum up:
To further that plot, we decided to play out a rescue mission. Not with our regular characters, but with a group called the Antarian Rangers. Also, since we like to try out new games at times (and have talked about some more narrative gaming for a while), we decided to use the Wilderness of Mirrors game by John Wick. This game can be found here: Wilderness of Mirrors [PDF] and a there is also a lengthy discussion about it on rpg.net on this thread
To sum it up, WoM is an agent-style game where you play your Jason Bournes and James Bonds. It is also a narrative, low-preparation game. Basically, the GM gives you a basic premise (Break in and rescue the diplomat, for instance) and then the players start to plan that rescue. When planning, the players can add things like "in order to take out those guards, we need a stun grenade" or "and when we enter that corridor, we have to hack the computer to shut down the weapon turrets". This way, the players build the adventure themselves. For each fact, the group get's a bonus die to add to their rolls when needed.
When the planning is done, the game starts, and together the GM and the players have the plan and the obstacles to use as the adventure. One important point is that skill-rolls don't actually decide if you succeed with an action or not, but rather, it decided who has narrative control. Even if you fail a roll, you might still succeed with the skill-check but the GM has the right to narrate what happens (which might include both good or bad things).
There is also an option in the game to add in negative stuff for other players (since betrayal and trust are major issues in agent movies), and this let's you get more dice. We didn't use that rule since we felt it didn't fit with the setting. However, in retrospect I have some thoughts on that. More on that later.
It should also be said that while all the players are experienced roleplayers, there is a varying degree of experience with more indie-type games.
When the GM told us to start planning, it did take a while for us to get into it. I'm guessing this is a matter of us being unused to the premise. However, after a while ideas where coming from all over the place. If there was one tendency it was to identify problems and then try to solve them in a fairly linear fashion. There wasn't so many ideas that introduced major obstacles or detours from the from-A-to-B-plot. I'm not saying this is a bad thing, but rather that it's a leftover from years of problem solving gaming.
The game itself went rather smoothly. As before, it felt a bit odd at times, and to some extent it was kept in the problem solving tradition. Basically, roll the dice, and if you roll good, you succeed with what you wanna do with no extra details around it. Now, it wasn't dull or plain, but I think that with some more experience in these kinds of games, we could have added more details and excitement to it ourselves.
There you have the next key-word: Excitement! Somehow, it didn't feel exciting, or as exciting as other games can do. To some extent I think it is a result of us as a group covering all bases with maxed attributes, but I also think that playing this kind of game with a problem-solving mindset is sub-optimal. It is to easy to "win".
So, you have to add that excitement yourself in one way or the other. We could have been better at this (again, I think it comes down to lack of experience) and added small tidbits ourselves. For instance, when we as players succeed with a roll, we have full narrative freedom. We can choose to make it easy for us (just say that we manage to do what we want) or to make it hard for us ("Yes, I shoot the masked Sith Inquisitor. However, when he falls to the ground his mask falls of, and I see that it's only a droid. It's a trap!!").
This is where I think the betrayal mechanic could come in handy. Perhaps not as betrayal as such, since that would be a bit out of genre, but as "Dark Side"-temptation-dice or something like that. There should perhaps be a limit to this, but basically, when I have narrative control, I should be able to add in something that makes it worse for me, another character or the group as such, and then get another bonus die. This way, another element of uncertainty is added to the game.
So, to sum up:
- This kind of game requires some experience to run smoothly
- It also requires some creativity and a mindset that it's not about problem solving, but finding interesting stories
- Adding excitement can be a bit hard. In a game with more rules (D20 or similar) you can always fall back on the rules and die-rolls to add some excitement, but in these kinds of games, excitement have to be based on story and events.
- Using some kind of "players as micro-opponents"-mechanic (be it Trust-dice or something else) is a good thing. Just as the players build the module in the planning stage, they can also add nasty and interesting side-effects in the actual game.