Dealing with uncertainties

Let me break Kayfabe for a moment, don’t worry it should not happen often.

As you probably know by now (if you read the rest of the posts), we are currently playing a game called Night’s Black Agents (NBA) by Kenneth Hite (see Pelgrane Press Site) based on the GUMSHOE system by Robin D. Law. And if you look at my first post you will see some of the reasons (I could/should have gone in more details then) why I like the GUMSHOE system so much.

The reason I break Kayfabe today is due to an event that happened in our last game. In short I was planning to have the Agents (PC in the world of NBA) attacked by some Nigerian pirates off the coast of Cyprus. In my mind this was pretty set as a combat encounter, the players would deal with the threat and go on to the actual operation knowing that the bad guys were really pissed off. Using the NBA system to its core a player managed to stave off the threat by “creating” a Nigerian contact and asked if he would be on the boat by any chance.

Now as most gamemasters probably know, this is really hard to deal with, even after reading “Play Unsafe” by Graham Walmsley, it can be daunting to venture in the unknown of letting other people add and create “unlicensed content”. I’ve got this comment from one of the other player in the very same game, a player with many years of role-playing experience. She was of the impression that giving that much control of game content to players would only results in problem.

Looking at it more deeply later on, I think what she was saying was that letting the inmates run the asylum would be probably break the rest of the game planning. That got me thinking on the medium itself, role-playing, and the games that form the rule structure that allows us to tell stories. She was right that letting players have that much control over creative content would break many story based medium but not all, and should never ever break role-playing. Role-playing is not a single person affair, it’s not story telling, it’s story making.

Going back a few years, for you youngsters imagine a world without the internets. Roaming the Bulletin Board Systems (BBS) we often created stories on forums called “Neverending Stories”, a never ending story was started by any forum dweller. In which they wrote about a page of text,  the next post coming from someone else took the story to yet another unknown location. To be able to write these you needed to take whatever was given and take to its next step.

Going back to most tabletop role-playing games I’ve played in the past, both as a GM and player (see the distinction here), player inputs has been mostly regarded with amusement or in the extreme case disinterest. First and foremost because any player suggestion of this kind could risk breaking the game master  / storyteller story. I have been guilty of not letting player input in my games, looking back this is pretty sad. It was me, I figure I am not alone here, confusing the medium. Role-playing and story based gaming are not story telling. Now that would break traditional gaming (board and computer alike) flow, but role-playing and improvisation will not break, they should even be strengthen by these types of players input.

The problem at that point is not an issue of player input, or even breaking the story arc, it’s confusing the medium. For several years we have approached role-playing as storyTELLERS and gameMASTERS which by definition implies some form of command, control and communication, the writers of these various games  perpetuated the problem by using these terms. Frankly it does not work. At least for me, and for some others I’ve seen, they let the title overpower everything else. Why is it so hard to deal with? As a game MASTER, I get to believe that I decide everything that comes up in the world. The world is my responsibility, any NPC actions, any events, anything. It also implies I am to be the sole provider of fun at the table, and if at the end of the night I was a bit off, then the players can blame me. In a game with five players, one of which in the GM, it means that 80% of the potential creative juice can blame the other 20% for not having a good time.

So most people responded in two ways, first they overworked their games, putting countless hours in designing completely railroaded sessions that would make sure that the players would find the story entertaining. Thus was reborn the dungeon crawl, disguised under the trope of Mage needs crew to retrieve artifact, crew does deed, gets screwd over by said mage, exposes/destroys evil mage, gets the tresor. We got this handed to us one way or another for the past 15 years, and since that’s all we got we took to it like junkies for one last hit.

The other more pervasive problem is that some players just threw their hands up and stopped/never tried to be gamemasters, gaming became/was hard. In my opinion Role-Playing should never be hard, it should just be fun. It should provide escapism for a moment, it should make me a boy playing with toy figures in the backyard inventing stories that only I knew the complexity and deepness of. When playing these crazy games in my backyard, most often with my brother, there were no real rules, just us inventing stuff on the fly, as needed and having a blast. Following this rather simple idea, please take a look at most modern RPG system character sheets, are they simple? They are black belt level mathematics, for a hobby. They transform ideas in formulas and then tell people that they can’t do stuff because the mystical rule set said so. For frak sake, dragons are flying around burning a village while the corrupt prince is accepting bribes from the barbarian tribes and the rules are telling a player that he can’t jump over a running horse while holding a torch to light the armory to destroy the fortified position of the corrupt prince, WAT?

At that moment creativity is destroyed, and the player becomes a passive participant. Might as well watch Law & Order. And I won’t talk about gaming session where some players are mostly reading through the rules to be able to do something that should be resolved organically at the table, by the player themselves and not some meta lawyer represented by an abstract rule set.

But “It is make believe, you can do anything you want” says the first time gamer at the table, while veterans sadly envying the innocence of the newly arrived recruit. The noob is right, we are wrong, the fact to the matter is, we are playing games to feel like kids, cops and robbers, cowboys and Indians, space dudes and aliens, we should be allowed/encouraged to dream impossible dreams, we should strive to offer the new players a mirage of reality instead of the harsh mathematical coldness of rules.

Reading the Fiasco companion foreword by Wil Wheaton, of Über Geek Fame, told us that Fiasco gave him a window to what role-playing gave him when it was fun… While I do agree with Mr. Wheaton on this, Fiasco is fun, Fiasco is role-playing at its core. I also believe that it should apply to any role-playing game.

I love role-playing because on the best of days, when I play,I feel like a young boy again, playing in the backyard with my brother, dreaming impossible dreams.

Conspiracy Goals

Shoot for the Stars actually contains two conspiracy leaderships, the criminal covert objectives of the Russian research group and the colonization objective of the Organism itself. The Tunguska organism objective is pretty clear; Using the spores already in the wild it is influencing the development of bio-warfare delivery technologies to insure that it can spread on Earth. To do so it uses the existing infected.

The criminal have more objectives but the are in a sense simpler to understand as they stem from the needs of power hungry humans. The campaign should focus on these objectives initially, only to reveal the organism truth at the end of the story.

Man of Tunguska Objective

  • Insure the survival of itself by spreading across the planet.

Russian Research Group Objectives

  • Harvest and Control the benefits of the S100A4 MR4 spores to create a new world order.
    • Recover the 3 remaining samples.
    • Recover the original research notes.
    • Recover the location of the Organism body.
    • Start new research projects
      • Hire or coerce the best biological experts in the world.
      • Develop better control mechanism to insure that the spores can be used on world leaders.
      • Develop a counter agent to limit the spread of the fungus.

Kyshtym disaster

The Kyshtym disaster was a radiation contamination incident that occurred on 29 September 1957 at Mayak, a nuclear fuel reprocessing plant in the Soviet Union. It measured as a Level 6 disaster on the International Nuclear Event Scale, making it the third most serious nuclear accident ever recorded behind the Chernobyl disaster, and Fukushima Daiichi nuclear disaster, both Level 7 on the INES. The event occurred in the town of Ozyorsk, a closed city built around the Mayak plant. Since Ozyorsk/Mayak (also known as Chelyabinsk-40 and Chelyabinsk-65) was not marked on maps, the disaster was named after Kyshtym, the nearest known town.

Shamelessly lifted from Wikipedia – Kyshtym disaster. (2013, May 1). In Wikipedia, The Free Encyclopedia. Retrieved 00:50, May 20, 2013, from http://en.wikipedia.org/w/index.php?title=Kyshtym_disaster&oldid=553051204

http://en.wikipedia.org/wiki/Wikipedia:Copyrights

S100A4 MR4 Dossier

Officer in Charge : Kapitan Nikodim Stepanovitch.

Project Start Date: September 21st 1946

Objective : Help wounded soldiers recover from fatal wounds and stem battlefield infections.

Kapitan Stepanovitch was a junior liaison officer during the first test trials on the Man of Tunguska, now one of the only living member of the initial project he was able to have the project re-activated. His expressed goal was to use the regeneration characteristics to augment the healing capabilities of wounded soldiers.

Project S100A4 MR4 was setuped in the city of Stalingrad with a discretionary budget and started clinical research on the frozen samples. While the research staff re-activated all the old protocols from the first project, Kapitan Stepanovitch went to work on the members of the Polit Bureau to re-acquire the body from Sevastopol bay.

Part of the political work done by Kapitan Stepanovitch was also to convince them that the project was to treat wounded soldiers and prevent infections from spreading in military wards. Nobody thought that the Kapitan would try to develop a longevity serum.

It took a whole year to get the body back in the Stalingrad laboratory. It seemed that the pressure was enough to keep the body from regenerating. 4 more years of research were required to discover that the body was starving for human blood. During that period it was also discovered that blood filtered through the body would gain regeneration characteristics. The only issue was that more they filtered blood through the vessel, faster it regenerated.

Fearing the consequences of passing to much blood through the body, it was decided that the 10 1cc. samples would be enough for further analysis, tissue samples were also taken and frozen. The analysis of the tissue samples enabled the research team to understand that the body was not coming back to life, but was only re-animated, as if the organisms was trying to mimic life. After further studies, spores were found to be slowly multiplying in the blood samples and tissue samples. The extremely toxic fungus like organism were discovered and isolated. Once isolated the spores started dying faster that they could reproduce as soon as they were put in the presence of sunlight or UV lights, this flaw prevented the mass usage of the spores for any military use.

The body went back in the lead coffin and was  immediately sent in deep freeze [Location Unknown]. From the 10 blood samples taken, 3 were injected to test subjects (political prisoners). It was discovered that a couple of weeks after the injections took place tests subjects started exhibiting the same characteristics as subject 0. Their strength, resistance to pain, wounds and infections was found to be increased tenfold, the only thing that seemed to have a controlling effect was to subject the patients to daily UV-light treatment.

The subject were also found to develop a thirst for human blood, tests from that period were not able to discover the root cause of this, only that it seemed to strengthen the organisms. Feeding them blood from other tests subjects even speed up the process of healing, even re-growing previously destroyed limbs in a couple of hours.

The research was completely abandonned when the test subjects started exhibiting extremely uncontrollable violent behavior, and went through complete system shutdown. Kapitan Stepanovitch and members of the research team were able to steal 4 of the remaining samples. They also created falsified research reports explaining that the research was a failure and that the samples were destroyed.

The stolen samples were injected to Kapitan Stepanovitch and to the lead scientists: Doctor Sorin Cimpeanuu, Professor Andrei Nikolaevich (Luciano Ruiz) and to Doctor Oleg Borodin. Following the project failure, the four members left the Russian armed forces, keeping in contact to one another.

Till 1957 the project dossiers were kept under wraps in a KGB data crypt under the Kremlin, the Kychtym incident gave KGB command the perfect location to securely store the last 3 remaining samples and all the projects notes. The conspiracy has been biding its time for a while, but recent developments in the field of biochemistry combined with DNA discoveries could mean that the Organism could be researched again. They are now trying to recover the location of the original research notes and the location of the body. 

Currently Infected

  • Nikodim Stepanovitch
  • Sorin Cimpeanu
  • Andrei Nikolaevich (Luciano Ruiz)
  • Oleg Borodin

The Tunguska event

The Tunguska event was an enormously powerful explosion that occurred near the Podkamennaya Tunguska River in what is now Krasnoyarsk Krai, Russia, at about 07:14 KRAT (00:14 UT) on June 30 [O.S. June 17], 1908.[1][2][3] The explosion, having the epicentre (60.886°N, 101.894°E), is believed to have been caused by the air burst of a large meteoroid or comet fragment at an altitude of 5–10 kilometres (3–6 mi) above the Earth’s surface. Different studies have yielded widely varying estimates of the object’s size, on the order of 100 metres (330 ft).[4] It is the largest impact event on or near Earth in recorded history.[5] The number of scholarly publications on the problem of the Tunguska explosion since 1908 may be estimated at about 1,000 (mainly in Russian). Many scientists have participated in Tunguska studies, the best-known of them being Leonid Kulik, Yevgeny Krinov, Kirill Florensky, Nikolai Vladimirovich Vasiliev, and Wilhelm Fast.[6]

Although the meteoroid or comet appears to have burst in the air rather than hitting the surface, this event still is referred to as an impact. Estimates of the energy of the blast range from 3 to as high as 30 megatons of TNT (13–130PJ),[7][8] with 10–15 megatons of TNT (42–63 PJ) the most likely[8]—roughly equal to the United States’ Castle Bravo thermonuclear bomb tested on March 1, 1954; about 1,000 times more powerful than the atomic bomb dropped on Hiroshima, Japan; and about two-fifths the power of the later Soviet Union’s own Tsar Bomba (the largest nuclear weapon ever detonated).[9]

The Tunguska explosion knocked down an estimated 80 million trees over an area covering 2,150 square kilometres (830 sq mi). It is estimated that the shock wave from the blast would have measured 5.0 on the Richter scale. An explosion of this magnitude is capable of destroying a large metropolitan area.[10] This possibility has helped to spark discussion of asteroid deflection strategies.

Shamelessly lifted from Wikipedia – Tunguska event. (2013, May 10). In Wikipedia, The Free Encyclopedia. Retrieved 00:43, May 15, 2013, from http://en.wikipedia.org/w/index.php?title=Tunguska_event&oldid=554515122

http://en.wikipedia.org/wiki/Wikipedia:Copyrights

Tunguska Dossier

In 1908 the Tunguska impact had more effect than believed until now.

After research by the Cheka in 1921, a body was discovered near the impact zone. The completely charred body was discovered to be Alejander Feidakin a Russian farmer that went missing a couple of months before the event, the scientist studying the body were baffled by the sheer fact that it had not been pulverized. The Moscow Cheka requested that the body be transferred to the central office.

After a broader analysis and many more tests, the body was found to completely resist decay, be it from abiotic or biotic decomposition. Further testing, using radiography equipment, showed that the body seemed to reconstructing itself in a completely autonomous way, Scientists and medical staff were baffled as to what process could be reverting the normal decomposition process, while keeping life-signs completely silent.

The Man from Tunguska was born. When the Cheka command was made aware of the results, it went in complete political crisis mode.

Internally, the command staff was divided, most high ranking officers, fearing possible contamination, advised caution and requested the body be destroyed immediately. Younger, brasher officers saw this as an opportunity for the advancement of their careers, by harvesting this regeneration process to help create better soldiers or even self-repairing armor. The crisis was so deep that it threatened to break the Cheka apart, to the pleasure of the other secret service branches. An agreement was finally reached, it insured that both camps would be able to save face. Without destroying the body, it was placed in quarantine and tissue samples were extracted to continue the research. The body itself was placed in a lead coffin, and sunk in the Sevastopol bay. The date was October 3rd 1925.

20 years later, following the staggering losses from WW2, the KGB and Polit bureau re-activated multiple research programs to help the soviet better face their enemies, they had to win the science race against their former ally, the United-States of America. One of these was Project S100A4 MR4, lead by Kapitan  Nikodim Stepanovitch.

Shoot for the Stars

This blog is my humble attempt at writing up the events leading to the demise of the Colonist; An alien entity/ies arrived in 1914 on the Tungustan comet. The Colonist is/are a fungus type infection that requires human antigens to survive, highly fragile to high level of ultra-violet light. Using porphyria to survive the organism is fighting to harvest the human blood, once the planet has been cleansed of non infected human lifeforms, it will go dormant, waiting for the next impact to move to the another world.

The Colonist entities themselves cannot be said to be intelligent in human terms, but they have a clear purpose; reproduce at all cost to insure survival. When combined with human DNA the Colonist organism slowly subverts it unless correctly controlled, but confers what could be regarded by external observers as powers. To insure survival of the spore, the organism regenerate most human tissues except for the brain.

Shoot for the Stars is our first attempt at creating a Night’s Black Agents game. Shoots for the Stars starts where the Lennart’s Dossier ends. The first series of posts will explain the background of the conspiracy and detail the organism itself and all of its mutations. Finally we will offers the operations, that the agents could encounter. Every couple of weeks or so, I’ll try to post a recap of the game session itself.

This is my first time writing that level of detail for a running game, hopefully it will be clear enough that other directors can use some of it for their own conspiracy. Also please note that English is not my native language, so please expect inconsistencies, syntax errors and grammar issues; Constructive comments welcomed.

A personal note on Night’s Black Agents, and the story driven Role Playing Games using the GUMSHOE engine and others. I had pretty much given up on Role-playing, the mapping aspects of it were and is turning me off completely. I find this cumbersome, and in a sense a complete creativity killer. Some players might love the precision of pushing figurines around, frankly I don’t; At least not when playing Role playing games. I rediscovered RPGs with Trail of Cthulhu, a new take on an old story. Most observers will talk about the GUMSHOE system, how it makes clues easy to get, hard to interpret, this has been discussed to death.

The thing for me that it brought forth was a simple concept, sharing the gaming creativity burden between the players and the storyteller. By introducing skills like preparedness, players could forgo the endless shop through the book to make sure they have the correct equipment. With the simple fact that players could keep unassigned points stored for a later use when the storyteller introduced something new in the story. All of these to make sure that the sessions go forward. Some might say that any house rules could make this happen in any system. Maybe, but GUMSHOE internalized all of this and made it part of the system.

The games created using this system are no longer a story told from the storyteller to the players, but a shared affair between all the involved parties. As one of my players commented; traditional gamemasters should be aware that they will lose control of some key parts of the story, this is the part where I sit back, listen to the players tell me a story and smile.

We currently play Night’s Black Agents, and sometimes when I’m lucky I can get people introduced to Fiasco from Bully Pulpit Games.

Hopefully, you will find my ramblings thoughts interesting.