I didn't say "just keep doing the exact same thing until you get it right" so I'm not sure why you brought that up. In any case, the boss isn't about "git gud", it's literally just "apply the techniques we have shown you already". It's like teaching a child about basic shapes and then, as a test, handing them a square peg and making sure they understand that it doesn't fit into a round hole.
But this is so broad and generic that it tells us nothing useful. You could use it to describe - or defend - any game's tutorial elements, no matter how dubious they are. Let's be more specific here. There's basically only one way to beat the tutorial boss, right? You have to close the distance and use your melee attacks to stun it, leaving it vulnerable for you to do some real damage to it. This is far from an ideal strategy, as the boss is fairly mobile, can "outrun" your assault boosts by flying away from you, and regularly travels out of bounds where you can't follow it, but nevertheless, that's really the only thing you can do. And this never happens again. You are never forced to fight a boss one specific way and with one specific build again in the game. In every other boss fight, and in fact in every other mission save for one (mercifully free of a boss fight), you're entirely free to modify your mech how you want with the equipment available to you. So this boss fight is a bizarre, entirely unique experience as far as boss fights go, not at all representative of the experience or in any way preparing players for what comes next.
It’s quite simple. Most characters and factions you encounter don’t know really anything about coral besides its capacity for weaponisation. The characters that do know about it have their reasons for concealing that knowledge, but more broadly you aren’t really told much of anything because of how the world sees you. You aren’t seen as a person, they call you a dog or a hound and they mean precisely that. You exist to follow orders as far as they’re concerned, and the less you know about what you’re doing or why, the better. As Walter says, “it’s just a job 621. All of it.” There is no conceivable in-universe reason for anyone—besides Ayre, who sees you as something more than just a tool, and who does actually tell you quite a lot about the nature of the coral—to give you information beyond what is strictly required for you to do the job.
I'm not saying that either 621 or the player should right off the bat know all the arcane secrets of Coral or Rubicon, but they should know the basics. 621 should already know them - not have to be briefed on them by the other characters, but already know them (which the other characters seem to assume they do, anyway) - and the player should be told them via exposition. The game never tells you what Coral is, which is about as basic a detail about this setting as you can get. When I say "the game," I mean the game in its entirety, not simply the other characters in the game, and when I say "you," I mean you, the player, not simply 621, the player character. Can you piece it together after a few missions, sure, just like if you miss the first twenty minutes of a movie you'll probably still be able to figure out who the main character is and what the conflict of the movie is about. That's not the same thing as timely, effective exposition.
Also, while it’s true that even less detail than usual is given regarding the PCA (Planetary Closure Authority), it’s pretty unambiguously Space NATO. They established a hold on Rubicon some time after the cataclysm to keep the coral-hungry corporations and other groups from gaining access to Institute City and the coral convergence.
I somehow messed up the name in my second post, despite getting it right in the first one. It's Planetary Closure Administration. Derp. Anyway, there's nothing unambiguous about them being Space NATO. That's just a guess on your part. A sensible one that I'd agree with, but still just a guess. It wouldn't have been difficult to include a quick explanation in the game of who they were to save us the trouble of having to guess. Incidentally, you know which faction isn't a complete mystery? RaD. Because with them, the game actually took the time to explain who they were. Instead of just saying, "Oh, look, here comes RaD, doing RaD things," they included a few lines of dialogue introducing us to them. That's all they needed to do. Ideally, I'd prefer a codex full of information that the player can peruse at their leisure, because I like lore lore lore, but they didn't really
need to include that to do their job as far as exposition goes. They just needed one or two lines at the right moment to give us context for what's going on.
I think one of the great strengths of the game is that the amount of gear available lets you tailor your mech almost perfectly to a design that suits how you feel comfortable playing. If a tank with heavy weapons is what suits you, go for it. I personally found the tank leg parts difficult to control, so I went with reverse-jointed legs for high evasive capability.
My AC is better than yours, though! I'll kick your ass in PvP! What weapons did you use? I used dual gatling guns (DF-GA-08 Hu-Ben) and dual stun needle launchers (VE-60SNA).
It isn't named in-game but the Divine Dragon uses it, complete with projectile attacks.
That's not good enough! It should have been a proper usable sword for the player. Even
Ninja Blade had that, and that's the game you'd get if you asked David Cage to make
Devil May Cry. I have heard that
Déraciné also doesn't have that sword, but as far as I can tell, nobody has ever actually played
Déraciné, so there's really no way to confirm.