Stitch – Spodley
Master: Iain McAllister
Team: Gregory Malkovich, Soldier - James
Alex Stepovich, Engineer - Janos
John Parish, Soldier - Claire
Alexander Khruschev, commander - Andrew
Overview:
Stitch is a game that I wrote for Game Chef 2007 and though it didn’t win, I am still very proud of what I managed to do in such a short space of time. I used the spodley event to give it its first playtest and was very happy with the way things turned out.
There is a problem with this AP, and I know that even before I write it. Stitch is a game based on causing the players to experience a sensation of stress and pressure. To do this is uses a system based on the amount of time passed in the individual events the team travels to. This is impossible to convey in an AP but I will try and relate how everyone reacted to it.
Report:
I sat down to this playtest feeling nervous and apprehensive. This was mainly due to the fact that it had not been playtested by anyone outside my own head since Game Chef and that I hadn’t even looked at it since then.
We took it slowly, partly so I could re-familiarise myself with the logic behind my design. Each player takes on the role of a Stitch team member and as such has a set of 3 skills ranked at 5,10 and 15. They also have 3 responsibilities ranked the same way. Last but not least they take a belief package with 3 beliefs ranked in the same way.
In total the character creation took about 15 mins which I was really pleased with.
I then set to explain the mechanics which is where I started to build the tension. When you enter a knot, a collection of events, you get 30 mins before you ‘quantum leap’ out of it again. When you want to do something the Master can call for a test which means you compare your skill against the minute value. Higher means you pass, lower means you fail. Beliefs and responsibilities are brought in back and forth by player and Master to raise and lower the skil value, all the while the clock is ticking. Argument just causes you to fail!
I explained all this to the players making clear, several times, that I would not, unless someone was actual dying, stop the clock.
The players then set about planning their jump. We were just going to do one event to test if things work. They played off the sketchy nuclear Armageddon described in the book and the first Knot consisted of the following events:
Physicist who creates the nuclear quantum bomb is born
They decide to do some crazy baby swapping at the hospital where he is born.
China enters trade negotiations with America after expanding to be the biggest economic power
Planting some false evidence about secret CIA operations by giving it to one of the translators for the Chinese delegation.
Future Russian leader Nikolay Sergeyev graduates from Princeton
They go back and change his records so that he fails and doesn’t graduate.
Once they had planned the mission, I sketched out a few things to throw in their way and then hovered my finger over the button of the timer. There was a genuine sense of tension round the table before I hit the button which was fantastic. I then counted them down…..5….4…..3…..2…..1….launch.
They pelted out of their ship and into the university, heading for the records department. Dealing easily with a couple of security guards along the way they set their engineer to falsifying records. After dealing with a couple of more security guard problems they made their way back to the ship and jumped to the hospital.
Their was a definite sigh of relief and then they were into the next event. The GM has to be a bit of a bastard in this game, providing a lot of problems. They arrived at the hospital to find it was under quarantine. Putting on their hazmat suits they made their way in, almost falling at the first hurdle as paramedics insisted on seeing their ID. Moving down through the hospital they made their way to the maternity ward and found the child.
Making their way out of the building they found themselves amongst panic and the police. Quickly swapping the child’s name tags the team made their way back to the ship and jumped to the next event. This was going to be the hard one as about 15 minutes had now passed.
They jumped to a point where they could speak to the interpreter alone pushed the evidence into his hands after much persuasion and jumped.
What was great
Throughout the event everyone was crouched over the table, panicked and speaking quickly. It was fantastic. The system really gave a feeling of stress and panic.
The system worked very well for a first time out.
What didn’t work
I had a mechanic whereby people got hindrances and benefits for failing and succeeding at a given task. This could not be more unnecessary.
I had to make notes on what each player’s beliefs and responsibilities were so I could throw them out but had no in game facility to do that i.e. no sheet provided.
Some belief packages are just crap and need changed. Something along the lines of one positive, one negative and one neutral.
What needs added
A list of common actions and the time they will take. Something like 30, 1 min, 1:30 and 2 min actions. Anything else can be assumed to take as long as it takes to describe.
Advice on the Gm for how many problems to throw in the face of the players per event. Advice on how to build tension. Expansion of the time travel info and make it look more like a document.
What equipment the team had came up a couple of times so that needs addressed.
Review:
All in all the game went really well and I was delighted how stressed I had managed to get the players feeling over their mission. They actually felt relieved at the end but enjoyed how the tension had been racked up as the game progressed. This game is going to see light of day, and I am looking forward to running it again in the not too distant future.
