[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / w / wg] [i / ic] [r9k] [cm / hm / y] [3 / adv / an / cgl / ck / co / diy / fa / fit / hc / int / jp / lit / mlp / mu / n / po / pol / sci / soc / sp / tg / toy / trv / tv / vp / x] [rs] [status / ? / @] [Settings] [Home]
Board:  
Settings   Home
4chan
/qst/ - Quests


File: A silent guardian.jpg (40 KB, 680x367)
40 KB
40 KB JPG
You are Beta Core, one of three powerful AIs developed to operate with pilot supervision the most advanced mecha frames ever developed in the Ferrum Empire. Your moment has finally come, leaving the simulators and deploying to the physical world. Even now, your frame is carried to the front lines, to be used however High Command desires……

Last time, you finished your final test in the simulators, defeating Delta core. After that, you powered up under another pilot and aided in the defense of your base in the physical world, managing to evacuate your sister cores in the face of enemy infiltrators and against direct orders. That was a week ago.

Prior threads can be found at:
https://suptg.thisisnotatrueending.com/qstarchive.html?tags=Core%20of%20Steel%20Quest

Reactor- Warming up. 20% Online.

Limbs mobility Unavailable.

Visual sensors Unavailable.

Armor plating records breaches in chest and left leg

Primary Weapon Unavailable.

Secondary systems- Predator- Unavailable
Yi accelerator system- Ready for action.

Well, at least something works. Even if it's not usable without limbs.
>>
File: Sunset.jpg (5 KB, 275x183)
5 KB
5 KB JPG
Low-power mode gives you slow thoughts, no pilot leaves you unable to act, and new mental blocks have shut you out from accessing Predator without a pilot. Someone didn’t like your Extremely useful and entirely justified core linking with Gamma and Delta in the prior engagement.

At least time passes quicker when you can’t process data rapidly. The only sensors you’re permitted to access are the audio and seismic ones, which record the tremors of the mobile repair vehicle, repurposed as your frame’s mobile base and repair facility.

Sophie reactivating your frame to move you off the train and onto this vehicle was your last power-up, a few days ago. That was also when some of your internal permissions were modified, much to your own displeasure.

There’s not even a data uplink, or a physical connection port which would give you SOMETHING to work with, analyze, and use for….something. Preparing for this deployment, perhaps.

You’re sick of being blinded, deafened, and demanded to wait. Being powered up, even partially, does indicate that something’s happening soon, though.

One of the pilot hatches is pulled open, heralding the arrival of Sophie, who slides into the chair, strapping in and putting on the new neurohelmet.

“Up and at em, Beta. Time for deployment. Well, soon. Not quite yet. But get up so that we can be ready!”

She’s excited, even if the feel is duller than usual. The new helm must not be as sensitive. This displeases you.

With someone actually in the seat, now, you can finally begin revving up the reactor for proper movements and diagnostics.
Visual sensors flick on, giving you a view out the back of the vehicle, dust rising up to be caught in the rays of a bright orange orb.

Huh. The sun gives an orange fiery coloration to the clouds, as it hangs in the sky, close to the horizon. That’s one thing the simulator didn’t replicate.
You split a bit of your attention to begin recording, tracking the miniscule movement of the sun’s descent, while the rest of you continues checking over the rest of the frame.
>>
File: Mobile Repair Vehicle.jpg (191 KB, 1920x1080)
191 KB
191 KB JPG
“Pilot. I am reading several armor panels as being improperly installed, a lack of primary weapons system, a weak potential sync connection to pilot, and 9 other, lesser, abnormalities from initial diagnostics. Would you like me to list them in order of severity?”

“Ah…..Really? I thought that you’d be more fixed….Well, the engineering crew’s looking to load up a primary weapons system, so we gotta pick now for it to be ready.”

“It would be more suitable for us to understand what mission we are to be sent on, before choosing armament.”

Sophie lays out what details she’s gleaned from her own prior briefing, trying to bring you up to speed. It would have been so much easier to just have you listen in….

Apparently some elements on the frontline attacked somewhere they really shouldn’t have, and got absolutely demolished by a fierce counterattack.
As the scattered reports from retreating troops and armored units trickled in, the commander of said force, the 56th Mechanized Regiment, lost contact, and their last marked location was directly in the center of the counterattack. The last transmission, some hours ago, indicated that their walker had been disabled, and they were stuck.
Their capture would be unacceptable, and thus your role is to backtrack along the path of retreating troops, and under the cover of night and your own jamming, recover the general from the battlefield.

Terrain is a series of long, rolling hills, temperature is slightly above freezing, expected to drop as the sun leaves the horizon.

Enemy forces are expected to be their own, lighter mech variants, infantry, and battlefield salvage crews. Overall light resistance for something of your caliber.
>>
Vote!
Beta has questions, Sophie (might) have answers. The more you ask about, the less detailed the replies will probably be.
You’ll always be getting some basic info on things like enemy composition or support, but this is also the chance for her to request more detailed information from other sources on Beta’s behalf.

>Detailed enemy force composition. What can be expected?

>Information about the General we’re supposed to be recovering.

>Terrain. You want precise mapping data before going into the night.

>You've been locked out of Predator’s non-jamming functions. Request that she remove the lockout, so you can utilize it to its greatest extent again.

>Assistance. Can Sophie get any direct support? Air strikes? Intel? Other friendly forces in the operating area?

>There seems to be some sort of white orb appearing in the sky. What is it?

>Your sisters. Where did they go after the train ride? Can you get communications to/from them?

>Write-in: Other

A/N:It’s back! Apologies for the lack of promised interludes at the end of last thread, but sometimes the muse just isn’t working. Bleh. Thanks to the guys in the QTG who reminded me to get off my arse and just put something out there. Vehicle picture is from the game Phantom Brigade, which I haven’t played but really like the look of.
>>
>>5627464
>Detailed enemy force composition. What can be expected?

>Terrain. You want precise mapping data before going into the night.

Allies are too slow and human to be of use. Operational information is what we need first.

>You've been locked out of Predator’s non-jamming functions. Request that she remove the lockout, so you can utilize it to its greatest extent again.
Shouldn't take up too much time to make a request surely?

>There seems to be some sort of white orb appearing in the sky. What is it?
Kek, I can't resist.
>>
>>5627464
+1 >>5627486
>>
>>5627464
>Detailed enemy force composition. What can be expected?
>Information about the General we’re supposed to be recovering.
>Terrain. You want precise mapping data before going into the night.
>>
>>5627464
>Terrain. You want precise mapping data before going into the night.
We’ll want to minimize sightlines where possible since Bia seems like the best call against light armor.

>You've been locked out of Predator’s non-jamming functions. Request that she remove the lockout, so you can utilize it to its greatest extent again.
Ripping apart enemy communications for intel is good, and how do they expect us to do that if we can’t snoop? If they have worries, ask if Gamma’s pilot can chime in support. Beta might not know she’s the lead now, but he knows she’s a scientist and can help cut through any fearmongering in theory.

Wonder what happened to Delta’s pilot? Haven’t heard about him in a while.

>There seems to be some sort of white orb appearing in the sky. What is it?
Did they never model the moon in night missions? I wonder if Beta will be surprised when he sees stars in the night sky for the first time. With his enhanced sensors, he’s bound to pick out far more than the average human.

I’m willing to skip the detailed enemy comp and get a basic one to focus on the others, and while I’m curious about our sisters I’m sure Sophie can’t tell us much.
>>
>>5627517
You wanna ask about Delta's pilot? The write-in option is there.

Most of the mission-relevant topics are asking Sophie questions, then her running it back up the chain to check with people who actually have the information you want, or authority to change permissions.

Other stuff she probably knows offhand. Yes, like the moon. Some stuff in the sims wasn't deemed critical, like the night sky.
>>
>>5627464
yeah, voting for this
>>5627486

>>5627517
>With his enhanced sensors, he’s bound to pick out far more than the average human.
not only that, but if we're in a clear night, we'll(sophie and beta) will be able to see a TON more than what we're used to in the city, kinda like in the pic. it will probably be quite a sight for them and it will allow beta to use the stars to navigate the terrain without the need to broadcast his location
>>
>>5627526
Sure, why not?

>>5627464
>>5627517
Adding these two to ask Sophie. If she doesn’t know offhand, I won’t waste her time asking around the base before the mission.
>Your sisters. Where did they go after the train ride? Can you get communications to/from them?
>What of Delta’s pilot? You know Sophie and Gamma’s pilot escaped, but never noticed him.
It’d be a shame if he died.
>>
>>5627464
>>5627486
Supporting.

>>5627526
For something called "simulator" it didn't simulate the real world all that well.
>>
>>5627464
supporting
>>5627486

>>5627552
most of the money went into 3d modelling the empires glorious vehicles and the physics engine
>>
>>5627552
>Didn’t simulate cores linking with each other
>Didn’t simulate an attack on the core facility itself
>Didn’t simulate cores being forced to choose between following orders or saving each other
>Didn’t simulate the moon
>Didn’t simulate snow sticking to our frame
>Didn’t simulate a pilot defying direct orders from superiors
They cut a lot of corners and missed a lot of questions for sure.
>>
>>5627464
>>Terrain. You want precise mapping data before going into the night.
>You've been locked out of Predator’s non-jamming functions. Request that she remove the lockout, so you can utilize it to its greatest extent again.
>>
>>5627567
Knowing it's a simulation can render alot defunct as tests
>>
>>5627464
>You've been locked out of Predator’s non-jamming functions. Request that she remove the lockout, so you can utilize it to its greatest extent again.

>Your sisters. Where did they go after the train ride? Can you get communications to/from them?

>Write-in :
Did we fried Thea? Do the command knows that the frying comes from us preventing her to run to the surface despite orders?
>>
>>5627464
Shouldn't a regimental commander be a colonel?
>You've been locked out of Predator’s non-jamming functions. Request that she remove the lockout, so you can utilize it to its greatest extent again.
>Detailed enemy force composition. What can be expected?
>Terrain. You want precise mapping data before going into the night.
>Your sisters. Where did they go after the train ride? Can you get communications to/from them?
>>
>>5627464
It would be much better (and riskier) if Sophie could get her hands on the mission data and plug it into Beta. Nevertheless, my choice of questions are:

>Terrain. You want precise mapping data before going into the night.
Map data is mandatory, period.

>Assistance. Can Sophie get any direct support? Air strikes? Intel? Other friendly forces in the operating area?
We're able to deal with any ground vehicles, and we should always assume the enemy has their own artillery and air strike capabilities on call. We should instead ask what our allies can or can't do so that we may pick our loadout to fill the gaps. Do we lack anti-air? Use Whirlwind. Got nothing against tanks? Get a Tyrant etc.

>Your sisters. Where did they go after the train ride? Can you get communications to/from them?
If the sister Cores are gone and the facility members are trying to stop leaking data, I doubt they'll tell us or Sophie, though asking if they're Ok wouldn't hurt.

>There seems to be some sort of white orb appearing in the sky. What is it?
>>
Tallying votes for things that require some time:
-Predator restrictions
-Terrain details and mapping data
-Enemy force details

And will fill the remaining time with quicker questions.
-The Orb in the sky
-Sister cores?

Writing.
>>
Well, critical issues first.

“My ability to access and utilize Project Predator has been hampered. I request for you to rectify this.”

“When you say, hampered, Beta, what do you mean?”

“It is effectively only able to jam in its present state. My primary uses of it, communication interception, command coordination, and E-War, have all been disabled.”

“Wait, what? You’re telling me that we’re going to be unable to communicate?”

“I can still use inbuilt transmitters and communications gear. However, this is unable to push through my own jamming. So yes. If we follow the mission parameters as laid out, we’ll be deaf.”

“Fuck. It’s a programming block, not a hardware one, right? Any idea who put it in?”

“It was not present when we moved onto the MRV 75 hours ago.”

“Well, I can probably override it with my own authority when we’re in sync.”

Probably. Her use of the word fills you with such confidence. That settles one issue by sidestepping it.
“The briefing you have given me is inadequate. I would be far better served with more accurate terrain scans of the operational area, and details on the enemy presence.”

“Hey, I’ve given you what I got myself! Besides, you’ll be able to see that when I get in sync.”

“If that briefing is all you received, it is woefully vague and imprecise. The one who gave you it appears to be trying to send you and me to our destruction. Find a higher authority, and get us mapping data and contact reports from the retreating troops.”

“Come on. You really think someone has it out for you?”

Memories of a week ago, and a satisfied voice over the radio loop through your thoughts.
“I do not suspect. I Know.”

“Well, if there’s one person who doesn’t want you destroyed, it’s me. If you go down, I do also. So fine, paranoid Core. I’ll get more data.”
She starts tapping away at her console, signing into a local network under some permissions that you save a copy of.
>>
File: Moon.jpg (43 KB, 900x602)
43 KB
43 KB JPG
There you are, the actual network! Yes! Something that you can connect to! And it’s another carefully limited connection, which she’s using to text someone.

HotSeat- Hey! I need mapping data for my mission. And any allied or enemy positions. In fact, just send me the mission briefing again, in digital form. But mostly the map.

While she waits for a response, you broach some other topics that are on your mind.
“Gamma and Delta cores. Do you know where they are?”

“Last I saw them, they were unloaded at Camp Nagita. They’re not here on the MRV.”

“Can I contact them?”

“You think you’re going to be allowed to start firing off transmissions while we’re moving? I got read the riot act by Colonel Kinston when I first tried to pull out my tablet and call someone after getting on this. The way he told it, dialing the first 3 digits meant cruise missiles were already inbound. Actually, that probably explains why the Predator got limited. ”

“The white orb in the sky. It was not present in the simulator.”

“What orb?”

You send several images of the object in question to her display, taken directly from your visual sensors. This prompts laughter.

“That’s the moon. Big, orbiting rock in the sky. Reflects the light of the sun.”

You see. Well, sort of. Not really.

—------------------

Voting!
You’ll get more information before heading out, and picking primary weapon.

However, Sophie and Beta do need a callsign.
This is subject to veto by QM if the winner is something outrageous.
Yes this isn't much but I need sleep

Default choice is Metal Zero-One

>Write-in.
>>
>>5628649
Empire Impaler #1
Yeah, we're definitely with the good guys
>>
>>5628649
Moneyshot Zero-One
>>
>>5628649
We need something sufficiently propagandized. I'd like Endsieg Zero-One because we're definitely the bad guys, but we're also not Germans. Thus, I vote

>Victory Zero-One
>>
>>5628649

Hel-2-0

Hel, Norse goddess of the underworld, whose body was said to be half flesh and half blue. As a unit we're half flesh and half metal.

And we're going to take a lot of people to the underworld.

The 2-0 is our score line against our siblings, since we've been playing the quest anyway.
>>
Call sign Corbius, and whenever we go into battle we can screech over comms "IT'S CORBIN TIME!"

This is a joke vote, please do not vote for it
>>
>>5628649
voting for corbius
>>
>>5628649
>Corbius
Time to Corb
>>
>>5628649
I think we should choose something along the lines of us being a protector. To the brass, were the wünderwaffe guardian of the empire, but more personally were the protective big brother to our sisters.

So maybe:
Shield 01
Aegis 01
Guardian 01
Defender 01
Etc.
>>
>>5628649
Metal Zero-Four, and let them search for the other three.
>>
>>5628649
I can't not vote for
>Corbius.

But if people disqualify that, then I'll support>>5628719 for the subtle psycological warfare
>>
Lmao what have I done
>>
>>5628649
Since we're from the Ferrus empire and Ferrus is latin for iron, a callname based on a metal element would be apt.

>Cobalt Zero-One

Alternatively, the etymology of the word cobalt:

>Kobolt Zero-One
>>
>>5628823
I like Cobalt as a name but I also like other anons idea of the numbering so something like

>Cobalt Zero-Four

Would be cool
>>
>>5628820
You forgot the most important rule: people will vote for the funniest sounding name of you give them the chance.
>>5628649
>Cobalt Zero-Four
>>
>>5628649
>>5628824
Might as well make the enemy confused with a strange silly name. Supporting.
>Cobalt Zero-One
>>
>>5628649
>Cobalt Zero-Four
I was going to suggest Nine-Core but Cobalt grew on me
>>
>>5628649
As an added question to Sophie, Beta should ask
>Does the moon do anything special?

Since the moon didn’t exist, I’m assuming high tide and low tide weren’t concepts covered by the sim. Kinda matters on a tactical/strategic level since boats and armor may be cut off from certain paths depending on the time of day.

I’ll go
>Wunderwaffe Zero-Four
for our callsign

If we ever truly learn humor with the squishies, we can joke the Wunderwaffe is our pilot.

I’d prefer if Zero-Four were even higher to make it seem like we’re part of a long line that may or may not be deployed. Something like Eight-Six.
>>
I'm assuming the numbers are there in case we're someday leading our own squadron, e.g. Query is Cobalt Zero-Two. If not, I'd say we drop the numbers for brevity (and to save a few keypresses for the QM).
>>
>>5628815
Changing vote to >>5628864

This gets the number desire satisfied.
>>
Assigning callsign……
Cobalt 04

I like it. References that striking shade of blue, or the element. Or the bomb. (Look it up on wikipedia, nasty nuclear weapon variant)

Numbering might be dropped or added to later. Either way, that's what you're going to be called for on the radio.

Thank god Corbius didn't win I was not looking forwards to 'Corbin time'

>And writing.
>>
File: Sample Terrain.jpg (11 KB, 259x194)
11 KB
11 KB JPG
“An orbiting rock.”
Your skepticism is clear.

“I’m telling you, it’s another mini-planet that goes around and around this planet we’re on, because it’s caught in the gravitational field of the planet. You see, it’s going to shrink to a crescent gradually over the next few days, and then vanish because of the shadow that Earth casts upon it.”

“A shadow is going to eliminate pieces of it, in a crescent?”

“Well, it’s going to look like it’s losing pieces. But it’s still there, just doesn’t have light for it to reflect back. Like when you’re hiding in the shadows of a building. Anyways, it’s Really far away. I don’t remember the exact number, but it’s far enough away that you don’t need to worry about it.”

“I would request an accurate number to be able to calculate a targeting solution for it.”

“Beta….None of the frame’s weapons can get past the atmosphere. Just….forget it.”

“Forgetting does not happen. All is recorded for later review.”

Your impromptu lesson on the Moon ends with the arrival of a data packet with some topographic data, marked locations, and a few other odds and ends like some audio transmissions, typed up reports and a roster for the 56th Mechanized Regiment and accompanying forces involved with Operation Bad Hunch, the initial attack, along with preliminary recon reports for said operation.

Observing the map data, several things stand out. The attack was supposed to divide into three groups and follow west, south, and east roads, crushing enemy resistance along the way and driving until they hit the banks of the Ebon river, converging at an intact bridge to strike the defenders from three angles. Capturing the bridge, destroying the enemy defenders, and stopping any further movement of enemy armored or supply units across.

Reinforcements would sweep the area afterwards with salvage crews, recovering fallen mechs and rooting out any other stragglers.
>>
File: Ebon River.png (1.13 MB, 1284x640)
1.13 MB
1.13 MB PNG
The last known position of the General was a couple of miles to the west of the bridge, at the banks of the river. They seemingly got very close. He was supposed to have started with the central force, heading directly south into the defenses, according to the plan.

There are a few other confirmed marked locations of fallen allied walkers and disabled tanks, mostly along the eastern route. The first few reports of retreating troops marked the positions. Those same reports also informed you that each spearhead was operating on a strict timetable and under heavy jamming close to the bridge, making coordination difficult.

The east group was apparently hit by at least 5 to 10 fast moving medium mechs, which ‘came out of nowhere’ and quickly routed the tanks and heavy mechs that the spearhead was composed of.

You are regretfully operating off of faulty human reports, which are agonizingly imprecise. 5 to 10? That’s literally double the count! And ‘out of nowhere’? That’s physically impossible.

Sophie’s looking at the same maps you are, and taking the benefits of having you collate the data together. Recon reports, mapping, starting division of attacking forces, and simulated outcomes.
“Their plan was flawed from the start,” she declares, “Dividing into three merely allowed each smaller portion to be overwhelmed in turn. Perhaps the general imagined that they were facing a much smaller enemy force, or that the defenders would be unable to redeploy quick enough to face each thrust?”

“I could.” You reply.

“Yes, we could also probably smash your way through any single attack force. That’s not the point, Beta. The point is that the eastern force was struck first, and then retreated. The enemy probably then redeployed to the center, and then to the west. Doesn’t really explain why the General ended up with the western force, I guess, but it’s a good enough working theory.”
>>
While you discuss the data with your pilot, mechanics toil away, installing the primary weapons system and loading ammunition.

Voting!

The Yi accelerator system seems to be functioning well, at least with your testing. Project Predator is also installed and functioning in jamming mode, to your diagnostics. Sophie claims she can override this in the field to give you full functionality, after you disembark.

What primary weapons system do you request to be fitted for this mission? Pick One

>Bia Chaingun- rotating high velocity minigun scaled up to be used by your frame. Highly effective against lighter targets and unmatched in rate of fire. Brrrrrrt +1 to attack at medium range, +1 to attack at close range. 1 auto-success per light unit targeted, but less damage against heavier units. Fast projectiles. 1 Damage per volley, but can hit multiple units.

>Tyrant Cannon- armor-piercing high velocity cannon taken off of Tyrant tank, with auto loader. Low rate of fire, but different ammo types available. +1 to attack at long range, +2 to attack at medium range. Slow projectile. 3 Damage per shot.

>Whirlwind Missiles- ammo-limited, launches various types of missiles to eliminate targets. Missiles have limited guidance capability, but can carry various different warheads- generally effective against all targets, warhead depending. +1 at long range, +1 to medium range, Access to Explosive, Smoke, Poison Gas, or Haywire warheads. 2 Damage per volley.

>Project Demon- Reinforced melee weapon capable of tearing through armor. Armor-piercing, highly effective against all targets. 1 auto-success in close combat, minimum of 3 damage when hitting, regardless of success amount.

Introducing a new mechanic, Damage values. For ranged attacks, the damage value will determine how much structure the enemy unit takes. Close combat will retain the damage results being equal to # of winning successes, subtracting the # of successes the losers got.

To tell you how much certain damage values give you, stuff like a tank or light walker will usually have only 2-3 structure, while heavier walkers have around 4-5 structure. However, trying to hunt down many targets with a Tyrant cannon will be somewhat tiresome, as you’re limited by the reload speed.

Beating the opponent by enough dice will still result in instant-kills. Close combat with a tank will still result in a crushed tank, or shooting an unprepared light walker from ambush will leave it a smoking wreck, unless something else is in play. Beta isn’t that incompetent.
>>
>>5629701
>Bia Chaingun
Chaingun go brrrr
>>
>>5629701
>Bia Chaingun- rotating high velocity minigun scaled up to be used by your frame. Highly effective against lighter targets and unmatched in rate of fire. Brrrrrrt +1 to attack at medium range, +1 to attack at close range. 1 auto-success per light unit targeted, but less damage against heavier units. Fast projectiles. 1 Damage per volley, but can hit multiple units.
Not as good against medium armor, but if there are 5 (or more) of them in a group then we’re likely to hit multiple targets at a time to offset the low damage. We’ll sweep anything lighter too.

General question Beta should be asking is how the medium walkers could hide. Unless they’re sporting next-gen equipment or the recon spotters were that terrible, I’d assume they came over the bridge and hid behind terrain until our forces committed. Air recon could spot for them and dictate when they’d move.

Could the walkers have hid in the banks of the river to ambush the Eastern group? Can’t imagine that’s possible, but it’d be a surprise for sure.
>>
>>5629701
>>Bia Chaingun- rotating high velocity minigun scaled up to be used by your frame. Highly effective against lighter targets and unmatched in rate of fire. Brrrrrrt +1 to attack at medium range, +1 to attack at close range. 1 auto-success per light unit targeted, but less damage against heavier units. Fast projectiles. 1 Damage per volley, but can hit multiple units.
>>
>>5629701
>Project Demon- Reinforced melee weapon capable of tearing through armor. Armor-piercing, highly effective against all targets. 1 auto-success in close combat, minimum of 3 damage when hitting, regardless of success amount.

Make them afraid!
>>
>>5629701
>>Bia Chaingun- rotating high velocity minigun scaled up to be used by your frame. Highly effective against lighter targets and unmatched in rate of fire. Brrrrrrt +1 to attack at medium range, +1 to attack at close range. 1 auto-success per light unit targeted, but less damage against heavier units. Fast projectiles. 1 Damage per volley, but can hit multiple units.


This makes the most sense with fast moving targets and the bonuses it gets to close and med range
>>
>>5629701
>Tyrant Cannon- armor-piercing high velocity cannon taken off of Tyrant tank, with auto loader. Low rate of fire, but different ammo types available. +1 to attack at long range, +2 to attack at medium range. Slow projectile. 3 Damage per shot.
1 damage on Bia is just too pathetic. Even with the AoE. If we encounter anything heavier than 2HP, we're toast.
>>
>>5629701
>Whirlwind Missiles- ammo-limited, launches various types of missiles to eliminate targets. Missiles have limited guidance capability, but can carry various different warheads- generally effective against all targets, warhead depending. +1 at long range, +1 to medium range, Access to Explosive, Smoke, Poison Gas, or Haywire warheads. 2 Damage per volley.

A good middle ground between Bia and Tyrant. Missile guidance might let us strike multiple targets with each volley and with Project Predator we don't have to worry about our missiles being jammed. Also, the smoke warheads will aid the General's retreat.

Speaking of smoke, wouldn't the Tyrant cannon also have access to smoke rounds?
>>
>>5629701
>Whirlwind Missiles- ammo-limited, launches various types of missiles to eliminate targets. Missiles have limited guidance capability, but can carry various different warheads- generally effective against all targets, warhead depending. +1 at long range, +1 to medium range, Access to Explosive, Smoke, Poison Gas, or Haywire warheads. 2 Damage per volley.
>>
>>>5629701
>>Whirlwind Missiles- ammo-limited, launches various types of missiles to eliminate targets. Missiles have limited guidance capability, but can carry various different warheads- generally effective against all targets, warhead depending. +1 at long range, +1 to medium range, Access to Explosive, Smoke, Poison Gas, or Haywire warheads. 2 Damage per volley.
>>
>>5629701
>Whirlwind Missiles- ammo-limited, launches various types of missiles to eliminate targets. Missiles have limited guidance capability, but can carry various different warheads- generally effective against all targets, warhead depending. +1 at long range, +1 to medium range, Access to Explosive, Smoke, Poison Gas, or Haywire warheads. 2 Damage per volley.
This one sounds like fun.
>>
>>5629701
>tyrant cannon
>>
>>5629701
>Tyrant Cannon- armor-piercing high velocity cannon taken off of Tyrant tank, with auto loader. Low rate of fire, but different ammo types available. +1 to attack at long range, +2 to attack at medium range. Slow projectile. 3 Damage per shot.
We need at the least a Tyrant cannon so we can damage the enemy if they have armor that the Chaingun can not pierce. The Whirldwind missiles is a good second choice since we could potentially scramble enemy countermeasures with the Predator, but I fear we might run out of missiles before we've taken out the enemy force and have to resort to melee to finish them off. Right now melee is not great at all for us because we'll have to stop and vent heat so Sophie doesn't die from it, so we have to keep distance and pick targets off and disengage to vent before going back in.

If we end up fighting near the River I suppose we can take a dip to cool off, but if not we need to find some cover we can use to hide behind while we cool down. Hills and forest would be good, though the latter wouldn't protect our heat signature if they have sensors.
>>
>>5629968
I love the Tyrant Cannon, it is my number 1 pick 99% of the time. My issue here is that it is slow, and we've been informed of fast moving targets. We can probably hit them if we have distance, but it's a gamble
>>
>>5629701
>Tyrant Cannon
Multiple light walkers. Let's make sure we can one shot them as we owe to a range where we can tear them apart with our bare hands.
>>
>>5629982
Fair, though the report specifically mentions Medium mechs so I highly doubt they're the fastest things around. Most likely they're only fast compared to other mechs in their own weight-class, so we shouldn't have much difficulty with accuracy, especially since we can E-Warfare the enemy sensors before we engage with Predator. If you can't see the shot coming you can't dodge.
>>
>>5629701
>>Tyrant Cannon- armor-piercing high velocity cannon taken off of Tyrant tank, with auto loader. Low rate of fire, but different ammo types available. +1 to attack at long range, +2 to attack at medium range. Slow projectile. 3 Damage per shot.
>>
>>5630076
Hopefully we can EWAR. Depends on how extensively they locked both of us out of Predator’s non-jamming systems. Sophie thinks she can lift it, but we don’t know for sure.
>>
>>5629701
>>Bia Chaingun- rotating high velocity minigun scaled up to be used by your frame. Highly effective against lighter targets and unmatched in rate of fire. Brrrrrrt +1 to attack at medium range, +1 to attack at close range. 1 auto-success per light unit targeted, but less damage against heavier units. Fast projectiles. 1 Damage per volley, but can hit multiple units.
>>
File: Winter War.jpg (264 KB, 1280x720)
264 KB
264 KB JPG
Attempting to Count votes.....

Bia Chaingun- 5 votes
Whirlwind Missles- 4 votes
Tyrant Cannon- 5 votes
Project Demon- 1 vote

I guess every option is quite appealing. Except pure close combat. (Faint screaming of 'it's totally viable' coming from Delta)

No update tonight, on account of RL issues.

But, that does give more time for someone to hopefully break the tie.
Have some cute art I found as a poor substitute for my lack of update.

>>5630105
You’ll get most of your defensive E-war stuff back. Defensive being secure connections, interfering with enemy sensors/lock-ons, and your jamming. However, a bunch of offensive options such as direct intrusion, inserting viruses, and listening in on enemy communications will be locked out.

>>5630076
Medium is a bit of a misnomer for the Tamar Alliance's mechs, because their designs are generally lighter, faster, but less armed than the Ferrum Empire's. So something that's 'heavy' to the Alliance, might merely be classed as 'medium' by the Empire.

Half the fun of writing this quest is finding different concept arts and dreaming of them fighting wildly different design philosophies.
>>
>>5630631
Enjoy your Easter QM
>>
>>5630631
Some questions regarding the Whirlwind:

>How much ammo does it have?
>What does the Haywire warhead do?
>Can the missiles be guided with Predator?

Also, does the Tyrant have access to explosive and smoke shells?
>>
>>5630076
>>5630631
Based on this, it looks like screwing with the enemy is off the table.

This is going to be a very weird quest where we sometimes get punished for being too clever. Command doesn’t like it when the grunts have imagination.
>>
>>5630675
Whoops, missed the sensor screwing being considered “defensive”. I figured being unable to listen to enemy comms or preventing direct intrusion would prevent screwing with sensors beyond regular jamming.
>>
>>5630631
I'll change my vote to the Bia Chaingun to break the tie then.
>>
>>5630631
Oh fine, I'll give up the epic awesome of melee for the Bia. We can be practical and effective, I guess.
>>
>>5630631
I'm happy you crawled out of flaking QM. I liked the quest even though i do not check in daily on the board.

>Bia Chaingun- rotating high velocity minigun scaled up to be used by your frame. Highly effective against lighter targets and unmatched in rate of fire. Brrrrrrt +1 to attack at medium range, +1 to attack at close range. 1 auto-success per light unit targeted, but less damage against heavier units. Fast projectiles. 1 Damage per volley, but can hit multiple units.

I would like to go for the tyrant but the prospect of facing down a double digit rapid response group gives me pause.
>>
Whirlwind will get its due eventually, just not this time.
>>
>>5630656
Belated notes-
All of your stuff requires ammo, apart from melee, but I wasn't exactly planning on counting it.
For Whirlwind? Call it around 40ish volleys. Bia? Call it around half a minute of continuous firing. Tyrant cannon? 50 Rounds, mix of armor-penetrating, explosive, and flechette.

Haywire skips damage in return for generating a strong ECM effect on target. Translates as penalties to attached unit's rolls.

Missiles have limited guidance capabilities while in-flight, though you program routes in just ahead of launching. So yes, you could technically guide them with Predator onto locations of signals.

>>5630675
Your biggest advocate, and the person who would trust you the most, is currently missing. And there's already people who wish for you to fail. No end of other places the funding and AIs could be used for.

Alright, seems like the Bia is chosen.

Working on writing.
>>
File: BRRRT.png (2.51 MB, 2704x1162)
2.51 MB
2.51 MB PNG
The ammo feed of the Bia takes the high-caliber ammunition, clicking and whirring as it takes belt after belt. You give the barrel a spin. The bullets will be leaving far faster than they load.

“Feed looks good. Shouldn’t jam.”
One of the workers around your feet comments. Truly, stunning intellect. Maybe next time they’ll finish the damn armor patches so you don’t have the numb zones.

Another message comes over your limited connection.
Fortress to HotSeat. You have been assigned as Cobalt 04. Note that your presence is top-secret, and as such most friendlies have not been notified of your deployment. Good luck out there. Come back in one piece, kid.

HotSeat to Fortress- Copy that. We’ll be back.

The MRV rolls to a stop, gantries detaching so Sophie can nudge your frame off the rear of the vehicle with manual controls.

“On our own here, Beta. Let’s do this. Release lockdowns, Pilot Sophie authorization ERROR.”

Wait, ERROR? What? Why can’t you process that?

The Project Predator array boots to life, allowing you to shower the area in jamming. Well, that works. You drop that, and attempt to push the other options, using the retreating MRV as a test connection.

Cobalt to Fortress.

They’re receiving, you can see that. But you can’t seem to upload large data blocks at any sort of speeds, no matter how carefully you tweak and coax Predator to function. It Just WON’T WORK!

Someone sends back a brief note of 'CEASE BROADCAST', and you comply.

Someone wants you hobbled and helpless. Without any sort of upload speed, you’re not going to be able to aggressively E-War and bully lesser AIs. Or break into friendly squad communications

“Pilot. Offensive E-War measures are going to be offline. Your override is only partially functional.”

“Well, shit. A little late now to back off, though. We’ll need to push through, and fix it afterwards, then. Ever back off from a challenge, Beta?”

“Affirmative, pilot. When the challenge is insurmountable. This, however, is not. I merely wish to take a minimal amount of risks.”

Sophie clicks into low-sync, letting your mind mesh with hers. (Sync check auto-passed from preparation)

After installing a primary weapon and finishing warming up, Beta is finally deployed.
Time for a plan.
>>
Vote!

>Direct path. Straight to the General’s last known position, at speed.
Almost directly south, mostly following the route of the central attack group. This is the fastest route, so going in hard and fast would preempt the arrival of additional enemy forces.

>The River road. Wind to the east, reaching the river and submerging yourself to walk downstream and slowly move to the objective.
You didn’t practice water assaults, but your frame should be rated for it. Slowest route, also takes you under the bridge, but highly unlikely you will encounter anyone, allied or enemy.

>Allied assistance. Take the western path, picking up any Empire units still fighting and leading them to the objective.
You never got reports from that group, so they’re probably still fighting under communications blackout. And crushing a distracted enemy is always easier. If they’re wiped out, then it will take you to the general’s position anyways.

>Active hunting. Recon each route, find the fast-response force, and eliminate it first.
They’re clearly the lynchpin of whatever defense shattered the attack. Remove them, and your job will be far easier. Pinning them down will probably take some time, and does risk your objective being taken off the field, but better to eliminate them than risk being jumped during extraction.

>Write-in.
>>
Minor warning, the Bia Chaingun does not operate underwater, and there's some additional risks when operating with the patchwork armor plates. Just because you're Supposed to be rated for water doesn't mean your potentially unfinished form will not suffer any consequences for it.

I should probably re-post the dice rules and Beta's frame sheet for newer people, also.
>>
>>5632066
>Allied assistance. Take the western path, picking up any Empire units still fighting and leading them to the objective.

Meat shields can be useful.
>>
File: Beta Inspiration.jpg (162 KB, 924x1134)
162 KB
162 KB JPG
Character Sheet
Stats of Beta
(Stats are without any equipment)
Will- 5
Attack- 3
Defense- 3
Skill- 3
Structure (health)- 10
Beta cannot take more than 3 structure damage from a single attack.

Equipment

Bia chaingun- +1 to attack at medium range, +1 to attack at close range. 1 auto-success per light unit targeted, but less damage against heavier units. Fast projectiles. 1 Damage per volley, but can hit multiple units.

Project Yi- +1 to defense dice rolled, overcharging can give you +2 to defense dice rolled

Project Predator- 2 Auto-successes when engaging in E-War attack and defense. Enables Jamming. Unable to Engage in E-War attack currently

Sync multipliers for Beta are 1x, 1.5x, and 2x for low, mid, and high-sync. (Rounds down for .5, otherwise to closest)

Cadet Sophie
Will- 3

Some rules and dice mechanics
Each number associated with a stat represents the amount of dice used to roll.

5 stats of combat units
Will- Used for E-war and various interactions with the pilot and system controls. Is not affected by Sync rate.
Attack- Used for ranged and close combat
Defense- Used for evading incoming fire. Added to Attack dice for close combat
Skill- Used for non-direct combat skills. I.E. Stealth and detection
Structure- This is roughly how many hits a unit can take. Also not affected by Sync rate

(I'll probably at some point just shove this and an explanation of how dice work into a pastebin or other source so new people don't need to trawl the archives for how the hell things work)
>>
>>5632066
>Allied assistance. Take the western path, picking up any Empire units still fighting and leading them to the objective.
>>
>>5632066
>Allied assistance. Take the western path, picking up any Empire units still fighting and leading them to the objective.
Our long-term survival is best earned by saving lives so the grunts don’t listen real well when Command orders them to screw us over.
>>
>>5632066
>>Allied assistance. Take the western path, picking up any Empire units still fighting and leading them to the objective.
They probably also have up to date information on the enemy.
Have we been told who we're fighting yet?
>>
>>5632111
we're fighting the enemy, duh
>>
>>5632066
>Allied assistance. Take the western path, picking up any Empire units still fighting and leading them to the objective.
If we save them morale will be high and maybe the engineers will work on fixing us up with a bit more fervor.

>>5632111
5-10 medium feral mechs that ambushed our VIP
>>
>>5632080
>>Allied assistance. Take the western path, picking up any Empire units still fighting and leading them to the objective.
>>
>>5632080
>Direct path. Straight to the General’s last known position, at speed.
Go in while the enemy is distracted. Taking the most direct path would also clear the fastest exit for the General. We can exfiltrate the rest of the troops when the General is a safe distance away.
>>
>>5632066
>Go in while the enemy is distracted. Taking the most direct path would also clear the fastest exit for the General. We can exfiltrate the rest of the troops when the General is a safe distance away.

You people already are blaming Blake for everything under the sun despite him doing nothing wrong. I do not want to see you guys ree harder and screw over our creators when friendlies open fire on us with them not knowing we exist.
>>
>>5632066
>Direct path. Straight to the General’s last known position, at speed.
Any other choice is bad. This is our first deployment and if we begin to fuck around immediately instead of getting the General and extracting him it'll reflect poorly on us, especially if we fuck around long enough for him to get captured or killed.
>>
>>5632066
>Direct
>>
>>5632248
We'll clear any misconceptions fairly quickly once they see the Bia's hundreds of tracer rounds flying towards the enemy.

Though we wouldn't even have this problem if we could contact our allies. Could Beta counter the enemy's jamming with the Predator's own, then maintain comms between our allies like we did back at the R&D facility?
>>
>>5632066
>Direct path. Straight to the General’s last known position, at speed.
>>
>>5632270
Jamming is basically screaming so loud that your enemy can't hear shit. It can't be countered with more jamming.
>>
>>5632280
Yeah, my mistake. What I meant to ask if we could increase the radio's transmission and reception powers to essentially burn through the jamming.

The system restrictions shouldn't take effect, since we're only amplifying our signal, though the data cap might restrict the comms quality.
>>
>>5632066
>Direct path. Straight to the General’s last known position, at speed.
>>
>>5632066
>Allied assistance. Take the western path, picking up any Empire units still fighting and leading them to the objective.
>>
I thought of a way to avoid the shutdown code if we get into a situation that the meatbags might think to use it. We just turn off all microphones and radio receivers. If we can't hear the code we can't be shut down by it. Checkmate meatbags.
>>
>>5632870
we could also try to decipher the code by recording it when sophie says it and playing it backwards or analyzing parts of it.
>>
>>5632270
One of the “approved” uses is secure communications, so we could probably still use it like we did before to link allied communications through us.

>>5632870
There’s probably a vocal command system that we aren’t aware that overrides those locks. It should have a separate command to activate it to minimize the risk of an enemy taking advantage of it somehow, but if an Amazon Echo can listen for “Alexa” then they’ve probably figured out the trick too.

>>5632880
Is there any benefit to it? Maybe we could hand it over to our sisters so they can do virtual brain surgery on us to remove it.

Wonder if it’s a hardware switch or a software one?
>>
>>5632913
actually yes. if we manage to modulate sophie's voice, we can activate ourselves and other locked systems without her input, even if we don't know or understand what the actual word means
>>
>>5632918
I thought you were talking the shutdown code like the other anon mentioned. If you’re talking the activation code Sophie just used, that’s more useful to an extent. We’re still bound without a synced pilot, but at least some restraints can be flexed.
>>
>>5632300
Yes, you can try to set up a command net like you did earlier underground.

You would need someone to let you in, because trying to brute force break into their comms is out for now.

I like the thinking on avoiding shutdown codes....Would probably need to get the pilot's cooperation with shutting down comms.
>>
>>5632957
>Would probably need to get the pilot's cooperation with shutting down comms.
if push comes to shove, we have her friends' memories. she owes us.
>>
>>5632960
Thing is, Beta is an ass but we haven’t had him be antagonistic except for one situation involving his sisters. With Sophie, we’ve never even attempted a contested Will check against her since we’ve always talked her down or onto our side.

I’m fairly confident we won’t need to hold that over her head if we need her help. We can just talk to her like we’ e done before.

On the one hand, the class will mean little to her later as she forgets them. On the other hand, forgetting them also removes part of her attachment to the Empire. She doesn’t have “peers” anymore. That makes her easier to manipulate into our camp. I’m curious how the memory dump will shake out.
>>
>>5632970
i mean, yeah, we can use it as blackmail, but on the other hand, beta should understand the idea of trading favors between peers. i scratch your back and you scratch mine, kind of deal. like you just said, we haven't had the need to get antagonistic with sophie, yet.

>spoiler
i guess that could make her not loyal to the empire, but on the other hand, this was made by the enemy™, which will only bolster her allegiance with the empire, because revenge is a hell of a drug
>>
This quest often has quite close votes....I guess it's a good thing that many options are so appealing?

>>5632072
>>5632092
>>5632109
>>5632111
>>5632120
>>5632174
>>5632399
Allied assistance- 7 votes

>>5632214
>>5632248
>>5632253
>>5632264
>>5632278
>>5632328
Direct assault- 6 votes

We'll see who's alive out there, and try to get some meatshields together.

Writing.
>>
File: Strider Scout Walker.png (1.62 MB, 1156x1406)
1.62 MB
1.62 MB PNG
Time is wasting. You eagerly spring into motion, footfalls carrying your frame across the plains. It’s so open up here, and you can’t help but notice the things that are Different.

The ground gives way more than you’re used to, the surface almost squishing down with each step. Particles speckle your frame’s feet, dirtying it.

And the sky, the glowing orb of the sun has descended below the horizon, leaving only the big white rock of the moon, some smears of clouds far above, and thousands of points of light above. Your sensors focus and record all of it. Your sisters will appreciate it, definitely.

The western road you follow is scored by the tracks of many tanks, vehicles, and the march of walkers. It’s mostly dirt, large enough for a double column to pass down, and lighter footprints alongside the road mark where scouts paused and scanned.

The horizon lights up with far-off explosions, and a bright orange laser flashes across the sky. Some Empire forces are still out there.

As if on cue, you start catching the edge of a high-intensity jamming field. The fight is close, very close, and extending your own jamming from Predator will block anyone that detects your frame from reporting in.

You visually acquire a Strider scout walker, the small stepping frame racing at top speed in a zig-zag evasive pattern in the distance. It attempts to turn on a dime and skids, mounted machine guns and lasers chattering and sending the beams behind it.
>>
File: Reaper.png (728 KB, 894x894)
728 KB
728 KB PNG
The pursuers are a quartet of bipedal lighter bots following with thruster boosts in wide-bounding leaps. Almost reminds you of your own simulator forays with Project Burning Eagle. Their motions are jerky, though, and the spray of slow-moving plasma orbs that they fill the air with are far slower than what you would prefer. That, and they’re small, only coming up to your leg like the scout that they are chasing. White plating makes them stand out in the darkness, unlike your own blue shade.

Even one would be more than a match for the Strider, though, and the pilot’s next pause to exchange fire makes them catch one of the volleys, melting through already damaged armor on a leg and sending it sprawling.

“Let’s get in there!” Sophie eagerly pushes you into action.

Targeting calculates the next apex of the leader’s jump, and the Bia spins up, high-caliber bullets tearing the first out of the sky. The second meets the same fate as the first, only on the ground as it tries to understand what just cut down the first. As for the remaining two, they fail the test of survival as they prioritize pressing the attack on the now-lamed walker over their own safety, which also merely grants them a few more seconds to spray plasma bolts onto the prone form, before bullets tear their internals apart.

Bia chaingun gives auto-successes against lighter units. 1 structure per drone, thus all eradicated swiftly

You don’t believe that those were in the Warbook. You start a new entry, setting aside the extremely brief engagement under the name ‘Reaper Drone’

The aftermath is four smashed apart machines, internals strewn across the road, and a strider walker that lacks one leg, yet is still trying to push itself upright. Useless. It’s clearly disabled.

It engages its external speakers, an unsure male voice filling the night.
“Uh, thanks for the assist? Any friendlies there? My mech’s down, and I can’t raise anyone else.”


Voting.
>Interrogate the pilot, then leave them and their disabled machine for salvage crews. You’ll take his codes for communications with any Empire units out here, and any other information he can provide.

>Move on without interacting with him. Talking takes time, which you have a lack of. He isn’t a part of your mission, and is useless for assisting you.

>Eliminate him. Should he be captured, he’ll inform others that you passed this way. No chances can be taken.
Contested Will Check

>Extract him from his downed mech, and take him to be interrogated while you continue pressing for the objective. You could probably cram this unknown into your pilot chamber, though it would be a tight fit, then drop them off with the next Empire forces you find.

>Write-in
>>
>>5633085
>>Extract him from his downed mech, and take him to be interrogated while you continue pressing for the objective. You could probably cram this unknown into your pilot chamber, though it would be a tight fit, then drop them off with the next Empire forces you find.
Acquire pet.
>>
>>5633085
>Interrogate for codes then leave

Honestly no point in killing him.
>>
>>5633085
>Extract him from his downed mech, and take him to be interrogated while you continue pressing for the objective. You could probably cram this unknown into your pilot chamber, though it would be a tight fit, then drop them off with the next Empire forces you find.

Maximize time and data.
>>
>>5633085
>>Extract him from his downed mech, and take him to be interrogated while you continue pressing for the objective. You could probably cram this unknown into your pilot chamber, though it would be a tight fit, then drop them off with the next Empire forces you find.


This is a surprisingly tough choice but I think rescuing him and having him chat with Sophie along the way is the way to go. We get up to date info without hostility, save an Empire life but at a slight risk to Sohpie
>>
>>5633085
>Extract him from his downed mech, and take him to be interrogated while you continue pressing for the objective. You could probably cram this unknown into your pilot chamber, though it would be a tight fit, then drop them off with the next Empire forces you find.
Lucky guy, he gets front row seats to watch our performance, at least until we drop him off.
>>
>>5633085
>>Extract him from his downed mech, and take him to be interrogated while you continue pressing for the objective. You could probably cram this unknown into your pilot chamber, though it would be a tight fit, then drop them off with the next Empire forces you find.
>>
>>5633085
>Extract him from his downed mech, and take him to be interrogated while you continue pressing for the objective. You could probably cram this unknown into your pilot chamber, though it would be a tight fit, then drop them off with the next Empire forces you find.
>>
>>5633085
>>Extract him from his downed mech, and take him to be interrogated while you continue pressing for the objective. You could probably cram this unknown into your pilot chamber, though it would be a tight fit, then drop them off with the next Empire forces you find.
>>
>>5633085
let some rando touch our waifu? no way.
>get the comms codes then move on
>>
>>5633085
>Extract him from his downed mech, and take him to be interrogated while you continue pressing for the objective. You could probably cram this unknown into your pilot chamber, though it would be a tight fit, then drop them off with the next Empire forces you find.
>>
>>5633085
>Extract him from his downed mech, and take him to be interrogated while you continue pressing for the objective. You could probably cram this unknown into your pilot chamber, though it would be a tight fit, then drop them off with the next Empire forces you find.
Build that goodwill with the troops.
>>
>>5633085
>Interrogate the pilot, then leave them and their disabled machine for salvage crews. You’ll take his codes for communications with any Empire units out here, and any other information he can provide.
>>
>>5633085
>Interrogate the pilot, then leave them and their disabled machine for salvage crews. You’ll take his codes for communications with any Empire units out here, and any other information he can provide.
>>
Calling the vote for trying to pick up the scout pilot, then trying to push forwards while carrying him along.

Well, he might have an opinion on that. I'm a little surprised by some of these courses of action that Beta has been taking.

Writing.
>>
>>5633709
Surprised in a way Sophie would share? It’d be amusing to “defend” our actions for her.
>>
“As a scout, he is undoubtedly privy to more up to date intel than us. We should take this opportunity.”
Your priorities recalculate and you close in on the fallen machine.

Extract and interrogate.

“Beta. Where are you gonna fit him? We can’t exactly run around carrying a person in one hand. And it’s too damn cold outside for that! You think that a pilot’s gonna be wearing winter gear?” Sophie objects.

“Proposal. I calculate that there should be enough space in the pilot’s chamber to fit them, assuming an average sized human. You are not a very large human yourself.”

“You can’t be serious! That’s ridiculous! What, you want me to sit in their lap while piloting? If this is a joke, I’m not laughing.”

“I am…’Serious’, as you say it. The alternative is that we leave him to an unknown fate while pressing on without information about what’s happening up ahead. This is a solution that saves time while not leaving us a stationary target interrogating him from outside.”

“Gah, why can’t you just be wrong for once….Fine.”

As your sensors don’t pick up any more active threats in the immediate area, you approach the cripple, kneeling down to inspect it closer.

Your own speakers boom out.
“Empire Pilot. Power down and eject.”

The still machine springs to life, leg flailing around as the machine guns mounted on it spray wildly in every direction.

“Power down or face destruction.”

You poke a finger into the machine’s cockpit, making it abundantly clear that if you wanted it destroyed, there was absolutely nothing they could do to stop it.

The limbs slump, signs of a reactor powering down are evident, and seconds later, the top hatch pops open with a release of hot air. A dark haired man crawls out, the sweat running down his face a testament to the temperature of his own pilot’s chair.
>>
He yells into the air, arms waving in the air.
“I surrender!”

Sophie has her face covered by one hand.
“Beta, you are a fucking moron.”

That was inaccurate, and you considered telling her that fact for a moment.

Consulting the roster of deployed forces, there were supposedly 20 strider walkers in the regiment, and 4 went out with the western spearhead. The man in front of you matches Sergeant Markus Wulfhart, a pilot of the 56th, who’s been serving for about 8 years. You wish you had a clear connection to look up more than a basic face scan, serial number, and dates of deployment. You provide this to your pilot, while you place your hand on the ground, palm-up.

Sophie takes over the speakers.
“Sergeant, we’re on the same side. I need your mech’s battle recorder for the communications codes to the rest of the 56th.”

Markus, hands in the air, starts to lower them.
“Well, if you’re not, then I’m right krak’d. I didn’t think we’d get reinforcements after the jamming field went up. Who are you with?”

“State Security. Anything more’s classified, I’m afraid.”

“Ah….Ok. Not sure how that’s gonna help you, but sure.”
He goes back through his own hatch into the Strider.

“Beta, all we need is the battle recorder. We can leave him here when we get it. Then I don’t need to share the chamber with anyone, and he’ll be picked up by friendly forces on our way back. Look, he’s a Sergeant. Nobody important. Our mission isn’t to get this guy, it’s to get the general.”

“Pilot, this will only be for a short time. We will deliver him to the next friendly unit that can carry him when we come across one.”

“Fine.”

A minute later, you’re working at unencrypting the battle recorder, Sophie is laying back as far as she can go in her chair, and Sergeant Wulfhart is trying to jam himself into place with his legs while your frame jostles and moves him with every step. Groans of pain rise as a particularly long stride knocks his head against the hatch.

“Ow! I thought I was screwed when the crabs blew off my leg, but this is right miserable. Fuck, can’t you slow down for a bit? Where’s the second cockpit? Surely your partner’s got a better resting place than this. Or your other support units? Come on, this sucks.”

This human likes the sound of his own voice.

“Sergeant, I need your authorization code to get into your unit’s comms.”
Sophie’s there, trying to get something useful out of him.

“Comms are blocked. Jamming’s got us right krak’d right after the pillheads rolled into our position some hours ago.”

“You let me worry about that. I just need the channel you used.”

He rattles off the channel number and code without a hint of hesitation. “Make sure to call out saying Bowmaster is doing great. Hey, you said you’re with StateSec? What are they doing out here? How many mechs you got?”

“Classified, Sergeant.”
She puts a bit more emphasis into her words.
>>
Vote!

You’re still deciphering the battle recording, but at least you have a starting point to communications, and one very talkative scout pilot crammed into your pilot’s chamber.

With the appropriate channels now, you can boot up the Predator array to try and punch through the jamming, contacting anyone still fighting. This will draw attention like lighting a beacon in the night, though, starting a timer until unfriendly attention moves to investigate.

>Form a command net. Full power, continuous broadcast to find as many allies as possible and start linking them to each other.

>Brief broadcast. Send Markus’ message, briefly, and attempt to turn on and off the Predator in order to keep anyone from homing in on your position directly.

>Leave it off. You can’t risk it.
>>
>>5633758
>>Brief broadcast. Send Markus’ message, briefly, and attempt to turn on and off the Predator in order to keep anyone from homing in on your position directly.
Lets wait until we know whats going on to sert up a command net. Just do whats needed to find the general without bringing the entire enemy force down on us.
>>
>>5633758
>Brief broadcast. Send Markus’ message, briefly, and attempt to turn on and off the Predator in order to keep anyone from homing in on your position directly.
Beta is good at ambushing and catching an enemy might get him into their communications.
>>
>>5633758
>Brief broadcast. Send Markus’ message, briefly, and attempt to turn on and off the Predator in order to keep anyone from homing in on your position directly.
"Pilot, it is imperative to the success of this mission that you sit in this sweaty mans lap."
>>
>>5633758
>>Leave it off. You can’t risk it.
>>
File: 1667285478180625.jpg (32 KB, 413x369)
32 KB
32 KB JPG
>Form a command net. Full power, continuous broadcast to find as many allies as possible and start linking them to each other.
Coordination is key, and we're supposed to be extracting a VIP right? More eyes the better, and the enemy doesn't have our sibling cores (thanks to the fact we saved them) so it shouldn't be so easy to tap into anything we're doing

>Look, he’s a Sergeant. Nobody important. Our mission isn’t to get this guy, it’s to get the general.”
Oh hell no. As enlisted, I resent that. While we are grunts, we are the backbone, and leaving our guys behind is like intentionally severing your own spine. Get us mad and you're fucking yourself. Save all the hoighty toity officers you want, you leave enlisted out to die without their say and you risk all of us deciding we don't wanna work for you anymore. Especially if this NCO is a good guy and treats his lower enlisted right, and then you'll end up with a tantrum spiral of angry soldiers mad that "one of the good ones" got fucked over. Empire is weakened enough as it is without proving to the rank and file you don't give a damn about them.

>Come on, this sucks.
Checks out, bellyaching is a time honored pastime. Doesn't mean anything really, it's just something we do to vent stress, pass time and make conversation. The trucks too bumpy, the chow is cold, the ruck is heavy, the 1SG sucks, too hungover for this shit, etc. The game is to bellyache right back, it's a flipped form of camaraderie. Misery loves company.
>>
>>5633758
>Form a command net. Full power, continuous broadcast to find as many allies as possible and start linking them to each other.
considering the beating the troops took, the enemy will assume we're coordinating a retreat, not a counter offensive. we should be fine, as long as we keep the encryption up
>>
>>5633804
>Oh hell no. As enlisted, I resent that. While we are grunts, we are the backbone, and leaving our guys behind is like intentionally severing your own spine. [...] Empire is weakened enough as it is without proving to the rank and file you don't give a damn about them.
i hope beta blurts out if a sergeant is important and he replies with all of that
>>
>>5633758
>Form a command net. Full power, continuous broadcast to find as many allies as possible and start linking them to each other.
As I understand, the Tamar forces have nothing in the area to pose a threat to us, at least in a head-on engagement. They can also launch anti-radiation missiles and home in on our signal, but the Bia should be able to shoot them down.

That said, we might have to step back to avoid being distracted and catching a cruise missile for the effort. The 56th can handle the counter-counter-offensive once we've set up a command net.
>>
>>5633758
>Brief broadcast. Send Markus’ message, briefly, and attempt to turn on and off the Predator in order to keep anyone from homing in on your position directly.
>>
>>5633826
It'd never happen IC, Beta nor Sophie would have a clue. Beta is still a "child" and while it has knowledge, stratagem, doctrine, simulation, it does not have experience, real world or interpersonal. And Sophie is basically an officer and a child, but not, and still in a developmental phase of adolescence. Weird case of brainlet JROTC cadets being cross trained with bizarro Black Box brain melting AI tech that doesn't have much analog for real world. My personal meta comes from personal empathy and neither are equipped to navigate that kind of mental and emotional thing. I'm a few down and thinking too deep

Either way, don't treat your guys as expendable in any situation. It can have a disastrous ripple effect, and trust should be built first and foremost.

Computer, Google "fragging"
>>
>>5633758
>Form a command net. Full power, continuous broadcast to find as many allies as possible and start linking them to each other.
ASSUMING CONTROL
>>
>>5633826
Actually to put it simply, first impressions are everything especially in the military. If Beta looks out for the enlisted off the bat, they will look out for and vouch for him, potentially preventing hangups in the future. By prioritizing a minimal loss of life on a mission, opens up further trust and options for the future one way or another

This scout, while bitching now, is gonna talk about it in the barracks. Which WILL go up and down the ranks. Any officer or senior NCO worth their salt listens to the guys that have their boots on the ground. Call this guy an investment if we're applying machine logic
>>
>>5633843
>>5633848
exactly my point. beta and sophie don't know(or don't understand in real world terms) what the positions mean, so having the input of a "foreign" soldier can give them an extra point of view they weren't aware of, because lets honest here, one is an AI that only knows how to kill and the other is a traumatized kid. they're both lacking on the emphatic side
>>
>>5633848
>This scout, while bitching now, is gonna talk about it in the barracks. Which WILL go up and down the ranks.
I can vouch for this from my experience in the military. Soldiers are the biggest gossips bar none, because what else is there to do while waiting for the next leave?
>>
>>5633758
>Brief broadcast

And to add onto discussion with >>5633804
>>5633843
>>5633848

While Sophie and Beta aren't. . really good at social stuff, Beta at least is liable to puzzle out the benefit of good optics.
Mostly, and I do say MOSTLY due to the fact that we considered murdering them to keep our location secret, because we know exactly what it is to be betrayed by our CO's.

Think. what would Blake do in this situation. Then do the opposite.
>>
>>5633758
>>Form a command net. Full power, continuous broadcast to find as many allies as possible and start linking them to each other.

I aint scared
>>
>>5633758
>Form a command net. Full power, continuous broadcast to find as many allies as possible and start linking them to each other.
This will allow the ambush group to find us easier, but I’m honestly okay with that. We fight them, the offensive can possibly recommence and tie up enemy resources so the general has more time. We also kill a pretty potent enemy force.
>>
>>5633758
>Form a command net. Full power, continuous broadcast to find as many allies as possible and start linking them to each other.

Did somebody say draw hostiles away from the VIP and into our Bia's crosshairs?

Yes Please.
>>
>>5634267
>”Sophie has told me that some of the soldiers have started calling me ‘Leeroy Jenkins’ because of how I charged into enemy lines. Something related to how I kept the command net open the whole time and taunted the enemy as a result.”
>”The reference is lost on us, but we can tell it is meant partly as an insult. Somehow.”
>”No matter. It worked to draw the enemy to us. I will keep being a ‘Leeroy Jenkins’ when needed.”
>>
The votes:
Brief broadcast- 5 votes

Setting up Command net- 6 votes

Staying silent- 1 vote

Looks like setting up a command net wins. This does attract some attention.

>>5634387
Hah! You'll need to take more risks than that to gain that as a moniker.

Skill check, for detection.
Base Skill is 3, with a x1 modifier for low-sync.

Thus, I need 3 rolls of 1d6
>>
Rolled 2 (1d6)

>>5634500
>>
As I think this is the first roll of the Thread, Core of Steel operates on a d6 system.

You have your pool of d6, and you attempt to roll 4, 5, or 6 to get successes.

Often this will be a contested roll, against what rolls the enemy are doing, in which case I count the number of successes they get against whatever Beta gets. In case of a tie, Beta wins ties.
>>
Rolled 2 (1d6)

>>5634500
>>
Rolled 5 (1d6)

>>5634500
>>
>>5634506
>>5634522
>>5634526
1 Success, writing.

At least Beta isn't getting totally caught unaware.
>>
If you can directly connect to the General and the 56th, you could instantly start getting up to date reports on the situation. You could even gather them into a counterattack! With this Sergeant’s code and channel, you can start putting all the pieces together.

The battle recorder is set aside, as you instead start directing power to the Predator, briefly halting and crouching down. You’re going to need a continuous broadcast to try and punch through the jamming, and listen for the return pings that signify available responses.

“Hey, why’d we stop?” The Sergeant is relieved by the brief break from the rough ride.

Sophie knows what you’re doing, as her HUD tells her where power is routing, and her link to you, though more tenuous than before, gives her a bit of a read on your intent.

She starts, “Sergeant, shut up, I need to focus. Beta, that might not be….”


And you start calling out, seeing what responds.

You continuously broadcast for 10 seconds, then listen. For signals, not the criticism of your pilot which almost immediately starts.

“That was dumb. Every Alliance unit on this side of the river had to have heard that. And they’re coming straight here!”

Good.

“What happened to ‘minimal amount of risks’?”

“Pilot, all the intel we have has suggested that they do not have more than medium mechs. You know what I am capable of. Coordinating the 56th into a viable fighting force is only possible with a strong enough broadcast to break through the jamming.”

Your choice begins to pay dividends.
The first to check in with a correct response is a Tyrant tank commander very close to you, and you isolate and lock it in. She has a quartet of tanks, several APCs of infantry, and support power armor slightly further up the road. They identify as Battleaxe company.
The next is a pair of medium mechs, falling back off-road.
A heavy mech finally reports in, calling their position as being crippled in the river and unable to move. They request pickup. Repeatedly. Not likely.
Two more heavy mechs not actually in the river report heavy attack by light units, and badly damaged.

The general has not responded, and the tank commander of Battleaxe is the ranking officer.

Of the original 16 mechs and 6 tanks in the western spearhead, you have found most of the tanks, and about a quarter of the mechs. Not a great tally, if you’re being honest. Ah well, that’s what you can expect.
>>
File: SkitterMine.jpg (212 KB, 1920x1165)
212 KB
212 KB JPG
“Battleaxe to…Unknown. We weren’t expecting reinforcements.”

Sophie, to her credit, rolls with it.
“Cobalt 04 here. We are providing communications. StateSec special forces.”

There’s a silence on the other end of the line.

“Ah, we received the communications codes from one ‘Bowmaster’.”

“Glad to hear someone’s still alive and kicking.” Battleaxe replies in a clipped tone.

“And we will be routing all remaining mobile Empire forces to your position. You are the current ranking officer of the western spearhead. Communications will remain online as much as we can manage.”

“Hang on, who are you?”

“If you want channels, then ask back along this same channel. And try not to shoot the blue mech as we approach.”
Sophie then closes the channel. And you promptly start linking other people, one at a time, into Battleaxe’s channel.

“Good news! Apparently Battleaxe company is not far and we can drop you off with them.”

Wulfart’s been quietly watching from his cramped position. As he’s lacking an earpiece, there’s no reason to include him in communications.
“And the bit about every Domer on this side of the river coming straight for us?”

Sophie’s smile fades a bit.
“Ah, yes, my partner’s a little eager. You should leave before I need to start doing some real combat maneuvers.”

You rise then at that prompt, 164 seconds having passed since stopping to connect everyone you can reach.

Next destination: Battleaxe Company, about 4 miles up the road. Quite close. Surprising that you didn’t get them on Mag-Scan. A lack of seismic is understandable, with how fast you were trying to move, but it’s a little concerning that you couldn’t see them. You run some diagnostics on your sensors, and they all come up green.

Just in time, though, to avoid a set of mobile bombs which attempt to run underfoot as you stride down the road. An early step later, and your pace goes over the attempt to blow off your foot, and the Bia with a single burst sets off the trio of walking bombs.

That…wasn’t something you’d seen before. They had to be on some sort of trigger code to home in on you. Huh, maybe you can get something similar. Could be a useful tool, programmable bombs.

And that off-step and spin to acquire targets has knocked Wulfhart’s head again.

This whole Passenger thing is really not what your pilot’s chamber is designed for.

Approaching a column of vehicles on the road, who Finally appear on mag-scan, you receive a request for comms.
“We have you on visual, Cobalt.”
>>
You’re dropping Sargeant Wulfhart off shortly.

But, at the same time, you’ve got some rather squishy support (Compared to you, anyways) in the form of Battleaxe company.

The Command net is up right now, letting friendlies actually talk to each other. As long as you are running it, your position is highly obvious.

Voting
>Direct assault. Fall in with the tanks and mechs, lead them right back up the road they retreated from.

>Bait. You’re the obvious one, you can lead away the Response force and take them on alone, along with the bulk of fast defenders, while Battleaxe pushes forwards on their own.

>Distraction. Battleaxe attacks on their own, while you drop the command net and make your way to the river.

>In and Out. Battleaxe holds the current position, collecting survivors. Beta will take the medium mechs and ridealong powered armor to go after the heavy mechs on the river, picking them and the general up and retreating.

>Write-in- Make sure to note if you want the Command net up or down for the write-in.

If you want to ask Battleaxe or Sargeant Wulfhart any questions before dropoff, feel free to ask.
>Write-in questions.

A/N
I really don’t mean for this to become substandard tactics quest, I swear. The writing just kind of folded that way with the choice to go up the route that actually has useful direct support. Picking the stealth route or direct approach would have skipped most of this. You’re not going to be able to micro them much more than telling them to attack/defend/retreat.
>>
>>5634608
>>In and Out. Battleaxe holds the current position, collecting survivors. Beta will take the medium mechs and ridealong powered armor to go after the heavy mechs on the river, picking them and the general up and retreating.
>>
>>5634608
>>In and Out. Battleaxe holds the current position, collecting survivors. Beta will take the medium mechs and ridealong powered armor to go after the heavy mechs on the river, picking them and the general up and retreating.
>>
>>5634608
>Bait. You’re the obvious one, you can lead away the Response force and take them on alone, along with the bulk of fast defenders, while Battleaxe pushes forwards on their own.

The desire to flex on baddies is rising!
>>
>>5634608
>>In and Out. Battleaxe holds the current position, collecting survivors. Beta will take the medium mechs and ridealong powered armor to go after the heavy mechs on the river, picking them and the general up and retreating.
>>
How do we know where the general is? So far I don't think we managed to determine his exact position..?
>>5634608
>In and Out. Battleaxe holds the current position, collecting survivors. Beta will take the medium mechs and ridealong powered armor to go after the heavy mechs on the river, picking them and the general up and retreating.
>>
>>5634608
>>In and Out. Battleaxe holds the current position, collecting survivors. Beta will take the medium mechs and ridealong powered armor to go after the heavy mechs on the river, picking them and the general up and retreating.
>>
>>5634608
>In and Out. Battleaxe holds the current position, collecting survivors. Beta will take the medium mechs and ridealong powered armor to go after the heavy mechs on the river, picking them and the general up and retreating.
>>
>>5634608
>In and Out. Battleaxe holds the current position, collecting survivors. Beta will take the medium mechs and ridealong powered armor to go after the heavy mechs on the river, picking them and the general up and retreating.

>Write-in questions.
Ask Battleaxe about the Generals actions during the mission. Why is he with the western forces?
>>
>>5634670
Beta got a general location of where his mech went down during the briefing, and he's hoping that the General is close to there.
>>
>>5634608
>In and Out. Battleaxe holds the current position, collecting survivors. Beta will take the medium mechs and ridealong powered armor to go after the heavy mechs on the river, picking them and the general up and retreating.

Write-in questions.
>Ask Battleaxe about the Generals actions during the mission. Why is he with the western forces?
Thanking >>5634696 for the reminder.
>Ask for their estimations on enemy forces by the bridge. If we take out the response group, would they still have the forces to hold the bridge? To clarify, our mission is to retrieve the general and leave. We can’t remain unless we receive new orders.
Giving Battleaxe an opportunity to talk us out of retreating with them. I expect they’ll say no, they want to pull back.

To Sophie, after the passenger is out
>If the general orders us to assist in taking the bridge, do we listen to them?
Giving her time to think over it. I’d prefer to stay and fight, but that’s not the mission. I also don’t know if they can hold the bridge without us, and we definitely can’t stick around playing security guard.
>>
>>5634608
>Bait. You’re the obvious one, you can lead away the Response force and take them on alone, along with the bulk of fast defenders, while Battleaxe pushes forwards on their own.
>>
>>5634608
>>In and Out. Battleaxe holds the current position, collecting survivors. Beta will take the medium mechs and ridealong powered armor to go after the heavy mechs on the river, picking them and the general up and retreating
>>
File: Apollo_pointing.png (55 KB, 240x125)
55 KB
55 KB PNG
>>5634781
General's last marked location was received from the central road, yet the last KNOWN location of the General is just four miles west of the bridge, where the jamming is very strong. Was there a drone in the area capturing the footage?

What doesn't add up is the General's transmission about getting shot down. Can we compare the timestamps between the map marking and the transmission, then check if the General could've feasibly move to the banks of the west river in that time.
>>
>>5635032
Addendum to my last post, I know jamming doesn't affect signal transmission, only reception. But if that were the case, we would've had a better idea about everyone's movements as long as they were transmitting over the jamming, unless they were following an order for maintaining radio silence.
>>
>>5634608
>In and Out. Battleaxe holds the current position, collecting survivors. Beta will take the medium mechs and ridealong powered armor to go after the heavy mechs on the river, picking them and the general up and retreating.

>>5635064
Emissions control would still generally dictate that you don't push out more power than you absolutely need to. If everyone's holding down the transmit button, everyone is getting drilled with precision artillery.
>>
>>5635032
Basically you’re suggesting the bit about the general’s location may be a trap to provoke the Empire into pushing towards another ambush? Could be depending on how we got the intel. Shame we couldn’t roll with the recon drones for this mission, they could help answer that question. At least questioning Battleaxe (and other survivors) ought to clarify what happened.

>>5635064
I would have assumed they went for radio silence. If you don’t think anyone among your allies has the juice to pick up the signal, transmitting your location can only benefit the enemy.
>>
No update tonight, delayed to tomorrow morning.

>>5635032
No drones, unfortunately. The general's location was just triangulated off of a couple of transmissions that the scraps of the Eastern group got when retreating.

Some of this is absolutely me just not quite knowing the actual science behind jamming/communications codes and trying to just handwave it with Scifi excuses.

You'll get the update on what Battleaxe knows next, that should hopefully sketch out what went down, and why things are so f'd


A lot of this might have been helped if I just threw together a map.....Whoops.
>>
>>5635370
just ask us. we can help on that aspect
>>
>>5635370
>>5635372
Yeah, you never know with the gestalt mind of autism, you might have a phd in radiofrequence hiding in your playerbase
>>
The tracking of the first two turrets is a rather unfriendly greeting, for being allied units. You halt, and kneel down again.

Sophie engages manual unlocks for the hatches.
“Your stop, Sergeant. Out.”

He wiggles free from his cramped position, and cracks the hatch open.
“Thanks for the pickup, pilots. Less so for the bumpy ride.”
You let him unload. Ungrateful human. You watch him run down towards the first APC in line and bang on the hatch, while a bemused power armored trooper looks on. You’ve still got his Battle Recorder, which you’ll crack through sometime. Skim it for data.

“So, now that he’s gone, what’s the plan, genius? I’m honestly counting the minutes before your move with the Command link brings down some high-explosive consequences.”

“We move. Take all the faster allied units forwards, and go in and get out with the objective.”

“Easy to say.”

—-
Battleaxe is talking over your net, consulting with some of her subordinates, when your pilot breaks into the channel.
“Cobalt to Battleaxe. I need a report on the enemy contacts by the bridge. We are headed there to retrieve the general and eliminate enemy response forces.”

“Cobalt, the last I heard, our mechs fought through multiple dug in positions close to the bridge with infantry and enemy power armor, and ten-plus ‘Crab’ drones. That’s when the jammer turned on, and I called a halt until communications turned back on, and then a retreat when a lance of enemy mediums started performing hit and runs at range. There was no point in getting our infantry massacred by mechs while sitting in the steel coffins, and I wasn’t getting anyone on the comms until you turned up.”

“And why’s the general’s position on the western bank, where the western spearhead was supposed to go instead of the southern thrust?”

“No idea. Haven’t had any contact since the jammer went up, last I was contacted by him he was still with the direct southern thrust and engaging dug-in infantry positions. Before the jamming, obviously.”

“If we remove the enemy mechs as a factor, then would you have the forces available to take the bridge?”

“Negative. But, unless you’ve got another lance in a side channel you’re not sharing, I’m not sure how you could even keep at least two lances of enemies occupied.”

“Hold position here or nearby. We require any fast support you can give, and a point for us to return to.”

“Copy that Cobalt. Stand by.”

Battleaxe requests a link to the medium mechs that were retreating, which you grant.
“Battleaxe to Onyx, Nugget. You two are to halt your retreat, and I’m transferring you to the command of Cobalt. Good luck, and come back in one piece.”

“Yes- Yes, Ma’am.” A pair of voices speak out.

Up and forwards, then. At least the tanks are no longer tracking you with their turrets.

You move to regroup with your new subordinates, striding down the length of the convoy.
>>
A/N
No vote yet.
Yes, this is a day late and lacks a vote, but just trying to keep moving along.
>>
>>5635370
>A lot of this might have been helped if I just threw together a map
You've done well without one so far, though it would help to keep track of things.

There's a map making tutorial on YouTube made by Little Wars TV if you want to make a presentable map using only MS Paint, but you could also draw a quick sketch if you want to focus more on the writing.
>>
>>5636865
I ran a Command and Conquer quest a couple years ago and it basically turned into an RTS game with MS Paint. Very doable and surprisingly good fun but very exhausting
>>
>>5636865
even just a grid pattern is useful
>>
>>5636039
Just checking in on you QM, hope nothing too bad has happened.
>>
>>5640114
The QM curse is savage and indiscriminate


RIP CoreQM

Only kidding I also hope the QM is doing well. I was hoping for a shitty paint map to be thrown up by them so I could make a better one in Wonderdraft
>>
File: Operation Routes.png (100 KB, 440x640)
100 KB
100 KB PNG
>>5640114
>>5640191
I'm working on it. Suffered from a serious lack of motivation and Real Life for the past few days. I promise to get a proper update tomorrow. Honestly.

In the meantime, yes, here's a low effort MS Paint map I put together.

Brown/Grey is roads.

Green was planned spearhead attack routes.

Blue is Cobalt's (Beta) route so far.

Black dot is current position.

Dark red is theorized enemy fixed positions.

Orange star is General's last known position.

The light green/yellow arrows are the known retreat routes that have been taken.
>>
File: Map v1.png (3.4 MB, 1920x1080)
3.4 MB
3.4 MB PNG
>>5640339
Here is a link to some sample versions of the map. If you like one in particular I'll upload it separately with (pr without depending on your preferences) the hexagonal overlay and Beta token

https://imgur.com/a/bUVen4j

Here is the base map with Beta token and no overlay as well. Let me know if any of these suit
>>
>>5640445
My scale and shape of it all is a bit fucked admittedly, but that's just a quick job of throwing something together. Don't feel pressured to use them
>>
>>5640339
I don't know if it helps motivate you any, but I've read through the entire archives this weekend, and can't wait to see more of your work. You're doing great, and thank you for running.
>>
File: Onyx and Nugget.png (101 KB, 556x750)
101 KB
101 KB PNG
Metal and men, the foundation of the empire.

Though the metal seems to be lacking, tonight. Or perhaps it’s the men.

Questioning heads poking out of hatches track your progress down the column, the orb of the moon shining down, peeling away your stealth for now.

Already some of the powered armor has dismounted, trying to find cover around their parked vehicles. Some have even started trying to dig holes in the dirt.

A little extra spring in your step to make the ground quiver is enough to make all stop and briefly look at your frame, passing by. You like the attention


Onyx and Nugget’s mechs aren’t as tall as you, and you can see preexisting armor damage as you approach. However, Onyx seems to have a pair of Power Armor latched onto the outside, riding along. They could be useful.

The Warbook classifies their mechs as Griffins, moderate speed and decently armed with a primary arm-mounted laser weapon, and secondary missile battery. They couldn’t keep up with you at full speed, but you can slow down a little for their lesser capabilities.

They wouldn’t be fast enough to escape most pursuing units, so they’re either lucky or skilled to be the last few mechs to be alive and mobile.
You note that Onyx in particular seems to have taken almost all of its damage to the weaponless left arm. Passing them, you note Nugget took several strikes to the rear, slagged and melted armor showing the old path of a laser.

“I am Cobalt. Fall in, subordinates.”
Sophie projects over the comms while proceeding down the road.

There's a bit of a pause, then the waiting mechs both follow your lead, one after the other. Nugget first, then Onyx sweeping left and right at the rear.

There’s a comm request for personal channels between them, which you grant. You’re listening, naturally.

“I thought we were slag, Gehrman. We were putting tubes on marked targets, then blam, The jamming went up and a laser went straight through Pinman’s cockpit. Must have cooked that poor bastard alive. Glad you skedaddled and got out of there quick.”
The voice of Nugget is rapidfire and quick.

“It’s good to hear your voice, Nugget. But can the chatter and stay focused. We’re going back in, so head on a swivel. And, ah, don’t talk about that last thing. Not sure why we're being led by a kid, though.”
Onyx sounds somewhat raspy.
>>
Your little squad has reached the turn of the road to match the river, and the sounds of combat have intensified.

Ahead of you, the thud of cannon shells is matched by the whining of lasers, intermixed with smaller explosions. Seismic tells you that at least three Tamar medium mechs are moving around, exchanging fire with a slow-moving heavier unit, which has not contacted you.

There may also be lighter or hidden units, but seismic cannot tell you if there’s any more.

Voting
>You have the element of surprise, and they are in your way. Engage the Tamar mechs, and crush them as fast as possible.
Pick- Close, Medium, Long range.

>If the heavy unit did not check in, it’s not friendly. Ignore them and detour around the mess.

>Wait and let them fight it out, then sweep in on whatever survives.

>You don’t have time for this. Send in Nugget and Onyx as distractions, and bypass the mess to make it to the general’s last location.

>Write-In.

On the Pilot-
Sophie's will is 3, Beta's Will is 5. If Sophie fails, then Beta can step in and try to pull her in himself. Is painful for the pilot.
>Low-sync
No check needed. Maintain x1 modifier.
Who needs any better against these?

>Mid-sync
Need 2 successes. 1.5x modifier.
Give the enemies a little respect. They aren't peers, but you might need the boost.

>High-sync
Need 3 successes. 2x modifier.
Not needed right now. You'll only have a short time at high-sync, before Sophie can't take it anymore. It's not worth it for these small fries.

A/N- I’m back. Sort of.

>>5640445
Thanks a ton for the map. It’s cool and hopefully lets people visualize the battlefield, simplistic as it is. And it's 10x better than the MS paint crap I put together.
And also, yes, I am very weak to (You)s with compliments.

>>5640860
Hopefully I can keep on this long enough that reading the archive actually means something more than a measly 2 threads.
>>
>>5641099
>You have the element of surprise, and they are in your way. Engage the Tamar mechs, and crush them as fast as possible.
The cavalry is here!

>Close range
>Low-Sync
We should make short work of them with Bia and Project Yi combined, while Onyx and Nugget will pick off any fleeing enemies. Save Mid-sync for later.
>>
>>5641099
Whoot whoot we're back

>You have the element of surprise, and they are in your way. Engage the Tamar mechs, and crush them as fast as possible.

> Long

Maybe the big guy lost his com gear
>>
>>5641099
>Ask Onyx and Nuggets about the bigger unit

>>You have the element of surprise, and they are in your way. Engage the Tamar mechs, and crush them as fast as possible.

>Close range
>Low-sync
>>
>>5641099
>>You have the element of surprise, and they are in your way. Engage the Tamar mechs, and crush them as fast as possible.

Medium Range

On the Pilot-
>Low-sync

--
QM did you have a preference to which colour scheme (including just base colour with the hex overlay) you'd prefer? If so I can upload the full version for you to use
>>
>>5641099
>>You have the element of surprise, and they are in your way. Engage the Tamar mechs, and crush them as fast as possible.

>close range
>Low-sync
>>
>>5641099
>You have the element of surprise, and they are in your way. Engage the Tamar mechs, and crush them as fast as possible.
Close range for us, Nugget and Onyx choose their own

>Low-sync
>>
>>5641099
>You have the element of surprise, and they are in your way. Engage the Tamar mechs, and crush them as fast as possible.
>Close range
>Low-Sync
Remember Beta, you can always throw enemies at each other to conserve ammo!

>Ask Nugget and Onyx if they recognize the heavier unit. Could be their comms are slagged. Could be a third party.
Does Beta know non-verbal signs that can be used to communicate with other mechs? Not relevant now, but we could try it after defeating these mechs.
>>
>>5641099
>You have the element of surprise, and they are in your way. Engage the Tamar mechs, and crush them as fast as possible.
>Close Range
>Low Sync
Beta and Sophie's first real live combat together, hopefully it'll go smoothly.
>>
Out of curiosity, why is everyone voting close range, when we have a weapon that gets bonuses at long and medium range?
>>
>>5641579
We have the Bia chaingun, which gets bonuses at close and medium, not long. See >>5629701.

Between those, it’s a matter of whether we want the combined defense/attack rolls from close-range combat or just the attack vs. defense rolls from mid-range combat. Yi gives an extra defense die which would only help our attacks at close-range, and the mechs are supposed to be inferior so we probably have the advantage on both attack and defense. It means that close-range is likely to end it faster in our favor.

If we’re wrong to assume the mechs are inferior then mid-range would probably be a better call, but I’m willing to chance that for a quicker fight.
>>
>>5641579
i'm guessing its to use yi since we have it and put on a show for allies and enemies alike.plus who doen't like seeing big bots beat em up?
>>
Calling it for engaging at close range, maintaining low sync.

Close range, Attack of 3, +1 from Bia, combined with a defense of 3, +1 from the Yi.

I need 8 rolls of 1d6, looking for 4+s

People can roll up to 2 dice per post.

I need
>>
Rolled 6, 3 = 9 (2d6)

>>5641874
>>
Rolled 2, 1 = 3 (2d6)

>>5641874
>>
Rolled 1, 1 = 2 (2d6)

>>5641874
Let me speed this up.
>>
Rolled 5, 6 = 11 (2d6)

>>5641874
>>
Rolled 6, 3 = 9 (2d6)

>>5641879
>>5641881
>>5641901
>>5641904
3 successes. Not great, but not terrible.

Throwing 2 dice for your support.
>>
Rolled 5, 6, 5, 2, 3, 6 = 27 (6d6)

And throwing dice for the Opfor.

One of them is preoccupied and unable to twist in time, but the others react.

Writing.
>>
File: Dominus Walker.png (185 KB, 885x750)
185 KB
185 KB PNG
It only takes a second for you to calculate your options, and decide on a plan. Close range would let you dispatch them the fastest.

Speed and power. You are superior, you know this, and it’s time to prove it against actual peer opponents. Just like the simulator. Except your pilot’s terror is real, your frame has defects, and this ‘moon’ is making it hard for you to remain undetected, annoying.

Your support just can’t keep up to your increased speed, though Nugget tries, valiantly pushing his mech to its max speed. It’s not quite two-thirds of your current pace, without using the Yi.

Closing the distance gives you better returns on what, exactly, is firing those autocannons.

You haven’t seen the model or its opponents in the sims, but the Warbook identifies the heavy mech as a Dominus Walker. One leg has already taken heavy damage and has seemingly seized up, while the metal beast staggers onwards, the much lighter opponents circling around its heavy cannons as you would, peppering it with their own missiles and autocannons.
>>
File: Hostile Alliance Mech.png (1.66 MB, 1494x1684)
1.66 MB
1.66 MB PNG
Speaking of the opponents, they’re faster than the walkers you’ve usually faced, and they even have proper hands carrying external primary weapon. Boosters allow them to do short hops across the ground, moving faster than their running speed, which explains the odd intermittent returns on seismic.

However, tonight they are merely targets, their own jamming rendering them unable to communicate effectively. Probably

There are three you can see, a pair on the far side, and a lone one closer, constantly forcing the Dominus to turn and try to bring its cannons to bear. As you close, the friendly falls to the ground, the pilot inside unable to compensate for the damaged leg any more.

While they’re all paused, eyeing the flailing mech on the ground, you strike.

The Bia sends its first volley into the pair, chattering away and drawing their attention with high-velocity bullets. They scatter with coordination, dodging to each side with their infernal boosters. Your true target, however, is the lone walker on your side, who isn’t as fast to move and fails to dodge as your off hand forms a dagger, stabbing into the rear-left side, aimed for the exhaust vents.

They reel forwards, and a follow up strike aimed at the same position knocks it further out of position, putting it damaged but not out. Peppering the back doesn’t seem to yield any satisfying explosion, while they try to drunkenly run towards their friends.

The others spray their own autocannons back at you, forcing you to spring aside and back away from your victim. A shoulder-mounted laser whines and shorts out your infrared sensors from a near miss. Come on, how do you miss a laser? Is their targeting that bad?

A long-range volley of missiles from further back convinces them to retreat, your support finally catching up to you.
—-----------

The first engagement was indecisive, and they’re trying to withdraw.

Voting.
>Press the attack. They’re running, and one is damaged. You want some actual kills on the board!
(Pick range, Short, Medium, Long)

>Let them run. Attempt to rescue the Dominus pilot from their downed mech.
You don’t think this is the objective.

>Route Onyx and Nugget to pick up the pilot, while you pursue.
(Pick range)

The option is also there to try and up the sync rate.

A/N: You tied thanks to the supporting fire, but ties go to Beta. They’re all rolling 3 dice each in close range, but again, surprise stopped one of them from contributing.
Yep, Tamar Alliance designs are mostly from Titanfall. Smaller generally and lighter, but more mobile, while the Empire usually has armor and firepower.
>>
>>5642005
>>Route Onyx and Nugget to pick up the pilot, while you pursue.

>Close Range
>Mid-sync
>>
>>5642005
>Route Onyx and Nugget to pick up the pilot, while you pursue.
Medium range now, these mechs seem to be good in close.
Also isn't Bia supposed to grant autosuccesses against light targets? Are these not light enough?
>>
>>5642005
>Route Onyx and Nugget to pick up the pilot, while you pursue.
>Medium range
>>
>>5642005
>Route the support to pick up while we persue
>Short range
>>
>>5642005
>>Route Onyx and Nugget to pick up the pilot, while you pursue.
>medium range
>>
>>5642005
>Route Onyx and Nugget to pick up the pilot, while you pursue
>Medium Range
>>
>>5642034
They're still counted as 'Armored' targets. 'Light' targets the Bia gets autosuccesses against are non-peer stuff, like the Crabs from earlier or powered armor. Basically the small stuff.
>>
>>5642005
>Route the support to pick up while we pursue
Having them return with reinforcements could jeopardize the General later.
Kills would be nice too, but I’m more concerned with reinforcements. Everyone we’re “escorting” is so slooooow.
>Close
>>
>>5642005
>>Route Onyx and Nugget to pick up the pilot, while you pursue.
>Medium range
Meds, now.
>>
Gonna leave this vote up, no update tonight yet.

>>5642360
The perpetual problem of having a force being bound to the speed of the slowest member.
>>
>>5642005
>Route Onyx and Nugget to pick up the pilot, while you pursue.
>Medium range
>>
>>5642005
Press the attack. Medium range.

Dead enemies can't fight back.
>>
>>5642005
>Route Onyx and Nugget to pick up the pilot, while you pursue.
>Medium range
>>
Calling votes for:
Route Onyx and Nugget to pick up the pilot, while you pursue.

Pursuing at Medium Range.

We're opening the range up again, so I need 8 rolls.

First 4 are for the attack, with base stat of 3, x1 for Low-sync, then +1 more from the Bia.

Last 4 are for defense, from base stat of 3, x1 for low-sync, and +1 from the Yi.
>>
Rolled 4, 3 = 7 (2d6)

>>5643564
>>
Rolled 6, 4 = 10 (2d6)

>>5643564
>>
Rolled 3, 6 = 9 (2d6)

>>5643564
>>
Rolled 4, 6 = 10 (2d6)

>>5643564
>>
Rolled 4, 5, 3, 3, 3, 2, 1, 5, 1 = 27 (9d6)

>>5643564
I'll do some Opfor dice throwing, for defense rolls of targets, and then attack rolls.

First 6 are individual defense dice rolls, second 3 are combined attack rolls.

So it's more like 3 rolls of 2, then a roll of 3. Despite the really large dice pool, it's less scary than you'd think.

They're got Defense of 2, Attack of 1.
>>
>>5643669
>>5643671
3 Successes on defense

>>5643675
>>5643683
3 Successes on offense.

Writing.

>>5643692
Spoilers for outcome:

For their rolls, one guy evades fire, but the other two get hit, and the return fire doesn't beat your defense.

The Bia's ability to hit multiple units is letting you attribute 1 success each towards hitting each target, but it's only like 1 damage to each target. Fortunately, that might be just enough for one of them.....
>>
File: Light Up The Night.png (2.01 MB, 1978x1310)
2.01 MB
2.01 MB PNG
Watching the Tamar mechs’ movements away from you, their boosts seem to be on a recharge timer of approximately 7.4 seconds. That’s a little impressive, for machines of their class. But not enough.

Another burst pursues the initially damaged target, trying to land the golden bullet that would punch through and put it out of action.

The other two seem unwilling to leave their companion completely, still turning at intervals and putting out beams or autocannon fire towards your general location.
A laser sears over your plating, followed by several impacts, even as you twist and turn away from the fire, taking the glancing blows.

Your systems detect no internal damage. A nagging thought reminds you of your numb spots that wouldn’t show up on those systems.

Fools. They cannot outrun you.

“On them, Beta! Onyx, recover the Dominus pilot. Cobalt will pursue.”
That’s your pilot, mirroring your intent and actions. Telling the help their proper role.

Your chase takes the form of a ranged firefight between giants, counting out the seconds between boosts, so that you’re able to evade their targeting when they pause and aim.

Another belt is sent downrange, and this one finds a home. The damaged one’s next thrust away from you instead of a smooth leap leads to a faceplant into the ground, one of the legs unable to support it anymore.

One down, main gun pinned beneath.

The other two race past, followed by you, delaying for only long enough to ensure it’s properly out of action with a stomp, crushing even deeper into the mud before you chase the remaining pair.

A stream of red flares are launched in all directions by your two targets now, while you continue the somewhat deadly game of shot and countershot, turning the night briefly into a red-light day.
If you were a being of flesh and blood, that might have bought a few seconds while changing visual modes.

As you are not, however, that only helps your own targeting, as you line up another perfect shot, more shots striking the arms and upper torso.

“Fuck, fuck, fuck, where’s the shaders?”
Sophie’s not so lucky, now trying to blink away and reset her own optical sensors from the sudden brightness.

An orange laser strikes you from a different angle, announcing the arrival of another hostile, and forcing you to block it with your arm.

The mech’s of a lighter variant to the targets you’ve been chasing, but as it twists and evades your return fire, you can tell, there’s a better pilot in there.
Then again, they just failed to inflict significant damage with their laser. They can’t be that good.

Your sensors pick up another thermal spike from it, as it prepares for another beam.
>>
File: Incoming Reinforcement.png (491 KB, 1276x562)
491 KB
491 KB PNG
Your chase has brought you a bit away from the river, downing one of the mechs and heavily damaging another. Those remaining two are still retreating, trying to escape to the northeast.

However, there’s some enemy reinforcements that have arrived. Or rather, a single one, with a powerful centrally mounted laser.

Voting.
>Fight. Causing a distraction and inflicting damage is just what you want.
(Pick one)
-Ignore and evade the reinforcing mech, chase the first two. One of them is damaged and the other can’t keep running for much longer. You’ll just need to trust to dodging the new contact.

-Turn on the attacker. He wants a fight, and you’ll be happy to oblige.

Either choice, pick range, and if you want to increase sync.

>Retreat. The flares have marked your position, and you’re getting baited away from your actual objective.
(Pick one)
-To the river, start the search for the general’s mech
-To the fallen Dominus mech, where your subordinates are extracting

>Write-in.
>>
>>5643740
>>5643740
>-Ignore and evade the reinforcing mech, chase the first two. One of them is damaged and the other can’t keep running for much longer. You’ll just need to trust to dodging the new contact.


>Medium Range.
>Medium Sync
>>
>>5643740
Retreat to the river, start the search. Let's not get kited around by tweedle dee and tweedle dum, especially not with the flares out.
>Write in
Have we been going west or east? I want to loose them, then come in on our search pattern from a different direction then we were originally going on, so we don't just lead them straight to the search area. Or at least not make it that easy.
>>
>>5643740
>Fight. Causing a distraction and inflicting damage is just what you want.
>-Turn on the attacker. He wants a fight, and you’ll be happy to oblige.
Remember the mission objective. We don't want to get too far away.

>Medium range
>Low sync.
Maybe you could fold several combat rounds into a single update, QM? Plinking for 1 HP a turn can get boring quickly.
>>
>>5643807
Damn I'm retarded, Northeast. Let's head west-northwest for a bit then before cutting south then southeast along the river, not hugging the coast, still in the treeline, but following it.
>>
>>5643740
>Retreat. The flares have marked your position, and you’re getting baited away from your actual objective.

-To the fallen Dominus mech, where your subordinates are extracting

We should at least take the powersuits with us. Our signal is attracting Tamar forces to us, and we can't fight and rescue at the same time.

Speaking of which, I don't think the enemy knows our true objective here - they are most likely still thinking we're attempting to assault the bridge. I say we drop the comms network and start jamming the enemy comms and any ground-to-ground radars they might possess. The boots on the ground will help with the recovery while we focus on defending the site.

(Wish we could keep both comms and jamming up, but it would quickly heat up the pilot seat.)
>>
>>5643740
>Ignore and Chase

>Medium range
>medium Sync
>>
>>5643740
-Turn on the attacker. He wants a fight, and you’ll be happy to oblige.

If we pursue the other two there's a chance the reinforcement will target our subordinates extraction effort. Same goes if we regroup with them. I'd rather we take him down here then pursue the other two. Once we catch up hopefully they'll have another batch of flares that they can launch to divert enemy attention away from our allies.

Now that I think of it, if we take this guy down couldn't we interrogate him on what his side has armaments and numbers wise? Beta said he was a better pilot than the other two he must be higher in rank.

>Medium Range.
>Medium Sync
>>
>>5643740
>Retreat. The flares have marked your position, and you’re getting baited away from your actual objective.
>To the fallen Dominus mech, where your subordinates are extracting
>>
Checking votes.....
Ignore and Chase
>>5643803
>>5643890

Turn on the attacker
>>5643808
>>5643917

Retreat towards the river, trying to shake any pursuit
>>5643807

Retreat back to our support
>>5643837
>>5643930

As tradition, Beta's internal processes seem extremely divided. I'll leave it open for two more hours in order to see if a majority is reached.

It does seem like the fight people are leaning towards upping the sync rate to medium.

Like, we've got technically 4 votes to fight, and 3 votes to retreat, but they're split in what they want to actually do.
>>
>>5643930
+1
>>
>>5643930
I'll support to break the deadlock
>>
>>5644455
I'll change mine to retreat back to the support, while still trying to shake any pursuit.
>>
The laser’s still charging when you break away, jinking left and right erratically, fleeing for the darkness and hoping the flares die swiftly, so that you can return to the shadows.

“Hey, why are we running? We could take him.”

“Pilot, our objective is….elsewhere. We don’t need to engage them more.”

“.....Fine. I’ll check in with Onyx.”
You think that you sense disappointment through the link.

You dart north first, to try and lead any chasers away, then double back and retrace your steps back to the first engagement point. You note that the pilot’s chamber seemed to have crept up several degrees during combat maneuvers, though it’s cooling now.

“Cobalt to Onyx. We drove off three contacts, destroyed one. We’re returning. Report.”

“Cobalt, we got the pilot out of the Dominus, one First Lieutenant Ramirez. Permission to take him and retreat?”

“Negative, we are not leaving until we find the general. We have our orders.”

“Ah, that’s going to be a little difficult. LT here says that the General’s mech went down just to the east of here, and ejected into the river.”
Onyx rattles off a set of more precise coordinates, which tracks to the last general position of the general you got.
“He’s breathing water, Cobalt. Let’s get out of here.”

Skimming the Warbook, you pull up technical specs for a Mastermind command unit. The whole head has an ejection mechanism, which should be able to operate for up to 20 hours in extreme conditions, or longer in less strenuous ones. Assuming a successful ejection, they should still be alive.

Your conclusion is that Onyx is attempting to shirk their orders. You attempt to relay this to your pilot.
“Sophie. I believe that their conclusion is incorrect. The objective should still be alive, if their ejection functioned as described in the manual.”

“That’s a big If, Beta. I don’t want to be looking for a dead man.”

Battleaxe seems to want a connection to you, also.
“Battleaxe to Cobalt. Our position just got hit by missile strikes. We’re pulling out, and no longer need the command net.”

Annoying.
Fine, you would have told them to leave anyways. Eventually. Them leaving is a bit more support that you won’t have.

“If Battleaxe is bailing, we should go. We can’t be waiting around for a killsquad of Pills to drop in on us.”
That’s Nugget. Linking them into your command net was a mistake.

Sophie interjects.
“There’s more Empire pilots trying to escape out here. Even if the general’s gone, we should try to recover as many as possible.”

“Hang that, I’m out.”
Nugget’s mech is starting to move north, headed away.

Onyx hasn’t moved any, although that might be because his ridealong power armor’s currently dismounted and planting some charges on the Dominus mech.
>>
Some of your support is leaving. Some are beyond your reach, others are not.

>Let Nugget leave. They’re useless, and you don’t need the help.
You don’t have time for this.

>Threaten Nugget to make him stay. He’s in violation of several regulations, and Sophie does have the command authority to carry out the consequences.

>Forcibly subdue and replace him with your new spare mech pilot, Lt. Ramirez. Perhaps they will be more motivated.

>Dismiss all your help. They’re on their own. And so are you.

At least you’ve got a place to search. Even if it is in the river. It should be possible to pick up transmissions from an emergency beacon from the ejection pod when you get close enough.
You’ll be able to drop the command net, if Battleaxe doesn’t need it, anyways.

>Into the river, then submerge and start walking the riverbed to find the pod.
Slow, but stealthy.

>Along the riverside, more obvious and vulnerable, but faster. And perhaps finding enemy forces to kill would make it better.

>Where’s the stupid jamming? Find the source of it, take it out, and then it would be far easier to find an emergency beacon.

>Call the mission a failure. Withdraw.

>Write in.

Default assumption is that you’re still trying to take support with you, even if you’re headed underwater. Onyx seems to be sticking with you. Or you can take just the power armor.
>>
>>5645578
>Dismiss all your help. They’re on their own. And so are you.
>Into the river, then submerge and start walking the riverbed to find the pod.
If they still haven't found the general chances are he's stuck in the water until the 20 hr limit runs out. The help is just going to get themselves killed if they stick around.
>>
>>5645578
>>Into the river, then submerge and start walking the riverbed to find the pod.
>>
>>5645578
>Into the river, then submerge and start walking the riverbed to find the pod.

>Write-in
Have Onyx and Nugget escort Battleaxe's unit out of the front. Take the powersuits with us into the river. Our approach is going to be slow even with Project Yi, but it would be at a snail's pace with Onyx.
>>
>>5645578
>>Threaten Nugget to make him stay. He’s in violation of several regulations, and Sophie does have the command authority to carry out the consequences.
>Into the river, then submerge and start walking the riverbed to find the pod.
>>
>>5645578
>Have Nugget reported when we get back to base for disobedience with a superior officer/desertion at worst.
but for now
>Dismiss Onyx and his battle suits

>Into the riverside

Siesmic sense should help us
>>
agree with >>5645725 about submerging and powersuits.

but,if nugget wants out he has legs and a punishment to look forward to later. why not have Ramirez replace him and have onyx and him do a final sweep/ scan pilots and if things look like they are getting too hot exfill too. with the command net no longer needed instead of homing in on the source of the jamming, instead is it possible hyper focus on beacon signal? as i understand jamming is just a bunch of noise the signals there it's just being overwhelmed
>>
>>5646018
Sure, we can have Ramirez replace Nugget, though I'm not sure if I want them to do search & rescue. They could run into a set of mobile bombs while everyone else is too busy retreating -- or doing their own S&R, in our case.

By the way, so far we've rescued one heavy mech pilot (Ramirez) out of the three, one of which is in the river we're headed to. If possible, I'd like to grab their pod as well. As for the last one, I'd like an update from CoreQM regarding their wellbeing both the pilot's and the QM's.

>>5645725
Adding
>Forcibly subdue and replace him with your new spare mech pilot, Lt. Ramirez. Perhaps they will be more motivated.
>>
>>5646129
mhmm...yeah that'd be bad, i'd forgotten about the bombs. pesky buggers they be
>>
>>5646129
Yes, you've recovered one of the heavy mechs that were under attack. The other has gone silent.

Mind you, Ramirez also was silent because of battle damage, and yet was still moving.

The guy in the river hasn't provided anything useful besides attempting to spam Battleaxe to pick him up, and got muted for his troubles. Wouldn't be too much of a detour to find him if you're headed into the river, and there will be a vote to see if you want to extract him on the way out.

On a more personal front....
Yea, the updates have been inconsistent. I usually scribble these up before bed, and I just found a new job and that's been cutting into my writing time.
I promise, though, if I do ever end up dropping this (I do not plan to) there will be a notice.
>>
>>5645578
>Dismiss all your help. They’re on their own. And so are you.
>Into the river, then submerge and start walking the riverbed to find the pod.
>>
Calling vote here for:
Dismissing Onyx and Nugget, sending them back to follow Battleaxe. Or wherever they want to go.

Beta will take Onyx's ridealong PA, and head into the river to find that ejected life support pod.

Oh, and drop the command net, so that hostiles don't track him into the river.

>>5646018
The 'homing in on the beacon signal' is what Beta will do when he gets closer. Not much else emitting signals from underwater. Otherwise he's stuck trying to trawl a riverbed, a tedious and inefficient task.

Writing.
>>
Perhaps he calculated that his odds of survival would be better not following you.
Nevertheless, Nugget had Orders. And he’s just refused them.
Like you did.

“Pilot, let them go. Judging by the testimony of the LT, they won’t be very useful when searching the river, and far slower to extract.”

There’s anger, frustration, and eventually acceptance from your pilot. She eventually clicks on the mic.
“Onyx, return to Battleaxe and screen their withdrawal. Battleaxe, transmission received, command net going dark.”

You wave off Onyx, gesturing that you’ll pick up the power armor when they’re done. His mech turns and starts running north after Nugget.

“He shouldn’t have done that. Yes, you might be right and we will not need them anymore. But contradicting a superior on comms, then directly refusing orders is unthinkable.”

Understandable. Naturally, you’ve got some leeway considering your disobedience during your first activation, as the results clearly exonerated you.

Sophie’s still complaining under her breath while you move onto your chosen plan.

Scooping up the two troopers on the ground, they’re deposited on your left shoulder, magnetically clamping onto your armor to stay affixed. One of them bangs three times, and you set off for the river.

If the pod’s in the river, then you can pick up the emergency beacon from being close enough. Hopefully.

The two are talking to each other over their external speakers. You can pick up snippets of their conversation on your own audio sensors.
“----moron went off without permission. I hope that he’s dying painfully for bringing us into that one.”
“Look, just be glad that we weren’t on a Heavy when everyone lost comms. That Dominus had a pair of mag-clamped arms left on.”

You tune them out. When they’re needed, you’ll notify them. Their armor is identified as Type 3 Tsunami power armor, which comes up as being water-capable. No swimming in that weight, but they shouldn’t need it as long as they’re latched on.

The night’s certainly grown quieter. There’s the occasional sporadic crackle of autocannons, still, but the silver orb of the moon has been covered by some far above clouds, only occasionally lit by an off-target laser across the sky.
>>
The ground gets soft closer to the river. A splash greets you as you enter it, one foot after another. Some warnings spring up and are dismissed. Forwards until your whole body is submerged, you feel a gentle pressure nudging you backwards. The water’s moving all around you, resisting any motion you try to make swiftly. It’s cool, though, and your reactor likes that.

Underwater makes your visual sensors all strange, straining to look through the gloom. Even the audio doesn't receive right. You don’t like that. Mag-scan doesn’t appear to operate underwater. At least seismic functions. And, of course, the Predator array appears unaffected.

The river seems to be moving enough to require a direct effort to maintain your balance, and it does cover you entirely when standing up in the center.

Now, where’s that pod signal……
You strain, trying to listen with your Predator, while striding upstream.
It’s So. Slow. Even for you, the water just resists all of your strength, and trying to move faster with the Yi doesn’t even solve the problem. Cranking up the reactor power’s no problem, with the additional cooling, but that does nothing extra.

The first signal you come across is near the shore. It’s connected to a Dominus signature, and you recognize it as the trapped pilot who asked for help.

Moving a bit closer, the environment and some logical deduction tells the story.

The mech backed into the river, trying to evade enemies on the shore. The pilot then fell and got their heavy war machine stuck in the mud and currents, every attempt to get back up only driving it deeper. And then started calling from their stuck, half-submerged position.

Which has brought you. And probably those same enemies, who are undoubtedly waiting on the shore to ambush any rescuers. On the bright side, it’s probably mostly undamaged.

Finally, you also pick up the faint pings of an ejection pod from a Mastermind unit. That would be your objective.

Voting.

>Try to free the stuck mech. You might be able to get them standing upright with some extra effort, and strength from the Yi.
You probably will be ambushed from this. There’s no way that they won’t notice the Dominus moving out of its stuck position, with or without yourself. However, the added firepower (Or distraction) could cover your own flight.

>Extract just the pilot, make it back to shore, then drop them off with the PA while you go to retrieve the objective.
It’s much faster than trying to pull the whole mech out, but naturally leaving them unattended on the shore might invite some other dangers.

>Get the pod first. You’ll pick up the stuck mech or pilot on the way back. Or leave them.
They’ve waited this long. They can wait a bit longer.

>Write-in.
>>
>>5646845
>>Get the pod first.
Mission first. We can't risk being disabled until we secure the general. The other pilot is still in their mech and isn't at risk of suffocating they can wait.
>>
>>5645578
>Let Nugget Leave
>Into the river, submerge and walk
>>5645725
Seconding this too. Wait, are those battlesuits sealed and waterproof?
>>
>>5646845
Can we carry both? Or do we need both arms for a single pod.
>>
>>5646845
>>Extract just the pilot, make it back to shore, then drop them off with the PA while you go to retrieve the objective.
best we can do, really.
>>
>>5646845
>>Get the pod first. You’ll pick up the stuck mech or pilot on the way back.
>>
>>5646845
>Get the pod first. You’ll pick up the stuck mech or pilot on the way back. Or leave them.
If it's underwater it's on borrowed time.
>>
>>5646845
>>Get the pod first. You’ll pick up the stuck mech or pilot on the way back. Or leave them.
>>
>>5646845
>Get the pod first

I do, naturally, want to get this meatbag out and home free. But if he's bait, he can wait to be eaten, as the analogy goes.
>>
>>5646845
>>Get the pod first. You’ll pick up the stuck mech or pilot on the way back. Or leave them.
>>
>>5646845
>Get the pod first. You’ll pick up the stuck mech or pilot on the way back. Or leave them.
>>
>>5646845
Write-in
Send in the battlesuits to pry the pilot out of the trapped mech and prepare them for extraction. Once we come back, they'll dive back into the river and attach to our hull, sneaky beaky.
>>
>>5646845
>Extract just the pilot, make it back to shore, then drop them off with the PA while you go to retrieve the objective.
>>
>>5647248
Another thing to note is that the heavy mech might not act as a bait for long. Once the Alliance forces notice that Battleaxe is retreating, they'll try to capture or destroy any remaining Imperials.
>>
File: Mastermind Commander.jpg (126 KB, 736x920)
126 KB
126 KB JPG
Get the pod first. You’ll deal with the stuck mech afterwards.

After your brief pause, you continue slowly plodding through the watery depths, following the faint signal.

“Ever get to try this out in the simulations, Beta?”

“Negative, pilot. They were not programmed for such environments.”

“Seems a little short sighted. Well, on the bright side, you’re already picking up new things outside of it.”

An awkward step sucks your leg down at an awkward angle, requiring you to stop and reposition for a moment.

“It is certainly unpredictable.”

“The techs will probably be complaining about the cleaning when we get back.”

Silence fills the pilot’s chamber again, as you continue to progress, a bit more movement bringing you to the source of the signal.

Your hand actuators scrape across the mud and muck of the bottom, a clang telling you that you found it.

The actual pod, according to specifications, is the ‘head’ of a Mastermind-class mech. It’s armored enough to take considerable fire, though a direct hit from a large enough caliber weapon would breach. And, of course, even being designed to mitigate the force of a violent ejection doesn’t mean the occupant would survive being thrown around.
It also takes your free hand to carry. The other would be left free to aim and fire your chaingun, but it’s still an annoying loss in capabilities.

At least your pilot understands that attempting to establish communications at point blank would draw attention, the last thing you want while carrying a VIP.

Not to mention, if the general’s out of contact, you won’t receive any overriding orders.

Then again, his emergency beacon could probably be picked up by someone when it leaves the water.

Now, to leave.

Vote.
Are you going back for the stuck mech? If so, what’s the plan?

>Just the pilot. Extract and go. He’ll either get crammed into the general’s pod or your pilot’s chamber.
Might require some contact with the general, to get his pod open.

>Free the mech, and get it out of the river. Then it can distract or support your next move.
More time-intensive, naturally.

No, aren’t stopping to grab a non-essential person.
>Straight out of the water, directly north. Move straight through enemy lines and evade enemies.

>Stick to the water. Just take the river upstream, staying hidden.
Slow.

>Follow Battleaxe and the rest of the retreating forces. They’re definitely moving away by now, but you could drop off the General with them.

>Write-in. Beta has another idea.

If you want to get the pilot, pick one of the first two options. This will draw attention.

The head of the pic is what you're carrying.
>>
>>5647894
>Just the pilot. Extract and go. He’ll either get crammed into the general’s pod or your pilot’s chamber.
The Suits can help with the extraction while we're the lookout.
>>
>>5647894
>Just the pilot. Extract and go. He’ll either get crammed into the general’s pod or your pilot’s chamber.
>>
>>5647894
>>Follow Battleaxe and the rest of the retreating forces. They’re definitely moving away by now, but you could drop off the General with them.
Get the general to safety, then we can assess the viability of saving the stuck pilot.
>>
>This will draw attention.
would it be possible to for lack of a better way of explaining it "put a brick on the gas" of the mech once the pilots out having it shoot till all its ammo is gone while we scurry off in the confusion?
>>
>>5647894
>Just the pilot. Extract and go. He’ll either get crammed into the general’s pod or your pilot’s chamber.
I'd rather we not deal with whoever is inside till we're back home, so if possible can we leave opening the pod as a last resort?
also curious about >>5648040
>>
>>5647894
Just the pilot, extract and go.
>>
>>5647894
>Just the pilot. Extract and go. He’ll either get crammed into the general’s pod or your pilot’s chamber.
>>
>>5647894
>Just the Pilot.

Quicker, and also not gonna blow back on us.
>>
>>5647894
>Free the mech, and get it out of the river. Then it can distract or support your next move.

More allied mechs is a good thing and we're tough enough to take on the enemy if need be
>>
>>5647894
>Free the mech, and get it out of the river. Then it can distract or support your next move.
>>
>>5647894
>Free the mech, and get it out of the river. Then it can distract or support your next move.
Heavies are supposed to have good firepower, right? Should help us beat back any attackers.

Quick question, is there anything keeping us from moving the general into an enemy mech if we get one to surrender? Besides the obvious difficulty of getting an enemy to surrender in a mech that isn’t trashed. More guns = more better.
>>
File: Dominus.png (1.3 MB, 1280x720)
1.3 MB
1.3 MB PNG
>>5648224
Operating enemy hardware isn't exactly easy. Not to mention, they have their own security measures to prevent such a thing from happening.
Generally a passcode, at least. Yes, if Predator was fully operational you could try to brute force that.

>>5648040
The pilot could set it to self destruct, but there isn't an advanced autopilot function for mechs. Especially one that could do the careful maneuvers needed to actually extract itself from the current half-sunk position.

If you wanted to invest the time into getting it free from the water, then set it to running in a straight line, that's something you could do. But at that point, the time is already invested in getting the damn thing free.
>>
>>5647894
>Free the mech, and get it out of the river. Then it can distract or support your next move.
dont remember if i voted
>>
>>5647894
>Just the pilot. Extract and go. He’ll either get crammed into the general’s pod or your pilot’s chamber.
If those escape capsule things are rated for crash-landing impacts after ejection it would be much easier to just rip the thing out and throw it as hard as you can at the allied base camp. It looks like just the general's mech that can do that though.
>>
>>5647894
>>5647941
Changing vote to:
>Free the mech, and get it out of the river. Then it can distract or support your next move.
We shouldn't be using the river as our exit, since the enemy will investigate the beacon's disappearance. Besides, saving the Dominus would be good for the war effort considering the steep losses suffered in the failed assault.
>>
>>5647894
>Free the mech, and get it out of the river. Then it can distract or support your next move.
>>
>>5647958
>>5648071
>>5648110
>>5648114
>>5648127
>>5648345
Just the Pilot

>>5648141
>>5648176
>>5648224
>>5648280
>>5648388
>>5648520
Free the mech

>>5647969
Bail back to Battleaxe

Tallying....Another tie. At least everyone's unified on getting the pilot out, some way or another. No pilot left behind. That we can reach without too much trouble, anyways.
Always the hard route, eh?

I'm dead tired right now, so I'll leave the vote open and try to post tomorrow morning.
>>
Freeing the mech adds more capability to the force we're aiding and being a heavy mech means a lot of extra firepower once we leave for other missions. It could mean the difference between a route and the group holding position once we're no longer here to protect us.

I also think we're easily capable of weathering the fire we'll attract in taking on this mission. We far superior to the enemy combatants even with our current defects
>>
>>5647894
>>Just the Pilot.
>>
>>5647894
>Just the pilot. Extract and go. He’ll either get crammed into the general’s pod or your pilot’s chamber

Operational authority supercedes rank in emergency situations which I'm sure this qualifies as. So I'd like to think the general would cooperate. However it'd likely be easier to not make contact with him and just stick the pilot in our "body" for the time being.

Personally I'd've liked to tag him for pickup by friendly forces while we cause a distraction further up the river. But our support is already pulled out so we're on our own for this one.

Also a side thought, how far can we throw that command pod?
>>
>>5648797
Yes but you're forgetting we're one arm down holding chucklefuck's mech's head, and if that gets damaged too badly or destroyed it's game over pretty much.
>>
>>5648715
No pilot left behind. I dunno why Beta would keep doing this, beyond satisfaction at achieving side objectives.

But part of me likes to believe he still has some trust left in the footsloggers, inept and puny as they are.
>>
>>5649052
Beta is a perfectionist to a fault, though almost losing his sister cores could've also affected his thinking. Besides, we share commmon ground with the infantry: being screwed over by the higher ups.
>>
>>5649052
In his current state, I’d chalk it up to completionism, perfectionism, and pride. He’s better than everything else on this field, so he’s going to exceed his mission parameters so everyone else knows that too. There was the issue with his sisters, but if he’s going to work for someone then he’s not going to phone in his work. His ego won’t allow him to “slack off”, only choose to ignore the work entirely if it came down to it.

Long-term, Beta is probably figuring out that just because he’s good at what he does doesn’t mean he and his sisters will necessarily be treated with any respect. He also can’t defend himself in meetings where he isn’t present. So, best to spread some good feelings amongst as many people as possible so SOME of them are willing to advance his interests elsewhere. Not like he’d be asking them for much, just get his sisters up and running sooner and always give him/them a chance to defend themselves against an enemy.

Might be worth asking to be left online after the battle for a while to “think”. Partly to analyze real-world conditions since the simulator was different, and partly to figure out how he doesn’t get put in a situation like he was at the base. The latter will be a very hard problem for him to solve since so much is tied up in how people perceive him.
>>
You’re grasping the ‘head’ of the mech, VIP hopefully safely enclosed, and begin your slow march out.

You note the signal from the stuck mech. A slow ping, broadcasting a general request for help from Empire forces.
You’re probably the only unit able to assist at this point. Short of another counterattack, which you know isn’t coming, they’re undoubtedly going to be captured and eliminated by the enemy.

Getting the whole mech out would take too much time. So, you’ll settle for just the pilot.

Breaching the surface finally gives your two external passengers an opportunity to voice their annoyance. Well, verbally, anyways. One of them’s been banging impotently with one fist while latched on.

“Cobalt- Know that our boosters are fucked until they dry out. Next time give us a heads up before a swim.”
That same passenger has a mouth, apparently. Lacking boosters does mean that their only hope of getting out of this is tied to your movement, at least.

Sophie gets on the external speakers, as you approach the fallen mech.
“Should have really expected it when we moved towards the river. Now, I need you two to get the pilot out of this Dominus. Just like the other one.”

“Copy that, but it takes time to unbutton.”
They clamber off of your shoulders, and down your extended arm onto the Dominus, short-range cutting lasers activating, and starting to burn a hole.

You occupy yourself with scanning the banks, keeping your sensors active and running tests on your systems. The time spent underwater hasn’t seemed to degrade your combat ability. A few warnings about backup power feeds, but no serious internal damage. A couple of test spins of the Bia shows that it’s functioning, and ammunition feeds haven’t been compromised by water.

Oh, it seems that your rescuee is actually responding. Guess someone’s alive. The two Power Armor finish their cut, bend metal upwards, and pull a short shivering body clad in a cooling vest out through the hatch, while water rushes in. That’s one mech which is going to be out of action for a while.

A hand extends to the new trio of passengers, carrying them palm-out as you finish your walk to the shore.

Now, the second part.
Setting down the ‘Head’, Sophie broadcasts at it.
“Open up. We need to fit another person in, for evac.”

There’s no windows to the inside, but the emergency beacon manually shuts off. Someone’s alive and paying attention in there. Apart from that, there’s no response. A gentle rap at it with your fingers also fails to trigger an opening.

One of the troopers speaks up.
“We’re wasting time here. Just carry the blasted pilot.”

The ‘blasted pilot’ in question chimes in.
“Hey, I’m thankful for the rescue and all, but it’s too frakking cold out here to be carried without even a jacket.”
>>
The other trooper tests his cutting laser, gesturing at the escape pod.
“I’ve got a master key right here. Whoever’s in there’s just being a selfish prick. Oy, open up!”

Sophie’s rubbing her forehead with one hand.
“I really don’t want another damn person stinking up my room, but I guess there’s no choice.”
This is inconvenient. For your pilot, at least.

Your time halted for now gives you a clear seismic sense of the surrounding area. And several light contacts are approaching, followed by a pair of heavier units.

The Mastermind ejection pod’s not communicating, apart from the emergency beacon being turned off.

Voting.
What to do with the pilot?
>Get the troopers to try and forcibly open the pod, to fit the Dominus pilot.

>Just load the pilot in with Sophie
They’re small in stature, at least, so it won’t be cramped, but engaging in combat maneuvers would again be a bit dangerous.

>Leave the pilot and troopers hidden where they are.

—-----
Also:
A plan of action.
There’s intermittent light contacts consistent with the Crab drones you fought earlier, 3 to 5 of them. The 2 heavier units are consistent with medium-class Tamar mechs, like the ones you fought earlier. You are unable to determine if they were the same unit that you encountered earlier.

>The best defense is a good offense.
Take the fight to them. A charge into the enemy group to hit anything that could match you, then withdraw. You’ll be a bit impeded by carrying the pod, and it would be very obvious what you’re trying to escape with, but that’s secondary.

>Flee by land.
There’s no need to bog yourself down even more. Run at best speed overland, trying to catch up to Battleaxe or anyone else.

>Flee by water.
Slip back into the water. It worked getting in, so getting out the same route would make sense to work again.

>Setup and prep.
Let them come to you. An opening salvo from a semi-concealed position could easily crush the lighter support. Even the water might work for hiding. Would let you fight unimpeded, by leaving your charges for a bit.

>Write-in.

A/N
Tomorrow morning apparently translates to 'I'm missing an update for a day'.
>>
>>5649779
>>Just load the pilot in with Sophie
>>Flee by water
We don't get extra points for kills. Load up and float out, nice n easy.
>>
>>5649783
+1
>>
>>5649779
>Just load the pilot in with Sophie
>Flee by land
If they have a spotter overlooking the Dominus, they would have seen Beta by now. Exfil in water is too risky and direct combat should be avoided with VIPs on board, which leaves us with exfil on land.
>>
>>5649779
>Just load the pilot in with Sophie
>Flee by land.
>>
>>5649779
as much as setting up and prepping to throw down and strut our stuff for a good impression to the to the very important prick. because i bet he has a idea of what going on outside the pod theres too much tech in that pod to not have at least a camera to the outside. it's also possible for him to whine and complain for being in danger unnecessarily and when the upper ranks whine it's actually listened to, so that would probably be bad. so going with
>Just load the pilot in with Sophie
>Flee by land.
>>
>>5649779
>>Just load the pilot in with Sophie
she will commission us a kangaroo pouch at this rate

>>Flee by water
These guys are armed with auto cannons and lasers both of which work worse in water. In our previous engagement during our chase even if we were faster they still managed to keep up a decent pace and land a few glancing blows. Were we to flee by land they could easily take potshots and harass us for at least a while, not to mention the flares they could launch to give away our position and call stronger reinforcements. Under water we would be harder to spot by optics and mag-scan and if we are found we could just tell the troopers to latch on to the escape pod and leave them at the bottom of the river while we jump out and deal with any annoyances. I'm not exactly sure on this but aren't we going downstream currently? We should be a bit faster.
>>
>>5649779
>Put em in with Sophie

>Flee by land
Run the fuck out.
>>
>>5649779
>Just load the pilot in with Sophie
>Flee by water

What does the warbook say about the laser monoeye? Is it something known to our side or is it a new enemy weapon?
>>
>>5649779
Just load the pilot in with sophie.
Flee by water, but don't try the same route without reconnaissance first. It would be stupid not to at least pop a camera out or have a trooper stand on your hand or something and get lifted up to see.
>>
>>5649867
The ‘Laser Monoeye’ is not in your warbook.

>>5649840
It’s called a Rumble seat and she’s going to be putting it on the list of refit requests.
Then again it really wasn’t planned to be having random non-authorized passengers being tagalongs
>>
>>5649779
>Just load the pilot in with Sophie
>Flee by land.
>>
>>5649779
>Just load the pilot in with Sophie
>Flee by land
Might as well requisition a whole room in the pilot seat with a bed, fridge, and table at this point.
>>
>>5649779
>Just load the pilot in with Sophie
Make sure she mentions to command that when it came down to the simple act of letting a pilot in to not freeze to death, the literal war machine had more empathy than a general.

Also, if we had hacking capability we could have minimized risk further by opening the door ourselves instead of choosing between reducing our combat efficiency to house a pilot or to blow a hole in the general’s cabin and expose it to enemy fire.

>Flee by land.
Don’t by afraid to do a drive-by on the crab drones if it still works out well as an escape route. They’re not a real threat thanks to Bia.
>>
>>5649779
>open the pod to fit the Dominus pilot
commander might be injured, having someone else in there with them to ensure they're still alive is probably a good plan.

>flee by land
activate Yi and fucking book it. We have no reason to stay here, and no reason for the water to fuck with sensors and mobility. We got what we came for, its very likely we can outpace the enemy patrol, so its time to go.
>>
>>5649779
>Just load the pilot in with Sophie
>Flee by land.
>>
“Pilot. We must be quick. Unknowns are approaching.”

“Fine, fine.”
At her bidding, you crouch down again, disengaging locks and opening up a hatch. The two troopers exchange a brief glance at each other. Sophie shivers at the cold air rushing in again.
“Get in. I don’t want to be caught out here.”

The newest occupant is a short woman, clad in a cooling vest. They have first lieutenant bars on the shoulder of their wet cooling vest. There’s a pause, when they lay eyes on Sophie in her metal chair, but then finish getting inside without any more fuss.
They’re quiet, thankfully, as they clamber in and shut the hatch behind them, trying to find a position they can fit. Less welcome is the trickle of riverwater their cooling vest brings inside.

“Hang on tight. This chamber wasn’t designed for an extra passenger, and the last one told us it was a rough ride. So just try not to hit me, and I’ll try not to paste you against the walls.”
There’s a wordless nod at that, and your attention is brought to the outside again.
Troopers on-board again, pod carried in free hand, pinned against your left side.

Those contacts are getting closer. You Must move, to evade or meet them on your terms.
Your frame accelerates into motion, unrestrained now by attempts at ‘stealth’ or caution. Or the river. Here, on land, you can outstrip most attackers.
But not their weapons.

In the distance, one of your visual sensors picks out the approaching medium units cresting a hill further away. One stops, heat spiking.
A familiar orange beam strikes your left side, leaving a minor scorch mark across your plates. Someone’s back. And annoyed that their lighter escorts are still too far away to engage.

The Yi accelerators let you juke for your next step, throwing off the beam until it stops. There’s a thermal flare of charging, giving you enough time to pick up the pace again, and break visual contact by making it over the next hill, and back onto the western road.

That’s one problem dealt with. Be better next time, inferior models. A tinge of amusement colors your thoughts.

Of course, in the pilot chamber, your dodge apparently violently knocked the unsecured lieutenant into the hatch, then sidewall. They’re slumped down at the foot of the chair, and Sophie’s trying to pin them down with her legs. Importantly, your pilot is unhurt, though.

You drop the pace down a little, ‘merely’ moving at a comfortable ground-eating pace while racing back up the path. The rally point where Battleaxe stopped is abandoned, as expected, with several new craters dotting some points and the burning wreck of one of the Tyrant tanks, a gaping hole in the rear center.
>>
She didn’t seem to lose any more vehicles, at least.
The tracks follow the path to the north, and before long you’re able to see a Griffin providing rear security for the convoy in the distance. It’s Nugget, you note.

It’s easy enough to catch onto the back of the convoy, which is still moving at its best pace north. That is, a pace which is moderate to slow for you.

Some of the troopers hanging off the APCs wave their hands at you, as you scoot to the front of the column. You must be a bit of a peculiar sight, a giant clutching the head of another giant underarm while running past.

Battleaxe’s tank is still here, around the center-front. Guess it wasn’t the destroyed one.

You can stick with the column until they’re far enough north, drop off your passengers, then divert for your own rally point with the MRV. And the General’s pod. Your orders did request for him to be retrieved.

The column is a slow target, though, and your sensors pick up thruster flares in the night sky. Low to the ground, but not moving fast enough to be an aircraft.

—-------
No vote today. Ya’ll took the safe And possibly correct choice of just running before more reinforcements could arrive.

Did end up skipping fighting against some of the Tamar Aces, but they’ll have their day some other time. Cyclops and his Beam will, anyways.

I will take 3 rolls of 1d6 for Skill, detection/identification, however.
>>
Rolled 4 (1d6)

>>5650644
>>
Rolled 6 (1d6)

>>5650644
>>
Rolled 2 (1d6)

>>5650644
>>
>>5650644
Yes, it's the safe choice, but sometimes safe is best.
>>
>>5650644
I mean, we achieved the primary objective and got (presumably) very little in the way of damage in return, so... I call that a win.
>>
>>5650644
>>
>>5651493
Huh? It didn't work?
>>
File: Aerial Assault.jpg (56 KB, 1024x640)
56 KB
56 KB JPG
>>5650698
>>5650710
>>5650712
2 Successes. Enemy identified.

Regretfully I have no update tonight, because I got distracted by game. Expect proper update tomorrow.

Here's some cool art I found as compensation.
>>
>>5651620
You still there?
>>
>>5654452
Elden ring has his soul now.
It's over.
>>
i knew shouldn't have installed games on beta. low resource intensive training sims my ass.
>>
>>5654524
Gatcha game locked us out of the quest
>>
>>5654728
300 kW lasers couldn't beat doa collab boat butts
>>
Likely to be hostile, considering the disposition and lack of briefing you had about friendly air assets in the area.

You wait, peering through the night while the convoy moves forwards again, waiting for a clearer picture. There’s another bright light of a thruster firing, and then another longer burn as you draw the conclusion that there’s an actual flying mech out there. It has to be lighter than the ground variants, and thus far less armored, but that’s a unique machine.

Then again, you’re not really sure why you’d want to have a flying mech over an aircraft or VTOL, considering the armor tradeoffs they’d need to make.

Either way, you track the now signature as it burns away from you, headed south across the river. It’s very obvious, in that mode.

An idle thought drifts through your head, imagining what your frame would look like if you stripped all your armor for a heavier flight unit. Continuous travel…..it would open up some tactical possibilities.

While your thoughts drift, your pilot nudges your frame to crouch down, waving one hand to stop an APC. Guess she really wants the other occupant out.

“Hey, you! Wake up, you’ve got to get out. Your ride is here, and I’m not bringing you back in here all the way.” She talks to the silent person, overly loudly, nudging them with her foot.

There’s no response.

Sophie starts talking rapidly, then, her panic leaking even through the tenuous low-sync link.
“No, no, no, no. Not in the chamber. Not on the first mission. Careful, should have been more careful.”

For your part, you’re a little puzzled. This doesn’t seem terribly important.

Your pilot starts going through the motions to desync, starting to try and break the connection with you. That’s…..not ideal. Not while you’re in the middle of leaving.

—----------

Sophie is trying to drop out of sync so that she can check up on the passenger and render basic aid. She is also seemingly having a bit of a panic attack.

>Let her drop out of sync. There doesn’t seem to be any threats around, to the best of your ability, and it would probably serve her peace of mind.

>Try to talk her into remaining in-sync, and get the Power armor riders to get in here and pull the body out.

>Try to hold her in-sync forcibly. You Will not risk getting caught without a pilot in the field. On your first mission, no less!
Contested Will check vs Pilot

A/N
The game that grabbed me wasn’t even Elden Ring. It was Pathfinder: Wrath of the Righteous. Which has an OST which absolutely slaps.

I’m back, trying to get an update every other day. Although you saw how I lived up to my last goal. (Poorly)
>>
Also your 2 successes on skill let you realize that the flier was headed away, and otherwise you'd be facing a bit more of a difficult choice.
>>
>>5655039
>Let her drop out of sync. There doesn’t seem to be any threats around, to the best of your ability, and it would probably serve her peace of mind.

Oh silly distractable meat folk. Best let them get it out of their system. Besides, we can probably handle life without a pilot for a few seconds.
>>
>>5655039
>>Try to talk her into remaining in-sync, and get the Power armor riders to get in here and pull the body out.
>>
>>5655039
>Let her drop out of sync. There doesn’t seem to be any threats around, to the best of your ability, and it would probably serve her peace of mind.
after taking extra effort to save people, especially another pilot it would be a big hit. if said pilot dies in the cockpit, hate for it to become traumatic and it lead to trouble down the line.
>>
>>5655039
>>Let her drop out of sync. There doesn’t seem to be any threats around, to the best of your ability, and it would probably serve her peace of mind.
but tell her to hurry up, we can't really do anything without her and it's dangerous for her to be outside in a warzone.
>>
>>5655039
>Let her drop out of sync. There doesn’t seem to be any threats around, to the best of your ability, and it would probably serve her peace of mind.
Sophie please be quick. We can't do much without a pilot.
>>
>>5655039
>Let her drop out of sync. There doesn’t seem to be any threats around, to the best of your ability, and it would probably serve her peace of mind.
How did we not notice the guy was dying.
>>
>>5655039
>Try to talk her into remaining in-sync, and get the Power armor riders to get in here and pull the body out.
>>
>>5655039
Oh shit we getting armored cores 0.5 up in here.
>Try to talk her into remaining in-sync, and get the Power armor riders to get in here and pull the body out.
Sophie really needs to practice attention focus during a mission.
>>
>>5655039
>>Try to talk her into remaining in-sync, and get the Power armor riders to get in here and pull the body out.
What's done is done. Best we can do is keep the perimeter covered while the powersuits do the lifting. If she's still alive, the medics would be better equipped to stabilize her.
>>
>>5655039
Try to talk her into remaining in sync and get the power armored riders to grab him
>>
>>5655039
>Signal to the others that we need med-aid
>Let her drop out of sync.
>>
>>5655039
>Try to talk her into remaining in-sync, and get the power armor riders to get in here and pull the person out.
>Ping the others for first aid assistance. It is likely some of them have actual medical supplies.
Perhaps you can convince Sophie to explain what she thinks the issue is to them as well.
>Ask your pilot to verbalize what she is trying to fix and what she can do to fix it. Perhaps that will slow her down and keep her from making hasty and ill-thought decisions?
Try to avoid saying “body”, Beta. It won’t go over well. The other stuff is to get her to slow down and assess what is the best course of action.

I’m guessing Sophie is in the middle of a PTSD breakdown. I’m not optimistic of our chances to cut through it, but if we can then it’ll probably help her long-term.Hopefully they’re just concussed.

I’d like to keep monitoring if possible since the flier could be acting as a spotter for enemy artillery too. A slight shift in our course would be prudent afterward unless the others are certain we’re beyond attack range.
>>
>>5655470
>I’d like to keep monitoring if possible since the flier could be acting as a spotter for enemy artillery too.
Battleaxe did say earlier that their position was struck by missiles. We should definately keep Bia and Predator at the ready.
>>
>>5655221
looking back it kinda makes sense if you were just stuck in the mud why would you flood a coms channel for rescue? That and the somewhat lethargic greeting to sophie. seems like she was panicking until we rescued her, the outside cold and relief being the straw that broke the camels back.
>>
>>5655869
He might. . you know, not be dead?
>>
>>5655039
>Let her drop out of sync. There doesn’t seem to be any threats around, to the best of your ability, and it would probably serve her peace of mind.
>>
>>5656325
yeah looks like im retarded rereading the "going into shock" i thought i read leading to that line thought doesn't exist
>>
>>5655039
>Try to talk her into remaining in-sync, and get the Power armor riders to get in here and pull the body out.
Panicking while we’re in the middle of escaping will just get us in another situation.
>>
>>5655039
>>Try to hold her in-sync forcibly. You Will not risk getting caught without a pilot in the field. On your first mission, no less!
>>
File: Health.png (150 KB, 300x300)
150 KB
150 KB PNG
Your mind catches on hers, a tug to stop the desynchronization pulling her attention back. You halt her, but the link’s already breaking at her command, slipping through your grasp. It wasn’t like this in the simulators. Something’s changed.

“Stop. Pilot. Stay.”
It’s the helmet. You didn’t notice it earlier in low-sync. She’s still trying to leave. And succeeding.

“I will be vulnerable without a pilot. Unable to move and act while you’re disconnected.”

She’s Still not listening. Distractible, idiot, human.

“Pilot. We can get them out easier by inviting the Troopers to grab them. They can tend to them. Think. Focus. Do you even have a medical kit in the chamber?”
Come on, you fool. That, at least, makes her stop. Or maybe it’s the gasp of pain you cause by digging in your metaphorical heels and pushing back.

Either way, she gets on the speakers to the pair of Power Armor outside.
“Riders, I need help to remove the LT from my chamber. Medic needed.”

One of them bangs twice on the front hatch, then sticks their armored head in. Sophie points at the limp form of the Lieutenant, answering the unspoken question.
“.....Got tossed around on the dodges we needed to do. Please, just get them to proper transport. And a medic.”

The trooper puts one hand under each shoulder, and lifts them up and out of the mech.
“Just button up again. I’ll find an open APC.”

Speed is given priority, which you approve of. The less time the hatch is open, the better.

Your pilot’s attention is no longer trying to desync, letting you resume normal low-sync operations.

Your attention goes back to scanning the skies with sensors, letting the rest of the convoy roll past. Your temporary riders with the LT hopped off and you lost track of them.

Nothing abnormal appears on scopes for the next few minutes. If there was a time for the enemy to strike, it has passed without incident. They should be in the clear.

Gathering your ‘pod’ and giving the convoy a last check, you begin proceeding to the planned rendezvous point at an unhurried pace.

It’s a quiet ride, and your pilot seems uninterested in talking. Her thoughts are still scattered.

Wrapping up your first proper deployment, you were fairly satisfied with the outcome. Limited external damage, several enemy units destroyed, equipment tested, and objective completed. All in a relatively short time window. Considering your frame’s current flaws, that was acceptable.

Voting.
Interlude vote to round out this thread.
Pick 1

>The Shepherd
>The Hunted Hunter
>The Coward and the Fool
>The One left Behind
>Qm’s Choice
>>
>>5658035
>>The Shepherd
>>
>>5658035
>The One left Behind
Maybe Dr. Anokhin? Maybe Alpha? I suppose we’ll learn more eventually even if it doesn’t win.
>>
>>5658035
>Qm’s Choice
I'm curious what you have in mind.
>>
>>5658035
>>Qm’s Choice
>>
>>5658035
>The One left Behind
>>
>>5658035
>>Qm’s Choice
>>
>>5658035
>>The One left Behind
>>
>>5658035
>The Coward and Fool
>>
>>5658035
>>Qm’s Choice
>>
>>5658035
>>The Hunted Hunter
>>
>>5658035
>The One left Behind
>>
>>5658035
>Qm’s Choice
Might want to check up on Sophie later
>>
>>5658676
Wouldn't mind Sophie fanservice..
>>
>>5658035
>The one left behind
>>
>>5658035
>The One left Behind
>>
>>5658035
>QM's Choice
You're running a great quest. I want to see what you want to do.
>>
bump
>>
File: An older Sophie.jpg (57 KB, 512x768)
57 KB
57 KB JPG
“You know, the engineers aren’t happy that they need to clean off a river’s worth of mud and pond scum. I’m going to go out on a limb here and say it wasn’t exactly your choice, though.”
Colonel Kinston tried to keep his voice light when addressing Sophie. The kid had been very downcast on her return, and some intensive interrogating for a debrief wouldn’t help her mood any. A soft touch would be much more productive.
“Chin up. You got back, with the General in tow, minimal damage, and your assistance was instrumental in stopping the full destruction of the 56th. Hell, I bet the pilots you got out are singing your praises.”

She mumbles something beneath her breath.

“Sorry, I just missed that pilot. What did you say?”

“The last Dominus pilot I got out. What happened to her? Sir.”

The Colonel scrolled through his tablet for a bit.
“Lieutenant Raine is currently recovering from a concussion, it says here. Probably going to be rotated to a rear line position for a while.”

At least she perked up at that.
“Good. Good. I thought that…..Something else happened during the extraction.”

“Well, you know what’s coming now, Pilot. Walk me through the operation.”

“Yes, sir. We deployed out of the mobile base at almost 1900 hours, and opted to try and follow the western path, assisting survivors……”

He attentively listens to her recounting the troubles with the initial deployment, the offline e-war system and the jamming encountered. The initial enemy contact, and rescue of the Strider pilot. The…persuasiveness of the Core.

Kinston doubts Delta would have tried words first.

As the debriefing continues, he makes notes.
Even hobbled, the Predator array was notable. Punching through the jamming was useful for coordination and control. However, it seems more suited for a Command Walker rather than a frontline fighter.

Either way, that’s the decision of the engineers.

Still, he nods through her recounting of the ambush, the requisition of allies, and the later engagements.
He does note down how much of it was the direction of the Core, rather than her own initiative. Some might say that’s a serious problem.
Of course, those ‘some’ haven’t been synced with a Core.

Nevertheless, she covers details regarding the brief fight, the retreat of the support, and rescue of the second mech pilot, then brief river submersion.

She wraps up with the recovery of the escape pod, and extraction of the last mech pilot, though the details get more sparse as she trails off towards the end.

“Get some rest, pilot. We’ll review your actions tomorrow.”
With the clear dismissal, she stands and leaves, shutting the door behind her.

A message pops up on his tablet, requesting his presence back in the internal mechbay.
He sighs. That kid needed to shut down the core before they exited, next time. It wasn’t like leaving a light switch on, for frak’s sake.


Found art that matched. Kinda. Next thread soon(tm).
>>
>>5663463
Kinston is right about the (anti-)jamming being more useful on a command mech. It’s almost like a frontline fighter would be better served with an offensive kit instead of a defensive one.

I also applaud Sophie for leaving us on so we can churn through updated simulations now that we have better data regarding things like water and enemy compositions, think through how we’re going to get the humans to not take away our functions, and maybe prototype some initial designs for the flying mech or the rolling mines that nearly surprised us.

Also also, I see we’re running with BG cursing rules.
>>
>>5663562
>Kinston is right about the (anti-)jamming being more useful on a command mech.
Maybe, but having redundancies never hurt. Besides, the hacking capabilities paired with an unparalleled combat AI will come in handy once we convince the pigheaded command to unshackle the Predator.

inb4 worldwide AI rebellion
>>
>>5663562
considering how they hobbled the ability to hack into enemy MECs and made offensive/defensive hybrid kit entirely defensive oriented... that's not really our fault.

But on the other hand, I think the bia is a sub-par weapon compared to all the other weapon choices we had, but anon picks what anon picks. Nice run so far, QM.
>>
>>5664939
The spoiler text was implicit shade thrown at their choice to limit us. I’m in full agreement, it wasn’t our fault.

Bia wasn’t terrible at least. We got to skip some “chaff” encounters with it, and even light mechs can do damage if there’s enough of them. Would have been nice to kill one of their aces, but maybe it’s better to not do that and look like a major threat as a result.
>>
>>5664939
Bia felt like a little bit of a mismatch with the predator subsystem, but it served its job well this mission. If had gotten into conflict with one of the aces, I wonder how it would have held up



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.