A Mamba Minesweeper. The Andromedan M&M. The perfect shape and a green one at that!

Seriously though, give it mine racks from which it transports the t-bombs out. It can drop one out the hatch at the shuttle launch rate or transport them. NO NSMs! It's way scary enough!

By Scott Tenhoff (Scottt) on Wednesday, August 13, 2003 - 02:49 pm: Edit

(R10.??) Andromedan Augmentation Modules
History:
Once the Andro's began their full-scale invasion of the Alpha Quadrant, they found out that their ships were to 'hard-wired' for missions, and could not quickly adapt them to surprise situations. The Andromedans came up with a plan that could be used two ways. One way was to dock these modules onto their Satellite bases to improve them and give them more capabilities, the other, for the same modules to be carried by Motherships to enable the mothership to be reconfigured easily for special missions. Thus allowing a Mothership to show up at a Satellite Base and take a module that had been mated to the base, then leaving with it, being more capable for the upcoming mission.

What this entailed was to take the basic Viper disk, (without engines) to use the hollow shell, and then install the necessary equipment to for each mission required. These Modules would take the place of the normal Cargo Module on the Sat Base, or 3/4 of a hanger space on a Mothership. If need be, some of these modules could be deployed by themselves into space and act as miniature Stations (equivalents to Commercial Platforms for Alpha Quadrant races).

There is more then listed here (but just haven't been created or imagined yet)

Any Satellite Base (or Base Station/Battle Station) with these augementation modules would labeled as SatB-I, BS-RD, BATS-RDII, etc.

Rules:
1) PA Costs: All PA Costs of these units are 3 reinforced, 1 unreinforced. If any of these modules are mated with a Satellite Base, the Satellite Base's PA cost is raised to the sum of all augementation modules+base cost of the original base.
2) PA Limitations: Because of the design of these Modules, only 2 PA Panels may be active while inside a Mothership. While docked externally to a Satellite Base or deployed independtantly, all 4 will work normally. (Designer's Note: This is to insure that they are not used as EM-S's which have 6 PA Panels, and these must absorb significantly less than them. The other choice would be to have 2-3 360deg PA panels)
3) These units may, once beamed into proper position, pay 1 AWR power to begin an Orbit (rule ____) around any planet.
4) These are all considered SC 4 units, but gain the small target modifier of being Nimble (even though they don't move).
5) All of these would have, Sensor 60, Scanner 09, Damage Control 20, and 2 Excess Damage.

Types of Modules:
Invasion Support Module. (I-Module)
This module was mostly seen as changing a Conquistador or Intruder to a mobile Beachhead creator against planets, where a Rattler or Diamondback was used more against mobile targets or when going on unknown missions where versatility was required. It served as Troop Transport Pods did with other Galactic Races. It may be used from within the Mothership, augementing the Mothership's facilities, or deployed to the planet to offload it's contents, or beamed into orbit for it to conduct it's own landing operations independantly from the Mothership.

SSD:
5 Transporter
4 Cargo
4 Barracks
2 CHULL
4 AWR
2 BATTS
1 Emergency Bridge
2 P-2 (1 LS/1 RS)
4 PA Panels (2FH, 2RH)

40 BPs, 12 GCV


Repair Augementation Module. (R-Module)
This module was designed to allow a Satellite Base to quickly repair Satellite Ships. It carried one transporter that could beam any Sat Ship to the exterior of the hull, for robots to immediately begin working on it. When this (and only this module's) Transporter beams a Sat Ship to the base, it may dock it at either of the Tractor Locations. 32 impulses after the Sat Ship has been beamed aboard, repairs may begin on it. Sightings have occurred of 1 or 2 of these Repair Modules with 1-2 Cargo Sleds and a Fabrication Module, acting as a Repair Point for Andromedan raiders. When deployed inside of a Mothership, this module may repair any other Satellite Ship in the Hanger with the Module, effectively adding it's repair capacity to the Motherships.

SSD:
1 Transporter
2 Tractors (one at opposite sides of the disk)
8 Repair
4 Cargo
1 Emergency Bridge
4 AWR
2 BATTS
4 PA Panel (2FH, 2RH)


Deep Space Survey Base. (D-Base)
This small base became a monitoring-type station, observing and watching the Galactic Powers military units, commerce units, and gathering of information. These were NOT part of the RTN and in no way connected to it, but isolated posts which were usually hidden to constantly watch their targets. These could be mated with a Satellite Base, making it a formible base to assault, giving it additional defensive weapons, it would not increase any Temporal Elevator costs. Only one of these may be deployed to each Satellite Base, as this is a design limitation of connecting the bases together (the shock of TRL beams firing). But, for Base or Battle Stations, it would be for each Satellite Base 'Section', would have to have one (for balance purposes), or the Core could have one if only one was deployed.

SSD:
1 Special Sensor
1 Probe
3 TRL (FA+L, RS, R+RA)
1 Emergency Bridge
4 PA Panel (2 FH, 2RH)
4 P-2 (2LS, 2RS)
10 AWR
4 BATTS
4 CHULL

Fabrication Modules. (F-Module)
This module provided the "works" to transform any ores retrieved by Cargo Sleds into the refined materials needed for repairs of Andromedan Combat Units. They were most often found near rich deposits that were extensively mined. Some (or multiple) were placed down on captured planets to quickly process the stripmined materials for transport away by King or Queen Snakes.

SSD:
3 Transporters
6 Works (hit on hull)
4 Chull
1 Emergency Bridge
6 AWR
2 BATTS
1 Tractor
2 PA Panels (FH/RH)

By Mike Raper (Raperm) on Monday, June 14, 2004 - 08:11 pm: Edit

Sigh. Probably shouldn't post this, but what the hell.

R10.?? Andromedan Hydra Fighter Carrier

I know, I know...there's no such thing as Andro fighters. But, I had this idea that if there were such a thing, this might be what they'd be like. Consider it a threat-file ship, and in no way historical at all.

Now, a few rules:

Andromedan Fighters

Andromedan ships carried a variety of satellite ships, but no data on a true Andromedan carrier was ever discovered, nor was anything like a galactic fighter-shuttle ever observed in use by the invaders. However, this didn’t stop Star Fleet, and others, from worrying about them. The Federation’s Andromedan Thread File included a hypothetical carrier ship, dubbed the Hydra class. This ship was equipped with a single squadron of very maneuverable and powerful little fighters, called Thread Snakes.

Shuttle Bays

Each shuttle bay box can carry or dock by transporter, similar to (G19.41) with a cost of 1 energy point per fighter. Each box carries one single space fighter. As with other galactic carriers, any hit on the shuttle bay will hit fighters in the bay, if they are on the ship. Fighters may be launched via the carrier’s displacement device (G19.42), though they may not launch with their own even when equipped with one. Only the carrier can launch its fighters via transporter; other ships cannot do this. Fighters cannot dock in standard Andromedan hangers.

Fighter Displacement Devices

Andromedan fighters do not carry heavy weapons or drones, but they do carry a small, single-use displacement device. Other than the differences noted below, these operate exactly as a full-size Displacement Device (G18.0).

Arming: The fighter DisDev costs 2 points to arm. This power may come from any source, and can be allocated over one or two turns at the owning player’s discretion. They can be held at no cost.

Procedure: A fighter DisDev can only be used for self-displacement (G18.322) of the fighter in question. Use the procedure outlined in (G18.51) to determine success, but when determining range, subtract one from the die roll.

R10.??: Andromedan Thread Snake Fighter: The Thread Snake is comparable to the top line galactic fighters such as the Federation F14 or Hydran Stinger in speed and maneuverability…in fact, they are a bit faster. They are armed with a forward and aft phaser-2, which gives them surprisingly hefty punch. However, this is offset by the total lack of drones or other fighter heavy weapons. They operate as fighters in most every other respect.

That seems nasty enough to me; displacing fighters armed with P2's. Just imagine the hell they could raise, if they got close enough.

By Robert Cole (Zathras) on Monday, June 21, 2004 - 03:06 pm: Edit

MWP COMMAND STATION (MCS): The MWP Command Station was a small base which could dock 6 Multi-Weapon Platforms in external "slots" (not represented on the SSD; MWPs dock to this unit externally using the normal docking procedures).

The MCS appears to have been a local defense facility; placed in locations where a full Satellite Base was deemed unnecessary (but then, who can really say what determined Andromedan base deployments); often in conjunction with a mining operation (such as an asteroid field). While not enough to stop most attacks, an MCS and its MWPs was often enough of a delay that heavier guns could arrive and run off or destroy an attacker.

MWP Command Stations were rarely deployed individually; 3 could be expected, though in one case 5 were encountered in the same asteroid field. The MCS did not act as an RTN Node, which may explain why they were placed in locations the RTN couldn't easily go anyway (asteroids are killers at warp 14).

MWP Command Stations can be carried in an Andromedan Mothership's Hanger and are considered a Small Satellite ship. MWPs cannot be docked to an inactive MCS. The MCS cannot use the MWP Augmentation Module (R10.55) due to its size. Note that while an MCS can be deployed during a scenario it cannot be activated without its positional stabilizers (which cannot be activated during a scenario).

Designer’s Note: Yes, a Satellite Base + MWP Module is better, or perhaps an MWP ground base on a large asteroid. However, I’m sure there are times / places where an RTN node is not the best idea (which means a SatBase can’t use its full capabilities). I’m also sure there are times / places where there are no nearby planetoids large enough for a ground base.

This idea was partly inspired by Loren Knight’s Copper Head and Snake Pit, and partly by a ship to be in R8.

- Ship designed by Robert Cole

By Robert Cole (Zathras) on Tuesday, September 28, 2004 - 10:23 pm: Edit

I have a slew of Andromedan designs, but one that would be interesting from a campaign perspective is this:

(R10.RC3) DEVIATOR (DVT): These massive ships provide a mobile repair / construction dock for the extra-galactic invaders. Though none were ever encountered within the galaxy, at least two were reportedly destroyed during the fiasco that was Operation Unity.

Mounting few phasers and PA Panels, and NO offensive weapons, the Deviator proved a fairly easy kill. At least it would be if encountered alone. Unfortunately, these ships were protected fanatically, and were often very close to an RTN node... which allowed escape (even at it's much slower speed).

It should also be noted that the hull found (code named Devestator) after the destruction of the Andromedan Starbase may have actually been another Deviator. However, Federation analysts believe the much larger warp engines on that ship meant it was in fact a warship (instead of a mobile construction dock).

- Ship designed by Robert Cole

By Joseph R Carlson (Jrc) on Sunday, July 17, 2005 - 11:36 pm: Edit

In CL31 SVC discussed possible future options In "Proposal Board" page 33. One though was the Andros set uo shop in the LDR.

NEW ANDRO OPS BASE
For the Andros to conduct operation they need a way to set up an RTN that is less subject to destruction. While they can't hide there signature perhaps they could develop a displaceable operations-style base, similar to the Galatic versions.

The base( core and two satelite base modules) are attached (hard welded) to a variant of the intruder (modified Infestor).

The route are still presurveyed and I suppose are a like spider web. Where routes intersect or where the base nodes used to be located the OPS base might be. The Ops base can, when enemy ships approach displace away along a number of routes.

The other unit would be a displacement beacon ship based on the Python, which is also a large satellite ship. The Ops base can carry 2 Pythons and 3 medium sat ships (6 hangar boxes).

Any comments?