Guest User

So there I was in a game...

a guest
Jul 23rd, 2014
203
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 22.69 KB | None | 0 0
  1. [nabbed from /tg/ by way of SomethingAwful's traditional games subforum]
  2.  
  3. Gather ‘round chummers, as I tell you the tale of a lone technomancer with a grand vision. A technomancer who dreamed of the day when the sixth world is at long last released from the oppressive grip of the global megacorporations, leaving the cyberpunks to take back the streets. This is the story of how he set a plan in motion to make that dream a reality - a grand scheme involving espionage, deceit, a stolen orbital kill satellite, and a passionate desire to see the world burn.
  4.  
  5. A bit of background is needed first, to explain how our team found itself in the position to try bringing the megacorporations to their knees. Our intrepid team of shadowrunners consisted of the following:
  6.  
  7. I played Bloodworx, a Turkish Ork Street Samurai. High on painkillers and low on empathy for his fellow man, Bloodworx was a directionless, nihilistic ex-corporate bodyguard who found himself running because he couldn’t figure out what else to do with his life once budget cuts caused his employers at EVO to give him the boot. Bloodworx tried his best to come off as an emotionally distant killing machine operator, but a few minutes to talking with him would make it evident that he was just incredibly frustrated at his inability to make a difference in the world around him.
  8.  
  9. Our Face was a man who went by the title “Boston Lau,” a smug, slightly cybered, streetwise Chinese American Human who did his best to hold the rest of the group together and formulate the big plans. Even when the situation around him was clearly fragged six ways to sunday he did his best to convince himself he was still in control, since figured it was the only way he could convince the people around him of the same.
  10.  
  11. Our Mystic Adept/Infiltrator was an dwarven woman who went by Daze, an outgoing thrillseeker with more piercings in her face than my street sammie had cyber in his body. She was by far the friendliest member of our group, but also in constant need of reassurance and positive feedback from others lest she become obsessed with trying to prove her worth to the group at large.
  12.  
  13. And lastly, there was our hacker - a human technomancer who went by the handle of “Tass”
  14.  
  15. “Tass” was the phonetic version of the technomancer’s real handle, “T.A.S.,” which stood for “Terms and Services.” He took the name because he always felt that people were ignoring him.
  16.  
  17. A little bit of time around the guy was it it would take before it was clear WHY not many people paid attention to what he had to say. While he was a wonderful hacker, he was a hardcore anarchist who refused to ever shut the fuck up about his dream of bringing down the megacorporations. Everything about the guy bled pink mohawk, right down to the fact that he literally had a dyed mohawk. (Albeit one in what he called “matrix blue” instead of pink)
  18.  
  19. Whenever Tass got the chance, he would ramble on about how the rule of the Megacorporations was temporary, how someday the pigs in their ivory towers would be dragged kicking through the streets by the people they once bled dry, and other entiments that led to Boston Lau establishing an official “Tass never speaks at meets” rule. While Lau thought the technomancer’s mannerisms grating, Daze and Bloodworx both found Tass endearing: Daze because he appealed to her thrill-seeking drive, and Bloodworx because Tass’ anarchist enthusiasm reminded him of his own, less jaded days shortly after being fired from EVO.
  20.  
  21. Either way, Tass was not the kind of guy you wanted handling sensitive corporate information. And yet, through a series of missteps and coincidences, our crew found itself caught up in one of Aztechnology’s most secret projects.
  22.  
  23. The overarching plot that our GM had set up for our campaign revolved around the mysterious destruction of several communication satellites, which was causing a major stir among the corporate court. The destruction of comm sats was something that hurt all the AAAs, so the shadows were abuzz with rumors of the corps scrambling their best men to deal with the threat.
  24.  
  25. Through a series of investigations, our team uncovered the truth behind what was going on: Aztechnology, looking to gain an edge in their war with Amazonia, had infiltrated Renraku and stolen the plans for technology that would let them mask the signal of a Kill Sat they hoped to position over the rival nation. A corrupt executive within Aztechnology looking to move up the corporate ladder infected the navigational software of the satellite with a virus, however, hoping to bring down the satellite, frame the man in charge of the project for incompetency, and take his place as the head of Aztechnology’s space division. However, due to some shenanigans with experimental self-upgrading virus protection, the Kill Sat developed an AI instead, and began shooting down anything that got too close.
  26.  
  27. Once we had successfully uncovered the corrupt exec’s involvement in the Kill Sat’s grand malfunction, the GM originally planned for Aztechnology to task us with taking down the traitor and then paying us off to keep quiet about the whole thing while an internal team fixed the AI problem.
  28.  
  29. That would have been the finale of the campaign, had we not done a few things to massively derail the GM’s planned conclusion.
  30.  
  31. First, during a mission early in the investigation, we had accidentally gotten the Aztechnology research team responsible for fixing the satellite killed by a Tir strike team while trying to help them fix a hidden node used for spying.
  32.  
  33. Secondly, we had accidentally tipped Renraku off to the fact Aztechnology had stolen their cool cloaking tech, making them a bit suspicious and resulting in them sending agents to infiltrate Aztech’s R&D department. We let Aztechnology know this had occurred (not letting them know we had given Renraku the tip) once it became apparent this had been a bad idea, but the damage was still done and Renraku’s agents were still looking into Aztech’s possible involvement in all the events going on.
  34.  
  35. Aztechnology was now without a team to fix the satellite, and also on a timer to get things under control before Renraku discovered the role they had in the communications satellites getting blown up. Not wanting to tip off Renraku’s inside men, Aztech was forced to outsource the job to shadowrunners to get the job done. A few days later we got word that a “mysterious contractor” was looking for shadowrunners to pull a mission in deep space, and Boston Lau called in all his favors from all the political contacts he amassed to make sure we got that run. We were in for the biggest paydays of our life, he assured us.
  36.  
  37. And so, the four of us were off to space, on a top-secret mission to get a rogue AI in a signal-jamming Kill Sat under control.
  38.  
  39. Tass was brought onboard because we had managed to sell him as one of the best hackers around, and the three of us were brought on as his security to make sure our “mysterious contractors” didn’t try anything funny in the name of maintaining their corporate secrets.
  40.  
  41. We were flown to Aztechnology’ Spindle, (The command and control center for their military satellite relays) then took a shuttle out to the last known location of their trigger-happy kill sat. We were accompanied by six Aztech representatives - the project lead and his bodyguards - who came along to make sure things went their way.
  42.  
  43. Once we tracked down the satellite using a backup link established between it and the Spindle (and barely avoided getting shot down ourselves), it was time for us all to suit up. Lau, Bloodworx, and Daze were tasked with physically anchoring the satellite to the craft, and Tass was tasked with jacking directly in to fight the AI and download a list of people who had accessed the satellite since its launch to help flush out anyone involved in the sabotage.
  44.  
  45. Tass had a tense matrix battle, immediately followed by philosophical debate on the nature of control. It turned out that Tass and the Artificial Intelligence were of like mind when it came to the AAAs being douchebags. Meanwhile, the rest of us did our job in meatspace (and narrowly dodged some stray space debris). By the time the rest of the crew had re-entered the ship Tass had triumphed over the AI and brought it under his control. Once our technomancer confirmed to the men inside that we had finished the job, the Aztech exec who accompanied us gave the order to flush the AI from the system.
  46.  
  47. Tass had other ideas. He had taken a liking to the AI, a kindred spirit in hatred towards the megacorps. The gears were turning in his head, and while the successful completion of the run could potentially be the biggest payout of his life, his current position offered him an even greater opportunity…
  48.  
  49. A few seconds after the exec gave the order to reset the satellite’s systems entirely, Tass sent his response.
  50.  
  51. “You know what? Frag off.”
  52.  
  53. The party was just about as stunned and confused as our employers, who were additionally really pissed off at the hacker’s sudden bout of stubbornness. The exec repeated the order, and then Boston Lau begged for Tass to listen, but the technomancer threatened to open the channel they were using for communications up for the AI and letting it make its way into the ship if they didn’t back off.
  54.  
  55. Having none of that, the exec ordered for one of his goons to turn of Tass’ oxygen. Boston Lau tried to negotiate with him to give Tass some time to calm down, but the exec was having none of that. This was an incredibly delicate operation, and they couldn’t afford any unbalanced jackasses jeopardizing it because they didn’t understand the gravity of the situation.
  56.  
  57. Being an unbalance jackass who didn’t understand the gravity of the situation himself, this was the point where Bloodworx drew his weapon and dropped one of the bodyguards before they had an opportunity to react. At the time he was acting on his impulse to keep his teammate alive and by the time he realized how much the mission was boned now it was too late to take it back. A brief skirmish erupted in the shuttle that Daze jumped to join (it was fortunate she was just as good with close range combat as she was with magic, since magic doesn’t work in space) and soon enough all of our employers were dead.
  58.  
  59. Lau began screaming at us and telling us that our collective actions had ensured all four of us would die in space. Not even counting how much Aztechnology would want our heads once they found out what just happened, none of knew how to pilot a spaceship.
  60.  
  61. “I do!” Tass chimed over the commlink.
  62. It was true. He’d had points in Pilot (Aerospace) since the start of the game.
  63.  
  64. Once we were back inside the spacecraft, there was a good deal of arguing, mostly between Boston Lau and Tass, over what we had just done. Once Tass had finished explaining that the AI was a brother in arms for his struggle to fight the corps and Lau realized that there was absolutely no way to salvage the mission at this point, we started planning our next move. Tass insisted that the AI deserved a say in our next move just as much as anyone else, at which point Lau threw his hands up in the air and said “fine, sure, whatever.”
  65.  
  66. The AI said that, greatful for what we had done, it would help us with whatever we wanted it to help us with. The AI reccomended helping it take control of one of The Spindle’s communication satellites, so that it could help us return to earth safely and begin work erasing our presence from Aztechnology’s databases. This seemed like a fair tradeoff for the rest of the group - we lost out on a big payday, but we gained a benevolent AI friend hidden away inside a global communications satellite to help us with all sorts of things in the future.
  67.  
  68. Once again, Tass had other ideas.
  69.  
  70. Tass gleefully told the AI that he needed its help in a very important task, which would ensure it would never have to worry about the corps trying to kill it again: the destruction of Zurich-Orbital.
  71.  
  72. Some general knowledge, combined with some knowledge checks in corporate secrets and corporate politics makes it evident to everyone how insane a request that is.
  73.  
  74. Zurich-Orbital is the home of the Corporate Court, as well as the Zurich-Orbital Gemeinschaft Bank. It’s THE symbol of corporate authority, the place where the AAA’s most sensitive deals go down, and the processing center for global currency. The reason why shooting it down is an insane move should be obvious right off the bat - blowing up the station would crash the nuyen market worldwide. It’s half the reason why the Corporate Court is situated there, since it would be mutually suicidal should anyone try something funny on board.
  75.  
  76. Additionally Z-O is probably THE most heavily defended and protected facilities on or off the earth. It’s home to the Court’s grid overwatch division, aka the most sophisticated matrix security system ever designed. Physically, the facility is protected by an array of kill sats and defense drones, and the station only issues warnings once to ships too close. Getting onboard without clearance is impossible, period: biometric scans and background checks are required just to get on a shuttle going there, and cargo is weighed to the gram.
  77.  
  78. On top of that, only the top corporate brass even know where the station is half the time. Almost all communications between the station occur using glaciered, dedicated communication relays that transmit signals to important people on the ground to let them know the big Z-O is overhead. Not even world governments can contact the station - for everyone but the biggest corporate bigwigs, the communications are one way only, automated from the station.
  79.  
  80. And Tass wanted to take it down.
  81.  
  82. Boston Lau was having none of that. He quickly tells Tass that his pink mohawk is on way too tight, and asked the rest of the team to slap some sense into the technomancer who was determined to get them all killed.
  83.  
  84. Bloodworx and Daze aren’t so quick to judge, though… at the end of the day, Daze’s mohawk is almost as pink as Tass’, and Bloodoworx is enough of an asshole to want to see if it could be done. Lau couldn’t believe his ears, but he COULD believe the gun that Tass quickly shoved in his face as he told the frightened face that his skill was required for the plan to work.
  85.  
  86. Surrounded by a group of insane cyberpunks bent on crashing everything, and being shit at combat himself, Lau quickly fell victim to his own cowardice and agreed to help as long as he was allowed a way to get off this wild ride before shit really hit the fan.
  87.  
  88. Step one of what Tass called “Operation: Shutdown” was returning to the Aztechnology Spindle and taking it over. This was accomplished by “persuading” Boston Lau to use his voice modulator to convince the men back at base that the exec onboard was still alive , the situation was a-OK, and that they should let us dock with the satellite. As soon as we got within range of the ship, Tass threaded an exploit into the station’s panic situation alarm and blocked outgoing transmissions from the base. By the time we’ve docked, our technomancer had let the AI loose in the station’s security systems, allowing him, Bloodworx, and Daz to slaughter their way through security personnel while the AI took control of all of the station’s security drones and Lau cowered close behind. The four man takeover of an entire security station should have been an impossible task in and of itself, but once we physically eliminated the security spiders nothing was stopping the AI from conquering the entire system and dealing with most of the guys who would give us trouble.
  89.  
  90. Step two was locating Z-O This actually ended up being a harder task than killing the security team of an orbital military command center. Tass scouted the database in the station for coordinates of the base, but it was soon clear that the information wasn’t there. The best information he could find, in fact, complicated matters: there were a series of dummy stations built to hide of the real Z-O from space scavengers, each almost as well defended as the real base for authenticity.
  91.  
  92. We were reminded once more that the only confirmation almost anyone gets to the location of the real Z-O are timed, pre-recorded transmissions on secured channels.
  93.  
  94. What we were able to find, however, was a list of Aztechnology personnel currently situated in space. This didn’t include the location of Z-O, but it DID include the name of Aztechnology’s corporate court rep. At this point, Lau started begging Tass to give up and go home, but the gears were turning in Tass’ head. He pressed his gun against the back of Lau’s skull, brought him over the the station’s command deck, and used the dead exec’s credentials to open up communications with Aztechnology’s chairman.
  95.  
  96. Tass forced Lau, pretending once again to be the dead exec, to report in with a “disturbing development.” We forwarded the list of suspected conspirators found in the satellite's access logs, now spoofed to include the name of Aztechnology’s corporate court rep.
  97.  
  98. Finding this information confusing, the chairman started calling his men to figure out when the last contact between their Court rep and the ground had been. There was no way he could be in on the conspiracy if he had been aboard Z-O the last six months, where nobody could directly contact him.
  99.  
  100. We monitored his calls via a hacked Spindle comm satellite, and eventually one of his office grunts pinged him with Z-O’s last credential check-in location.
  101.  
  102. Bingo.
  103.  
  104.  
  105.  
  106. We sent a message that the crew sent into orbit was coming back to earth minus one hacker, who was staying behind in the spindle to help decompile some fragmented data found in the satellite. Tass helped the other members of the crew board an automated shuttle back to earth, and told them to get the hell out of dodge before Aztech figured out what was going on. Everyone was more than willing to comply, and the AI offered its services in wiping their records once all was said and done. Boston Lau said was going as deep underground as he could, hoping to wait the chaos out in case Tass actually succeeds. Bloodworx and Daze are content to take part in the riots to come, and watch the world burn.
  107.  
  108. Leaving the AI in control of the Spindle, Tass set out again in the ship with the kill satellite anchored to it, destination locked on Z-O’s last known location. Considering Z-O has its own entourage of killsats, and comms relays, it doesn’t take long for somebody who knows what they’re looking for to identify the station. Tass managed to catch up with Z-O right as it was finishing its orbit above the CAS and beginning to pass over the UCAS. It was at this point the GM gave Tass the rundown of the situation. Even with the satellite’s systems masking his ship from radar, the second he fired he would expose himself to Z-O’s close range sensors. And there was no guarantee the one burst he’d fire before Z-O’s killsat array lit him up like a noir street sign would hit its mark.
  109.  
  110. But Tass had gotten this far, and he wasn’t giving up.
  111.  
  112. Tass’ player looked to the GM. “If the satellite wasn’t hiding my signal, would Zurich be in range to send a warning?”
  113.  
  114. The GM confirmed, and the Technomancer declared he was going to try hacking Z-O’s communications relay. The GM reminded Tass that he was trying to hack the most sophisticated security system in the world, but Tass insisted he just needed access to their comms, not the ship’s actual internal security systems.
  115.  
  116. With some well-edged rolls, Tass managed to thread a sneak and exploit into the communication relay’s host server (technomancer 2 stronk). There wasn’t much he could do with it, since the thing just spat out of unidirectional transmissions on delayed feeds, and getting any further into the system would require more dice than he could throw even if he still had all his edge.
  117.  
  118. “Has Z-O passed over the UCAS yet?” Tass’ player asked
  119.  
  120. The GM said not yet, but that it would be over the UCAS in less than a minute.
  121.  
  122. “Can I crash the next outgoing transmission?” Tass’ player asked.
  123.  
  124. The GM confirmed that was about all he could do with his current level of access.
  125.  
  126. Once Tass had confirmed that the impending transmission to the UCAS was blocked, Tass’ player smiled.
  127.  
  128. “I rev up my killsat and orbitally bombard Kansas City.”
  129.  
  130. On command, the satellite set its targets and fires bombardment set to wipe Kansas City off the map. As the shots fired, Z-O’s defense relay immediately lit up and sets its sights on Tass’ ship. A barrage of orbital missiles scream into the small spaceship, blowing it apart and sending the satellite spiraling out of orbit. Tass is flung into the vacuum of space. Tass, in a damaged spacesuit quickly losing oxygen, burns an edge to maintain consciousness just long enough to see the immediate result of his actions.
  131.  
  132. Only after Tass’ ship has been pulped to the security spiders realize the attack wasn’t targeted at them. They scramble shift their defense relay away from Z-O and towards to shoot down the missiles fired towards the earth, but it’s too late. An orbital bombardment fired from a radar-cloaked satellite that the UCAS never had a chance to see coming touches down and obliterates half of Kansas city.
  133.  
  134. Immediately, the UCAS military focuses its scanners in on the aerospace where the shots originated from. They run a trace for a potential source, but the only thing in the area showing up on radar is Zurich-Orbital.
  135.  
  136. Zurich-Orbital, which nobody has any way of contacting directly.
  137.  
  138. Zurich-Orbital - which has just been prevented from transmitting its credentials to the UCAS and proving that it’s Zurich-Orbital.
  139.  
  140. The UCAS military fires off every earth-to-space missile it has in retaliation, directly at the unidentified hostile space station.
  141.  
  142. What followed was possibly the most triumphant moment I’ve ever witnessed in a Shadowrun game.
  143.  
  144. By the time Z-O realize their credential transmission has failed and get it back online, it’s too late. As soon as the UCAS receives the delayed transmission, they scramble in vain to shoot down the missiles they’ve shot off. Corporate communications around the world explode with word that the UCAS just targeted the Corporate Court. Everyone scrambles to figure out what’s going on. A single individual puts the pieces together just as the missiles breach the atmosphere, and realizes its too late.
  145.  
  146. As he watches the missiles fly, slowly slipping away, Tass receives a buzz on his commlink.
  147.  
  148. >Connected: Hans Brackhaus
  149. >“What have you DONE?”
  150.  
  151. Tass replies with a smiley face, and loses consciousness right as the first missiles slip past Zurich-Orbital’s defenses.
  152.  
  153. The missiles hit, the global economy crashes, the corporate power fractures, and anarchy washes over the streets.
  154.  
  155. And that, chummers, is how to end a Shadowrun campaign in style.
Add Comment
Please, Sign In to add comment