This is hardly just an event anymore, it's like opening a whole new series of functions related to starfighters!
The technology related to starfighters largely determines the level of equipnt, while the training of starfighters, like the "Army Badge System", has many more training options.
Of course, it costs many tis more.
There's even sothing like growth acceleration.
If there were no other concerns, Gu Hang might really have used growth acceleration to speed up those three lads in one go, and get them in shape in a month.
But after so thought, Gu Hang still refrained from doing so.
There was no urgent need for a large number of starfighters at the mont, so he decided to let them grow slowly, and there was no need to stimulate poor Matins anymore. He had been through a lot of shocks recently, so it would be best to let him calm down first.
The all-out oath of allegiance from Phoenix had brought about more than just a change in the event.
Within the Army Badge System, Gu Hang could now see a special entry for "Phoenix Battle Group".
Upon clicking, he could view the details.
[Phoenix Battle Group: Special, Not Upgradable]
[Number: 394]
[Starfighters: 4]
[Starfighter New Blood: 3]
[Battle Group Servants: 387]
[Battle Group Arsenal: Slight]
The numbers 4 and 3 were straightforward; the 387 Battle Group Servants were likely the individuals found by Phoenix when they were authorized by Gu Hang to search and select young people on Rage Owl Star.
These nearly four hundred individuals almost certainly could not beco starfighters. Nonetheless, they were still considered assets of the Phoenix Battle Group, becoming Battle Group Servants. Find more to read at empire
They would subsequently take on a range of tasks such as maintaining Battle Group logistics, armors, weapons, cooking, cleaning, and even taking up arms to fight alongside the starfighters when necessary.
However, such situations were not what Gu Hang wanted to see in the long term.
In the future, his ideal vision for starfighters was for the Phoenix to only care for their own personnel and their own equipnt.
As for the rest, whether it be Mortal Troops or the Battle Group Fleet... they can forget about it.
It's not that he didn't have them, but even if he did, Gu Hang certainly wouldn't include those assets within the Phoenix Battle Group's order of battle.
The Battle Group leader should be concerned with the affairs of the starfighters only. If needed, the Planet Navy, Planet Army will provide unconditional support, but only with Gu Hang's authorization. Even the action of the starfighters themselves must be authorized by Gu Hang.
The traditional Battle Group expecting to beco an independent warlord in the Star Sea is impossible.
Training starfighters for Gu Hang is, to put it plainly, about nurturing elite enforcers, top-level battle forces designed to deliver decisive blows on the battlefield, not raising a bunch of grandees or a group inclined towards secession and independence.
Gu Hang nearly decided to eliminate all Mortal Troop configurations within the Battle Groups.
Need a flyer? Need air support? The Allied Air Force at your service!
Need orbital bombardnt? The future Fleet at your service!
Need heavy vehicles for joint attacks? The Alliance Army Armored Corps at your service!
Need logistical and supply support? The Alliance Military and Political Departnt, Equipnt and Logistics Departnt at your service!
Anyway, in Gu Hang's planning, Phoenix is ant to be a hub for super soldiers, not an independent warlord. Everything else that a Battle Group should have, Gu Hang will provide but in a different way.
Matins could command the Alliance Army granted to him by authorization, but such authorization was one-ti only, limited to that specific mission and did not alter affiliation.
Only if items like Rand Assault Boats and Rhino Troop Transporters, considered to be specialized starfighter equipnt, were developed would Gu Hang consider directly equipping the starfighters with them.
————
After thinking it over, I realized it was a bit confusing and made changes.
User Comments
0 comments from readers