Invid Commander




Technical specifications

3.8 meters


4.4 meters


9.5 meters


24.2 tons

Maximum speed
  • 1,162 km/h atmosphere
  • 112 km/h running
Engine unit(s)

2 x IE-5 plasma-shock expansion engines

Power plant

1 x Protoculture cell energizer


1 pilot





The Invid Commander, also known as the Royal Command Battloid and scientifically known as the Gosu, was the first Invid bio-mecha that could accomodate a late-stage humanoid Invid, and was featured in Robotech: The New Generation. Its strength and firepower were reminiscent of the Queadluun-Rau Power Armor, and was extremely deadly in the battlefield.


The Gosu was about the size of an Alpha fighter, but the combined thruster/missile launcher design was more reminiscent of the Quaedluun-Rau Power Armor than of any Veritech design features.

The huge engines in the back propel the Gosu at speeds up to 1160 kph. This meant that the Gosu could not go supersonic. The Invid, however, did not see this as a design flaw since most of their airborne warfare was fought at speeds between speeds of 20 kph (ground attack) and 1000 kph (aerial combat). The high speeds of the Terran Veritech mecha were not needed for the Gosu, since they were intended as command and ground attack mecha. Also, because of their large numbers, there was usually an Invid unit in range of a high speed hostile, where humans and Zentraedi, with their somewhat lower preferred density, would need faster mecha to cover equal amounts of ground in equal amounts of time. A such the Invid lack a dedicated high-speed atmosphere capable fighter, and rely on numbers to deal with fast, airborne, foes, although present trends in mecha design lean to more capable weapon systems (mainly missiles) to engage fast movers, and likely a true aerial mecha is being studied.

Technology and Combat CharacteristicsEdit

The weapons for the Gosu were more diverse than on other Invid mecha. Where the Iigaa and the Gurab carry two cannons each, and the Gamo had two cannons with two small secondaries, the Gosu had one (albeit large and multi-functional) plasma cannon, but also a secondary laser in its head, and a large number of anti-mecha missiles in the thruster housings. This was the first time that missiles had appeared on an Invid mecha. They provided the Gosu with a very powerful punch, and the design was exceeded in number of missiles carried only by the Quaedluun-Rau Power Armor. Two types of missiles were carried: a short-ranged dogfighting missile for use against slow-moving mecha, and a longer-ranged and faster missile used against faster targets. Combined, these weapons gave the Gosu a capability at all ranges that was totally new for Invid designs. Invid experienced with missile tactics was minimal in the Third Robotech War, and the Invid pilots seemed to rely almost exclusively on their cannons, using missiles almost solely as an afterthought. This could, however, indicate a lack of confidence in the missiles on the part of the pilots; certainly, only a few of the missiles reached their intended targets, most being decoyed by their targets' electronic warfare system, simply being outflown, or prematurely detonated. Likely this was due to the fact that the Invid were new to missile technologies.


The armor of the Gosu was composed of a composite of metals, ceramics, and organics unique to Invid manufacture. Research continues into the composition of this material, though results from X-ray crystallography, NMR, and mass spectroscopy studies remain classified. The armor stops all small arms, heavy infantry weapons fire, and light mecha-mounted weaponry, and provided fair to good resistance to medium mecha-mounted weaponry, such as the Valkyrie's 55mm APFSDS round. In addition, the armor is highly sloped, and rounds that hit at oblique angles are very likely to glance off it without penetrating.

External LinksEdit

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.