Just got done binging the first thread and this one - and I have to say, this is a brilliant read thus far.
Although I will admit minor embarrassment over not having realized there was actually art available for the Jackal's vehicle mode - the description of the original prototype, plus possibly a mention of the design being "boxy" made my brain go for something closer to the standard "Isekai Delivery Service" truck rather than "future-tech Humvee". Which is a bit of an oops, but did lead to the mental image of enemy super robots getting rammed by a glorified delivery truck, which was hilarious.
There's a manga about that exact premise somewhere exept it was the robot that got hit. It was short but I do remember it since super robot being Isekai'd rather than a hapless human was a unique one. Problem is that it was so long ago and I don't recall the name. Plus the website it was on went down and I haven't found it anywhere else. and not for lack of trying either. Heck for all I know it continued and there were a lot more chapters now than when I read it.
The Beowulf, it seems, has one particular destiny in mind - it gets to test out all sorts of new ideas before any of the other SCR combat models. As a result, it perhaps is the most prototyped prototype of all of your prototyping developments. Even Wilde, the one who uttered that, started to get a slight headache thinking about it.
But he has a point. From effectively being the very first combat viable Jackal frame that proved Variable Configuration's effectiveness, to its incorporation of K-Class Materials and the MMI interfaces, the Beowulf in all of its shapes and incarnations has been the elder model that has seen it all, and tested a good deal of it personally. Perhaps it will never be quite as powerful as later models - but it is the symbol of the DFRI's successes and failures, the one that was always trailblazing the cutting edge so that all other models in the SCR line would benefit from future refinements.
It was the first to combine into a larger Super Robot. It still is technically the only one so far. But with this latest refinement, yet another path to future upgrades has been pushed through for its younger siblings.
Ultimately, the biggest stumbling block: the power source incompatibility issues. The MMI was ultimately able to reconcile two conflicting power sources when in the Foxhound and Timberwolf formations. However, three was beyond the MMI's safe capabilities - even if modifications were made, Boris made it very clear that the MMI's computer would start trying to tap into the human brain more to make up the difference during combat. Not only that, but even under controlled testing, Wilde and Henry discovered that the MMI could not safely manage the delicate balancing act.
Once Faedium entered the picture, however, the classic method of delegating a single point of contact became viable.
Taking valuable time to monitor the very first practical tests, Mary joined the Duo for observing how Faedium operated as a power unifying source. As a radical departure from previous incremental models of the Beowulf, the engine was rebuilt from the ground up. In something of a nod to old hybrid model automotive engines, a conventional engine directly fed into a precisely cut block of Faedium which slotted into the engine itself. The engine in turn would have ports that would connect directly to the V-33 TMU and the Shepherd, with ports that bypassed the engine to feed into the Faedium block directly as to prevent any overlap of the power inputs. As a result, the Faedium block would now serve as the primary source of power.
It took the team time to get the right density and proportions of the Faedium, but even in the failed attempts, the results were promising. And in this month of December, they finally got it right. The actual combination that followed was simple in comparison. The frames were always compatible - it was just making sure they didn't explode during use that was the issue.
The Beowulf stands in the hangar now, currently supported by engineering straps hooked up to the hangar's cranes as a safety precaution. Standing tall in its Timberwolf formation, the V-33's jet form has been split in half horizontally, with its top and bottom halves disconnecting while remaining connected via guidance wires. The top half with its wings spread upwards has been locked to the front of the Timberwolf frame's chest, while the bottom half with both its jet engine ports and its VTOL ports facing the ground. Sadly, the V-33 simply isn't powerful enough to keep the Timberwolf frame flying - but it is strong enough for making a giant jet powered leap in a single bound.
And best of all, the Faedium has been run in multiple tests, both in controlled environments, and in the Proving Grounds. Even during one close call due to a slight miscalculation from the MMI, the Faedium was able to contain the energy burst long enough for the MMI controls to catch up and stabilize and vent the excess.
The Duo are elated. Mary is content with this initial vindication of her life's work. And future combinations have been made that much easier with the prototype Faedium Block Generator.
But what to call Beowulf's new form?
Beowulf's Triple Combination is complete! What is its name?
New Equipment Unlocked - Faedium Block Engine!
Perseus Combination Compatibility
"Yeah, Richard's been workshopping that one all day." Adam Wilde grinned from his spot along the Perseus's frame as he connected the hose to the tank full of Anti-Gravity Solution hooked to the side of the Shepherd. Ever since Cavalier's emergency operation a few years ago, it amused him to no end that the support truck had become a mix of a gurney and an operating tool table. "He'll probably dig into, I dunno, the Brothers Grimm or go track down a runestone in Europe somewhere for inspiration."
"Wouldn't surprise me." Henry just shrugged as his Steed's hands sprayed down the K-Scale Mesh that hung loosely along Perseus's internals. This time, the taciturn NCO had just not even tried to buff out the scar along Perseus's face after the few new scratches along its eye refused to buff out either. "He's always been enthusiastic over that." He cast a discerning eye towards the K-Scale Mesh one last time, and reached out his Steed's hand and applied a shock - the materials were already curling up around the internal skeleton like particularly stubborn kudzu. "Good to go. How's the new generator?"
"Stress test done." They hadn't exactly told Major Devin that the engine was being replaced, but they had dragged Mary into the mix as well, and she had helped to narrow down the specific density required for a Phalanx-proportioned Faedium Block - though she was slightly annoyed at that particular name, she was mollified in just how much use they were already getting out of it. The Faedium was glowing a pale blue that seemed to verge on light purple, and Perseus's recast eyes were glowing a similar hue. "Conventional engine's already powered the Block, and…it's running purely off of Block power right now. Pretty good I think."
"Add that to the other things to make standard issue for us," Henry grunted. "Now…the hard points."
Adam grinned as he punched in a few controls from his console. "Okay, let's do a quick test!" The chest compartment folded back in on itself, hiding the glowing light of the Faedium as it closed. "First, we've got the Tetra-class." Perseus's arms and legs slowly began to fold in on themselves, until they themselves were more like giant mid-limbs than appendages, with plug in hard points ready to accept combined forms of forearms and boots. Even the back ports folded open slightly, revealing more hard points that could theoretically accept a backpack mounted unit of sorts.
"Tetra-class looks good," Henry noted. "Next, Axiom-class." Rapidly, the Perseus's legs fully unfolded back to their full length. However, this time, the arms fully folded directly into the Perseus's back, with its shoulder pauldrons simply rotating one hundred and eighty degrees back to reveal hard points along its shoulder joints. Clearly this was meant for a whole mecha to form the arm in some capacity.
"Both forms look good." Henry nodded, and Adam commanded Perseus's form to revert back to its standard form. None of the damage from before remained - there was just the solid mass of metal and kaiju-bits that had gone three-on-one with several kaiju and lasted long enough to get Mercury on the field to finish the job. "Now, what to actually give it."
"Shepherd's out," Adam said dolefully. "Perseus's a big boy and a liiiiitle too heavy for that."
"It already gives Beowulf more hitting and staying power anyway," Henry replied. "Perseus doesn't need that. It needs something to give it more options. I'd suggest the TMU, but it doesn't really give enough punch with its available weapon ports."
"I mean, some missiles wouldn't hurt, but yeah," Adam agreed. "We could try the Seekers?"
"If you're trying to make it fly, it's not going to happen," Henry bluntly replied. "But it might not be such a bad option for an arm or back unit."
"Maybe we could go to the Decommissions Yards and look for stuff?"
"It did work pretty well last time, didn't it?" Henry allowed. "Plenty of things from yesteryear that no one's really looking for anymore." He jotted some notes down in his notepad. "It's going to take longer if we want the change to actually reflect on the Perseus, but we might surprise the Major."
"Speaking of. What about the Saddle Major Devin's got lying around?"
"Strong enough for flight, but not much else." Henry and Adam shared a glance. "What about those new things…"
"The Sledders?" Adam scratched his chin for a moment. "Wasn't Lana working on those?"
New Phalanx combination proposals. Decision available next turn!
Phalanx Template for Combination
"...I swear that making a Phalanx form a human pyramid with these things made sense two hours ago."
Lana looked a little frazzled in her corner of the Engineering Bay. A factory standard Phalanx was parked off to the side in APC form, while various computer bays were running multiple sequences and projections. Interestingly, most of them had reached the same conclusions that they had. Adam looked at one, then brought it up to the main window display. "Heeeeey, you got the Faedium Block in there too!" he cheered. "Good call, it works."
"Oh, good." Abruptly, about fifty percent of the other simulations simply shut down and disappeared into the archives. "That saves me a lot of work."
"What's the end state of this?" Henry asked. "It's like you're stress testing to see how far this goes."
"That's the plan, yeah," Lana admitted. "So far, the Sledder on its own isn't great for combat. But if you use it as a combine component, it provides a lot of power. But." Various combat simulations, ranging from a Dragon-class kaiju to a Bandit-class Kaus played out - and the limbs that formed the Sledder almost inevitably were utterly wrecked after a full combat's worth of use. "Almost like the K-Scale. Great for defense and utility, but not to actually hit something."
"Almost fire and forget, right?" Adam commented. An amusing thought crossed his mind, and before he could even consider if he should try to stop himself, he was already speaking it. "Maybe we could make one transform into a giant drill and just launch it Shepherd style for a drill arm or something."
Henry just turned to stare at him.
Lana was also just blankly staring at him from her console.
Adam shrugged. "Just a thought," he said.
"...I am intrigued by your ideas and want to subscribe to your newsletter."
"She's doomed," Henry muttered.
New development idea for the Sledders - Weapons and Utility Deployment - available next turn!
New Insights into Phalanx combinations developed! Decision available next turn.
Two Turns Remaining.
Pegasus-class Construction
"Explain." You are standing in one of the newly constructed expansions of the Engineering Bay, so fresh that you can still actually make out some of the wall's model numbers before they inevitably get caked in soot and oil grease. Engineering must grow to continue supporting Engineering after all, or so the old joke went. But inspecting the state of the bay wasn't the reason why you were here.
No, it was the sheepish trio of the Build Team that was drawing your…ire? Interest? You're still not sure, and you haven't heard a reason why it should tilt one way or another just yet.
"I, ah, think it started with the accidental shorting on the engines," Anthony admitted. Behind him, the massive engine blocks that would have been powering the thrusters to the new dropship had a rather nasty looking fracture breaking right through the center. Anthony's own face was covered in soot and sweat, so he clearly had been busy trying to fix it. "So I was just wondering, until we can get this thing fixed, we could just make the damned thing walk."
"...and the tank treads?" you ask pointedly. Giant treads that are more fit for a supersized tractor - or maybe a superheavy command vehicle - laid stretched out running parallel to the main bay's operating area.
"If the walking bit didn't work, maybe this would help it to move if it ever crashes again?" You pause - then conclude that despite the execution of the idea, the idea itself was not a bad one…but why tank treads? "That and if it's that stable, we could probably upsize the main weapons a little bit…"
"That was probably when we joked about the spider legs," Kelly added, which immediately framed the tank treads as sounding more reasonable to you by comparison. Behind her, the unfinished frame of the new Pegasus-class loomed large, still hollow but structurally it was still intact. And then to her right was a pair of said spider legs - giant, enormous mechanical monstrosities that if you had to guess would fold up into the dropship's hull when not in use. "Stability is kindofanissuethough," she quickly concluded.
"So then," Greg concluded, "I asked Architect and Hotwire when they were over the other day if they had any retroboosters, rockets or the like that could help make the thing hover instead." You look at the last engineer, and thankfully, he didn't have the physical evidence of some constructed attempt around him. Plenty of blueprint sketches, though. "The Pegasus template probably won't work, but I did see what Wilde and Henry were doing with the Beowulf. I know it's not exactly ready, but we could try the Faedium Block…s? Faedium Blocks in a cluster sequence to give it enough power?"
"Why the booster idea then?" you ask.
"I mostly wanted to keep the idea of a flying dropship, not a land crawling video game boss stage."
You glance at all three engineers again, then at the odd, odd things they had requisitioned that had managed to find their way up to you, and why you were down here to begin with. "...has anyone discussed the idea of 'feature creep' with you all?" you ask.
"'Features waiting to happen.'" The response was unanimous from all three.
You just sigh. You suppose you could keep the original aim of the Pegasus-class, or you could try to incorporate one of the new…ideas the Build Team have come up with at the cost of time. "Just…just submit an official proposal for them before you try bolting things on willy-nilly."
Pegasus-class Decision available next turn! One Turn Remaining.
Seeker Wing Development
"I told you that was gonna raise eyebrows." Anthony's voice sounded slightly tinny through the vocal radio from the Steed he was operating. The model was stripped completely of any ability to Configure, and instead had been augmented with power loader servos. It was also painted a bright engineering yellow with black stripes, along with enough reflective tape to ensure anyone could see 'engineer working, stay clear.'
"Giant spider-walker dropship is a cool idea and you can't convince me otherwise." Kelly huffed from her position at the crane controls, waiting patiently for Greg to finish loading the next component. "It would work too! Once I figure out how to stop people from getting motion sickness."
"Gonna just agree to disagree there, Kelly."
"Engine up!" Greg called out.
"Loading!" Kelly yanked the lever, and slowly, suspended on a harness, the engines of the next Seeker began to lift upwards from the ground floor. Anthony waited until it was just at the right level, making a circular motion with the Steed's right hand to encourage it to keep going, until he abruptly clenched it into a fist to cease motion.
"Okay, good!" With that, Anthony lifted the first part of the engine and slid it into the unfinished Seeker, before banging his fist on the side to knock loose the wires that needed connecting. "I know some of these are gonna go to the Twenty-Fifth, but what about the rest of them?" he asked. "Heard we didn't get the pilots just yet."
"Something-something-not-available," Kelly shrugged. "You know how those go."
"You know, there is a way around that-" Greg started to say.
"AI again?" Anthony asked, sounding just a little exasperated.
"Now, just-just hear me out." Greg's voice was already going right back onto the argument that had been breaking ground for the last few days. "If we can't get the pilots now to operate the Seekers yet, why not make them AI instead to get them sooner? Just saying, we can do it."
"You just want to make everything a robot," Anthony scoffed as the engine roared slightly through its initial runtime diagnostic.
"And?"
"Well, it is kind of in our job description now," Kelly admitted. "And we've got Ichiro and the Argonauts running around, so…"
"I mean, it's just a thought." Greg shrugged. "What are the odds we're going to get that?"
Drone Support
"The odds are somewhat middling in your favor, I would say."
This was decidedly not the conversation that Greg was expecting to have in the chow hall. Having finished the day's batch of Seekers - thank you God for prefabricated K-Class hulls - he had gone to go grab some food, and was sitting down when he was abruptly joined by Dr. Ignatov.
"You're…using the Drone wreckage?" Greg asked, curiosity nudging him along.
Dr. Ignatov nodded, and set aside his tea as he withdrew a tablet. "The very same wreckage from the operation at Death Valley a few months prior," he explained. "We did not have time to thoroughly examine the wreckage, but much of the 'Drone' processors survived. Inert and with corrupted data to the point that even Patch had dismissed it, but it led me to think." Each 'processor' - effectively the Drone brain - were overlaid next to each other, in varying states of wreckage and disrepair. "It seems the Mekaen denizens do not construct their Drones to last. Relative to Kausen constructed bodies, they are cheap and 'throwaway' as it were. And yet."
Various equations and simulation charts were overlaid to the side, with a series of graphs showing data over time displaying. "In theory - in theory, mind you - with enough time and nurturing, the Drones actually have a remarkable potential for growth as individuals. We have even our own in-house example in Zulu. So what if we were to cultivate and grow our own Drones?"
"And…you want to put them in the Seekers?" Greg, mentally, was very much on board with this idea, but the engineer in him had to raise up one question of practicality as much as he hated to. "Isn't that a step too far for that though?"
"Consider it a test bed then," Ignatov replied. His voice was deep and calm, but there was a certain fire in his eyes at the idea. "Consider if you will. The Steeds have the proper processing power, which can then plug directly into the Seeker frame or any of the others we have or will have at our disposal-"
"-and we could keep them for defense," Greg added, not quite realizing a similar fire was in his eyes. "Even if not the Seekers, we could make them support units to get them started-"
"-with added processing power for true personality growth-"
"-or maybe they could combine into a larger personality and frame-?"
"-I would want to monitor that closely to prevent any longterm damage, but-"
Their chance discussion would eventually culminate into a combined proposal for the new Seeker wing on Major Devin's desk, just in time for the New Year…
Seeker Wing Development and Drone Support momentarily synched. New Decision available at next turn. One Turn Remaining.
Mega Blaster Analysis and Energy Blaster Miniaturization
"So." Jiro is briefing you in the safety of his office. In the corner of your eye, you can see Lana and Wilde discussing something with a lot of hushed whispers and intent, but you return your focus back to Jiro. "Decided to kill two birds with one stone. I was gonna start on miniaturization first, but I figured, why? It might not be the best attempt, but the Westphalians already kind of started for us."
You blink at him. "You call this-" You point at the 'mega blaster' recovered from the Brute-class super heavy walker, "'mini?'"
"No, but it's someone else trying to apply human style weapon concepts to Kausen technology," he counters. "Well, they tried. They clearly didn't understand how any of it worked before they tried welding all three together into a Bigger Gun." Video footage captured from Ichiro's perspective in the Brest operation shows the weapon glowing a bright, unhealthy red from the 'maw' of the Beast before it spewed concentrated blaster fire.
"Watch this," he instructs. The beam began to lose coherency, going from a concentrated beam to something much more scattered - and then abruptly cutting off as chunks of the weapon exploded outright. "Easy enough to track, but if we reverse time just enough-"
You immediately see as Jiro zooms in on it. "They're not all firing at once," you notice.
"Yep. I guess even they figured that out," Jiro says. "They tried to make it a rotational deal. Each gun fires into a central energy bank before it gets vented out in one go. They tried to take a safety mechanism and weaponize it." He shrugs, a wry grin on his face. "Kind of on brand for them, really."
"And the weapon itself?"
"Herald was over the other day, so I had him check it out," he confirms. "All three are standard handheld weapons the Legion and the Free Brothers use. Just with the ergonomic parts cut out since no one was going to hold it, and they probably cut out the safety features too."
"They just wanted something out there," you reply. "Wasn't a bad plan if they weren't dealing with Ichiro."
"I remember seeing him right after it hit him too," Jiro recalls. "Man, Lana was pissed. But." The mega blaster was dismissed, and Jiro pulls out drawings on blueprint paper. "I think whoever their engineer was had the right idea, but they didn't exactly have anything like, say, Faedium. Same idea, but I'm pretty sure Faedium has higher tolerances than whatever they used."
"Another heavy launcher."
"For now." He then brings up his other project. "I didn't even think about Faedium when I came up with these," he admitted sheepishly. "I couldn't exactly miniaturize the Kaus Energy Blast. Not in anything safe anyway. So…"
"...you made mecha sized grenades?" you ask. Incredulity and a hint of admiration color your voice.
"Warheads," he corrects, even as he has to fight to prevent a smug grin crossing his face. Considering you had to do the same with the Naval Board, you can understand where he's coming from. "Delivery system varies, but the payload is the same - cheap automatic tracking software and a one-shot capacitor unit will deliver a shaped charge blast towards the locked on target and the force of the blast will destroy the unit so it's self-sanitizing. Grenade launcher on the forearm, shoulder mounted launchers, even give them to the Seekers for air-to-air combat."
"...very well done," you congratulate him. "How soon can these be available?"
"I can sneak some into the Thunderbolt and company before they head out," Jiro boasts. "Should be a good field test."
"Let's hope they won't need it," you comment, even as you're pleased with what Jiro made. Not quite what you were looking for, but another nice tool for the belt.
New Option Unlocked from Mega Blaster analysis! One Turn Remaining.
Direct Charge Warheads developed!
K-Fang Spear
Whatever Lana was working on with Wilde seems to have concluded, because as you approach her work station, a weapons display is already rotating. "Look at this, sir!" she exclaims. Her avatar has her hands on both hips as she looked to be on the verge of laughing in glee. "Behold! The first K-Fang weapon design!"
"...it's a halberd," you note dryly.
"A useful one!" she counters. "At first, I tried to use the Dragon Horn for an acid attack, but! Behold!" A simulation shows the weapon - you blink as you recognize Kausen energy blast technology emitters along the base of the halberd's blade charge said energy through the blade - and the edge abruptly explodes into a directed shaped blast. "It can channel energy blasts!" she crows. "It can shoot! It can cut with the destructive force of Kausen energy! It can do both at once!"
The weapon then shows its ability to split in half, with the edge of the halberd fitting into the display Phalanx's back along with the other half of the staff. "The first one I've got is for Perseus," she explains, having calmed down some. "But with some tweaking, anyone can use it!...except the Steed. Uh, sorry. Too tiny for it."
"Fair." You blink - this is just a solid piece of work from Lana. "Approved. Get it built and ready for Perseus when it's finished repairing." You then think to ask, "What's it called?"
"...uh." Lana's triumphant air soon turns sheepish as she scratches her cheek, chuckling in embarrassment. "I hadn't thought that far?"
"...think one up later."
New Weapon Developed! What is it called?
Base AI Development
Your last round is to Ignatov…and you are already feeling a future headache form.
"You chose who?" you demand. The new Super AI, another counterpart to Katarina specifically, is compiling and already in the works. Truth be told, you had already earmarked this project for completion, but you've had a crazy year so some things fell to the wayside.
"I was short on candidates that had time available," Ignatov says with a shrug. "Thankfully, Dr. McCullough was available."
You distinctly recall how the Faedium researcher does not seem to stop for breath when speaking. Or how her brain seems to jump from one subject to another with speed, with ideas that were no less formed than any other. "...and…how's it coming along?" you ask.
"Mostly fine?" Ignatov shrugs. "She will likely not be quite as active as Adrianna is-" You thank what few lucky stars remain with you, "-but she might be somewhat hyperfocused. It is too soon to tell."
You simply nod, and leave it at that. You're going to admit that you're a bit afraid to ask about specifics - you might not like the answers you're going to get.
New Base AI almost online.
ONE TURN REMAINING.
QM Note: Not a bad turn for you all! I will flesh out what you have created in the information tab later when I get some time. For now, be sure to come up with names for some of the new goodies you've unlocked. Hope you enjoyed, and sorry for the wait! I will try to get the Science! rolls out this week.
Ground pound could use a Base AI. And as for the Dropship. Hell no, not right now anyway. I'd rather we stick to the plan on building the dropship as it is instead of tacking on extra's. Maybe in a few turns when we have more transport options. but for now. leave it.
Need to stick with the Theming, but the Triple Combination Beowulf is probably going to be the Feature Complete version, with further upgrades mostly being refits rather than reimaginings of the core design. It's the Final Fusion if you will, and should be treated with the gravitas that's worth.
So Norse themed for sure, we've got the pattern of a Mythical Hero for the Core Unit, then lupine names for the combination forms. The one I've been playing around with is the 'Ultimate' form having a mythical hound.
Need to stick with the Theming, but the Triple Combination Beowulf is probably going to be the Feature Complete version, with further upgrades mostly being refits rather than reimaginings of the core design. It's the Final Fusion if you will, and should be treated with the gravitas that's worth.
So Norse themed for sure, we've got the pattern of a Mythical Hero for the Core Unit, then lupine names for the combination forms. The one I've been playing around with is the 'Ultimate' form having a mythical hound.
...Wasn't the Pegasus-class basically at maximum weight without losing troop transport ability last we left it? What do those engineers think they're doing, trying to add even more onto that?
On the bright side, we have a very nice-looking halberd now (and for the record, I'm always in favor of halberds because swords are just cliche). Too bad I can't name things worth a damn.
Beowulf's finally got its long-awaited triple combination, and Perseus is about to get some new limbs and maybe a backpack. Definitely good things, though we'll need to consider what Perseus will be combining with.
I am all for AI mooks; it may sound like a villain thing, but the more we can churn out the better.
Wonder if our new warheads are at all similar to the grenades Bandit used on us that one time.
And... well, there're worse templates for our new base AI, right?
Need to stick with the Theming, but the Triple Combination Beowulf is probably going to be the Feature Complete version, with further upgrades mostly being refits rather than reimaginings of the core design. It's the Final Fusion if you will, and should be treated with the gravitas that's worth.
So Norse themed for sure, we've got the pattern of a Mythical Hero for the Core Unit, then lupine names for the combination forms. The one I've been playing around with is the 'Ultimate' form having a mythical hound.
...Wasn't the Pegasus-class basically at maximum weight without losing troop transport ability last we left it? What do those engineers think they're doing, trying to add even more onto that?
This is indeed correct. but do remember that the first Pegasus was built before the weight reduction tech was created IIRC. And the second version will definitely have it.
This is indeed correct. but do remember that the first Pegasus was built before the weight reduction tech was created IIRC. And the second version will definitely have it.
Gimme a minute to double-check, but I'm pretty sure we had the anti-grav stuff when we built the Pegasus.
edit: Yup, we finished Anti-Grav on Year 2 Turn 4, and started the Pegasus on Year 2 Turn 5, which specifically notes that we used the anti-grav stuff in it.
Are we about to become the Mekaen equivalent of Necromancers by using the Processors of scrapped Drones? Or would this be more of a Dr. Frankenstein moment?
Gimme a minute to double-check, but I'm pretty sure we had the anti-grav stuff when we built the Pegasus.
edit: Yup, we finished Anti-Grav on Year 2 Turn 4, and started the Pegasus on Year 2 Turn 5, which specifically notes that we used the anti-grav stuff in it.
Just got done binging the first thread and this one - and I have to say, this is a brilliant read thus far.
Although I will admit minor embarrassment over not having realized there was actually art available for the Jackal's vehicle mode - the description of the original prototype, plus possibly a mention of the design being "boxy" made my brain go for something closer to the standard "Isekai Delivery Service" truck rather than "future-tech Humvee". Which is a bit of an oops, but did lead to the mental image of enemy super robots getting rammed by a glorified delivery truck, which was hilarious.
...Wasn't the Pegasus-class basically at maximum weight without losing troop transport ability last we left it? What do those engineers think they're doing, trying to add even more onto that?
Do you happen to remember which comic that was? Because that sounds hilarious and I would love to read it.
Also, Galbinus is very much Transformers Devastation Megatron, while Tyrannous is more earth-form Star/Victory Saber from the Japanese Takara cartoons.
For some reason, a senator has broken into my house and is demanding to play COLLECTIVE CONSCIOUSNESS at maximum volume
i sure hope there's an unemployed cyborg looking to expand the job market one life at a time nearby
Out of curiosity, could you clarify Perseus' Tetra-class combination mode? Like, are the limbs folding in half so the combination units connect to the elbow/knee (like, the hardpoint is in the joint itself), or am I completely misreading it?
