star trek armada species 9341

Species 9341

Species 9341 Mother Entity and Spawned Entity by Captain_Reisen Remember those squirmy, wormy creatures from the third Borg mission in Armada I? Well, they�re back with a vengeance and allied with Species 8472 (yeah, I know the real Species 8472 wouldn�t ally themselves with inferior lifeforms but as they�re both completely organic, why the heck not?) If you have a mod already installed and wish to include this in that mod, I have provided a means to do so (no new gui_global.spr, no new tech1.tt; instead, I have lines for you to copy and paste into those files, thus leaving any other game mods intact) If this messes up your game, tough luck. Nah, just kidding, simply uninstall the files and delete the offending lines. What�s included in this zip: 1. all necessary .odf files (zmama.odf, zentity.odf, gnttblst.odf, and nttblst.odf) 2. all SODs needed (zmama.sod and zentity.sod) 3. all textures needed (Z_mama.tga, zentity.tga, MamaW.tga, EntityW.tga, gbzmama.tga, gbzenity.tga) What�s not included 1. Admiral�s log pictures 2. AI support (for the AIPs) Installation 1. Place the .odf files in their respective folders (ships in Ships, gnttblst.odf and nttblst.odf in Special Weapons) 2. Place the SOD files in the SOD folder (duh) 3. Place the textures (the .tga files) in the RGB subfolder of the Textures folder Tricky parts 1. In the gui_global file, add the following lines underneath the last build item of Species 8472 (NOTE: gbzenity is not a misprint): b_zmama gbzmama 0 0 64 64 b_zentity gbzenity 0 0 64 64 2. In the same file, scroll down to the last Species 8472 wireframe and add the following lines: @reference=128 @tmaterial=interface zentityw1 EntityW 40 0 40 40 zentityw2 EntityW 0 40 40 40 zentityw3 EntityW 40 40 40 40 zentityw4 EntityW 80 0 40 40 zentityw5 EntityW 0 0 40 40 zmamaw1 MamaW 40 0 40 40 zmamaw2 MamaW 0 40 40 40 zmamaw3 MamaW 40 40 40 40 zmamaw4 MamaW 80 0 40 40 zmamaw5 MamaW 0 0 40 40 In your techtree folder, open the tech1.tt file and scroll down to the last Species 8472 ship and add: zmama 0 zentity 0 Open the regular ODF folder, select the Ships subfolder, and open the 8472_passive.odf file (make sure read-only is off for this file or you�re gonna have some trouble) Scroll down to the last build item (should be: buildItem5 = �8472_mothership�) and add the line: buildItem6 = �zmama� (as zmama builds zentity, the Passive embryo doesn�t need to build the entity) Credit where credit is due: Captain_Reisen (me!) for the .odf files The folks at Activision for the buildbuttons, the SODs, and the original textures Chu�Yu Chen for his excellent Species 9341 wireframes Friendly advice 1. Don�t alter the SOD size of these files (animated SODs, being composed of multiple segments, can only have the non-animated portions enlarged�this makes the animated parts look much smaller) 2. Be careful not to build too many Spawned Entities too quickly (they may be cheap, but they add up rapidly and given the tenuous nature of resource supply for Species 8472, it�s not a good idea to deplete your biomatter stores) 3. The Spawned Entities are weak creatures but readily replaceable�they make good scouts but they will not detect cloaked vessels

Comments  

Commenting is currently disabled.

Memory Beta, non-canon Star Trek Wiki

A friendly reminder regarding spoilers ! At present the expanded Trek universe is in a period of major upheaval with the continuations of Discovery and Prodigy , the advent of new eras in gaming with the Star Trek Adventures RPG , Star Trek: Infinite and Star Trek Online , as well as other post-57th Anniversary publications such as the ongoing IDW Star Trek comic and spin-off Star Trek: Defiant . Therefore, please be courteous to other users who may not be aware of current developments by using the {{ spoiler }}, {{ spoilers }} OR {{ majorspoiler }} tags when adding new information from sources less than six months old (even if it is minor info). Also, please do not include details in the summary bar when editing pages and do not anticipate making additions relating to sources not yet in release. THANK YOU

• View history

• 1 Description
• 2.1.1 Mission 1: "Premonitions"
• 2.1.2 Mission 2: "Paradise Revisited"
• 2.1.3 Mission 3: "Vendetta"
• 2.1.4 Mission 4: "Dark Omens"
• 2.2.1 Mission 5: "To the Gates of Sto'vo'kor"
• 2.2.2 Mission 6: "The Enemy Within"
• 2.2.3 Mission 7: "A Good Day to Die"
• 2.2.4 Mission 8: "Gray Eminence"
• 2.3 Romulan Campaign
• 2.4 Borg Campaign
• 2.5 Omega Campaign
• 3.1 Characters
• 3.2.1 Species 9341 ships
• 3.2.2 Borg ships
• 3.2.3 Breen ships
• 3.2.4 Cardassian ships
• 3.2.5 Federation ships
• 3.2.6 Ferengi ships
• 3.2.7 Jem'Hadar ships
• 3.2.8 Klingon ships
• 3.2.9 Romulan ships
• 3.2.10 Son'a ships
• 3.3.1 Borg stations
• 3.3.2 Cardassian stations
• 3.3.3 Dominion stations
• 3.3.4 Federation stations
• 3.3.5 Ferengi stations
• 3.3.6 Klingon stations
• 3.3.7 Romulan stations
• 3.4.1 Planets and planetoids
• 3.4.2 Stars and star systems
• 3.4.3 Stellar regions
• 3.5.1 Nebular classification
• 3.5.2 Technology and weapons
• 3.6 Races and cultures
• 3.7 States and organizations
• 3.8 Other references
• 4.1 Related media
• 4.3 External links

Description [ ]

Summary [ ], federation campaign [ ], mission 1: "premonitions" [ ].

The USS Enterprise -E, accompanied by two Akira -class ships, must eliminate rogue Jem'Hadar attack ships in the sector, in order to secure colonization efforts. A construction ship is also present to build a permanent outpost in the system. Once all Dominion ships are destroyed, a temporal vortex is detected, and a Starfleet vessel emerges, pursued by two Borg spheres. Picard recognizes it, like he has seen it before. The vessel identifies itself as the U.S.S. Premonition , and its CO, Captain Thaddeus Demming, informs Captain Picard that a major Borg invasion is imminent. Within the hour, a force of Borg ships will attack and destroy Starbase 612, the first step to the assimilation of the Alpha Quadrant.

Mission 2: "Paradise Revisited" [ ]

Ambassador Worf, on temporary assignment to the Ba'ku settlement, and commanding the U.S.S. Avenger , must eliminate a force of Son'a warships intent on reclaiming the planet. He receives word of the Borg invasion, and heads to Qo'noS to gain reinforcement.

Mission 3: "Vendetta" [ ]

En route to Qo'noS, Worf is ambushed by Toral, and a small force of Klingon warships. Outgunned, he must traverse the Ikolis Expanse, a hazardous region of space, to escape, salvaging derelict vessels and even a Federation Starbase and Shipyard to assist along the way. In order to prevent Toral seizing the Klingon throne, Worf takes the Avenger to the location of the Sword of Kahless.

Mission 4: "Dark Omens" [ ]

The Enterprise arrives at Starbase 612, only to find its defense fleet in ruins and most of the station's facilities heavily damaged. The player must salvage as many ships as possible, and bring local stations back on-line in order to repel a second wave of attack, including an assault by assimilated Starfleet vessels, and eliminate the local Borg base.

Klingon Campaign [ ]

Mission 5: "to the gates of sto'vo'kor" [ ].

The Borg have struck at Klingon territory as well. Chancellor Martok must lead an assault on a Borg force attacking the Gamma Eridon system. Once the Borg have been eliminated, Martok heads for his command base to find out why expected reinforcements did not appear.

Mission 6: "The Enemy Within" [ ]

Having escaped from Worf in "Vendetta", Toral has assembled a formidable fleet, and launches an assault on Martok's starbase. The base must be held until the Avenger arrives, when Martok evacuates to the Defiant -class vessel, and leaves the sector, bound for Qo'noS, to present the Sword of Kahless to the Klingon High Council.

Mission 7: "A Good Day to Die" [ ]

Qo'noS is embroiled in conflict as Martok arrives aboard the Avenger . Worf's vessel is refitted with a cloaking device, and dispatched to trail Toral. Martok must attack and destroy Toral's main base. Toral manages to escape the attack, with Worf in hot pursuit...

Mission 8: "Gray Eminence" [ ]

Continuing from the end of "A Good Day to Die", Toral escapes to a Romulan base near the border. Martok's fleet follows behind, and launches an assault to clear the sector of all Romulan presence. With Toral and the Romulans routed, Martok announces that this is only the beginning of a larger war with the Romulans.

Romulan Campaign [ ]

Borg campaign [ ], omega campaign [ ], references [ ], characters [ ], starships and vehicles [ ], species 9341 ships [ ], borg ships [ ], breen ships [ ], cardassian ships [ ], federation ships [ ], ferengi ships [ ], jem'hadar ships [ ], klingon ships [ ], romulan ships [ ], son'a ships [ ], stations and outposts [ ], borg stations [ ], cardassian stations [ ], dominion stations [ ].

Dominion cloning facility • Dominion research facility • Dominion Shipyard Station Alpha ( Dominion shipyard )

Federation stations [ ]

Ferengi stations [ ], klingon stations [ ], romulan stations [ ], locations [ ], planets and planetoids [ ], stars and star systems [ ], stellar regions [ ], science and classification [ ], nebular classification [ ], technology and weapons [ ], races and cultures [ ], states and organizations [ ], other references [ ], appendices [ ], related media [ ].

• ST video game : Armada II
• " The Best of Both Worlds " ( TNG episode)
• " The Sword of Kahless " ( DS9 episode)
• " The Omega Directive " ( VOY episode)
• Section 31: Cloak ( TOS novel)

External links [ ]

• Armada article at Memory Alpha , the wiki for canon Star Trek .
• Gamespot.com review
• Gamespy.com review
• 1 Achilles class
• 2 Ferengi Rules of Acquisition
• 3 Odyssey class

Big, Giant Space Creature

I’m looking to see if anyone has any good ideas for a big, giant space threat creature. Something comparable to a Crystalline Entity or Fargate Jellyfish alien. (I want to break away from constant call-backs to various episodes for an adventure).

Has anyone conceived of a good threat monster that’s nicely different than ones we’ve seen before?

An episode of my campaign was set in an alternate future where people lived on the inside of a Dyson Sphere. They only existed as a feeding ground for a number of crystalline entities.

Star Trek Armada introduced Species 9341. They were unsuitable for assimilation, that’s way they were eradicated by the Borg. But they could be potentially valuable if one could discover a defense against assimilation.

The Star Trek: Titan novel “Orion’s Hounds” features several cosmozoans, including the Jellyfish species which is used by other aliens as spaceships.

I thought about a cosmozoan which lies dormant in space until a planet has formed around it. Then it feeds on the life on its planet somehow, killing thousands of people each day. I thought this would be an interesting dilemma for a crew.

In one of Iain Banks’ Culture novels, there are Coty-sized creatures called Behemothaurs, which have entire ecosystems inside them.

Something like that might be interesting.

One of the earliest Star Trek adventures I gamemastered a quarter of a century ago was about a gigantic could creature consisting of complexe organic molecules on lead basis which was destroying colonies on both sides of the neutral zone in early 2270s (TMP era). The crew of the completely overhauled USS Reliant had to find a way to stop this creature before it destroys more colonies. They did this by constructing a special torpedo.

What about a creature that feeds on stars, e.g. entering an orbit, collecting solar radiation and emitting some radiation that is dangerous / deadly to humans as product of their digestion? Or maybe something involving subspace? Living in/feeding from/manipulating…

Never forget the cyclopean possibilites posed by entities f4om Outside, where the angles are all wrong and and the shifting eyes are mouths and you are unsure if it even has a shape, tantalizing some with the lure of lore wont to drive seemingly sane beings mad. The province of Lovecraft and Hermaeus Mora, the deadlights of Stephen King.

flying spaghetti monster anything that resembles a tyranid (from warhammer 40k) ship a sentient quasar that moves through different systems and gas clouds to get more mass to feed it some kind of 'space trapdoor spider" that sucks its prey into a dimensional pocket. space dragon space amoeba a “space worm” that travels via “worm holes”

You know that a quasar is the center of a galaxy and thus a supermassive black hole!

wouldn’t be the first time that something from another galaxy was invading and needed to be stopped. Okay but maybe a pulsar star, or something else.

An entire supermassive star moving through a system would be enough to destroy everything just with the gravitational pull. Wouldn’t even have to be supermassive… just a regular star, or even an average planet in the right place would totally disrupt a star system.

I mean, a system is built around one or more stars… and now you have another, and it’s moving… and that actually would be a way for it to feed. It tears apart other stars and planets with it’s gravity, absorbing them and becoming larger.

If you want to have a star in your series, try using an avatar like Trance Gemini.

It wouldn’t “destroy” most objects - star systems and planets are much bigger than you might suppose - but it would disrupt orbits. The process would happen very slowly (over months, years or even decades) but depending on the speed, trajectory and size of the invading object, the system would be completely reconfigured.

Deleted a couple of posts there folks.

Please play nicely…

Mod hat off.

Sol is an average star as the Universe goes, but Earth could crash into it and not be noticed.

A supermassive object like a quasar would completely disrupt a system as it moved thru it, and the ewnergy given off would likely sterilize any planets therein, and if it got close enough to the primary would start drawing it into itself.

It might take a while for the effect to be noticed, but not for it to happen.

Yeah a quasar (as in the system of superhot gas and matter surrounding the central black hole of a galaxy) would wreak that kind of damage. You were specifically discussing stars, which are signifcantly smaller.

A quasar or something on the scale of Eta Cassiopiae would definitely wipe out the system - some time before it actually arrived there!

I was referring to the quasar or pulsar originally suggested by JDW, and suggesting even an ordinary star would destroy any system in travelled thru.

Sorry if it wasn’t clear

Even an object of the size of a small planet or a moon would wreak havok with any solar system it passes. V’ger in its large size of several AU could not have an equaly huge mass, because it would have the same effect on a solar system as a black hole. Thus the V’ger could could not have a significant mass and V’ger itself could not be larger that a large space station.

A quasar would definitely wipe out the whole system, a pulsar would incinerate anything caught by the beams, and both a pulsar and a star would disrupt orbits which would likely destroy the system - but not the worlds. (Except in the long run of course.)

Note that the chances of an actual collision with a body in the system are very small.

They’re all very different things - even if Trek’s writers never really figured out the difference!

Sorry, but no, it wouldn’t. You’d need something significantly more massive to “wreak havok” - a body the size of Neptune would distort orbits as it passed through and leave some worlds on very different paths, but it would leave most of the system untouched. A moon-sized world would sail merrily through, be deflected from its original path by the star’s gravity and then leave again. It would affect very little.

I believe V’Ger the vessel was less than a hundred km long, making it the size of a small dwarf planet. It probably had a high density and therefore an higher mass. The cloud’s mass would have been less. Again not much in the grand scheme of a star system.

Sorry, but every mass influences everything around it. your moon-sized world would not “sail through” a solar system and leave the rest on the system untouched. Its mass would automatically influence every single object which comes close to it. Asteroids, comets near its path would change their course. Even other planets are affected. A rogue planet entering a solar system will change that system. But this would be a slow thing, because it would months or even years to pass through thy system.

Related Topics

• Show Spoilers
• Night Vision
• Sticky Header
• Highlight Links

Follow TV Tropes

http://tvtropes.org/pmwiki/pmwiki.php/YMMV/StarTrekArmada

YMMV / Star Trek: Armada

Edit locked.

• Demonic Spiders : The Species 9341 organisms you encounter in the Borg campaign of the first game. They're highly resistant to conventional weapons, they can't be assimilated, and their weapons? Psychic blasts that ignore your shields and armor and instantly wipe out a percentage of your crew every time they hit you. The only truly efficient way to kill them is to use the Diamond's Ultritium Burst ability, which requires a lot of time and resources to deploy in decent enough numbers. To make it worse, there are several 'Mother' entities that crank out the smaller creatures at a rapid pace. Said mothers are also effectively indestructible to conventional weapons.
• If you've played these games before reading this Trope page, you probably didn't realize how little value people's lives have in them.
• Appropriately, the Federation have some of the best counters to them in high-level play, downplaying this trope. The Sovereign Class ships can turn on their Corbomite Reflector to prevent the cubes' devastating torpedo damage, the Steamrunner can disable their engines so the cubes can't move, the Temporal Stasis Field (superweapon) can render a group of them completely helpless to the Federation fleet, and the Nebula Class can completely remove their shields. This helps curtail the Fusion Cubes' power to a degree, but facing them head-on without sufficient abilities and planning is a suicidal proposition due to their absurd firepower and durability and a few mistakes can still spell defeat.
• Also Borg Transwarp gate+Romulan Subspace rift ship. Bypasses the weakness of the Romulan weapon and clears a nice foothold for your fleet.
• The Klingon Frigate, the Koloth Class, can qualify as well. Combine a couple with some Science Ships for the "Death Chant" buff and a fleet of Negh'Var &/or Qeh'Rel battleships and watch your fleet tear through the enemy's fleet and base. The fleet is not as durable as the Fusion Cubes but still delivers rivaled mass destruction.
• The Species 8472 Battleship is a formidable ship. While not as overtly powerful as Fusion Cubes, they can still be massed to devastating effect. They also possess the researchable ability Psionic Insanity which is essentially a temporary mind control spell. Sail your Battleships into the enemy fleet, leveraging their considerably durability (comparable to Tactical Cubes) and you can force an enemy fleet to fight one another, while your Battleships destroy the helpless ships. Not even Fusion Cubes are immune to this spell.
• Along the Neutral Zone is particularly nasty, especially if you don't explore the map to see that the enemy base is behind a wall of turrets. And that's before the Enterprise flies in demanding repair ships situated behind the wall.
• Most later missions actively start with you having to chase Borg ships away from your base if you want to build anything, rarely ever giving you a moment to breathe.
• Hilarious in Hindsight : The first game, released in 2000, has the Borg decide that, in the name of capturing an Omega molecule, they require "an independent mind," leading to their assimilation of a Dominion cloning outpost, creating a clone of Jean-Luc Picard in order to recreate Locutus. Two years later, Star Trek: Nemesis says that the Romulan Empire had enacted the same plan for their own reasons.
• Nightmare Fuel : The Premonition is one of the last remaining ships from a future where almost everybody, including most likely all of the major characters from the series set in the TNG era, are now mutilated, cadaveresque, cybernetic Borg drones, trapped within their own minds for the rest of their existance until they're disposed of like meat and used batteries .
• Obvious Beta : The first game suffered a really bad case of this on its initial release, and the 1.1 patch didn't do a whole lot to help things. Worse still, Activision cut off support for the game only a couple of months after its initial release, leaving incoming Armada II developers Mad Doc Software to create a 1.2 patch that finally fixed all the major problems with the game. Armada II itself suffered a few bugs on its initial release, including one very obvious problem in that ship explosions weren't implemented properly, but was nowhere near as bad as the first game.
• Scrappy Mechanic : The requirement for officers to build any structure or ship. Players used to StarCraft — which this series emulates to an extent — may be surprised that structures cut into their "supply limit" which means choosing a good ratio of base defenses & structures to your mobile fleet. While this is supposedly meant to prevent players from spamming base defenses with their spare resources, it means that you need to decomission extraneous buildings to free up supply if you need a larger fleet. On the plus side, warp speed in Armada II helps you zoom home if you need to defend.
• Sequelitis : Armada II isn't bad enough to cross into The Problem with Licensed Games territory, but it's widely seen as an inferior sequel due to poor game balance, the 3-D battlefield being mostly superfluous, and a less interesting story for the single-player campaign.

Important Links

• Action Adventure
• Commercials
• Crime & Punishment
• Professional Wrestling
• Speculative Fiction
• Sports Story
• Animation (Western)
• Music And Sound Effects
• Print Media
• Sequential Art
• Tabletop Games
• Applied Phlebotinum
• Characterization
• Characters As Device
• Narrative Devices
• British Telly
• The Contributors
• Creator Speak
• Derivative Works
• Laws And Formulas
• Show Business
• Split Personality
• Truth And Lies
• Truth In Television
• Fate And Prophecy
• Edit Reasons
• Isolated Pages
• Images List
• Recent Videos
• Crowner Activity
• Un-typed Pages
• Recent Page Type Changes
• Trope Entry
• Character Sheet
• Playing With
• Creating New Redirects
• Cross Wicking
• Tips for Editing
• Text Formatting Rules
• Handling Spoilers
• Administrivia
• Trope Repair Shop
• Image Pickin'

Advertisement:

• skip to content

mwohlauer.d-n-s.name / www.mobile-infanterie.de

• Recent Changes
• Media Manager

Table of Contents

Statistical values, production capabilities, armada 1 mother entity.

The Mother Entity is Species 9341 's pendant of a Starbase and a Tier 1 Yard . It produces Entities on a very high rate. It has no other defensive properties, although this was probably never the intention (see the campaign bug in the Extermination mission on the matter). This station cannot be built by conventional means, as there is no constructor for this faction. It is only part of the single-player campaign and may be part of custom maps.

[  Star Trek: Armada  ] [  Game Play  ] [  Technical Support  ]

[  Units  ] [  Hero Ships  ] [  Campaign Ships  ] [  Ship Types  ] [  Stations  ] [  Station Types  ] [  Special Weapons  ] [  Factions  ] [  Modding  ]

[  Back to the Games Database  ]

Species 9341 Entity

• Edit source
• View history

The species 9341 entity is a small scout ship used by species 9341 and later reverse engineered to serve the Borg.

A species 9341 entity

Star Trek: Armada II

• View history

Following some complaints about the length of the Armada version, the single-player campaign was altered for this game; now only three races are involved, and each storyline is mostly independent of the others: the Federation must repel a Borg invasion via a new type of transwarp gate, taking the assault into the Delta Quadrant ; the Klingons must deal with a resurgent Cardassian military, while the Borg, affected by events in the Federation campaign, must stave off an attack by Species 8472, before combining with the Federation to eliminate this galactic threat.

• 1.1 Voiceover
• 1.2 Additional voiceover
• 3.1 United Federation of Planets starships
• 3.2 Klingon Empire starships
• 3.3 Romulan Star Empire starships
• 3.4 Borg Collective starships
• 3.5 Species 8472 starships
• 3.6 Cardassian starships
• 4 Construction ship
• 5.1 Ferengi starships (non-playable)
• 7.1.1 "Invasion"
• 7.1.2 "Lifelines"
• 7.1.3 "Recovery"
• 7.1.4 "Along the Neutral Zone"
• 7.1.5 "Into The Breach"
• 7.1.6 "Inferno"
• 7.1.7 "The Cavalry"
• 7.1.8 "Data Retrieval"
• 7.1.9 "Staging Grounds"
• 7.1.10 "There And Back Again"
• 7.2.1 "Uprising: A Dagger at Zarush"
• 7.2.2 "Executioner"
• 7.2.3 "Brave New Worlds"
• 7.2.4 "Blockade"
• 7.2.5 "The Unknown Prize"
• 7.2.6 "The Romulan Connection"
• 7.2.7 "Battle of Crucis Major"
• 7.2.8 "Trojan Horse"
• 7.2.9 "To Cardassia And Victory"
• 7.2.10 "The Final Battle"
• 7.3.1 "Werewolf Pack"
• 7.3.2 "Pink Slips"
• 7.3.3 "Interdiction"
• 7.3.4 "There Goes the Neighborhood"
• 7.3.5 "The Catch"
• 7.3.6 "Interception"
• 7.3.7 "Strange Bedfellows"
• 7.3.8 "Tidal Wave"
• 7.3.9 "The Maw"
• 7.3.10 "Rifts"
• 8 Multiplayer mode
• 9 Game tips
• 10 Cheat codes
• 11 Romulan-Federation War
• 12 External links

Voice cast [ ]

Voiceover [ ].

• Patrick Stewart as Picard
• J.G. Hertzler as Martok
• Alice Krige as Borg Queen
• Judi Durand as Computer

Additional voiceover [ ]

• Ron Surma – Casting Director
• Kris Zimmerman – Voice Director
• Brian Mysliwy – Mad Doc Software core Armada II Team
• Special Thanks to Rick Berman and Peter Lauritson
• Very Special Thanks to Gene Roddenberry

Featured starship classes [ ]

United federation of planets starships [ ].

• USS Coltrane ( β )
• This is a marine carrying class of ships named for the Battle of Iwo Jima . One of these ships is named the R.L. Ermey after R. Lee Ermey .
• USS Tolunay ( β )
• Defiant -class
• Saber -class
• Steamrunner -class
• Akira -class
• Intrepid -class
• USS Caddebostan ( β )
• USS Douglass ( β )
• USS Tonawanda ( β )
• USS Allegheny ( β )
• USS Oxford ( β )
• USS Danvers ( β )
• USS Enterprise -E
• USS Saratoga (NCC-31911-A)
• Ships of this class are named after Earth cities, e.g. USS New Delhi ( β )
• USS Incursion ( β ) (appears in the final mission; originally depicted in Star Trek: Away Team )

Klingon Empire starships [ ]

• NuQ'Duj -class ( β )
• Chava'Kal -class ( β )
• Koloth -class ( β ) (mainly a re-designed K't'inga -class )
• B'rel -class
• Chuq'Beh -class ( β ) (artillery cruiser resembling the K'Vort -class )
• SuQ'jagh -class ( β )
• Vor'cha -class
• Fek'lhr -class ( β )
• Qeh'Ral -class ( β )
• Martok 's flagship
• Jach'Eng -class ( β )

Romulan Star Empire starships [ ]

• Talon -class
• Kestrel -class
• Shrike -class ( β )
• Veles -class ( β )
• Raptor -class ( β )
• Griffin -class ( β )
• Draconarius -class ( β )
• Shadow -class ( β )
• Venator -class ( β )
• D'deridex -class
• Phoenix -class ( β )

Borg Collective starships [ ]

• Borg interceptor
• Borg detector ( β )
• Borg wedge ( β )
• Borg assimilator ( β )
• Borg harbinger ( β )
• Borg sphere
• Borg Queen 's ship
• Borg harmonic defender ( β )
• Borg tactical cube
• Borg fusion cube ( β )
• Borg tactical fusion cube ( β )

Species 8472 starships [ ]

Cardassian starships [ ].

• Hideki -class ( β )
• Janissary -class ( β )
• Vasad -class ( β )
• Gul Vystan -class ( β )
• Legate -class ( β )
• Brinok -class ( β )
• Rasilak -class ( β )
• Sartan -class ( β )
• Kulinor -class ( β )
• Galor -class
• Gul Kentar's personal ship
• Dreadnought missile

Construction ship [ ]

• All playable races except Species 8472 use them to build installations. The Borg call their ship an "Assembler". When the game starts, the player gets one starbase and/ or one, maybe two construction ships. In the main scenarios, such as the Federation Scenario, the player has one, maybe two of these ships which is used to construct the base(s) needed to complete the scenario(s).

Other ships/races [ ]

Ferengi starships (non-playable) [ ].

• D'Kora -class – ( though can be assimilated for use in the Borg campaign )
• Ferengi merchant vessel

Setting [ ]

Star Trek: Armada II takes place from stardate 54522 to some time after stardate 54881, some six months after the events of the first game. The Borg have been spotted in Federation space using a new vessel employed to assimilate planetary surfaces. The Cardassian Union is becoming increasingly aggressive, and the Klingons are growing tired of their role as peace-keepers.

Single player campaign [ ]

Federation campaign [ ], "invasion" [ ].

Stardate 54522.2: A Borg force has invaded the Regula Badlands. The Enterprise is dispatched to eliminate the Borg presence, reclaim the colony world, and determine how the Collective was able to make it so deep into the Alpha Quadrant . It is discovered that a new type of tachyon nebula may hold the answer to this question.

"Lifelines" [ ]

Stardate 54544.2: The Federation starbase at Alpha Theta VI is under attack, and badly needs supplies. Convoys of cargo ships need to be escorted through a treacherous nebula, and a Borg defense network, in order to resupply the base.

"Recovery" [ ]

Stardate 54566.1: Starbase 176 has been attacked by the Borg, and the area is devastated. The Enterprise must defend the base against further attacks, and rebuild its defenses to act as a staging area. The assimilated USS Douglass is recaptured from the Borg.

"Along the Neutral Zone" [ ]

Stardate 54588.0: A small fleet, led by a single Akira -class starship under the command of a Captain McDermott, is dispatched to the Romulan Neutral Zone to establish a presence in a hazardous nebula field. The Enterprise suffers severe damage en route to the area, and must be protected from an assault by a squadron of Borg cubes.

"Into The Breach" [ ]

Stardate 54612.7: The transwarp portal is known to be located within the Regula Badlands. The Enterprise and her fleet must find, capture and hold the portal to allow an assault on Borg territory.

"Inferno" [ ]

Stardate 54637.3: The Federation invasion force enters the Delta Quadrant through the captured transwarp portal. Its counterpart must be captured, and all Borg within the area eliminated. The mission is hampered by the presence of a powerful subspace field that prevents warp travel.

"The Cavalry" [ ]

Stardate 54664.7: The Federation Third Fleet is ambushed in system J-356 by vessels of unknown origin. The Enterprise responds to a distress call from the USS Allegheny , the vessel leading the fleet, and the only survivor of the attack. The presence of Species 8472 is strongly suspected, as the Federation forces scour the system of a heavy Borg presence.

"Data Retrieval" [ ]

Stardate 54694.9: A modified freighter is used to retrieve vital data on the location of the Borg staging grounds from a Borg Nexus base. A heavy assault fleet must protect the data miner until its mission is complete.

"Staging Grounds" [ ]

Stardate 54727.7: The Borg staging grounds have been located in system J-361, and a huge Borg fleet is detected. The Federation forces must assemble an assault force without alerting the Borg to their presence. Once the attack is completed, the Enterprise and the surviving vessels must retreat to an extraction point, prior to returning to the transwarp portal.

"There And Back Again" [ ]

Stardate 54760.6: The Federation forces are in full retreat. A massive Borg counterattack, coupled with the arrival of dozens of Species 8472 vessels, has forced Starfleet to pull back to the transwarp portal, and back to the Alpha Quadrant. The evacuation is almost complete, when the portal suddenly explodes, leaving the Enterprise and several dozen vessels trapped behind enemy lines...

Klingon Campaign [ ]

"uprising: a dagger at zarush" [ ].

Stardate 54642.8: A massive Cardassian force, led by Gul Kentar, has attacked and destroyed the Federation reserve fleet at its dock in the Pearl Nebula. The Klingon defense forces must hold the line at Zarush, and strike back at the invading Cardassian fleet over Vanoshan.

"Executioner" [ ]

Stardate 54656.5: With the Pearl Nebula secure for the moment, Chancellor Martok orders a retaliatory strike against the Cardassian-held world of Kestian, and other Cardassian bases in the Doltec system. The planet must be eliminated.

"Brave New Worlds" [ ]

Stardate 54670.2: The Efate system is a key location for colonization and resupply. The system must be secure before the Cardassians get there and claim the worlds themselves, denying them a crucial resource.

"Blockade" [ ]

Stardate 54683.9: The Cardassians are on the back foot, with supply lines crumbling. A chance to break the front line has emerged at Mornaur II – however, a Romulan supply convoy is en route to the system. It appears that the Romulans have been behind the Cardassians sudden rearmament. The convoy must be intercepted before it reaches the planet, and before an assault on the system can take place.

"The Unknown Prize" [ ]

Stardate 54697.6: The Kulinor class of Cardassian vessel has been seen with additional, unidentified modifications. A prototype vessel, the "Quantum Singularity Ship" has been detected on the far side of the Ketch'Tor asteroid belt, and must be captured to determine its secrets.

"The Romulan Connection" [ ]

Stardate 54711.3: Romulan duplicity in the Kentar Uprising is now clear. The Star Empire must be "persuaded" to cease its support for the Cardassians. In order for this to proceed, a series of Romulan colonies must been conquered and Romulan bases destroyed.

"Battle of Crucis Major" [ ]

Stardate 54725.0: Despite cutting off most of their supplies, Gul Kentar's forces are able to launch a massive assault on the Klingon base at Crucis Major. With defenses incomplete, Martok is barely able to escape. However, the presence of a secret base operated by the House of Tagesh may allow the Klingons to fight back and clear the system of the Cardassian invaders.

"Trojan Horse" [ ]

Stardate 54738.7: To attack a Cardassian base, a Cardassian vessel must be captured and employed to disable vital defense systems. Without it, the Klingon forces will be unable to press on and take out the base.

"To Cardassia And Victory" [ ]

Stardate 54752.4: The Klingon counterattack has reached the Cardassian system itself. The surrounding planets must be captured, before a final assault on Cardassia Prime and its powerful defenses can be mounted. Gul Kentar is able to escape as Cardassia Prime falls, but Martok and his fleet are close behind.

"The Final Battle" [ ]

Stardate 54766.1: Kentar has fled to his secret base in the Hurik system. Here, he must be destroyed, along with the quantum singularity technology the Cardassians have developed, which is how they are bringing Species 8472 into the galaxy. The station is destroyed and Kentar's ship is destroyed in combat with Martok's armada.

Borg Campaign [ ]

"werewolf pack" [ ].

Stardate 54771.6: With the destruction of the transwarp portal in "There and Back Again", a number of Borg ships, including that of the Borg Queen, have been trapped in the Alpha Quadrant, as Picard and some of the Starfleet vessels have likewise in the Delta Quadrant. The Collective must assimilate cargo vessels in order to gain resources to rebuild their forces. However, Species 8472, having been drawn into the quadrant by the Cardassians' experiments in quantum singularities, are also in the sector, and the Borg are forced to retreat.

"Pink Slips" [ ]

Stardate 54785.3: Species 8472 vessels are attacking a Federation outpost , with the Borg caught in the middle. Both sides must be eliminated if reconstruction is to proceed. Since 8472 cannot be assimilated, Federation vessels must be captured and used against them.

"Interdiction" [ ]

Stardate 54799.0: The Borg now have sufficient resources to begin consolidating their position with a Nexus base. Cargo and other vessels must still be seized until resource gathering can be initiated.

"There Goes the Neighborhood" [ ]

Stardate 54812.7: All planetary bodies in Grid 967, a Romulan-held sector, must be assimilated in order to maintain reconstruction efforts.

"The Catch" [ ]

Stardate 54826.4: A pair of Federation starships have been captured, with key information on recreating the transwarp portal. With Species 8472 in pursuit, the two vessels must be relocated to the nearest Borg Nexus immediately for disassembly and analysis. Progress is hampered by intense nebular activity.

"Interception" [ ]

Stardate 54840.1: The Klingons have captured a Species 8472 bio-ship . In order to determine how the aliens are getting into the Alpha Quadrant, the facility analyzing the ship must be assimilated, and the Klingon forces suppressed.

"Strange Bedfellows" [ ]

Stardate 54853.8: Technology 2702 – the transwarp portal – has been reacquired. In order to successfully drive Species 8472 back into fluidic space , the Borg must retrieve the Federation forces stranded in the Delta Quadrant, and negotiate an alliance. The transwarp portal must be reconstructed, and used to accomplish this objective.

"Tidal Wave" [ ]

Stardate 54867.5: The Federation and the Collective have come to an agreement – Species 8472 must be eliminated, and the only way to accomplish this task is to combine forces. A massive fluidic rift has been detected, which is allowing the bio-ships access to our galaxy. Nearby sectors must be cleared before an assault can take place.

"The Maw" [ ]

Stardate 54881.2: The fluidic rift has been located. In order to successfully traverse the barrier into fluidic space, the Federation forces need to collect sufficient resources, and scout the rift for any dangers. Meanwhile, Species 8472 bio-ships continue to flood into the quadrant, and must be eliminated.

"Rifts" [ ]

Stardate unknown: The combined Federation and Borg fleet has entered fluidic space. Three additional rifts are being generated by an unknown entity, and must be located. The rift maker must be destroyed to prevent further incursions.

With the threat from Species 8472 eliminated, the alliance is dissolved – the Borg vessels are escorted back to the transwarp portal, and sent back to the Delta Quadrant, and Picard warns that further incursions into the Alpha Quadrant will be met with the strongest force.

(A cameo is made on this level by the USS Incursion from Star Trek: Away Team . It is a fully playable ship, and features the holo-disguise ability from Away Team .)

Multiplayer mode [ ]

As with Armada , multiplayer mode (and Instant Action) sees the player competing against up to seven opponents – the last one standing wins. Armada II adds some additional gameplay modes to the on-line game, including "Capture the Flag" and "Assault". The Internet game used Gamespy servers to run online games.

Game tips [ ]

To allow complete access to and use of an enemy race's technology, capture either a starbase or a construction ship. By working up the technology tree, a player can even have access to enemy weapon technology. For example, if a Federation player captured a Borg construction ship or a nexus, that player could eventually build and use tactical fusion cubes and even a transwarp gate . Note that this is only available in Instant Action and Multiplayer mode; it cannot be done in single player mode.

To use the extra dilithium crystals (see cheat codes, below), construct a trading station to exchange them for metal or latinum . If playing as the Borg, who do not use latinum, construct a recycler to change the dilithium for metal. Species 8472 have no resource exchange capabilities.

Cheat codes [ ]

Star Trek: Armada II contains many of the same cheat codes as the original. To access the cheat codes, which are only available in single player mode, press the "Enter" key and type one of the following codes, followed by the "Enter" key again:

• showmethemoney adds 2,000 dilithium crystals to the player's stores. These extra crystals can be sold or used like regular dilithium. This can come in handy in fluidic space (which lacks resources). This code is repeatable, to obtain more crystals, press enter, then type this code, press enter each time you need more crystals.
• kobayashimaru will allow the player to automatically win the current mission and advance to the next mission.
• youstopmecold will increase the speed at which ships are built.
• avoidance will increase the rate at which new crew are recruited.

Romulan-Federation War [ ]

If Starfleet intrudes upon the Romulan Neutral Zone in the 4th Federation campaign mission more then once, it will trigger hostilities between the Federation and the Romulan Empire. Hordes of Romulans invade Federation space and begin attacks on Starfleet. The Enterprise -E becomes a priority target for the Romulans upon arrival. Even if Starfleet is able to destroy or capture the Romulan base, additional Romulan reinforcements continue arriving from outside the sector, therefore the Romulans will keep up their attacks until all mission objectives are achieved. Despite having a common foe, the Romulans and the Borg still attack one another; one could potentially cripple the other beyond recovery thereby making it easier to achieve primary mission objective. This Romulan-Federation War has no impact on later missions whatsoever.

Since the Romulan invasion virtually rivals Gul Kentar's surprise attack at the start of the Battle of Crucis Major, the best strategy is establishing a new base where the Enterprise -E arrives with a defensive line consisting of Starbases, Torpedo Turrets, Pulse Cannons, and Sensor Arrays used to ambush any enemy ships approaching through the nebula. Provided the Romulans destroy most of the Borg base, a few captured Warbirds should make short work of any Borg stragglers while using cloaking to evade Romulan patrols.

External links [ ]

• Star Trek: Armada II at Memory Beta , the wiki for licensed Star Trek works
• Star Trek: Armada II at Wikipedia
• Star Trek: Armada II at TrekCore
• Fleet Operations at the Star Trek Expanded Universe , the wiki for Star Trek fan fiction
• 2 USS Enterprise (NCC-1701-G)
• 3 Star Trek: The Next Generation

"Their Raider Dwarfed Our Ship by a Factor of Three": Star Trek's New Armada Is the Ultra-Powerful Opposite of the Borg

• The Tzenkethi, a mysterious and xenophobic race, are the only species to defeat the Federation, despite their low-tech ships and stone hulls.
• Unlike the Borg, the Tzenkethi rely on fusion reactors and reject contact with other races, making them a unique and powerful adversary.
• Despite their lack of advanced technology, the Tzenkethi's massive and resilient ships prove to be a challenge for the highly advanced Federation.

Warning: contains spoilers for Star Trek #13!

There is a new armada in the Star Trek universe, and they are the ultra-powerful opposite of the Borg. Captain Sisko and the crew of the USS Theseus have a new mission: to travel to the home world of the mysterious Tzenkethi, and de-escalate a tense situation. In Star Trek #13, Sisko paints a picture of the xenophobic race, and they are the opposite of the Borg, but no less powerful.

Star Trek #13 is written by Jackson Lanzing and Collin Kelly and drawn by Marcus To. On route to rendezvous with a Starfleet operative on the Tzenkethi home world, the crew hold a briefing on their adversaries. Tom Paris notes the Tzenkethi are technically pre-warp. That is, they do not use standard warp drive units like the Federation. Instead, their ships are giant nuclear reactors that hurl the ships at light speeds. Sisko, who has had experience with the Tzenkethi, relates the story of one of their ships. It was three times the size of his, with a hull made of stone, so thick torpedoes could not dent it.

The Tzenkethi Are the Only Species to Beat the Federation

The Tzenkethi have never been seen on-screen, only mentioned in several episodes of Star Trek: Deep Space Nine . They have made appearances in spinoff media, including the game Star Trek Online , but they by and far remain an enigma. Past encounters between the Tzenkethi and the Federation have not gone well: 127 people were killed during first contact, and the two parties have fought in the past, with the Tzenkethi taking the Federation down to the wire every time. Captain Sisko has first-hand experience with the Tzenkethi, noting the unique nature of their ships: atomic reactors made of stone.

Related: Star Trek's 2009 Movie Hid the Full Power of Nero's Ship (& Its Borg Connection)

The Tzenkethi Put a Low Tech Spin on the Borg's Methods

With this in mind, the Tzenkethi are the opposite of the Borg. The most feared race in the universe, the Borg are a high-tech collective that assimilates other species, gaining their technology and experience. The Borg will assimilate nearly any species they encounter. Their ships, resembling giant cubes, can travel through transwarp conduits to practically anywhere in the galaxy. The Tzenkethi, on the other hand, have decidedly low tech ships, with stone hulls and powered by fusion reactors. And unlike the Borg, the Tzenkethi are highly xenophobic, shunning contact with the rest of the galaxy.

On the surface, this would seemingly make the Tzenkethi easy pickings for the Federation. Federation ships are some of the fastest and best-designed in the galaxy, and yet the Tzenkethi and their low-tech ships have made fools of Starfleet on multiple occasions. Their ships are massive and hard to destroy, meaning the Tzenkethi place an emphasis on might and strength. The Borg also use massive ships to overwhelm their opponents, yet the Tzenkethi, Star Trek’s newest armada, puts a low tech, but still powerful, spin on this.

Star Trek #13 is on sale now from IDW Publishing!

Armada 2 Files , i need permission for ships and stations

Tryptic wrote: Are you making the mod for Armada 2 directly, or are you using the Fleet Operations engine? I would recommend that you do it through Fleet Ops, as it is more stable and easier to run on new computers. If you do this, then even if you are using Armada 2 assets, you are technically working on a Fleet Ops mod, and the developers have given everyone permission to use Fleet Ops assets in Fleet Ops mods. That seems to me like it would help with a lot of the permissions you are looking for. If you keep asking around, you may be able to get an answer directly from a Fleet Ops Dev who can confirm this.

Who is online

Users browsing this forum: Bing [Bot] , Google [Bot] and 0 guests ( Details )