Super Robot Quest

So the machines used to make Kaiju were something that Sheol found and initially didn't know how to use. Sounds like alien shenanigans to me.
 
His spite is to our benefit. Think of how easy it is to divert the Kaijiu with a drone designed to do nothing but look like Mercury and carry all the armor/forcefields.
Too bad we cannot learn that IC yet.

Mercury V is a reskinned Mazinger Z,

Speaking of: Which attacks/powers are commonly known besides the freeze-thrower, @Basarin ?

and the DFRI is increasingly becoming the organization who's name I can't remember from GaoGaiGar.

GGG, aka Gutsy Galaxy Guard, making NERV look incompetent since 1997.*

But Valiant's part seems weirdly...original.

Someone mentioned Voltron I think.

Are both Valiant and Mercury black-colored though? I think both have been referred as having said color.


* EDIT: I finally finished watching the OVAs. Boy, how do they go up to eleven and beyond, especially during the ovas, which fix lots of issues of the originals but add a few ones, like the excessive quantity of fanservice, sometimes to absurd levels. I know Mamoru is getting to that age, but really?
 
Last edited:
[X] Damage Repair Crews

BTW @Basarin a minor gripe:
So could you make multiple Super Robots? If you ignored the turn options, sure. But I wouldn't imagine you'd want to, and I'd discourage you from doing so. This is your first proper Super Robot; I'd focus on just building the one for now.
This is something you said in response to the idea of throwing some Resources the Perseus' way during the 1.0 Super Build in case we wanted to deploy two units.

After this WoG, we just focused it all on the Beowulf, which I don't necessarily regret, because it's awesome and it probably needs every advantage it can get against the Kaiju.

But this then got followed up with a deployment against two separate attacks, where the only way for us to respond to both required us to spend extra RP in order to kitbash the Perseus into combat readiness. That's...not the coolest move.
 
Speaking of which, what is the Valiant show based off of, if anything? I mean, Mercury V is a reskinned Mazinger Z, the Kausen are reskinned transformers, and the DFRI is increasingly becoming the organization who's name I can't remember from GaoGaiGar. But Valiant's part seems weirdly...original.
Since people had already mentioned Combattler V, all I can do is provide some illustration.

Or rather, it would be much more honest of me, but less informative, to provide this illustration. Because that's the only reason I've heard those names at all.
 
Last edited:
@universalperson

Valiant, FYI, is largely a knightly take on Kotetsu Jeeg. Valiant's entire premise is a big shoutout to that one; I only ever found out about the franchise thanks to SRW Alpha 2.

@NaanContributor

That's a valid complaint, and I'll try to avoid doing that in the future. But I did explicitly say that while NYC is going to take damage, the known anti-Westphalian troubleshooter, Valiant, would be there eventually to contain what it could. I only presented the choice to you all to kitbash a Core Unit; deploying a support unit instead (or NOTHING at all and trusting the present forces to deal with it) was also a valid choice.

Still, I hear your complaint. I'll keep it in mind for the future.

@HeavyBane

About what you'd expect. He does in fact have a rocket punch, along with the freeze attacks and energy attacks that draw in Aeon Particles. You may get the chance to see it in action soon.
 
Thought it was Jeeg right when you described him as being held together by electromagnetic power.
 
Last edited:
Valiant, FYI, is largely a knightly take on Kotetsu
Lel, ain't the first version ridiculous? Not only the mecha looks like its wearing underpants, it also runs behind that bike in a little embarrassing way. The second, improved show makes it look more dignified.

About what you'd expect. He does in fact have a rocket punch, along with the freeze attacks and energy attacks that draw in Aeon Particles. You may get the chance to see it in action soon.

Oh my, how classic. Has the Institute received suing attempts from whoever digged the copyrights of Mazinger Z? :V

As for seeing it in action, I was hopeful that we could destroy/force to retreat the monster before the SR arrives.
 
We couldn't respond to both adequately to begin with, we only have one carrier.
That's what we believed at first, but now we're sending the Perseus out on a borrowed Stork anyway, so that's no longer true.

Now I'm certainly not going to complain about Basarin giving us the chance to have our cake and eat it too by improvising a response to the second attack. If he were using the X-COM model we'd only be able to do one or the other, full stop. It's just that the nature of the response contradicts a previous WoG, which is something to watch out for.
 
That's what we believed at first, but now we're sending the Perseus out on a borrowed Stork anyway, so that's no longer true.

Now I'm certainly not going to complain about Basarin giving us the chance to have our cake and eat it too by improvising a response to the second attack. If he were using the X-COM model we'd only be able to do one or the other, full stop. It's just that the nature of the response contradicts a previous WoG, which is something to watch out for.

Duly noted.

Just remember this discussion in the future please. :D

EDIT: That, and I DID say earlier you could improvise another response if you so desired; the Stork was a hurried improvisation.
 
Last edited:
Duly noted.

Just remember this discussion in the future please. :D

EDIT: That, and I DID say earlier you could improvise another response if you so desired; the Stork was a hurried improvisation.
To be clear, my original issue isn't about the response itself. Having to spend extra resources to deal with another attack makes perfect sense.

I just didn't like "Don't worry about making a second combat ready robot, just focus on one." followed by "You can send out a second robot to deal with this other attack, but it'll cost you extra because you didn't get it ready ahead of time."
 
[X] Preston-class munitions. Normally reserved as air-to-ground munitions for naval bombers, Lieutenant Cahl is more than happy to have ground crews load them onto your V-33 flight for this mission.
 
To be clear, my original issue isn't about the response itself. Having to spend extra resources to deal with another attack makes perfect sense.

I just didn't like "Don't worry about making a second combat ready robot, just focus on one." followed by "You can send out a second robot to deal with this other attack, but it'll cost you extra because you didn't get it ready ahead of time."

Are you asking me to NOT give those choices? I am honestly curious here.
 
Last edited:
Are you asking me to NOT give those choices? I am honestly curious here.
Wha? No that's not what I-. *Sigh*. I feel like I'm being less clear the more I try to clarify it.

I'm not talking about this:
Stork-class Dropship Amerigo Vespucci
Heavily Burdened:
- It's already full of cargo heading towards NYC, so it's got enough time to load one Core Unit or Support Unit. Nothing more.
Which is representative of the option to send an improvised secondary force with whatever we can spare. That's fine.

I'm talking about this:
As much as Lana grumbles, she and the Duo understands the need to deploy something. If you think you need to retrofit a Core Unit right now you can, particularly if you're thinking about trying to send it to NYC. It's not going to be at full effectiveness, however, and you risk getting it damaged more easily.

To repeat myself: while I will allow you to bring ONE Core Unit, you are paying half of its build cost just to get it battle ready. If you choose to do this, I will let you purchase one Upgrade and one Finisher (think of it as an emergency installation). If you choose to do that and pursue eventual full-scale production of that model, I will waive those upgrade/finisher costs in the future.
Needing to spend more resources to rush another Core unit to battle (which is the most effective choice because it's better than a Support unit) than we would if we had already gotten it ready also makes sense. But a big reason it's not ready in the first place, which we're now paying the price for, is because we were told not to when we had the chance.
 
Wha? No that's not what I-. *Sigh*. I feel like I'm being less clear the more I try to clarify it.

I'm not talking about this:

Which is representative of the option to send an improvised secondary force with whatever we can spare. That's fine.

I'm talking about this:

Needing to spend more resources to rush another Core unit to battle (which is the most effective choice because it's better than a Support unit) than we would if we had already gotten it ready also makes sense. But a big reason it's not ready in the first place, which we're now paying the price for, is because we were told not to when we had the chance.

I get your point. I'll drop the discussion here. I'm just going to agree to disagree and keep your feedback in mind in the future.
 
On that note, calling the vote here.
Adhoc vote count started by Basarin on Jun 24, 2018 at 6:44 PM, finished with 49 posts and 18 votes.
 
[X] Preston-class munitions.

Edit: 3 min too late. Oh it's not as if it would have changed anything.
 
DamCon is love, DamCon is life.

After all, killing the Kaiju is just a nice bonus. We win just by limiting damage.
 
Deployment #2: Defense of Naval Base San Diego, Kaiju Incoming
0854, 28 November A.D. 2071
Command Center Bridge


"We are as ready as we are going to be," Sasaki reports through the sat-link. "The Lieutenant was able to secure the services of the damage repair crews should the worst happen."

"Beowulf?" you ask.

"On ground and ready to deploy." Sasaki's image is replaced with the overlay of the naval base, with an arrow showing the projected course of the kaiju. "While thankfully the majority of personnel and equipment have evacuated, there is nothing we can do for the drydocked vessels. When the kaiju emerges and makes landfall, the Beowulf is going to have to do what it can to keep its attention away from the vessels and the facilities. The Pegasus and the First Support Wing are on hand to deliver fire support as needed."

"We'd always wondered if the kaiju were intelligent," you mutter to yourself from your seat. "Well, suppose today's as good as any day to find out."

You glance down at the maintenance bay below you. Though their jobs were already finished awhile ago, you know the majority of the ground crews are huddled around view screens being fed from the Pegasus, and that they're unlikely to be returning back to rest no matter what you order.

Among them is Ichiro and Satsuma. Ichiro's face is pensive, as if seeing something he wasn't particularly happy with. Satsuma...

...you honestly don't know. Anxious is the closest you can think of.

You are about to say something else when the klaxons blare from Satsuma's side of things. "Here it comes," she mutters. "Signing out, Sir."



0857, 28 November, A.D. 2071
Naval Base Docks


Richard wasn't sure what to expect when he found he was going toe to toe with a kaiju today. Anxious, nervous, resigned. Those were all good words.

Overwhelmed would have been another good one.

He was not prepared for the giant plume of water that burst not far from the hard stand's edge. One massive scaled claw slammed down hard onto the concrete with enough force to shatter the concrete. Another joined it. Then another.

Before long, Richard was being forced to look up at a hulking monster straight out of the older movies. Crawling on all four legs, the heavily-scaled kaiju carried an aura of menace around it. Green smoke exhaled from its snout with every breath it took, and the sharp horn mounted on its crown flickered green every so often, as if holding an energy source that desperately wanted to get away from its host. Four baleful eyes glanced around, seemingly for prey, and the massive tail behind it swept back and forth, idly snapping a forklift platform in its passing as if it were just a tree branch.

It then stood shock still as its eyes saw the drydocked vessels in the far distance. In their varied states of disassembly and rust, they must have looked to the kaiju like a pack of landed whales ripe for the picking.

The kaiju reared its head back and roared. Richard winced even from inside the armored form of the Beowulf, as the force was enough to shatter the windows of every building around him.

Richard shook his head fiercely, then allowed his mind to settle into the MMI. At once, he calmed down, and only took a few moments to rev the engine. The Beowulf seemed to snarl in response, as if it were taking affront to the presence of the beast in front of it. It wanted to leap into action. It wanted to hurt the damned thing.

"Pegasus, this is Beowulf. Permission to engage?"



Outline your battle plan.

Actions per Turn: 1 +1 (K-Suit) = 2 Actions Total

Enhanced Reflexes:
- The K-Suit upgrade grants One Free Re-Roll per Combat Turn (Must be declared)​
Notable Character:
- Can make two attacks per turn at 2d6 for 1 HP each. Counts as a single Action.​
Intuitive Piloting:
- You may Re-Roll One failed Strike or Agile Roll per Turn​
Assigned to: 1LT Callaghan

The Beowulf
HP: 18 HP
Agile: May roll to avoid a successful enemy attack at 2d6, Threshold of 4-6.

Diminishing Returns: After two successful agile rolls, Threshold increases to 5-6.
K-Scale Mesh: You may attempt to reduce damage at a 2d6 roll (Threshold of 5-6).
Reduce damage by -1 HP.
Applies once per combat turn.
Strikes:
Counts as One Action (Notable Bonus may apply).
Roll 2d6, Threshold of 5-6, inflicts 1 +
2 HP on success.
Ramming Speed: Counts as One Action. May roll to ram an enemy at high speeds at 2d6, Threshold of 5-6, inflicts 2 HP. Success may have additional effects if declared prior to attack, to be ruled by QM.
Follow-On Strike: May attempt a Free Strike at Disadvantage if Ramming Speed succeeds.
Combine: May Combine with either the SV-10 Shepherd or the V-33 Falcon at reduced cost (see Combine Units)
Energy Blaster
Cost
: 2 RP
- Heavy Weapon upgrade package. Can make Heavy Weapon Strike against Enemy at Advantage (3d6) for 4 HP.
- Wide Blast Zone: If you do not meet the Threshold, you will still inflict 2 HP.​
Charges: 3
- If not utilizing Shepherd Armor Pack, can only be used Twice per Combat
- If using Shepherd Armor Pack, Demolisher Applies (Timberwolf Formation Only)​
NOTE: An upgrade package to the Heavy Weapons reverse engineered from Bandit. Expensive, but delivers a good punch.
Upgrade Slots: 2 + 1 Bonus Used
-
Anti-Gravity Treatment, K-Circuits 2.0, K-Scale Mesh, K-Suit Upgrade
V-33 TMU 'Longship Configuration'
First Experimental Support Wing
Heavy Weapons:
- Strike at Advantage (3d6 for 2 HP).
- Usable once every three turns.​
Experimental Mecha Modes:
- After a Heavy Weapon Strike, V-33s can now launch a follow-up Strike.​
- Roll 2d6, Threshold of 5-6, to inflict 1 HP.​
- Not for mass production.​
Pegasus-class Dropship

Bigger Guns:
Energy Blaster
- Heavy Weapon upgrade package. Can make Heavy Weapon Strike against Enemy at Advantage (3d6) for 4 HP.
- Wide Blast Zone: If you do not meet the Threshold, you will still inflict 2 HP.​
Charges: 3​
- If not utilizing Shepherd Armor Pack, can only be used Twice per Combat
- If using Shepherd Armor Pack, Demolisher Applies (Timberwolf Formation Only)​

Foxhound and Timberwolf are still there, I just didn't post them up here at the time.
 
Last edited:
Back
Top