Road to Collaborative Storytelling #4: The Turing Project (Patreon)
Content
Picking up from last week, around the time I was working on Legendary, two other things were going on. First, Beth ran a Buffy the Vampire Slayer game for something around two years. Second, I started working on The Turning Project. Both of these revealed the gaming possibilities when not only the Storyteller becomes collaborative but when the players do so as well.
Buffy was the first media adaptation TTRPG I played for a significant length of time and the only one I've played that managed to consistently model its source material through its mechanics. Like a lot of games I've played since, it had a narrative control mechanic (drama points), but it was a beefy one - no "get a small bonus to a roll" stuff. At its base, you could spend a drama point to heal half the damage you had taken so far (which you could apply multiple times and reflexively), end a scene in a way that didn't get you what you wanted but ensured no one got beaten up further (handy for when you picked a fight with something that turned out to be way too powerful for you), or come back from the dead with narrative consequences (the plot point cost was discretionary; 1 plot point meant you'd come back eventually, while 20 plot points meant you could come back the next turn). As I recall, you could also get a large bonus to a single roll or a beneficial plot twist.
You know that thing where a GM rolls behind a screen so that if a roll would kill someone in a boring way or would result in an antagonist looking completely stupid, they can overrule it? Drama points were powerful enough to let the players do that in a limited way. This enabled a lot of scenery chewing antics, which was in keeping with the tone of the show.
It didn't hurt that all the players had watched at least a season or two of Buffy, so we all knew what the game should feel like. Moreover (and this is the important part), we leaned into the genre's tropes hard - a mix of action, interpersonal drama, and comedy. Succeeding gloriously (often with the help of drama points) was great, but so was doing reckless, dangerous, or stupid things that would come back to bite you (and possibly everybody else) later. The spirit of cooperation between players and GM made that game way more successful than it would have been otherwise.
The Turing Project (which for the longest time was simply known as Android) was an offshoot of my work on PARANOIA. When Mongoose moved the game's writing in-house, a bunch of the freelancers who had been working on the game got together to brainstorm game ideas to work on instead. Android was my pitch - a game where half the players were androids in an interplanetary (but not yet intergalactic) setting where they were sent on missions (ranging from rescue and recovery to espionage and assassination) and the other half were their human controllers who worked for various corporations. Yes, I had been exposed to Wraith by this point.
The androids were AIs sleeved into bodies (shells) chosen by the controller (who allocated points of attributes based on the mission). Shells also had Patents, which were special abilities that reflected the corporation that owned them. Controllers also issued and prioritized commands that their androids had to obey. In addition, the controllers had various kinds of access and could create complications for enemies or plot twists to benefit the mission, their employers, or themselves. The controllers were therefore rivals and earned XP through a combination of doing what the military (whom they all worked for) and their employers wanted.
The androids were self-aware and had things they wanted, but they were also bound by their commands. They had a Processor represented by a line of eight coins, which could be manipulated in various ways to control when they succeeded. They developed Glitches, which gave them ways to manipulate their code in various ways (swapping the priority of commands, modifying them, or using their Software Attributes to enhance the Hardware Attributes of their shells). They earned XP (Drift) for achieving mission objectives (whether corporate or military) and pursuing personal goals.
This set up a dynamic where half the players were rivals of one another (but they couldn't let their rivalry cause shared missions to fail) and nominally controlled the other half, while the other players had no reason not to cooperate with one another but had every reason to buck the control of the other half. This intentionally antagonistic relationship between characters meant that if the players couldn't separate themselves from their characters the game would be a disaster for OOC interpersonal relationships. The split roles also meant that one player's absence could render another player largely irrelevant.
Hey, even Famous Game Designers (to borrow the tongue-in-cheek gag from PARANOIA) can make silly mistakes.
Later versions removed the split roles (among many other refinements). The players were the androids but could also negotiate with their controllers to manipulate the mission zone to send reinforcements, create distractions, or do any number of other things that I gleefully plundered for the conspiracy actions in The Devoted Companion. Waste not, want not.
The Turing Project never made it to press. The freelance group broke up not long after I started working on the first draft, and although I tinkered with it whenever I wasn't tinkering with Legendary, as one more unknown name in a sea of indie game designers (I had all of two writing credits), I had trouble finding an audience (or even playtesters).
At this point, I was pretty set in my collaborative ways, and although these weren't the last games I played, wrote for, or developed, they were formative experiences for me as a player and GM and would have an outsized influence on me as a game designer.