[X] Damage Repair Crews
Sounds like a Super Robot take on a lot of Real Robot concepts, honestly.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.
Too bad we cannot learn that IC yet.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.
and the DFRI is increasingly becoming the organization who's name I can't remember from GaoGaiGar.
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.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.
Since people had already mentioned Combattler V, all I can do is provide some illustration.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.
So, do you mean to say that Valiant could have raised quite a Kotetsu-Shindig all by itself?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.
So, do you mean to say that Valiant could have raised quite a Kotetsu-Shindig all by itself?
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.
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.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.
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.Duly noted.
Just remember this discussion in the future please.
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."
Wha? No that's not what I-. *Sigh*. I feel like I'm being less clear the more I try to clarify it.Are you asking me to NOT give those choices? I am honestly curious here.
Which is representative of the option to send an improvised secondary force with whatever we can spare. That's fine.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.
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.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.
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.