Star Trek Armada Ii Fleet Operations

[Suyay Escarsega]

FleetOperations is a popular skirmish and multiplayer orientated total conversion modification for Activision's real-time strategy game Star Trek Armada II. The project's goal was not only to create a simple "modification" but as total conversion to make Armada II a worthy successor to the second best selling Star Trek game Star Trek: Armada (behind Interplay's Star Trek: 25th Anniversary by a small, but fair margin).

The first public version of Fleet Operations was released in 2003. Today, version 3 includes a whole new user interface, an updated game and graphics engine, completely replaced ship models, 5 balanced races with totally new gameplay and tons of new possibilities making Armada II a real real-time strategy multiplayer game.

T his patch - most importantly - fixes the frequent, frustrating multiplayer out of sync (OOS) problems, some of which that have been present since the first 3.0.0 release. These issues made playing cooperative AI games online nearly impossible without resulting in a desync and eliminated the possibility to use wormhole-rich multiplayer maps.

We would like to thank everybody profusely who was involved in those long and tedious (but fruitful!) hours of out of sync testing.

The multiplayer Tunngle integration is also fixed, allowing you to immediately jump into the correct Fleet Operations lobby to play online games!

Although this is not the long awaited next version - rest assured, 4.0 is still well on track. These bug fixes are a direct result of work on our next version.

I cannot get this to work. Ive downloaded multiple online versions of Armada 2 as my original copy died a long time ago but nothing works. Even installing an apparent No Cd patch stops the game from even starting. When i loaded an apparent proper version of armada 2 and load fleet ops it wont play as "You need you own CD"

I doubt we will ever see this nx game they are making. I really like this mod but only a few maps are even fun to play on, resources are too scarce or far between in most of them if you want 4 players or more.

Your mod needs updating a lot cause of the ff:

1. Federation vessels are much weaker than the other races.

2. From the specs you've only included. There are a lot of federation arsenals. Such as 'Sovereign and excelsior class can fire photon torpedoes other than quantum torpedoes'.

3. Federation vessels have the ability to use their deflector dish to fire beams and resonance burst. At longer range since feds don't have artillery ships. How come this is not included in your mod?

4. There's a thing called 'refit' Which allows most federation vessels to upgrade their systems. Why only include officer rank upgrade?

FleetOps in this current iteration will no longer be developed. The team's current focus is creating a whole new engine (which they call NX for now) from which they will proceed further, and nobody on the team is doing anything Armada-related anymore.

Wow !

You guys are here ! This is amazing. I've been playing this since its early days.

How goes the progress ? You promised more races or something like the Noxter , the Iconians but all i found was updates and bug fixes and it's been quite a long time

Your comment action was successful. When a comment is deleted all replies to the comment will be removed as well. Because you are an admin, you can click the \"view deleted\" link above to view deleted comments in-case you wish to undelete them in the future. If this was a mistake, click the link again to reverse the change.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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...

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.

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.

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.

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.

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.

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.

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.

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.

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.

3a8082e126