Our second session of Mass Effect Heroic descended into madness. Well, madness might be a strong word. More like ridiculosity.
A third player joined us this week, who coincidentally also decided to play a Human Engineer. Thankfully, they chose entirely different Human powers (one has Enhanced Intellect d6, Enhanced Reflexes d8; the other has Enhanced Stamina d8, Enhanced Strength d6) and different Bonus Engineer Powers (one has a Machine Pistol d6, the other has a Combat Drone d6). Last week's Engineer will be referred to as The Hacker and this week's new Engineer will be referred to as The Mechanic.
Given the choice between three basic scenarios (go to the Citadel and dick around, hijack a medical supply ship and sell it on the black market, or smuggle some civilians off of a war-torn planet) they choose to be pirates. This seems to be a running theme with games in which two of these players play. I don't really see a problem with this.
So the MSV Triton sets off towards the Aralakh System. Upon their arrival, the Mechanic wants to try to dampen the ship's heat output so their approach will be stealthier. He rolls and gets a 10 with a d8 effect die, but with 2 Opportunities. The target ship is aware of them, but believes them to be a small shuttle instead of a freighter. The Mechanic launches a pair of docking cables and attaches their ship to their target. The Hacker gets the door open through a rather amazing roll (16 with a d10 effect die) against the Doom Pool (4 with a d6) so the door slides effortlessly open. Unfortunately for our heroes (I guess protagonists works better, as they're not as much Heroes as they are Pirates), there are some armed guards waiting for them in the entry hall.
Our Drell spots an overhead conduit and tells the Hacker to close the door after he fires a shot. The Drell's sniper rifle punctures a hole in the conduit, causing a power overload. The Drell's player spends a Plot Point to change the weapon that one of the guards is carrying into a Flame Thrower. The power overload arcs to the guard with the flamethrower, which has the predictable result of exploding rather violently. Thankfully, the Hacker has there wherewithal to get the door closed before the explosion engulfs Our Protagonists.
After a few moments, the fire suppression systems turn off and our protagonists are free to explore a bit more. The Hacker seals downloads a schematic of the ship to his Omnitool while the Mechanic starts unlocking doors. They decide to make their way through the sterile hallways to Engineering, because it'll be easier for them to override the Autopilot than it will be for them to take control of the ship via the cockpit.
The door to Engineering is locked down tight (Deadlock d10, Hardened Metal Door d10) and neither the Hacker or the Mechanic can seem to bypass it. Meanwhile, the Drell has found an access point to the ventilation system (this guy loves dropping Plot Points) and shimmied his way through to the other side of the door. He drops down into a creepily darkened Engineering and unlocks the door for his companions.
Upon further examination, it appears that the ship is on Autopilot, heading for a spatial anomaly which used to be a moon orbiting the third planet of the system. No craft or probe or other thing that's gone into the anomaly has come back out. Some say it's a doorway to another dimension, others say it's a quantum schism which turns reality into candy, still others believe it to be the doorway to Heaven/Hell/Purgatory/Alien analog of one of those things. Whatever it is, it is not a place that one wants their newly acquired ship and treasure to go.
It also appears that the Autopilot is on lockdown, with only the captain's command key to override it. So our protagonists decide to hoof it to the captain's quarters. As the first of their group sets a foot outside engineering, the lights go dead. The Mechanic scans the area with his Omnitool and realizes that Life Support has failed as well. The group puts on their helmets and flashlights, continuing towards the captain's quarters.
Along the way, the Hacker's flashlight illuminates a door with large dents protruding from it. Something on the other side is trying to get out. Cue dramatic music as a Very Angry Yahg bursts through the door. (At this point, I admit I may be overusing the Yahg in my examples, but who cares?) Combat starts.
Combat seems slow and ponderous until I realize I was doing Stress entirely wrong. Apparently getting 2 hours of sleep the night before a game and then working for 10 hours tends to make people forget some basic rules. After I adjusted for previous results that should have been successes, the Yahg was rather badly injured. Fortunately for the Huge Lumbering Ragebeast, the protagonists had generated quite a few Opportunities along the way and the Doom Pool was at 3d6+2d8+2d10. The Yahg picked up one of our protagonists' security escorts (whom they'd retconned, via some plot points, into existence after the lights went out) and threw him at the Hacker. I rolled exceptionally well (17 with a d12 effect die from the Yahg's Enhanced Strength) and nearly stressed out the poor, hapless Hacker.
The Mechanic stunned the Yahg with a conveniently placed Shotgun blast and the Drell finished it off with a pair of bullets to the eyes. As it turns out, Yahg are weak to Bullets-in-the-Eyes.
The protagonists carried on, their security escorts having all been rended into tiny bits by the previous encounter, towards the captain's quarters. A little Omnitool work and the door was open.
The room was in a rather bad state, clothes and supplies thrown everywhere. They stumbled across an audiolog from the captain, describing an attack by pirates and many of his crew being killed before they knew what was happening. Our protagonists thought pretty well of their success, until they realized that the timestamp on the audiolog made it clear that the recording had been made six hours before they arrived. The guards they'd killed on the way in? They were the last of the previous boarding party, left behind by their compatriots for some reason (justified or not) when they sent the ship towards the rift.
A rather frantic search through the quarters and the command key was found. The group nearly sprinted the entire way to Engineering. Upon their arrival, the Mechanic used the command key and a lot of elbow grease to disengage the Autopilot. Not a moment too soon, either. Had they waited another few minutes, the ship would have been past the event horizon of the anomaly; potentially lost forever to whatever hell dimension or Whimsyshire lay on the other side of it.
The protagonists reset the Autopilot to take the ship to the scrap yards, as was the original stipulation of the mission. In the meantime, Datok (their ship's captain and their boss) revealed that the reason they'd taken the mission is because he *knew* that the ship had been taken by pirates, so it should have been easy pickings. Unless, of course, the pirates had still been aboard or there was a muderous ragebeast being transported from its homeworld to a Salarian research outpost. Or the ship had been set on a suicide course into an unknown anomaly.
With that, the talk of mutiny began. Several quick conversations and everyone on board was convinced that their captain was a jerkface and needed to be spaced. And so, they did. Right out the airlock.
Next time, on Mass Effect. Who will step up to fill our Volus Captain's tiny shoes?
No comments:
Post a Comment