Naval Vessels Notes |
|||||
 |
|||||
 |  |  |  |  |  |
Little data exists for this vessel, aside from the pictures of it in _M:PM_ and a length listed in a comparative chart of the RDF and Zentraedi vessels. Hence, most of the entry is purely speculative.
The Japanese source material lists this vessel as
"semi-submersible". Not really understanding what is meant by this - possibly that it can
submerge
only to the flight deck, or to only limited depths - we have removed the qualification and
have
made it fully, if cumbersomely, submersible.
Go to Prometheus Technical File.
Little data exists for this vessel, aside from the pictures of it in _M:PM_ and a length listed in a comparative chart of the RDF and Zentraedi vessels. Hence, most of the entry is purely speculative. It is apparent from the
limited source material that the
Daedalus-class is supposed to be submersible.
Go to Daedalus Technical File.
This file arose out of what was probably an animation error made by the studio to which this episode was farmed out. In a scene of Earth's fleet under attack bt the Zentraedi, in addition to several Oberth-class vessels and ARMDs, several vessels clearly identifiable as Prometheus-class carriers can be seen. This is seemingly nonsensica, especially considering Gloval's later comment about the unspaceworthiness of the Daedalus and the Prometheus.
To explain away the bizarre appearence of these ships, we have supposed the existence of a test bed for the anti-grav pods used in the SDF-1, and that the test bed used the Prometheus hull.
Go to Technical File.
The Warspite-class submarine is an invention of
Pieter's, taking
a double-hulled version of the modern Seawolf, and adding MHD drives, Russian-style
sail, and
protoculture powerplants. This vehicle is not seen in the animation sheets or the sources,
but was
created to fill a strategic need for escorts for the submersible Prometheus- and Daedalus-class
vessels.
Go to Warspite Technical File.
Little data exists for this vessel, aside from its appearance in the footage. Hence, the entry is almost purely speculative. The weapons fit can be extracted from the combat the cutter participated in in attacking an invid patrol.
Go to Barracuda Technical File.
Little data exists for this vessel, aside from its appearance in the footage. Hence, the entry is almost purely speculative. The weapons fit can be extracted from the combat the remoted-control patrol boats participated in in attacking an invid patrol. The missiles launchers fired at the invid, and a tube on the fore deck can be seen that suggests torpedo tubes.
Go to Kennedy Technical File.
Like many other vessels, the data for this ship is
limited mainly to pictures.
Macross: Perfect Memory lists data like the tonnage, engines and
powerplant,
some weapons, and fighter complement. The This is Animation Special
book
lists several names of the various vessels, and the Macross chronology lists the dates of
their entry
into service. Most data beyond this, however, is speculative.
The entries for the Armor-10 series were an
invention to
account for the Valkyries seen on one of the
vessels in episode #1 ("Boobytrap"); though no
Valkyries were listed in the aircraft
complement. We have also boosted the numbers built from
what is listed in Macross, to account for the "Armor 10", which began as an error in the
Robotech
dialogue, likely caused by a misinterpretation of the "01" written on the vessel.
Go to ARMD Technical File.
Virtually no data exists for this vessel, save for the
pictures and mention of this vessel in the Chronology. Its size is never explicitly given, though it can be inferred from the footage in episodes #1 and #3, and by comparative drawings on the cover of Macross: Perfect Memory. Most of the data in the entry is speculative, except for the general weapons fit and dimensions of the vessel, and the historical entry regarding the hijacking of one of the vessels by the Anti-Unification League to destroy the return fleet from Mars. Only two names for this vessel were given in the television series; in episode #3, we hear of the destruction and damage of several "Armor" vessels, and of two vessels named "Miranda" and "Circe"; moments before, two of this class of vessel were seen destroyed.
Because of the glaring size error in the RPG's
adaptation of this vessel (it was made into a fighter, not a destroyer), we have ignored this source altogether. We invented the name for the second subclass of the vessel because the two examples of names we had were both women from literature, and we have followed this trend with the other vessels of this class. Thus, we began following the "Oberth" scheme, and quickly changed to one consistent with the other known names.
Go to Oberth Technical File.
Our entry for the Pegasus-class is loosely based on what is seen in the footage. The weapons fit is based on scenes from 'The Volunteers' where we see three primary turrets and four very small, side guns. Aside from what could be found in the footage, no data on this vessel exists.
The Pegasus is seen operating with a solid rocket booster to achieve and break orbit. This would be inefficient for the REF whom would have to make repeated landings and take back off, so we decided the Pegasus would be restricted to the Southern Cross. This vessel must have some limited VTOL capabilities, as they are seen to make soft landings on the moon, where standard glide-style re-entries would be impossible.
Go to Pegasus Technical File.
The Predator-class is based on very brief footage of Transport Squadron 85 landing on the moon base seen in episode #54 ("Mind Game"), when a fleet arrives from hyperspace (originally, from Glory's sister colony of Liberty) to aid the Southern Cross. The show implicitly identifies this fleet as being from the Expeditionary Force, so we assigned the Predator to the REF and the Pegasus to the Southern Cross. Both vessels must have some limited VTOL capabilities, as they are seen to make soft landings on the moon, where standard glide-style reentries would be impossible because of the lack of an atmosphere. Aside from what is seen in the footage, no data on this craft exists.
Go to Predator Technical File.
Details on this aerospacecraft are very sparse,
forcing us to base almost all of our entry on speculation from animation footage and
one animation sheet with two views of this craft (one with an external fuel tank). There are squadrons of these shuttles advancing on a suborbital Mothership, leading us to speculate the EC-32 Eyrie configuration as well.
Go to Gossamer technical file.
The only information about this craft is wehat we can glean from the footage. All we can see is that five of the tugs are capable of lifting a Battle-class cruiser.
Go to Ox technical file.
This vessel is seen very briefly in episode #60, but is mainly seen in episode #47 ("Outsiders"), when a ship from the "SDF-3 Pioneer Mission" (which we have named the Hannibal) is seen to return under the command of Major John Carpenter to Earth. The vessel engages the Robotech Masters, and destroys one (and itself) by ramming. (In the original Southern Cross, this vessel was a border patrol vessel from the planet Liberty, Glory's parent/sister colony under the command of Major Lombard). The fact that this vessel was in service with the REF before the REF's departure for Tirol is evidenced by Carpenter's aide, who speaks of the ship as their home for the last fifteen years - this makes this ship's construction date around 2015. Most data in this entry is speculative, based on the limited footage available of the ship. A single animation sheet has been unearthed which provides a better view of the vessel.
Go to Tokugawa Technical File.
The Montgolfier-class tender is a speculative variant of the Tokugawa-class battlecarrier, based on the obvious logistical need for such a craft in the REF fleet. It is never seen in the show or source material, and is Pieter's invention.
Go to Montgolfier Technical File.
No data exists for these ships, aside from what can be seen in the footage. Hence, these entries are largely speculative.
Frames indicate a widely varying size for the
Southern Cross ships. As such, we used the size most consistent with the number of fighters that seem to be operating from the ships as well as the mission profile we think they use. We also try to estimate based on the most common views that include view ports from the bridge.
In our attempts to better figure out the Banshee, we came across a varying number of configurations. At times the bay protrudes from the bottom and other times, it barely does. Also, the side sponson turrets are not visible on all drawings, even when sufficient detail is in the drawing to suggest they should be present. This lead us to speculate different classes and the Gremlin was born, although Rob still disagrees due to the wildly varying images in Southern Cross. Pieter asserts the need for a long range patrol ship capable of sustained operations, and decided the Gremlin should be able to fill the role.
There is a clear picture of a twin barreled main turret with other single turrets with protruding barrels. All other pictures clearly show integral barrels. This lead us to speculate a weapons upgrade at some point in time. The other possibility is a retractable barrel, but no sensible reason could be given, so it was dropped.
Go to Banshee Technical File.
No data exists for these ships, aside from what can be seen in the footage. Hence, these entries are largely speculative.
Frames indicate a widely varying size for the Southern Cross ships. As such, we used the size most consistent with the number of fighters that seem to be operating from the ships as well as the mission profile we think they use.
We gave the REF vessels of this class as well, because the fleet seen to return to Earth from hyperspace in episode #54 ("Mind Game") includes vessels of this class. This also requires that the class predates the REF's departure for Tirol.
Due to the size of this ship, Pieter felt the rare designation of cruiser was most applicable. Also, there are frames that clearly show the two twin-barreled main deck turrets. Other footage shows a retractable PB-25 and PB-45. This led Pieter to speculate different variants including a different weapons mix, which is the up-armed battlecruiser variant. Rob is uncertain as to whether those weapons are all available on a single version.
Go to Battle Technical File.
No written data or animation sheets are known to exist for this class, and we have yet even to acquire a really good picture of the Tristar-class, because its extremely dark hull makes it hard to distinguish from the background in the footage. Hence, these entries are largely speculative, based on the footage.
The RPG appears to have completely missed this ship or has confused it with the Battle class. The Tristar-class is mainly seen in episode #53 ("The Hunters"), and Emerson's vessel is identified as the Tristar in this episode. The presence of a fold-drive on the Tristar-class is confirmed in episode #53 by the "Orbital Warp Blast", which employs a jump of the ship into hyperspace. Additional vessels of this class are confirmed by the characteristic diamond configured engine set passing the viewscreen the of the Tristar, as well as a pair of large cruisers in the final assault on the Robotech Masters in 'Catastrophe'. 'Love Song', episode#52, would have us believe there are at least 5 Tristar type vessels in Emerson's fleet.
Frames indicate a widely varying size for the Southern Cross ships. As such, we used the size most consistent with the number of fighters that seem to be operating from the ships as well as the mission profile we think they use.
We gave the REF vessels of this class as well, because the fleet seen to return to Earth from hyperspace in episode #54 ("Mind Game") includes vessels of this class. This also requires that the class predates the REF's departure on their search for Tirol. Based on the comments by Major Carpenter dating the service life of the Tokugawa class, and comments in 'To The Stars' about the RDF's lack of knowledge of the location of the Robotech Masters' homeworld, we decided it would be appropriate for a fleet of ships being available to scout out the location of the planet before the completion of the SDF-3.
Episode #53 displays a very full chin for the Tristar, while later footage indicates other vessels that the peak of the nose is not vertically centered. This led Pieter to hypothesize the Argonaut Missile Cruiser as a variant.
Go to Tristar Technical File.
No written data or animation sheets appears to exist for this class of ship, and the very existence of this Tristar-variant is predicated upon animation frames that show a significantly different
nose styling than the 'Tristar' commanded by General Emerson.
Pieter justifiable argued that the REF needed a
landing ship between the sizes of the Tokugawa-class and the small Predators, which
aren't capable of landing heavy artillery mecha. Since we had a Tristar variant, Pieter decided to make this ship be his missing landing ship, since it was the appropriate size. Rob was the dissenting vote feeling it was probably just a Tristar variant with reduced long-range capabilities to support local system defense, instead of the additional features that would have been included in a ship designed to help scout for the Robotech Masters homeworld, but was overruled.
Frames indicate a widely varying size for the
Southern Cross ships. As such, we used the size most consistent with the number of fighters that seem to be operating from the ships as well as the mission profile we think they use.
Since the Southern Cross has little need for space-borne landing ships, this class is considered REF-only.
Go to Argonaut Technical File.
No reliable written data on this vessel is known to exist; it is not even seen in its entirety in that portion of the Sentinels footage that was completed. Most of the information is based upon the animation sheets reprinted in Palladium's REF Field Guide and Eternity's Illustrated Handbook. Most of the data in this file is speculation,
based upon these drawings.
We chose to name this vessel the Pioneer after the reference in episode #47 ("Outsiders") that mentions the "SDF-3 Pioneer Mission" - because of this reference, we thought naming the SDF-3 the Pioneer would be an amusing play on words.
Macek's plan was to describe the SDF-3 as
appearing like the Macross did prior to its arrival on Earth. However, this is never mentioned as the intent of the REF in the Sentinels video, where it is merely described as being "wrapped up in the shell of a Zentraedi battlecruiser". Similarly, the footage indicates that the Macross appeared before its arrival much the same after its refit on Earth. Hence, a rare class of Zentraedi ship, intermediate in design between the Zentraedi monitor and the Macross was hypothesized, and the SDF-3 was
supposed to be based upon it.
We disagree with the RPG about the "cannon arms"
of the SDF-3. The antennae on the arms do not appear to be traversable, and aren't straight, like one might expect a weapon barrel to be. Furthermore, the arms themselves look to have a limited traverse, if one at all. We have chosen to make the appendages to the "arms" sensors.
Go to Pioneer Technical File.
Aside from a pair of animation sheets, no hard data on this vessel is known to exist. We have but one wireframe picture from which we have speculated, and a size comparison chart that gives its length. Most of the data in this file is speculation, based upon this drawing, and the need for escort vessels for the SDF-3.
Because of the shape of the body in comparison to the Pioneer, we decided this would be a smaller, single reflex cannon fleet ship for the Pioneer mission.
Go to Valivarre Technical File.
Almost no written data on this ship exists, though there are several animation sheets and the footage from which we could work in developing this craft.
The RPG's crew and complements are unreliable; we have based ours upon inspections of the footage. Similarly, the RPG's claim that Beta egress is possible while docked is in error, for the reasons given in the file.
The presence of anti-gravs are speculative, meant to explain the lack of VTOL thrusters on this craft; without them, it could neither land nor take off. Similarly speculative are the details of the interior spaces, which are only sketchily dealt with in the source material and footage.
The C3I bunker is speculation on
Peter's part, as are the uses of the Alpha bay onboard ship and on a planetary surface.
Go to Horizont Technical File.
Almost no written data on this ship exists, though there are several animation sheets and the footage from which we could work in developing this craft.
The Japanese source material gives the length of this ship to be 180 meters. We have retained the primacy of the source material on this matter, and have scaled up the troop and mecha complements from the RPG's numbers accordingly. The source material also indicates that the ship only carries 9 Legioss, yet in one of the first scenes in Episode #61, we see one launch 12 Alphas.
The tri-barreled gun is larger than the secondary guns on the SDF-1; as such, it should have similar - if not superior - yield. We have reflected this in our files.
The presence of a fold drive on this relatively small vessel was prompted by the reference by the narrator to the vessel as "hyperDimension" in episode #78 ("Ghost Town").
Likewise, the dialogue of episode #78 requires that the first vessels of this type have been in service during the war against the Robotech Masters; the one in this episode probably came to Earth in the relief expedition hown in the episode #54 ("Mind Games"), though it is obviously not seen in the footage.
We have renamed the vessel - and described all the members of the class, in an attempt to give it the feel of a true naval vessel. All of the names and dispositions are speculative.
Go to Garfish Technical File.
The Marathon-class is a speculative variant of the Garfish-class destroyer. It is never seen in the show or sources, but was created by Pieter to fill the obvious logistical need for a transport vessel for the REF.
Go to Marathon Technical File.
Almost no written data on this ship exists, though there are several animation sheets and the footage from which we could work in developing this craft.
The addition of turrets on the ventral hull and a main gun in the nose for later refits of this vessel are purely speculative. We have followed the RPG with regard to the armament otherwise, as well as large parts of the description of the internal arrangement.
The B-Club Special#9: ARTMIC Design Works
lists the length of this vessel at 300 meters, and the Gakken file for Animeca lists it as 350 meters long. However, a close examination of the ratio of the lengths of the Alpha launch bays on the sides of the hull to the width of the Alpha from the animation sheets, combined with an analysis of a side-on view of the vessel to yield the total length (sans engine fins) as a ratio of the bays requires that the vessel's total length be somewhere in the 650 to 750 meter range. I felt that 700m is most consistent with the footage. This has been a controversial decision, though we stand by it - the footage simply does not agree with either Palladium or the written Japanese source material.
All of the names and dispositions
are speculative
Go to Ikazuchi Technical File.
Again, very little data on this vessel exists. It took us a long time to even find a picture or frame on the footage that shows the external arrangement of this vessel from the point aft of the command bridge tower. Hence, almost all of the data in this file is speculative.
The Gakken File for Animeca source lists the length of this vessel as 500m. However, it is clearly larger than the Ikazuchi, and because of the error in the size of the Ikazuchi as listed in the source material, we have been forced to scale up the size of this vessel as well. The Sentinels source material (in a picture provided by Alex Fauth) agrees with our estimation of the length. All of the names and designations of the vessel, save for the class name, are speculative - holy cities were chosen since Izumo is known mainly as one of the holiest sites in Shinto.
Go to Izumo Technical File.
Aside from what we see in the footage and one animation sheet, we have been able to gather no data on this awesome weapon, and our entry is purely speculation. The size was arrived at by the observation that Ikazuchi carriers were attached to the missiles during the early stages of launch. The warhead yield was arrived at by calculating the volume of the warhead, and estimating a relatively efficient thermonuclear weapon with that volume.
Go to Neutron S Technical File.
No written data on this vessel exists. We have based our entry mainly on the footage, though most of the file is speculative.
Go to Tirolian Mothership Technical File.
No written data on this vessel exists. We have based our entry mainly on the limited footage, though most of the file is speculative. This ship is seen under Zor's command when he scouts out the SDF-1 crash site early on and later appears to be accompanying a fleet pursuing General Emerson's Tristar on its way to the moon. This led Pieter to speculate its use as a fleet tender and tanker.
Go to Tirolian Transport Technical File.
No written data on this vessel exists. We have based our entry mainly on the limited footage, though most of the file is speculative. The presence of a Reflex Cannon on this vessel is confirmed in Episode #60, Catastrophe, when the nose of this vessel is seen to fire on the Southern Cross' military headquarters in Monument City.
Go to Tirolian Taul Detrel class Destroyer Technical File.
We were not overwhelmed with data on the Macross
from the source material, but the situation was far better than for any other class of ship in the Robotech universe. The length was gleaned from the source material, but the other dimensions were acquired from side- and top-view drawings of the vessel.
The brief footage we see of the Macross prior to its collision on Earth reveals very few differences with its appearance after it is refit by the RDF: the command tower and sensor set atop the citadel attached to the main body appear to be missing, and the hull is a dark gray.
The artists for the original Macross have apparently since rethought the pre-crash Macross' design, and several pictures of it exist. The engine sections are taller, and the main gun booms thinner, with some sort of lump on the upper surface, mid-way from fore to aft on the booms. As this is not the vessel portrayed in the footage, we have neglected these versions in favor of the version that is: namely, a virtual copy of the post-refit vessel.
It is widely supposed that the Macross was unique and that it was designed by Zor himself. This conventional wisdom is not supported anywhere in the TV series or Sentinels video, and is unlikely in any case. Zor is supposed to be mainly a biologist - we can infer this from his discovery of the details of the Flower of Life, and from the importance of
cloning in the technologies he developed. To make him a spacecraft engineer as well seemed absurd. Furthermore, the ship was not special in and of itself either in Macross or Robotech. In Macross, the Macross was merely the Inspection Army's version of the Zentraedi Cannon Ship (aka Monitor).
By making the Macross one of a few prototypes of a new class of Border Fleet Battlefortress, we have expanded upon the naval history of Tirol, as well as tending away from the "fannish" nature of the conventional wisdom's version of the Robotech milleu. The Border fleet was generated in an attempt to find a parallel to an Inspection Army that oversees the Zentraedi troops. This was viewed to be a mixed Tirolian/Zentraedi force that polices the Zentraedi forces as well as protecting those areas the Masters did not trust the Zentraedi alone to handle.
Go to Macross Battlefortress Technical File.
This is the proposed vessel upon which the Pioneer class SDF was based. Most of the information is based upon the animation sheets reprinted in Palladium's REF Field Guide and Eternity's Illustrated Handbook. Tthe data in this file is entirely speculation, based upon these drawings and our concept that the SDF-3 was attempting to mimic a Border Fleet vessel.
Macek's plan was to describe the SDF-3 as
appearing like the Macross did prior to its arrival on Earth. However, this is never mentioned as the intent of the REF in the Sentinels video, where it is merely described as being "wrapped up in the shell of a Zentraedi battlecruiser". Similarly, the footage indicates that the Macross appeared before its arrival much the same after its refit on Earth. Hence, this vessel was proposed as the rare class of Border fleet ship, and the SDF-3 was
supposed to be based upon it.
We disagree with the RPG about the "cannon arms"
of the SDF-3. The antennae on the arms do not appear to be traversable, and aren't straight, like one might expect a weapon barrel to be. Furthermore, the arms themselves look to have a limited traverse, if one at all. We have chosen to make the appendages to the "arms" sensors.
Go to Sian Dereta Technical File.
Aside from a pair of animation sheets, no hard data on this vessel is known to exist. We have but one wireframe picture from which we have speculated, and a size comparison chart that gives its length. Most of the data in this file is speculation, based upon this drawing, and the need for a similar Border fleet vessel to serve as the model for the escort vessels for the SDF-3.
Because of the shape of the body in comparison to the Pioneer, we decided this would be a smaller, single reflex cannon fleet ship for the Pioneer mission.
Go to Seron Thoun Technical File.
This is the proposed vessel seen by Breetai and folks on their way to capture the Factory Satellite. Rob performed some hypothetical image reconstruction on it and we extrapolated from there. There was disagreement from the team whether the vessel should be a spade-like shape similar to the Thuverl Salan or is a twin boom design. Majority opinion went with the spade design.
Functions extrapolated from the shape of the vessel and the proposed mission profile.
Go to Tou Salaam Technical File.
The 'Tiluvo' is the best known version, the Tirolian Bioroid assault vehicle of choice. It is seen often in the series. The 'Luhoutzs' command vehicle is seen only once. It is the corvette in the episode 'Clone Chamber' blown up as the last act in the fighting. The 'Lihinal' gunboat too is seen only once, as it fires its bombardment weaponry in the one-but-final episode of the SC segment. The names of all and the armament of the 'Lihinal' variant are speculation only.
The 'Quel' ECM carrier is also based on the episode 'Clone Chamber', in which the Tirolian force closes with the Terrans without them detecting so until very close by. It also appears that the Tirolians were in at least three task forces, the only ships seen with all forces are the Roil craft. In the Macross segment Khyron had to 'get the ECM in place' in episode 'Bursting Point', and he does not use starships for that task, so it appears as if the ECM can be loaded into smaller craft. However, while implicated, the esistance of such a variant is not unequivocally seen in the footage. The name and equipment are therefore pure speculation.
The Roil Destrin is a Border Fleet variant, meant for Tirolian crew and Zentraedi troops. The 'Tiluvosen' is an intended Zentraedi version that the Masters never got into production because their protoculture was running out on them. Finally, the Listradin is an unarmed, civilian version. These three versions are complete speculation, but they sound plausible.
Virtually no hard data on this aerospacecraft exists. TIA#10 refers to this as a small spacecraft. The 'My Anime' insert refers to it as a 'Landing Frigate'. The dimensions and general weapons fit were taken from the footage and animation sheets. While previouis version were primarily based on the RPG entry, the '99 version tries to base more on the footage and source material. The presence of Reflex Cannons on this vessel is confirmed in episode #60, when the cannons to either side of the nose of this vessel are seen to fire on the Southern Cross' headquarters in Monument City.
Go to Assault Corvette technical file.
Nupetiet-Vergnitzs flagship
Quaedol-Magdomilla battlecruiser
Thuverl Salan cruiser
Quiltra Queleual landing ship
Rineunadou Lojmeuean monitor
Tou Redir scoutBeyond the vessel sizes and appearance, and the
basics of the
weapon systems (but not their number on each ship), little data on these vessels exists.
Hence, most data is speculative. The name of the Zentraedi flagship follows that given by later source material,
and not Macross: Perfect Memory, which neglects the 'g' in
'Vergnitzs' (in our own internal discussions, the "g" is an uvulazitaion of the "n", and because of the ambiguous romanization, is probably written with a diacritical in Zentraedi).
The "odd" vessels are based on footage of them seen
in
episodes #29 (the old Cruiser) and #30 (the Exploration Cruiser, in Macross
apparently the Inspection
Army's equivalent of the Thuverl Salan).
Based on episode #27
("Force of
Arms") we have concluded that the only ship with a Reflex Cannon is the Monitor
(aka "Cannon Ship"), contrary to the RPG sources' claims.
Go to Flagship Technical File.
Go to Strike Cruiser Technical File.
Go to Landing Ship Technical File.
Go to Cruiser Technical File.
Go to Monitor Technical File.
Go to Scout Technical File.
Zentraedi Fulbtzs Berrentzs class Home BaseRobotech Factory
SatelliteTBD
TBD.
Go to Dolza's Command Base Technical File.
Go to Robotech Factory Satellite Technical File.
Though the Japanese source material, especially
Macross: Perfect Memory, is not exactly overflowing with information about this mecha, the basics, such as the dimensions and weapons fit, are amply described. The rest is speculation on our part. Some of the Zentraedi/Tiresian names for the mecha were our invention, though most were from the source material.
Go to Quel Qualie technical file.
Though the Japanese source material, especially
Macross: Perfect Memory, is not exactly overflowing with information about this mecha, the basics, such as the dimensions and weapons fit, are amply described. The rest is speculation on our part. Some of the Zentraedi/Tiresian names for the mecha were our invention, though most were from the source material.
Go to Re-entry Pod technical file.
As little is known about this ship as is known about the Enforcer mecha. Hence, the description (beyond mecha complement and physical appearance) is mainly speculative. Source material indicates a size of 150m and the ability to transport 480 boostered Iigaa. The possibility of fold-drives on this vessel is based upon visuals from the Sentinels video.
Go to Mollusk Technical File.
This entry is speculated based on the footage of the invid invasion and to try to explain how the invid hives came to Earth.
Go to Mobile Hive Technical File.
Go to the Robotech Reference Guide Home Page.
Robotech (R) is the property of Harmony Gold, © 1985. The Robotech Role-Playing Game is the property of Palladium, Inc. This document is in no way intended to infringe upon their rights.
Content by Pieter Thomassen and Peter Walker, and Robert Morgenstern