>>3237902
>>Run silent and passive, see what you can observe.

>>3237902
>>Run silent and passive, see what you can observe.

>>3237902
>>Run silent and passive, see what you can observe.

“Understood. All stations, rig for ultra-quiet running.” You ordered after a second. Best case scenario, the rest of your wolfpack was running late and would arrive soon. Worst case scenario, the rest of the wolfpack had either been destroyed or forced to retreat by a force of covenant vessels, in which case you’d be best served by hiding for now. And somewhere between those, your wolfpack was already in system and you were just overreacting.

Ultra-quiet running was a very simple idea. All sources of emissions were to be either shut down or have their output considerably reduced. As such all active sensors would be shut down, the MAC would be depowered, and your primary thrusters would be brought offline. That would reduce your signature down to the smallest it could possibly be but would also greatly reduce your overall capabilities.

“Navigation, move us towards the planet, keep our signature low.” You ordered, if there was an opponent in the area, they would likely have spotted your slipspace entry signature, and would be heading over to have a look.

“Sir, longsword squadrons alpha and bravo are fuelled and ready for launch sir. Should I give them the go-ahead?” Your aviation officer notified you. The longsword would give you a good ability to see what was going on without having to power on your sensors. But at the same time, sending them out to scout would also leave you open to enemy fighters. And while those enemy fighters would not be a significant threat on their own, if they informed their mothership of your location, you’d be in a whole load of trouble.

>Launch all of your fighters, they will be useful for scouting duties.
>Launch half of your fighters, keep the other half in reserve.
>Keep your fighters onboard. You’ll launch them as needed.
>Other (write in)

>>3237993
>Launch half of your fighters, keep the other half in reserve.

>>3237993
>>Launch half of your fighters, keep the other half in reserve.

>>3237993
>>Launch all of your fighters, they will be useful for scouting duties.

>>3237993
>Launch half of your fighters, keep the other half in reserve.

File: longsword.jpg (21 KB, 637x358)

21 KB JPG

“Launch one of the squadrons with orders to scout for other craft in the area. Keep the other squadron on alert for launch, just in case we encounter inbound enemy fighters.” You ordered, you didn’t like the idea of seeing with only half of your available eyes, but you also didn’t like the idea of a covenant fighter telling it’s mothership where you were.

If the covenant were able to get their shots off before you knew they were there, then chances would be that you’d die before being able to get a return volley off.

“Understood sir.” Lieutenant Krickstein confirmed, before turning back to his console. “Longsword squadron alpha, you are cleared for launch. Longsword squadron bravo, remain ready for launch.”

You didn’t have to wait long before you saw the triangular fighters depart. The three craft launched from the array of hangers on the port of your ship and launched off into the distance. Their small but relatively powerful sensors would give you a good amount of visibility, though that was mostly due to your own lack of sensors.

“Commander, I feel as if I should remind you that we do have a mission here.” Your XO, Dyad, reminded you. And sure, you were here to look out for illegal shipping, but at the same time, you were also told to expect friendly support. Not to mention that entering the northern graveyard without your sensors up and running would be a major issue. With tens of thousands of items of debris floating around, and dozens of wreaks of similar size to your own vessel, a collision would be very hard to avoid, and could even be very dangerous if you accidentally hit a wreak.

>Delay the mission and wait. You don’t want to make a move without friendly support.
>Slowly make your way to the northern graveyard, try and keep as quiet as possible.
>Drop the silent running and make your way to the northern graveyard.
>Other (write in)

>>3238112
>Slowly make your way to the northern graveyard, try and keep as quiet as possible.

Could we have the other fighters launch and guide through so we don't hit anything?

>>3238127
That's certainly an option, but keep in mind that it may prevent them from quickly responding to inbound enemy fighters.

>>3238112
>>Slowly make your way to the northern graveyard, try and keep as quiet as possible.

>>3238131
That's a risk I'm willing to take

>>3238112
>>Slowly make your way to the northern graveyard, try and keep as quiet as possible.

>>3238112
>>Slowly make your way to the northern graveyard, try and keep as quiet as possible.
thread 2 is still up and being refreshed with each post, not sure why a new thread was created

“I suppose we do. Nav, take us slowly towards the ship graveyard over the north pole of Edrianus II.” You shrugged. Your XO was right, you did still have a mission, but you weren’t about to reveal that your exact location to anyone nearby.

“Sir, navigating in there is going to be almost impossible without hitting something.” Your navigation officer pointed out as he rotated the Dawn’s Early Light towards the graveyard.

“I was just getting to that Lieutenant Toulali.” You turned to your aviation controller. “Lieutenant Krickstein, launch longsword squadron bravo. Order them to scout ahead and monitor the debris. Lieutenant Helena, establish a data-link with squadron bravo and feed the data to Lieutenant ‘s station.”

“Toulali, the sensor range and detection quality on the longswords isn’t as good as your used to. So, take that into account while you are doing your thing.” Lieutenant Helena, your sensor systems officer instructed your helmsman. A set of aviator glasses sat on the edge of her station.

The graveyard over Edrianus II was made up of all of the human vessels that had been destroyed during the battle over the planet. While there was a few UNSC and CMA warships in the mix, most of the warships were destroyed and gutted transports, industry ships and even the odd station. The remains of the Elysium city space elevator’s docking station being a prominent station that hung like a broken chandelier in the city of dead warships. Debris flaked off the various ships, creating a hazard for navigation. The leaking and broken remains of fusion reactors blanketed the area in radiation and radioactive debris. And without your main sensor suite, you were going in with long odds of not hitting something. And your odds of hitting something large was much higher than you liked.

>Continue heading into the graveyard with your sensors off and main engines powered down. (1d20-6)
>Reactivate your sensors and main engines, you don’t want to risk it. (1d20-2)
>Other (write in)

>>3238313
>>Reactivate your sensors and main engines, you don’t want to risk it. (1d20-2)

>>3238330
You have to roll 1d20-2

Rolled 19 - 6 (1d20 - 6)

>>3238313
>>Continue heading into the graveyard with your sensors off and main engines powered down. (1d20-6)

Rolled 15 + 6 (1d20 + 6)

>>3238313
>Continue heading into the graveyard with your sensors off and main engines powered down. (1d20-6)
I suggest it, might as well stick with it

>>3238344
You are meant to roll 1d20-6. it's a - not a +.

Rolled 12 - 6 (1d20 - 6)

>>3238313
>Continue heading into the graveyard with your sensors off and main engines powered down. (1d20-6)

Rolled 11 + 6 (1d20 + 6)

>>3238349
For the record I did pass 1st grade math.
The question is whether or not the site it messing with me and changing the post.

>>3238356
Huh its changing my - to a +

>>3238358
If it's changing your - into a + then I'll just take your first result and swap the + for a -.

Rolled 5 + 6 (1d20 + 6)

>>3238313
>Continue heading into the graveyard with your sensors off and main engines powered down. (1d20-6)

Mean roll: 9.333
Success threshold: 8
Result: Success (minor)

Almost an hour later, your frigate was on the edge of the graveyard. Your navigation officer shut off the ship’s secondary engines, and slowly began to move the ship in with the tertiary docking thrusters. The mass of debris, including titanium A battle armour and girders, was a navigation nightmare, and you could hear the sound of small pieces of debris bouncing off the bridge’s armour. This would have worried you, if you also didn’t see much larger pieces of debris pass harmlessly over the bow of the ship. The closest of them scoring a large scratch into the hull of the ship.

While you certainly didn’t like the fact that your navigation officer was a kiss ass, you could appreciate his skill.

“We are in the debris field sir. Should I take us through a random but safe course, or should I take us towards a specific point of interest?” Lieutenant Toulali, asked. And you had to admit to yourself that you hadn’t actually thought about it. You had to boot up a 3D holographic map on the small projector on the right arm of your seat in order to come to a decision.

You had a couple of specific points of interest to look at. The first was the Halcyon class cruiser, the UNSC Surigao Strait. The vessel was a later-model Halcyon, without the internal cross bracings and honeycombs that made the first 15 vessels so hard to kill, and so horrendously expensive. This made the Surigao and the sister-ships of her sub-class much cheaper and easier to build. But those very bracings would have saved the ship during her final battle, as she was gutted by plasma torpedoes and ultimately suffocated. Her spaceframe was gutted, her reactor was leaking and her weapons had been expended, but her hull still carried a bounty of scrap, chief among them being the ship’s MAC gun.

The next point of interest was the remains of the Elysium city space elevator’s docking station. Unlike the vast majority of wreaks, it didn’t have a reactor to leak radiation. And it hadn’t been significantly damaged by energy weapons fire. However, it also lacked the titanium A battle plating that many scavengers wanted. However, the station still had a number of cargo pods attached, and the powerful systems used to pull cargo containers up the space tether that it was once at the head of would certainly be worth a lot of money to anyone willing to check it out.

>Check out the Surigao Strait, it’s the biggest and most obvious location for salvagers to go.
>Investigate the docking station. Some smaller, but more enterprising salvagers might go there.
>Patrol a random course, you’ll cover more area and run less risk of hitting something.
>Other (write in)

>>3238452
>Investigate the docking station. Some smaller, but more enterprising salvagers might go there.

>>3238452
>Patrol a random course, but make sure to hit the Surigao Strait or docking station at some point.

>>3238452
>>Investigate the docking station. Some smaller, but more enterprising salvagers might go there.

>>3238452
>Investigate the docking station. Some smaller, but more enterprising salvagers might go there.

>>3238452
>>Investigate the docking station. Some smaller, but more enterprising salvagers might go there.

“No, take us towards the remains of the Elysium city space elevator.” You ordered, you knew that an area search would allow you to cover more of the debris field, but you wanted to specifically check out the space elevator first. The powerful electromagnets used in the docking system on the tether tended to sell for a high price due to how powerful they were.

It didn’t take long for the frigate to make it’s way over to the remains of the space elevator, but it was enough time for your VBSS teams to load up onto a pair of pelican dropships. And soon enough, you were close to the remains of the station. From a distance, the station looked like some sort of distorted jellyfish, with the segmented dome of the station’s hull forming the body and the remains of the and the remains of the space tethers that once anchored it to the planet filling in the role of it’s lappets.

Up close, the station seemed more damaged than it had been during the reports. A couple of noticeable gouges had been left in the wake of pulse-laser fire and could be seen from even a distance. And the rest of the hull had been blemished by fire from covenant fighter-grade plasma weapons. The remains of at least two freighters were still clamped onto the station, one having been bisected by a heavyweight energy weapon, while the other one had been shot to shreds by smaller plasma weapons. A couple of hangers were still open, but others remained closed. A few cargo-climbers were still attached to the hull of the station, but hung free from the tethers, adding yet further to the jellyfish look of the station.

Now you had to figure out how you were going to even investigate the station. You could use the frigate’s own sensors, at such short range you would need less output in order to get a good scan of the station. However, that ran the risk of alerting any nearby vessels that were here being up to no good. You could use the longswords to do the same, but their scanners were less effective at scanning into a target, and as such would have a harder time detecting living things within. Finally, you had two VBSS teams that you could send over. But they would take time going through the station, and if they encountered trouble, they would take heavier losses. A gunfight in space tended to be over a lot quicker than in atmosphere.

>Scan the docking station with the frigate’s own sensors, a short burst should be fine (1d20+2)
>Scan the docking station with your longswords, you don’t want to reveal your location (1d20-10)
>Send a marine VBSS team, you can’t trust your sensors to get the job done without you getting found out.
>Other (write in)

Rolled 1 + 2 (1d20 + 2)

>>3238588
>>Scan the docking station with the frigate’s own sensors, a short burst should be fine (1d20+2)

>>3238595
I think our scanners broke...

OP, please don't make a new thread with every session. Keep the old one until you get too many posts (like 650+) or you hit page 9-10.

Rolled 18 + 2 (1d20 + 2)

>>3238588
Welp, rollan to save.
>Scan the docking station with the frigate’s own sensors, a short burst should be fine (1d20+2)

Rolled 17 + 2 (1d20 + 2)

>>3238588
>Scan the docking station with the frigate’s own sensors, a short burst should be fine (1d20+2)

>>3238595
Well shit.

Rolled 3 + 2 (1d20 + 2)

>>3238588
>>Scan the docking station with the frigate’s own sensors, a short burst should be fine

Rolled 9 (1d20)

>>3238313

>>3238875
meant to go to the most recent post

>>3238588
>>Send a marine VBSS team, you can’t trust your sensors to get the job done without you getting found out.

Rolled 12 + 2 (1d20 + 2)

>>3238612
fourthing: short burst scan. Can we widen the net so we can see if we're alone in here at least? I don't want to get ambushed.

I’d still be totally down with waifuing Livia. Or daughter- waitwaitwait hol’ up.
“Ambrose”?

Please tell me you pulled that name out of a hat.

>>3238603
This.

>>3238603
Thisx2

>>3237902
OP, first thread in suptg is not tagged Halo: Wolfpack and therefore is not showing in the archive link you posted

>order passive mode
>primary thrusters shut down
>"Nav, take us towards the planet"
>not even waiting for the rest of our group
>"Launch the fighters"
>"Move us towards the graveyard"
>sensor sweep
At this point we are as passive as a car crash. Wouldn't be surprised if we got hit by a plasma beam out of nowhere. My bet is on twintails girl to be one of the first casualties.

>>3239795
>>3239817
>>3238603
Oh come on, give OP a break. It's actually a solid quest, no shame in it strongarming its place in the board. Besides, something something one narrative arc per thread

>>3239940
I agree OPs quest is great, but smaller quests might get pushed off faster.

>>3239940
It's a cool quest but with how slow the board is it's entirely unnecessary to make new threads so often. Currently he has two on page one (sorted by Last Reply)

>>3239940
I like each session having it's own thread. Fresh start, new header to set the tone, doesn't feel like it's lost in the wake of the previous thread. And so far we've done a good job of having one arc per thread, and one thread per arc. If it's really just a "hey, intermission, we're in the middle of hunting through this minefield but we're stopping here for the night" yea, sure, same thread, but if it's a different segment then new thread.

>>3239946
Oh no, the small quests that the QM abandoned after 6 posts....

>>3240920
His twitter said his internet was down. I'm giving him the benefit of the doubt

Why wasn't the first thread archived? Its still on the board....

Ah, nvm. It wasn't archived properly.....

>>3240920
i'd rather have that than 4 of these threads clogging up the front page

>>3242365
Suck it up then cause there's nothing you can do about it

Internet is finally back and stable, next post will be in an hour's time.

“Lieutenant Helena, scan the station with the ship’s primary sensors. Quick scan, I don’t want us emitting for too long.” You ordered, going for the least subtle approach. But still, you hadn’t encountered any reading that would suggest you had company thus-far. So you had reason to take a little gamble.

“Understood sir, standby.” Lieutenant Helena replied as she brought the frigate’s sensor suite online. In spite of you asking for as quick a scan as possible, it still took around a minute for the scan to be complete. You brought up the results of the scan on your personal screen.

For all intents and purposes, the station was dead. No sections still held atmosphere or any sort of stored power. There were no active computer systems, and those few remaining solar panels that sat at the very top of the station and had not been destroyed by enemy fire were not able to supply power to the rest of the station, most likely due to damage further down the station. There was limited radiation output from the remains of one of the freighters slipspace drive, but almost all of the drive had been vaporised by enemy fire, so the resulting radiation bleed was far lower than it could have been.

However, there was still evidence of recent activity on the station. There were areas which carried more heat than other parts of the station. Additionally, significant parts of the station had been wholly carved off. Almost all of the powerful electromagnetic docking collars had been removed, the only ones left being the ones that had practically fused with the two remaining freighter hulks. And a couple of cargo climbers had been robbed of their containers, while others had been left free and untouched.

“Looks like it’s been picked clean.” Dyad commented from behind you, having looked over your shoulder to look at your screen. “There is nothing of real value left.”

“Not everything, the solar panels are there, as are some of the computers. And I’m pretty sure that the mass lifting system for the tethers is still in there.” Helena pointed out, making sure to ping the rough location of the systems within the station overlay on your screen.

“Removing them might not be profitable for scavengers. Keep in mind that we aren’t just worrying about human scavengers.” Dyad reminded the sensor systems officer. You had to worry about jackals too.

>Send a VBSS team to investigate the station, you might be able to figure out if you are dealing with humans or not.
>Head off to investigate the Surigao Strait, it’s the biggest and most obvious location for salvagers to go.
>Patrol a random course, you’ll cover more area and run less risk of hitting something.
>Other (write in)

>>3243172
>investigate the Surigao
All's quiet here, let's move on to the Surigao. We're looking for active looting at the moment. Also, the Cov would probably be interested in our computers, so the fact those are some of the last things lying around lends me to think we're dealing with good old desperate humans.

>>3243180
also, where's Alpha squadron? Bravo's escorting us for sensor purposes, but are we still in contact with Alpha? We might want to bring them closer in for this.

>>3243172
>Head off to investigate the Surigao Strait, it’s the biggest and most obvious location for salvagers to go.

>>3243172
>Send a VBSS team to investigate the station, you might be able to figure out if you are dealing with humans or not.
I smell a rat. Or rather, a jackal

>>3243235
Support

“Nav, take us towards the wreak of the UNSC Surigao Strait.” You ordered your navigations officer to take you away from the remains of the space elevator. You had seen enough of nothing.

“Sir, there is a large amount of debirs between us and the wreak. I’ll need either the ship’s primary sensors or the other longsword squadron in order to safely navigate through it.” Toulali reported as he slowly began to move the Dawn’s Early Light away from the station.

“Can you go around it?” You asked, you weren’t too keen on recalling your other squadron. Afterall, they could be on the other side of the planet for all you knew.

“I can sir, but it will require me to retract our course back towards where we entered the debris field, and then head towards the Surigao Strait from there. I estimate that it will take around two hours to complete.” Toulali explained, and you couldn’t help but wince at that. Two hours was a lot of time for a group of scavengers to escape in. And your sensor burst might have tipped them off.

“Aviation, where is Alpha squadron?” You asked Krickstein , your aviation officer, for an update about where the other half of your combat air wing was.

“They are outside of the debris field, scouting for the rest of the wolfpack. I can recall them back if you would like, though they will take around an hour to reach us.” Krickstein reported back a couple of seconds later. “They shouldn’t take as long as us getting through the debris field.”

>Recall Alpha squadron to help guide you directly to the Surigao Strait (1d20-5)
>Take the longer but safer course to the Surigao Strait. (1d20-3)
>Activate your sensors and take the direct course to the Surigao Strait. (1d20-6)
>Take the direct course to the Surigao Strait on longsword sensors alone. (1d20-10)
>Other (write in)

>>3243263
>Recall Alpha squadron to help guide you directly to the Surigao Strait (1d20-5)

>>3243263
>Activate your sensors and take the direct course to the Surigao Strait. (1d20-6)
KNOCK KNOCK MOTHERFUCKERS
FREEDOM’S HERE

Rolled 12 + 6 (1d20 + 6)

>>3243263
I think we're out of time for twiddling around. Let's get there, we've already announced our presence to anyone paying attention, no point going in blind.

>activate sensors, direct route.

(btw, I was under the impression that our sensors were far superior to the longswords, even two squads of them, why the modifier difference?)

Rolled 8 + 6 (1d20 + 6)

>>3243271
whoops. wrong roll.

>>3243274
ok i definitely typed "-6" that time... whatever.

Rolled 12 + 6 (1d20 + 6)

>>3243268

Rolled 17 - 5 (1d20 - 5)

>>3243263
>>3243266

Rolled 10 + 6 (1d20 + 6)

>>3243263
Wait, I thought Alpha is our eyes and Bravo is sitting in hangar...? In any case, full burn towards Surigao Strait. Activate all system, recall all fighters to our vicinity if some are far away.
>Activate your sensors and take the direct course to the Surigao Strait. (1d20-6)

>>3243299
>>3243282
ok i'm glad it's not just me.

>>3243271
I messed up on that. The option to activate your sensors is meant to have a -5 while the longsword option is meant to have the -6. I will take the intended debuff into account when deciding the mean score.

>>3243299
You deployed Alpha first to scout out for the fleet, before deploying Bravo squadron to act as your eyes.

>>3243351
lol we told Toulali to take us toward Toulali. Waifu confirmed?

>send a patching team

Mean roll: 6.333
Success threshold: 8
Result: Failure (minor)

“Bring us out of silent running. I want all sensors up and weapons online. Lieutenant Toulali, take us directly towards the Surigao Strait.” You ordered. And the bridge crew snapped into action. Consoles flashed as weapons were keyed into activity, sensor suites were roused and began mapping the area around you, and soon your navigation officer was taking you directly towards the gutted light cruiser.

The fact that the bridge viewport screen was brought up was just one of the first visual cues that the ship was headed into a very precarious position. And if that wasn’t enough, you could hear the micro-debris striking the side if the bridge. Much of it wasn’t heavy enough to cause any real damage. But it didn’t take long before you did run into something that could punch through your hull.

The frigate was soon knocked by a sudden jolt, depressurisation alarms immediately snapped on as your “Impact! We’re losing pressure in hanger port six!” One of your bridge officers, the damage control director, called out.

“Isolate the hanger, and shut off that alarm. Is there anyone inside the hanger?” You ordered, and a couple of seconds later, the loud, whooping alarm was shut off.

“Negative sir, it’s one of our storage areas. Should I dispatch a damage control team to check the damage?” Your damage control director asked, turning from his station to face you.

>Deploy one of the damage control teams, you need to patch the damage before something worse comes around.
>Hold your damage control teams, you don’t know if there is something worse out there.
>Other (write in)

>>3243351
>>3243361
Anyone who played FTL should know that we have to
>Deploy one of the damage control teams, you need to patch the damage before something worse comes around.
In any case, if they are not already, have longswords help with navigation. Also, what's the status of our Alpha wing?

>inb4 our first loss comes from environmental damage while no hostiles are around, caused entirely by the commander's ill judgement

Also, no proofreading OP? I noticed way more errors than in Pilot Quest

>>3243355
It's a guy

>>3243361
>Deploy one of the damage control teams, you need to patch the damage before something worse comes around.

>>3243361
>>Deploy one of the damage control teams, you need to patch the damage before something worse comes around.

>>3243361
>Deploy one of the damage control teams, you need to patch the damage before something worse comes around.

>>3238364
To get a - you need to use +- because fucknows why

>>3243461
I blame Hiroshimoot

“Deploy one of the damage control teams to patch the damage.” You ordered. You didn’t want to take the chance that another piece of debris would enter in through the hole made by the first, an cause a breech deeper within the ship.

“Understood sir, damage control team one is en-route.” The damage control director reported back after a few seconds. You endured the sound of lighter debris pinging off your warship’s hull for almost 10 minutes before you finally broke through the worst of the debris field and arrived before the Surigao Strait.

The Surigao Strait had been hit by a covenant energy projector, which had destroyed the reactor cooling systems, vaporized a number of hangers and reduced a significant portion of the hull to little more than overheated vapor and free-floating molecules. However, this wasn’t the only damage that the ship had sustained. Vast craters had been blown into the ship by plasma torpedoes, leaving craters in the large vessel’s hull. Her reactor had melted down and breached, flooding the aft of the ship with deadly radiation that would have surely killed the crew had the lack of air not got to them first.

But there was more damage than that. Whole sections of her bow and underbelly had been carved away, revealing the internal structure of the vessel to the void. Sensors had been cut off and large sections of two-meter-thick titanium A battle plating had been removed.

Unlike the space elevator, the Surigao Strait had been obviously scavenged.

>Scan the cruiser with the frigate’s own sensors, you’ll need it in order to cut through the radiation (1d20-2)
>Send a marine VBSS team, you can’t trust your sensors to get the job done with the radiation polluting the area.
>Other (write in)

Rolled 18 - 2 (1d20 - 2)

>>3243489
>>Scan the cruiser with the frigate’s own sensors, you’ll need it in order to cut through the radiation (1d20-2)

No sense in sending marines until we have recent evidence of activity. Not to even mention the radiation leak.

Rolled 18 - 2 (1d20 - 2)

>>3243489
>Unlike the space elevator, the Surigao Strait had been obviously scavenged
Space elevator had been scavenged too, wasn't it?

>>Scan the cruiser with the frigate’s own sensors, you’ll need it in order to cut through the radiation (1d20-2)
Also, where the fuck is Alpha squadron?

Rolled 4 - 2 (1d20 - 2)

>>3243489
>>Scan the cruiser with the frigate’s own sensors, you’ll need it in order to cut through the radiation (1d20-2)

>>3243504
They are outside of the debris field, looking for the rest of the wolfpack. And they will continue to unless you recall them back to the frigate or assign them to do something else.

>>3243511
In that case I also vote for recalling them immediately

Rolled 12 - 2 (1d20 - 2)

>>3243489
>Scan the cruiser with the frigate’s own sensors, you’ll need it in order to cut through the radiation (1d20-2)

Rolled 14 - 2 (1d20 - 2)

>>3243489
>Scan the cruiser with the frigate’s own sensors, you’ll need it in order to cut through the radiation (1d20-2)

>>3243489
>Send a marine VBSS team, you can’t trust your sensors to get the job done with the radiation polluting the area.

Mean roll: 11.333
Success threshold: 8
Result: Success (minor)

“Same as before lieutenant, scan the vessel with our sensors.” You ordered your sensor systems officer. And this time, she leveraged as much of the scanning power she could get out of the sensors mounted on the Dawn’s Early Light. She had to. The radiation leaked by the reactor core demanded it.

Unlike the space elevator, the Surigao Strait was far more interesting. The damaged reactor still put out some limited amount of power. Enough to run some of the lights and the computer systems. There wasn’t an AI still onboard, as the main matrix that housed the ship’s AI had self-purged on the captain’s orders. And with so much of the ship’s internal sections exposed to the hard vacuum, you didn’t need to look hard in order to see active lights.

However, the most interesting part was deeper inside the ship.

“Sir, I see heat signatures in the vessel’s mess hall.” Lieutenant Helena called out, pinging the location on your screen. Sure enough, there was a good dozen or so heat signatures within. Though the signatures were hampered by the sheer amount of metal in the way and the suits themselves. As such, you couldn’t get a solid read on just how many signatures were inside.

>Deploy a VBSS team to investigate the heat signatures, you don’t want them trying to escape.
>Try and gain access to the Surigao Strait’s computers remotely. You can take a look without needing to set foot on the ship (1d20-6)
>Scout out the debris field nearby, those heat signatures must have come from somewhere.
>Other (write-in)

Rolled 19 - 6 (1d20 - 6)

>>3243625
>Send Bravo to scout around for whatever it is these heat signatures came in on
>Try and gain access to the Surigao Strait’s computers remotely. You can take a look without needing to set foot on the ship (1d20-6)
>Try to contact our Alpha squadron, recall them back to our ship

Rolled 7 - 6 (1d20 - 6)

>>3243625
>Try and gain access to the Surigao Strait’s computers remotely. You can take a look without needing to set foot on the ship (1d20-6)
>Scout out the debris field nearby, those heat signatures must have come from somewhere.

Try to get more info before sending our men in.

Gotta say averaging rolls is pretty shit for a system

>>3243625
>Deploy a VBSS team to investigate the heat signatures, you don’t want them trying to escape.
>>3243663
Agreed but c'est la vie

>>3243625
>>Deploy a VBSS team to investigate the heat signatures, you don’t want them trying to escape.

>>3243663
Agreed, only first roll should be taken into account and at the same time the dice should be the same and for all the options. Obviously GM knows which choices actually need the dice and would apply any bonuses/penalties himself.

Rolled 10 - 6 (1d20 - 6)

>>3243625
>>Try and gain access to the Surigao Strait’s computers remotely. You can take a look without needing to set foot on the ship (1d20-6)

File: halcyon mess hall.jpg (37 KB, 800x600)

37 KB JPG

Mean roll: 6
Success threshold: 5
Result: Success (minor)

“Lieutenant Koekemoer, try and access the Surigao Strait’s computers. See if you can gain access to the ship’s security camera system.” You instructed your intelligence officer, before turning your attention to your navigation and sensor officers. “Nav, take us away from the Surigao Strait. Sensors, begin a wide search of the area. Some ship must have dropped off those heat signatures off, and I want to find it.”

“Sir, I will need one of bravo’s longswords to stay near to the cruiser for relay purposes.” Koekemoer requested flatly, though you had little room to deny her a relay.

“Granted. Aviation, order one of bravo’s craft to stay near to the cruiser. Dispatch the other two to assist in the search.” You ordered as the Dawn’s Early Light moved away from the much larger cruiser, before then adding. “And recall alpha squadron. We may be getting into a fight soon.”

After your aviation chief gave you the confirmation that the orders had been given, the next quarter of an hour was filled with reports of nothing being found among the debris field. The untold millions of pieces of debris, ranging from centimeter-size flakes of armor all the way up to entire ships made searching a tedious affair, and the leaks of various types of radiation made things even worse. And worse still, it took you further away from the cruiser. However, you were finally given some good news from your resident spook.

“Gotcha, commander I have a connection. Piping the feed to your screen now.” Your intelligence officer notified you with mirth in her voice. You looked down at your screen in time to see it change to see it flick over to a semi-corrupted, grey-scale feed of the insides of the Surigao Strait. The mess hall was packed full of assorted pieces of equipment, personal effects, and weapons. MA5B assault rifles, rocket launchers and canisters of C7 foaming explosives sat side-by-side with computer stacks, holographic projector tanks, and LCD screens.

“Damn bird bastards.” Dyad commented, once again leaning over your shoulder as one of the scavenging aliens walked into view.

The jackal was named not for its looks. But for its demeanor. The semi-avian, semi-reptilian aliens were pack scavengers. That often looked to expand their own wealth and personal status before trying to save others of their own species. Groups of jackals were often employed by the covenant as harassing troops and skirmishers. And in space was no different, with jackal cutters often acting as raiders and scouts. This suited the jackals well, as it allowed them to do work while partaking in their darkest indulgences. And right now, you had a front-row seat to look at one of their vices.

That being their rampant kleptomania.

>CONT

>>3244170

The jackal that walked into the picture before you wore a dark, form-fitting vacuum suit that mimicked the undersuit that VBSS teams and ODSTs used. On top of that, it wore an armored suit, complete with an opaque visor that saved you from having to gaze upon its ugly face. On its hip it carried a plasma pistol. Which usually meant that it carried an energy shield on the other arm. Covenant plasma weapons tech were superior to human tech in some regards, but shield were where they knocked it out of the ballpark. In spite of the idea of a personal energy shield being in the minds of humans for some 500 odd years, one could never be produced outside of massive lab-based prototypes that could barely stop a bullet. The covenant, on the other hand, were mass producing enough of the damn things to equip their disposable troops.

“Well, I guess that we know who’s been stealing everything. Your orders sir?” Dyad commented, prompting you to give the next order.

>Deploy a VBSS team to kill the jackals and take their gear. The idea of scavenging from the scavengers is entertaining.
>Obliterate the jackals with an archer missile. You aren’t in the mood to waste lives for tech that is easy to obtain on a battlefield.
>Leave the jackals and act interested in some other ship. Maybe you can draw their mothership out to play.
>Other (write-in)

>>3244174
>>Deploy a VBSS team to kill the jackals and take their gear. The idea of scavenging from the scavengers is entertaining.

>Leave the jackals and act interested in some other ship. Maybe you can draw their mothership out to play.
we still hold the cards, no reason to blow our cover yet

>>3244174
>Leave the jackals and act interested in some other ship. Maybe you can draw their mothership out to play.

>>3244174
>>Leave the jackals and act interested in some other ship. Maybe you can draw their mothership out to play.

I want to be prepared to fire an archer missile on this ship should things go sideways though. If we have to run, or if we get into another fight I want a missile launched, and the jackals killed before we forget about them. They could very well have hidden a smaller ship in the wreckage of this one and I'd rather not let them escape

File: space phantom.jpg (39 KB, 640x360)

39 KB JPG

“Nav, sensors, keep up the search and act as if we are interested in some other wreckage. Intel, leave a backdoor in the Surigao Strait’s computer system so we can access it as needed. Aviation, once Intel is done making the backdoor, have the longsword closest to the Surigao Strait back off into the debris field and go dark to observe the ship. Weapons, I want you to key and archer missile to fire on the Surigao Strait’s mess hall. But do not fire it until we engage the enemy or are engaged ourselves. And run up the MAC while you are at it.” You began firing off orders in rapid secession. You didn’t like the idea of the jackals remaining un-killed. But you didn’t want to give any covenant ship in the area reason to leave just yet. Hell, there was already a high enough likelihood that the jackals in charge of the ship that dropped the raiders off had already decided to cut its losses and come back later.

Probably after the ones onboard the Surigao Strait had run out of air. But that was just how things worked among the bastards, one dead jackal was one less jackal to split the spoils with.

It took you another half an hour of slow searching, you surveyed the wreaks of two more freighters and a gutted Mako class corvette. The old Mako class had a similar blocky construction to the Halcyon-class, but it was under a quarter of the size. Though it was a very lightly armored vessel, as evidenced by the one you surveyed having been almost cut in two by a plasma torpedo hit amidships. However, the monotony was soon broken by an inbound transmission.

“Dawn’s Early Light, this is longsword bravo two. I’ve got a phantom leaving the Surigao Strait. Requesting permission to pursue? The man on the other end reported, and as if to provide proof for what he was seeing, you received a short video recording of the phantom leaving the stricken vessel. A quick look back into the mess hall confirmed that there were still jackals onboard, and loot as well. The phantom leaving the vessel was probably transporting loot back to their mothership.

>Order the bravo-two to tail the phantom quietly and at range. If anything goes wrong, get out fast. (1d20-6)
>Order the bravo-two to chase the phantom as aggressively as possible. Try and force them to run back to their mothership. (1d20-4)
>Order the bravo-two to hold position. If the jackals have fallen for your bluff, they will return.
>Other (write-in)

Rolled 6 - 6 (1d20 - 6)

>>3244476
>I’ve got a phantom leaving the Surigao Strait.
Fucking new it

>Order the bravo-two to chase the phantom as aggressively as possible. Try and force them to run back to their mothership. (1d20-4)

Lets take the fight to them, I don't want them getting away

Rolled 20 - 6 (1d20 - 6)

>>3244476
>>Order the bravo-two to tail the phantom quietly and at range. If anything goes wrong, get out fast. (1d20-6)
This is our chance to find where their mothership is.

Rolled 10 - 6 (1d20 - 6)

>>3244476
>Order the bravo-two to tail the phantom quietly and at range. If anything goes wrong, get out fast. (1d20-6)

Rolled 1 - 6 (1d20 - 6)

>>3244476
>Order the bravo-two to tail the phantom quietly and at range. If anything goes wrong, get out fast. (1d20-6)

File: 1538187673176.jpg (227 KB, 810x892)

227 KB JPG

>>3244867
Fuck me

Rolled 7 (1d20)

>>3244880
Well, this sortie is off to a great start.

Rolled 2 - 6 (1d20 - 6)

>>3244476
>>3244648

Rolled 11 + 6 (1d20 + 6)

>>3244867
>>3244922
>>3245872
we should probably all stop rolling now.

File: Space Banshee.jpg (46 KB, 640x360)

46 KB JPG

Mean Roll: 6
Success threshold: 6
Result: Success (minimal)

“Bravo-two, begin tailing the phantom. Keep emissions low and break off if engaged.” You ordered, not wanting to lose your chance to find the covenant raider. Your longsword didn’t respond audibly, but you watched as the IFF for the tailing longsword began to move after the phantom. Even running with most of its systems off and it’s thrusters at almost minimal output, the longsword was able to keep up with the enemy dropship. The Phantom moved lazily along, keeping a wide berth from the larger pieces of debris while allowing the smaller pieces to bounce harmlessly off its shields. It lead your longsword past at least five destroyed freighters, a partially vaporized Diligence class destroyer, and towards a bisected Springhill class mining vessel.

That was where they sprung their trap.

“Dawn’s Early Light! Banshees incoming, they’ve spotted me!” The pilot of the longsword called out, as six more contacts appeared from the space surrounding the longsword. It didn’t take long for your sensor officer to match their signatures to space banshees.

The space banshee. Essentially a modified version of the typical banshee used by the covenant for in-atmosphere air superiority, the space banshee made up the “quantity” arm of covenant’s space-fighter wing. What it lacked in energy shielding and anti-ship weaponry was made up for in its cheap construction and small profile. ONI’s docket on the craft suggested that it may be an older design in the process of being phased out, which partially explained why it was all the way out here. As history had shown, it was far easier to steal from a boneyard than from a military base.

>Order bravo-two to continue tailing the phantom, you will order the rest of the squadron to get the banshees off them. (1d20-4)
>Order bravo-two to destroy the banshees before continuing the pursuit, there is no point in chasing the phantom with banshees on their tail. (1d20-4)
>Order bravo-two to disengage, you have a rough area to work with now.
>Other (write-in)

Rolled 6 + 4 (1d20 + 4)

>>3246347
We know generally where they are, no point continuing to tail if they are intimately aware of it.

>B-2, engage, Bravo wing to their location. ETA on Alpha?

>>3246380
omg I'm never rolling again.

Rolled 14 - 4 (1d20 - 4)

>>3246347
>>Order bravo-two to destroy the banshees before continuing the pursuit, there is no point in chasing the phantom with banshees on their tail. (1d20-4)

Rolled 1 + 4 (1d20 + 4)

>>3246347
>>Order bravo-two to destroy the banshees before continuing the pursuit, there is no point in chasing the phantom with banshees on their tail. (1d20-4)

>>3246391
Fuck

>>3246385
hey man did you do "dice+1d20+-4"? because i'm doing dice+1d20-4 and it keeps changing it to a plus

Rolled 3 - 4 (1d20 - 4)

Can one longsword destroy 6 banshees effortlessly? I don't want to risk this.
>>3246347
>Order bravo-two to disengage, you have a rough area to work with now.
>Order Bravo to regroup as one cohesive unit then attempt to continue tracking Phantom
>Start mapping the quickest way out of the debris in case we need to bail
>Status of Alpha wing?
Also how effective would debris be in deflecting enemy sensors and fire?

>>3246396
You’ve got to do +- in order to get a m8nus, because Hiroshimoot is retarded

Rolled 19 - 4 (1d20 - 4)

>>3246347
>Order bravo-two to continue tailing the phantom, you will order the rest of the squadron to get the banshees off them. (1d20-4)

Mean Roll: 4
Success threshold: 6
Result: Failure (minor)

“Bravo-two, you are cleared to engage the enemy Banshees. We’re vectoring the rest of bravo to assist.” You ordered, before turning to your aviation officer. “Vector the rest of bravo squadron to assist bravo-two. And what’s the ETA for alpha squadron?”

“Alpha Squadron is just entering the debris field, eta is between twenty and thirty minutes. Bravo squadron is en-route, eta is five to ten minutes tops.” Zaied replied quickly, after giving out rapid-fire orders to the rest of bravo squadron.

While you could work with bravo’s arrival time, you just couldn’t rely on alpha squadron to be a credible source of help for the rest of Bravo Squadron. You needed to get there, fast.

“Nav, plot us the fastest course to bravo-two’s location. You have full access to the primary thrusters and sensors.” You ordered, and a couple of seconds later, you felt yourself being pressed into your seat as Toulali brought your vessel’s primary powerplant online.

And for the entreaty of that journey, you were powerless to help bravo-two. Had the debris field not been there, you could have fired off some Streak anti-fighter missiles to swat the banshees out of the void. But with so much debris floating around, there was little chance that the missiles would reach their targets. You watched on your holographic display tank as the single longsword faced off against half-a-dozen enemy fighters. Almost immediately, bravo-two scored a kill with a pair of missiles. But soon the fight closed to guns range. And here, the longsword had the disadvantage. While it was tougher, faster, and better armed than the banshees. The longsword was also much larger and less maneuverable.

Still, bravo-two proved that his training had not been wasted. The large fighter damaged one banshee in a head-on merge but also soaked some damage in return. And soon, bravo-two began a pattern of slashing attacks. Where he would gain separation with his longsword’s powerful engines before turning around and trying to carve a chunk out of the enemy formation. However, the enemy pilots were not stupid and soon began to counter this strategy by dodging out of the way of his slashes and firing on your pilot as he tried to escape.

And soon enough, they scored a serious hit. The longsword began to slow down, as the banshees began to catch up.

“Bravo-two to Dawn’s Early Light, I’m losing engine one. I can’t keep up the pursuit much longer!” The pilot reported back, the phantom was retreating as fast as it could, headed towards the remains of the Springhill class mining ship. But it could just be trying to lure your suspicions away from the actual mothership.

>Order bravo-two to retreat, you can’t risk one of your pilots like this.
>Order bravo-two to continue, you can’t lose that phantom.
>Other (write-in)

>>3246537
>>Order bravo-two to retreat, you can’t risk one of your pilots like this.

>>3246537
>>Order bravo-two to retreat, you can’t risk one of your pilots like this.

>>3246537
>Order bravo-two to retreat, you can’t risk one of your pilots like this.

Is our MAC pre-charged by this point?

>>3246537
>>Order bravo-two to retreat, you can’t risk one of your pilots like this.

>>3246537
>Order bravo-two to retreat, you can’t risk one of your pilots like this.
>Get in contact with Alpha squadron, have them report what they encountered while they were out scouting

>>3246606
where TF is the wolfpack.

>>3246701
I'm assuming no-show or DOA. It's not like we're using warp travel where time varies.

>>3246537
>Order bravo-two to retreat, you can’t risk one of your pilots like this.

Rolled 5 (1d5)

>>3246701
Rolling for what happened to them.
1. Slipspace drive malfunction
2. Ambushed and killed
3. Ambushed and fled
4. CSO out of fucking nowhere
5. Very late

>>3246792
Good omens

>>3243774
First roll only is also shit

>>3246537
>>Order bravo-two to retreat, you can’t risk one of your pilots like this.

“Get out of there bravo-two. The rest of bravo squadron will finish the fight.” You ordered, recalling your damaged longsword away from the fight. You didn’t want to lose someone on your first ever mission.

The banshees began to gain on bravo-two for a few seconds before the longsword pilot kicked his engines on to full. And soon, the Banshees were left far in his wake. The sheer thrust output from the longsword’s engines allowed it to outpace the banshees even with an engine damaged. They kept up the chase for a couple of minutes before breaking off their chase and heading back towards the phantom, which they escorted behind the bisected mining ship.

Bravo squadron arrived on-scene a few minutes after they disappeared from your sensor picture. And the Dawn’s Early Light arrived a few minutes after them. Your vessel only having slowed down once to allow bravo-two to land in one of the hangers.

>Wait for Alpha to arrive, before sending them and the remains of Bravo in first to try and force the enemy out.
>Head in there first. You don’t want the longswords to run head-first into a bunch of point-defense lasers.
>Other (write-in)

>>3247020
>>Head in there first. You don’t want the longswords to run head-first into a bunch of point-defense lasers.
The element of surprise is already ruined. Might as well start swingin' our dick on this one.

>>3247020
>>Head in there first. You don’t want the longswords to run head-first into a bunch of point-defense lasers.

>>3247020
>Head in there first. You don’t want the longswords to run head-first into a bunch of point-defense lasers.

>>3247020
>>Head in there first. You don’t want the longswords to run head-first into a bunch of point-defense lasers.

Rolled 13 (1d20)

>>3247020

>>3247026
>>3247035
>>3247058
>>3247080
Support but
>Before going in there blind order Bravo to spread wide and circle behind the mining ship in order to see what's lurking there
We have a spare fighter if I remember correctly...? If it's feasible
>Let the pilot from damaged craft reship and send him out again
Also
>Alpha status report for fuck's sakes
We managed to communicate orders to them so why are they unable to report what they saw on their trip?

>>3247020
>Head in there first. You don’t want the longswords to run head-first into a bunch of point-defense lasers.

File: Jackal raider.png (1.64 MB, 1510x648)

1.64 MB PNG

“Chances are that the enemy vessel is sat behind the remains of the mining ship.” Dyad stated as your frigate knocked the remains of the destroyed space banshee out of the way. The vessel of composites and light materials shattered like glass against your ship’s hull.

“And chances are that they are sat back there with weapons charged and ready to shoot down whatever comes around into their weapons range.” You added to her comment, bringing light to your predicament. And right now you had no real idea if you were facing off against a basic raider, or something much larger.

“Missile systems will not be functional, there is too much debris.” Your weapons officer piped up, giving you just another piece of bad news to deal with. The loss of your missiles left you with only ballistic weapons options, of which you had two. The first being the MAC gun, and the second being the point defence guns. You had always planned to use the former, but the latter was only good for slaughtering fighters and maybe plasma torpedoes. Granted, the guns could be useful against smaller warships. But anything over 300 meters long would be invulnerable to them.

It took you almost a minute to weigh up your options, before finally deciding to leverage as much firepower as possible. “Nav, bring us around the mining ship. Make it steady, I want to have a good shot at the enemy ship with the MAC gun.”

Toulali executed your orders with some slight creativity. He accelerated the frigate on a course that would take it past the mining ship, before deactivating the ship’s inertial dampening systems and using the vessel’s manoeuvring thrusters to track the spinally mounted MAC at whatever was on the other side of the ship. And it seemed that you were in luck, as you found yourself face-to-face with the covenant’s lightest warship.

The covenant raider. Mostly used by jackals, the covenant raider was the rough equivalent of the UNSC’s Mako class corvette. Fast, and carrying an equal mix of 6 anti-fighter pulse lasers and 6 anti-ship plasma cannons. The raider was designed to get in close and cause as much damage as possible, all while keeping itself protected from fighters. However, this particular vessel seemed to have seen you coming, and was waiting with weapons charged and ready to fire. Each blotch of purple fire along the hull marking out a single weapon that was ready to spit burning plasma right at you.

>Take evasive action! You don’t want to get hit by their weapons, even if that means spoiling your MAC gun shot. (roll 1d20-4 for evasive action, MAC shot will be resolved in the next post)
>Soak the hits and get a MAC gun shot off. At this range, you should only need one shot to cripple the ship! (roll 1d20+4 for the MAC gun, evasive action will be resolved in the next post)
>Other (write in)

Don't frigates have those emergency boosters?

Rolled 11 + 4 (1d20 + 4)

>>3247212
lel, americans saying "is sat" or "are sat"

>Soak the hits and get a MAC gun shot off. At this range, you should only need one shot to cripple the ship! (roll 1d20+4 for the MAC gun, evasive action will be resolved in the next post)
i'm confident in my roll.

Rolled 19 + 4 (1d20 + 4)

>>3247212
>>Soak the hits and get a MAC gun shot off. At this range, you should only need one shot to cripple the ship! (roll 1d20+4 for the MAC gun, evasive action will be resolved in the next post)

Rolled 12 + 4 (1d20 + 4)

>>3247212
>Soak the hits and get a MAC gun shot off. At this range, you should only need one shot to cripple the ship! (roll 1d20+4 for the MAC gun, evasive action will be resolved in the next post)

>>3247234
>>3247235
>>3247238
hell ye

Rolled 15 + 4 (1d20 + 4)

>>3247212
>Soak the hits and get a MAC gun shot off. At this range, you should only need one shot to cripple the ship!
If I know anything about space combat in Halo it’s that playing it safe never works. Balls to the wall, that’s the only way

Just gonna take a moment to say I'm enjoying playing at being an officer. Even if I'll never be one.

Rolled 1 + 4 (1d20 + 4)

>>3247212
>Soak the hits and get a MAC gun shot off. At this range, you should only need one shot to cripple the ship! (roll 1d20+4 for the MAC gun, evasive action will be resolved in the next post)

>>3247231
"Booster" is a bit generous for what is essentially a controlled explosion. But yeah, they are standard on UNSC vessels, but are one-use systems that can only be replenished when you enter dock. You have a total of 4 of these systems installed on the ship (up, down, port and starboard).

However, using them right now is not advisable for a couple of reasons. First being that you are in the middle of a debris field, so you might dodge out of the way of burning hot plasma, only to pretty much ram into a massive piece of debris. And the second being that usually you have to have everyone strapped into harnesses for when those systems are used, as they have a tendency of sending things flying.

>>3247250
No more rolls past this, please.

Seems like we have our very first kill

File: paris class mac.jpg (134 KB, 1916x805)

134 KB JPG

Mean roll: 18
Success threshold: 10
Result: Success (significant)

“Fire the MAC!” You ordered your weapons officer, but he was already ahead of you. And at such close range, with the navigations officer having already pointed the Dawn’s Early Light’s bow on target, all he had to do was use the RCS system to fine-tune the shot and press a single button.

The covenant warship sat with its bow facing you, giving your weapons officer a massive target to hit. And at just a little over two kilometers away, it was pretty much at point blank range. A humming noise began to emanate from the ship and rose in pitch over the course of a couple of seconds as the MAC gun’s coils charged. Before with a crash, the coils discharged with only a few milliseconds between them. Propelling the 300-ton tungsten shot to ludicrous speeds.

Even at long range, there is rarely enough time for a covenant ship to dodge an incoming MAC round. And this was practically a point-blank shot. The equivalent of holding a .50 caliber sniper rifle a centimeter away from someone and pulling the trigger. At such close range, you could watch as the enemy raider was hit with a weapon that could cripple a much larger warship with one hit.

The raider managed to fire off four plasma cannons, and three pulse lasers before your MAC fired. The enemy ship’s shields flickered for less than a second as it worked in futility to stop the MAC round, but it failed. The impact of the shot sent the enemy vessel flying away like a discarded doll, it’s central hull almost split in half like a log. One of the vessel’s arms was snapped off completely as the vessel tumbled away, venting atmosphere.

However, the raider had already managed to get its shots off. And while the pulse lasers had been rushed, the shots from the plasma cannons had been handled with far greater care.

>Roll 1d20-6 to dodge.

Rolled 14 - 6 (1d20 - 6)

>>3247311
Big money. Big money. No whammies and STOP

Rolled 11 + 6 (1d20 + 6)

>>3247311
wew

Rolled 15 - 6 (1d20 - 6)

>>3247311
Eh who cares, we have point-defense guns, r-right?

>>3247331
Plasma torpedos aren’t actually torpedos. There’s nothing to shoot with our point defense.

Unless they retcon’d something. Again

.

>>3247334
Oh, wait. It’s a plasma cannon.

Still. Unless they’ve retconned something, there’s not a physical thing to destroy, as it’s basically a ball of magnetically contained plasma. So actually the best bet is murderize the fuck out of the ship and hope the plasma dissipates

Rolled 19 - 6 (1d20 - 6)

>>3247345
fucking godd amnit

No more rolls anons, I think we got this!

>>3247346
Yeah I just read wiki and it says the shots need guidance from the firing ship. Here's hope with debris floating all around and the ship itself being exploded we are gonna make it.

>>3247334
According to the new lore, plasma torpedoes are essentially canisters wreathed in plasma that are "guided" towards a target. Apparently you can shoot them down, but I have no idea about the specifics of it. I imaging it's something along the lines of shooting so much stuff into the torpedo that it somehow damages the canister within, detonating it before it hits your ship.

>>3247357
well sure let's give that a go then. I probably would've taken a shot at it anyway, maybe if we pump it full of lead it'll... disrupt the plasma containment... or something.

Beats the hell out of doing nothing.

>>3247357
That’s fucking retarded.

>>3247391
343i are retarded in general.

>>3247393
Yep, this is also the company that says that a light cruiser based off a battlecruiser design should be smaller than a corvette.

Mean roll: 7.33
Success threshold: 8
Result: Failure (minimal)

You didn’t need to speak for your next order to be carried out. With a sudden roar, the frigate’s engines snapped into life. Working in unison with the maneuvering thrusters to quickly move your ship out of the way of the enemy fire. He brought your thrusters online and forced the ship towards the enemy vessel, headed up and over where it once sat.

He managed to get you out of the way of all but one of the plasma cannon shots. Had they all been aimed properly, they would all have hit where the Dawn’s Early Light would have drifted into. However the one rushed shot, the one that should not have hit, ended up being the only one that did.

A muted thud reverberated through the ship, and alarm klaxons soon followed it.

“Hull breach on the ventral hanger! Nobody is in the section, isolating it.” Your damage control officer crowed out, before silencing the alarm. All things considered, it was a hit. But at least you hadn’t lost anyone to said hit.

And with the enemy now vanquished, you had some options to consider, as your crew cheered at your first successful kill.

>Investigate the covenant raider, pick through their spoils.
>Destroy the covenant raider completely. You don’t want it limping off back home.
>Return to the Surigao Strait, you don’t want to leave any jackals alive.
>Leave the debris field and head out. The jackals on the Surigao Strait can suffocate well enough on their own.
>Other (write-in)

>>3247413
>Destroy the covenant raider completely. You don’t want it limping off back home.
They would do the same to us. REMOVE FOOD NIPPLE

>>3247413
>Destroy the covenant raider completely. You don’t want it limping off back home.

>>3247413
>Destroy the covenant raider completely. You don’t want it limping off back home.

let's not retreat in the midst of ass kicking

Rolled 14 (1d20)

>>3247413
>Status report on the extent of damage we sustained
>If possible, launch our spare fighter and have it rejoin Bravo
>Alpha wing status/report?
Raider is the ship we just hit? Wasn't it a total loss? If not
>Investigate the covenant raider, pick through their spoils
>Confirm Banshee location near/within the raider with a directional scan, if we cannot confirm send Bravo to search for it
>after this enter passive mode again

>>3247413
>Investigate the covenant raider, pick through their spoils.
Covenant tech is always valuable

>>3247413
>>Destroy the covenant raider completely. You don’t want it limping off back home.

>>3247413
>Investigate the covenant raider, pick through their spoils.

LOOT

>>3247413
>Investigate the covenant raider, pick through their spoils

>>3247413
>>Investigate the covenant raider, pick through their spoils.

>>3247577
>>3247564
>>3247525
>>3247413

We could also learn a lot from what they find valuable. What they're carrioning for is probably what they have the hardest time finding. Might be helpful to the war effort. And who knows, it might be helpful to us.

>>3247619
On the other hand, it’s entirely possible that they’ll wait until our VBSS team is on board and then allah ackbar. Better to not risk it

>>3247638
a fair point. I got the impression their craft was in multiple pieces all venting atmosphere and assumed we're probably pretty safe to board.

We get a bonus to that too, don't we?

>>3247413
>>Destroy the covenant raider completely. You don’t want it limping off back home.

>>3247645
I think it would safe to assume the VBSS team has vacuum sealed suits for just such a situation. And I doubt the Jackals are gonna suicide bomb themselves. They don't have the same general fanatic devotion to the Covenant the other races have. They are primarily pirates and mercenaries after all.

>>3247413
>>Investigate the covenant raider, pick through their spoils.

>>3247413
>Destroy the covenant raider completely. You don’t want it limping off back home.

Need a tiebreaker between destroying the enemy ship completely, or trying to board it.

Rolled 2 (1d2)

>>3250043
1 - Destroy
2 - Board

>>3247413
>Investigate the covenant raider, pick through their spoils

Hey Thunder, ONI is still in the ‘loot all the tech’ stage with the covies right?

>>3250067
It’s ONI. They’re never NOT in “loot all the tech” mode. Unless they’re in “let’s commit war-crimes and crimes against-nature” mode

>>3250043
>>3250065
Yes, board. Take it back home for the boys in R&D to reverse engineer.

>>3250647
I thought we wanted to avoid getting involved with spooks.

>>3250779
Getting involved with Spooks is the fastest way up the ladder

>>3250838
But at what cost?

>>3250779
I thought we were involved whether we want to be or not

“Nice work people, that’s splash one raider for us.” You congratulated your bridge crew on the kill. “Nav, weapons, great work on that you two.”

“Thank mister Bergen. That was his kill.” Lieutenant Toulali credited your weapons officer with the kill.

“Well, then congratulations to mister Bergen then.” You corrected yourself, before getting back to business. “Sensors, what’s the status of the enemy vessel.”

“Significant damage, their reactor is basically gone. They are also venting atmosphere. They are on course to collide with the wreak of a large cargo ship in just under half an hour’s time. It will take ten minutes for a team to arrive on ship for salvage. The resulting damage from the crash will cause significant damage to the ship, and may even fully destroy it.” Your sensor officer explained to you, sending the predicted elementary of the raider VS the wreak.

This gave you an impasse. You could order a salvage team out immediately and try to get as much out as possible in the 20 minutes you had before the raider crashed into the cargo ship wreck. Most of the ship had been critically damaged by the MAC gun hit, but even a couple of intact pieces of warship-grade tech would be incredibly valuable to ONI. However, you would be on a time limit. You could also wait until after the ship had crashed into the cargo ship. You wouldn’t be up against the clock, but there would be even less to recover.

Alternately, you could just leave the wreak alone.

>Launch a salvage team immediately, you want some semi-intact salvage for the ONI eggheads.
>Hold the salvage team for now, you don’t want to risk anyone by rushing.
>Leave the wreak to crash. It’s time to go.
>Other (write-in)

>>3250904
>>Hold the salvage team for now, you don’t want to risk anyone by rushing.

>>3250904
>>Hold the salvage team for now, you don’t want to risk anyone by rushing.

>>3250904
>Launch a salvage team immediately, you want some semi-intact salvage for the ONI eggheads

Do longswords have tow lines?

>>3250904
>Launch a salvage team immediately, you want some semi-intact salvage for the ONI eggheads.

>>3250904
>>Hold the salvage team for now, you don’t want to risk anyone by rushing.

>>3250914
This. Is there any way we can slow or stop or maybe change the wreck's course?

>>3250904
>Launch a salvage team immediately, you want some semi-intact salvage for the ONI eggheads

>>3250914
>>3250953

Neither longswords nor pelicans have tow lines. Nor are they powerful enough to move the raider, even if they tried.

>>3250979
>>3250979
How about the Dawn itself?

>>3250981
You could try and catch up to the raider and nudge it off it's current course. But you would have to roll high in order to both catch up to and successfully move the raider off it's current course, and avoid the wreak of the cargo ship itself. During said time, you would not be able to launch a salvage team, as it would be unsafe for them to be on the raider while you are ramming it. Additionally you also run the risk of damaging the raider during the manoeuvre.

If you want to try it, then you'll have to roll 2d20.

>>3250904
>Launch a salvage team immediately, you want some semi-intact salvage for the ONI eggheads.

>>3251006
Right, too much effort

File: Screenshot (1).png (686 KB, 1275x731)

686 KB PNG

Also, I have to do some stuff and won't be able to continue running today. As tomorrow will be the start of the new week, I won't be running on Monday and Tuesday. I will try and get single updates out on those days, but no promises.

As this is pretty much the end of the thread for the day, and probably for the next two days. If you have any questions then feel free to ask them.

>>3251022
are you having fun?

>>3251006
Sounds like balls THROUGH the walls crazy!

Lets do it!

"Lieutenant Zaied, launch a pair of pelicans loaded with salvage teams to the wreak." You ordered it didn't take the next Sun Tzu to realize that the only way you were gonna get a level playing field with the covenant would be through taking any and all opportunities to gather intelligence and steal tech where possible.

And besides, when else would you have a chance to raid the raiders?

Within three minutes, the pelicans were out of their hanger and en-route. But it took another seven for them to reach the broken warship. Up-close however, the damage was plain to see. The hull of the vessel had been carved open with little issue, like a hot knife through butter. The ship's atmosphere had already vented, and there were no life signs remaining on the ship. At least, none that you could detect with either the dawn's sensors or the sensors on the two pelicans.

By the time the two teams had been deployed onto the ship, you had just a little over 20 minutes before the raider impacted the drifting cargo hulk. You had to move, fast.

>Prioritise recovering weapons and sensor systems! (bonus to recovering the ship's weapons and sensor systems)
>Prioritise recovering engines and shielding systems! (bonus to recovering the ship's engines and shielding systems)
>Prioritise recovering data and computer tech! (bonus to recovering the ship's data and computer systems)
>Begin a general search of the ship! (bonus to recovering general salvage)
>Other (write-in)

>>3258900
>Prioritise recovering weapons and sensor systems!

We cored the ship. I don't think there's much left of the shields or engines, and the data might be to hard to take without an A.I.

>>3258900
>Prioritise recovering engines and shielding systems! (bonus to recovering the ship's engines and shielding systems)

>>3258900
>Prioritise recovering weapons and sensor systems! (bonus to recovering the ship's weapons and sensor systems)

>>3258900
>Prioritise recovering data and computer tech! (bonus to recovering the ship's data and computer systems)
If this gives us any insight at all into local troop movements, it'll make it all worth it

>>3258970
Change this to


>Prioritise recovering weapons and sensor systems! (bonus to recovering the ship's weapons and sensor systems)

>>3258900
>>Prioritise recovering data and computer tech! (bonus to recovering the ship's data and computer systems)

“Commander, all salvage units are deployed and are entering the wreak. Commanding officers are requesting guidance on what they should prioritize searching for.” Zaied responded as you flicked your command console to the view from one of the officers of a salvage team.

“Order the teams to look for weapons and sensor systems that are intact enough to salvage. Order them to move through the wreak with caution, we don’t want anyone damaging their vacuum suit.” You ordered as the salvage officer entered the wreck and walked along a carved and cratered hallway. The passage of the MAC shell had also caused considerable amounts of shrapnel to fly off the vessel’s walls, in a manner that was eerily similar to the spalling caused by HESH rounds.

Around seven minutes later, you were given a list of items. Sent directly to your console.

The first two were easy to identify, both in name and in how beneficial it would be to have them. The enemy raider still featured an undamaged light plasma cannon and a pulse laser turret. The former being an effective if close-ranged weapon, one that was often upscaled to form massive batteries on covenant ships for close-in brawls. Meanwhile, the latter was a very useful anti-missile and fighter system, which was usually responsible for cutting down entire volleys of archer missiles and mauling fighter squadrons. If either of them could be used to

The next pair were sensor systems. The first being the ship’s long-range scanners and the second being their pulse-laser guidance system. The long-range scanners would be very useful to ONI, and the missile-tech guys as if it could be somehow jammed, then the movement of entire battlegroups could be hidden from the covenant. Thus allowing ships to relocate and recharge their MACs without suffering from return fire. Meanwhile, the pulse-laser guidance systems were the send half to the covenant pulse-laser system, which as aforementioned was the covenant's best defense against archer missiles and UNSC fighters. If a countermeasure to them could be found, then the firepower of all UNSC ships could be roughly doubled.

The final pair didn’t fall into the prioritized list of items. But were marked as interesting regardless.

The first of the “Uncategorized” items was a covenant energy barrier, a similar system to the energy shielding used on covenant warships. The energy barrier is a system used to hold pressure and atmosphere in a certain area, while still allowing objects to pass through. This particular one looked to be a temporary or deployable version, as it had been set up in the place of a damaged doorway that leads to the engineering area. However, it was welded to the floor. And that would make it harder to salvage.

>CONT

>>3259138

The second “Uncategorized” item was not actually an item. But a series of banging noises that had been heard in the still-pressurized corridor protected by the energy barrier. The men who had reported the noise had described it as “[i]too constant to be lingering damage, but not frantic enough to be a living crewman[/i]”.

[b]NOTE: You have two salvage teams, so you can either pick two options (assigning one option per team), or just pick a single option for an increased chance of success (assigning both teams to a single task)[/b]
>Recover the light plasma cannon.
>Recover the pulse-laser turret
>Recover the long-range scanners
>Recover the pulse-laser guidance system
>Recover the energy barrier
>Investigate the banging noises

>>3259145
>Recover the light plasma cannon.
>Recover the long-range scanners

>>3259145
>Investigate the banging noises
>Recover the long-range scanners
Also OP, I don't think formatting works unless you're posting with the same ip address as actual first post of the thread

>recover pulse laser guidance
>investigate banging
If the banging isnt frantic and couldnt be debris then im thinking maybe an engineer? They dont exactly seem the frantic type but definitely value their lives. Would be a super cool find.

>>3259145
>>3259190
This

>>3259138
It's wreck, my dude. Wreak is a different word.

Why did we recover weapons and sensors? The UNSC needs energy shields to even the playing field. It's a layer of defense that can bring it down to a 2:1 ratio or even a 1:1 ratio.

File: Marine vacuum suit.jpg (106 KB, 1032x774)

106 KB JPG

Looking back at your console, you took stock of where the teams were dispersed around the ship, before making your decision. Your first team was the furthest aft, while the second team had the most people near to the sensor cluster. “Order the first team to the pressurized corridor, they are to open the door leading to the engineering bay and investigate the source of the noise. Meanwhile, the second team is to remove the raider’s long-range scanners with assistance from their pelican.”

You switched through the feeds from the helmets of the various members of the salvage teams until you found the feed from the sergeant of the first team. He was one of the last to arrive, his team already positioned near to the door. The door’s control panel had been pried off the wall, allowing access to the wiring behind it. A number of wires connected the guts of the door control system to a small, remote access box that had been attached to the wall by an electromagnet.

The salvage teams were not armed or equipped for direct combat, and as such, they were equipped with a mix of pistols and submachine guns. Their armor was made up of an off-white undersuit, chest armor, a helmet and a backpack containing a small life support system and the various systems used to support their primary salvaging mission. In spite of this, however, they were still trained well, and most of them stayed out of the pressurized corridor lest it rapidly depressurized.

“Jervis. Pop the hatch.” The sergeant ordered one of his men as he kept his SMG pointed directly at the door. One of the men pressed a button on a data-pad, and the door quickly cycled open. Revealing the cold, dark void of space on the other side.

The air in the corridor was swiftly sucked out of the room, and while many of the marine salvage team did not follow it out thanks to their mag-boots. One man did. His mag-boots filed and he was instantly swept off his feet, he went ass-over-head as he was pulled towards the hull breach. But as he passed the door, the man was grabbed by a trio of tentacles, which arrested his momentum and righted him.

The alien that had grabbed the marine was best described as being similar to a closed flower with some tentacles nailed to it. Its large body was covered with curved, triangular armor panels, some of which featuring in-built thrusters. A number of tubes were attached to the armor, which it used to interact with the environment around it. Some of the tentacles were wrapped around a pair of handholds attached to the wall, it used a pair of tentacles to hold onto the marine engineer’s arm. A single, cyclopean helmet was attached to a long neck that protruded from the armored suit. The alien didn’t seem worried about the gun pointed at it. But none-the-less it took the marine’s M7 SMG off him with little effort, you were about to order the rest of the squad to shoot the alien when it did something unexpected.

>CONT

>>3259447

The alien turned it’s attention from the marine and released him, before beginning to quickly disassemble the SMG right in front of its former owner. The alien left the tiny pieces of the weapon dangling neatly in zero-g, and within seconds it had taken the weapon down to its component parts with the magazine empty and disassembled. It picked five rounds out of the neatly arranged group of similar rounds that it had removed from the weapon’s magazine and set them aside before reassembling the weapon and its magazine. It then reloaded the magazine before inserting it back into the weapon’s receiver and handing it grip-first back to the marine.

And with its work done, the alien let go of the railings and began to push itself into the now depressurized corridor, where it began to get to work repairing the damage done to the door controls by the splicing into its controls.

“What… what the hell is that?” One of the soldiers asked. If the alien had noticed the various guns pointed at it, it didn’t seem to care. The marine who had gone flying quickly made his way back over to the rest of his unit, though unlike them, he did not keep his weapon fully raised at the unknown alien.

NOTE: Regardless of what you choose, roll 1d20-5 for the removal of the plasma cannon by other team.
>Extract the alien alive, this is the first time an alien has attempted to help a human. Not to mention the almost autistic drive to repair the damage.
>Kill the alien and recover the body, you can’t risk this being a ploy to harm your ship and crew.
>Other (write-in)

Rolled 8 - 5 (1d20 - 5)

>>3259452
>>Extract the alien alive, this is the first time an alien has attempted to help a human. Not to mention the almost autistic drive to repair the damage.
A non-hostile alien is a boon. Bring it back and keep it secured and under constant surveillance until back in friendly territory.

Rolled 4 - 5 (1d20 - 5)

>>3259452
>Extract the alien alive, this is the first time an alien has attempted to help a human. Not to mention the almost autistic drive to repair the damage.

Always wondered, are these guys fully sapient/sentient? They come off as organic drones to me.

Rolled 1 - 5 (1d20 - 5)

>>3259452
>Extract the alien alive, this is the first time an alien has attempted to help a human. Not to mention the almost autistic drive to repair the damage.

>>3259463
>>3259467
>>3259474
Well, so much for the damn plasma cannon. Looks like it's useless.

>>3259463
>>3259467
>>3259474
It explodes in their face, wiping out the whole team.


Should have voted for the shields anons.

File: time has come.png (45 KB, 155x169)

45 KB PNG

Rolled 1 (1d2)

>>3259463
>>3259467
>>3259474

>our first crit-fail
OH BOY

>>3259515
Critfails combined with an averaging system makes for a pretty brutal system.

>>3259258


>>3259447
Ha! I was right!

But got damn, those rolls....

Mean roll: -2
Success threshold: 10
Result: Failure (CRIT)
Determinator roll: No detonation.

“Salvage one, this is the commander. Escort the unknown alien out of the ship and onto your pelican. I want it alive and unharmed.” You radioed the sergeant of the salvage squad and made sure to also include the rest of the squad in the call so that they would also hear your orders.

“With respect sir, how are we meant to do that?” The sergeant asked, sounding both confused and conflicted. You didn’t blame him for feeling conflicted though, most people had a kill-on-site for all aliens for the crimes of the covenant.

“It seems to be interested in repairing damaged tech. Try breaking a data-pad and using that to lead it out. If that doesn’t work, then just push it out.” You recommended you didn’t have much to go on aside from what you had just seen. But your hope was that you could use it’s almost-autistic need to repair things would allow your soldiers to move it out of the ship.

Before the sergeant of the first squad could respond, you were hailed by the sergeant of the second squad. “Sir, this is salvage two, we are currently halfway through removing the sensor suite, but all of our nearby sensors are picking up an energy build-up just beneath the sensor cluster. Requesting orders in light of the new development.”

“It’s a trap, get out of there salvage two! Get in the pelican if you have to.” You barked at the salvage squad. Men and women willing to undertake such risky salvage missions were rare indeed, and you didn’t want to lose those few you had under your command.

What happened next was a mad-dash away from the sensor cluster. Almost 30 seconds after the order to run was given, the sensor cluster was erased by a small plasma bomb, effectively vaporizing the sensor cluster and guidance systems. And with nothing left to salvage, and no time left to attempt to recover anything else, the second team climbed into their pelican and left the ship. A couple of minutes later, the first team managed to lead the unknown alien to a hole in the ship, where they essentially shoved it the short distance between the jackal raider and their Pelican. A minute later, their pelican left with all of the unit embarked.

>Recall all of your salvage teams back to the ship. You are done here.
>Order the first salvage team back to the ship, you’ll want the second team to pick through the wreak after the impact.
>Other (write-in)

>>3259669
>>Recall all of your salvage teams back to the ship. You are done here.
we do not want to lose men on our first field op

>>3259669
>Order the first salvage team back to the ship, you’ll want the second team to pick through the wreak after the impact.

GIVE. ME. SHIP. SHIELDS.

>>3259669
>>Order the first salvage team back to the ship, you’ll want the second team to pick through the wreak after the impact.
I doubt there's going to be anything of real value after it impacts, but who knows. We might find something small but still worthwhile.

>>3259669
>Order the first salvage team back to the ship, you’ll want the second team to pick through the wreak after the impact.

Let s see if there is still something here.

-----
We need to take out even the jackals team that we have find before their ship.
Unless they have flee already, we can still get our hands on their gear and especially on their transport ship if they have one.

>>3259669
>Recall all of your salvage teams back to the ship. You are done here.
Let's not push our luck

>>3259669
>Order the first salvage team back to the ship, you’ll want the second team to pick through the wreak after the impact

>>3259669
>Other (write-in)

Highjack one of the alien ship or raiders in their hanger and call it?

How much time do we have left?

>>3259515
What, your surprised with such a shit dice system? Averaging rolls is bad enough, but your modifiers bascally make it stupid to expect anything other than failure, be suprised when we suceed a roll instead if you want to keep using this mess.

>>3259669
>Success threshold: 10
Hahahahahahahahahaha, yeah we were never going to pass that crit or not.

>>3259669
Also wtf we were going for the sensor suite yet you said roll for a plasma cannon?

>>3260206
Was 7 minutes before the engineer was discovered, they wont have enough time to get anything before the raider hits that mining ship hulk, they can pick through it after that if theres anything left (there won't be)

>>3259669
>Order the first salvage team back to the ship, you’ll want the second team to pick through the wreak after the impact

OP don't coddle us. -2 crit failure on a roll with 10 success threshold should have been the death of at least one salvage team.

Also >>3259333

>>3261218
What this anon says. It's Halo, people die. A lot.

>>3259669
>>Order the first salvage team back to the ship, you’ll want the second team to pick through the wreak after the impact.
may as well try

>>3261218
>>3261268
With the system we've got if the OP doesn't, the ship and everyone on it, including us, will be dead the moment we get into combat next time.

>>3261324
Then we'll play as another captain/ship. It's not that hard.

>>3261397
You say that, except every time someones tried that, no one sticks around.

Killing off the MC and cast tends to kill the players interest in a story.

>>3261470
That's so stupid though. Pity.

>>3261472
If the quest is centered around such a concept, as in specifically designed, thematically and mechanically, around it, and the players are there for that, and the QM manages to write it damn well, it can work.

Unfortunately it usually pops up in quests that aren't designed around that, with players not looking for that in a quest, where the QM decides that the dice are sacrosanct and god and infallible, then the quest falls on the QM's sword.

I don't want this quest to go down the path of so many others that have died needlessly, good Halo quests are fucking rare and this one shows some damn good promise.

>>3260507
Fuck everything else! WE GOT A ENGINEER!

“Order salvage team two to retreat to a safe distance, I want them ready to board the raider after it has embedded itself into the destroyed cargo ship. Order the first team one back to the ship, I want them to offload the alien and hand it over to our marine compliment before heading back out.” You ordered as the pair of pelicans moved away from the doomed raider. Both pelicans evacuated to a safe distance of over 10 kilometers, just in case any leftover fuel detonated. The dropship containing the second salvage team began to slow down as it reached the minimum safe distance, while the other one continued it’s burn towards your ship.

Ten minutes later, your aviation officer piped up. “Sir, the first salvage team has landed in port hanger three, they have offloaded the alien, and it is being escorted to the ventral hanger.”

“Have the marines taken custody of the alien?” You asked as you watched the feed from the second salvage team, as they boarded the jackal raider. The vessel having embedded itself into the destroyed transport ship.

“Yes, security chief Chambers has taken custody of the alien and is taking it to storage bay two in the ventral bay. It’s the only one that doesn’t contain anything lethal.” Dyad answered, before handing you a data-pad. It showed a string of messages between her and Chambers.

Yeah, he certainly wasn’t pleased with being saddled with an alien.

“Have the salvage team departed?” You asked your aviation officer once you finished reading the data-pad, you were interested in speaking to one of the members of the salvage team before they left.

“Yes, sir. They are currently en-route back to the raider.” Zaied replied, before shrugging. “Not that they’re gonna find anything interesting.”

“That remains to be seen, Lieutenant.” Dyad commented from behind you, before asking a question. “Sir, do you plan to see the alien? I don’t think I need to remind you of the security risk that would pose.”

>Head down to the ventral hanger, you want to see this thing up close.
>Send your XO to investigate the alien, you will watch via the cameras.
>Question one of the salvagers that found the alien, you want to know what to expect before you make a decision.
>Other (write-in)

>>3262051
>Question one of the salvagers that found the alien, you want to know what to expect before you make a decision.

>>3262051
>>Question one of the salvagers that found the alien, you want to know what to expect before you make a decision.

>>3262051
>Question one of the salvagers that found the alien, you want to know what to expect before you make a decision.

>>3262051
>>Question one of the salvagers that found the alien, you want to know what to expect before you make a decision.

What is this, a fucking Mass Effect? We don't have time for this shit.
>>3262051
>ship damage report
>Alpha wing status report for the umptieth time dammit
>send doctor (suspected spook) to check on the alien, have him report to Dyad