Review of Star Trek: 25th Anniversary

by Florian Haag

As this game forms a miniseries, with several missions presented as single episodes that are at best weakly connected to each other, I am going to comment on them separately.

 

Demon World

Synopsis

After a training battle with the U.S.S. Republic, the Enterprise receives an order from Starfleet to travel to Pollux V. The colonists on that planet report being attacked near their mines by creatures that resemble mythological demons. An Enterprise landing party encounters a group of Klingons, who, after being disabled, turn out to be androids. A gate in the mountain leads to a hidden chamber where the Nauians, the original inhabitants of the planet have remained in stasis during a recent ice age on Pollux V. A safety system of that installation was responsible for artificially creating android guardians based on the greatest fears of whoever came close to discovering the chamber. The stasis systems were programmed to wait for the next eclipse, which never happened as the moon had been destroyed in the meantime. After Kirk manually terminates the stasis and establishes peaceful contact with a Nauian representative.

Commentary

The first episode in the game provides a straightforward, if interesting story. It manages to establish that the story takes place in the Star Trek universe by incorporating various known elements (Tellarites, Klingons (albeit not real ones), ...) without obsessively clinging to the shortcomings in terms of storytelling and production techniques that TOS sometimes suffered from. For instance, the first unknown alien lifeform appearing in the episode, the Nauian, is decidedly non-humanoid. Moreover, the motivation seems more credible than the usual plot-device-of-the-episode that needs to be fetched from a particular planet, as for once, the Enterprise travels to a Federation world simply because the inhabitants have a particular problem that they want Starfleet to deal with. Also, it is a refreshing change that the colony is not another nondescript standard colony, but actually something like a monastery, which gives the colonists some distinctiveness.

Overall, the episode feels a little bit bumpy, which may have to do with the fact that the direction of the story seems to change quite often in only very few locations. At the same time, the score relies very heavily on TOS's "effect" music. Other than that, the dialog with the Nauian in the end appears a bit drawn out, as it is made excessively clear that the Nauians happen to be monotheistic and open toward other monotheistic religions, making them a perfect match for the colonists already on the planet. This could have been toned down a bit. The other dialogs with the crew, including the final banter between Spock and McCoy about demons, feel very natural.

Annotations

Rating: 7

 

Hijacked

Synopsis

The Enterprise is told to travel to Beta Myamid, where contact to the U.S.S. Masada has been lost. After arriving in the system, the Enterprise is attacked by a vessel of the Elasi pirates, who have captured the Masada. An away team manages to overpower the Elasi aboard the Masada.

Commentary

This episode prominently features the Elasi pirates, an additional faction introduced by the game. In hindsight, it is not clear why no existing faction with similar characteristics, such as Orions, was used. In any case, using this faction gives the stories the freedom to show major incursions such as hijacking of starships without making them political issues between the Galactic superpowers such as Klingons or Romulans. Little becomes known about the motivation of the Elasi pirates, although they appear to be more than mere thieves and rather come across as a kind of separatist group. The Elasi captain states the Masada had been taken to broker the release of 25 captured Elasi, and he calls the Federation "Imperialists" at one point. Still, it does not get clear what the Elasi have been waiting for, as they have locked themselves in the bridge (that seems to be surrounded by an additional forcefield to prevent beaming onto the bridge even if the ship's shields are lowered) and make no attempts to escape the system. Moreover, they have set up booby traps in the ship, as if they were intentionally waiting to be boarded by the enemy.

In general, the story is pretty straightforward again, and more action-heavy than the previous episode. In turn, it doesn't feature any new revelations once it is clear the Elasi have captured the ship.

Annotations

Rating: 6

 

Love's Labor Jeopardized

Synopsis

The Enterprise is sent to ARK7 near the Romulan neutral zone, as Romulans have shown up near the research station where Dr. Carol Marcus conducts experiments. The airborne Oroborus virus that is dangerous to Romulans has been accidentally set free on the station. McCoy manages to synthesize a cure for the virus, and the Romulan intruders on the station are cured.

Commentary

This episode features a similarly straightforward retake-captured-vessel plot as the previous one, but the action feels better embedded into the story. Somehow, the technical difficulties the crew encounters come across as less contrived than in the previous episode. This may also have to do with a slightly larger amount of information being available in the library database on the station than what was provided in previous episodes. Moreover, the ending feels comparably rewarding, as the Romulans can be cured and call of their attack. Moreover, we get to meet Carol Marcus (and her colleague Dr. Cheevers), although there is not much interaction with her in the end. At the same time, however, everything presented does seem a bit incomplete, as it is hardly believeable there are only the two scientists on the station.

While the previous redshirts that joined the away teams were rather quiet, this episode brings us Lieutenant Ferris, who occasionally throws in some snappy remarks almost on par with McCoy's outbursts. It is nice to see some different personalities in the security details, which gives them a little bit more to do than serve as an optional casualty for cases when the player is not careful enough.

Annotations

Rating: 7

 

Another Fine Mess

Synopsis

After fending off an Elasi attack on a scout ship, the pilot of the scout ship turns out to be Harry Mudd, who has taken over a derelict ship originating from the extinct race of the L'Shaians. Apparently, the Elasi are after the origin of some artifacts from the alien vessel, which can be used as weapons. Soon, the away team finds out the alien vessel was a warship with advanced weapon technology. With the Enterprise temporarily under attack by Elasi pirates, the away team manages to reactivate some of the aliens' systems. However, Harry Mudd accidentally erases the database of the vessel, meaning that all knowledge on the culture of the L'Shaians is lost.

Commentary

The episode starts out much more light-hearted than the previous episodes, despite the opening battle against two Elasi fighters. This is underlined by the frequent use of the "funny" TOS music, essentially every time that Harry Mudd appears. While he remains fully in characters by claiming the alien vessel, and everything aboard, for himself, it does not get clear at first why the Enterprise away team tries to repair the alien weapon systems. It almost seems like they are acting on principle because they are dealing with Harry Mudd, not because they are trying to achieve a particular goal. Their actions only become understandable when the sensors are reactivated and the away team discovers more Elasi ships are attacking the Enterprise.

Nonetheless, the "serious" part of exploring and reactivating the alien warship with its miraculous experimental weapon system and the "funny" part of dealing with Harry Mudd and the issues he causes somehow balance each other well and result in a satisfactory mixture. Only the ending comes a bit abrupt and leaves a rather bitter taste, given that the alien database is lost. In a way, though, it is only realistic that the away team beam back as soon as there is nothing more to do for them on the alien ship.

Annotations

Rating: 7

 

The Feathered Serpent

Synopsis

Stardate: 5097.3: The Enterprise travels to a planet near Klingon space, as Klingons have entered Federation space to search for a criminal. After coming to an agreement with Klingon commander Taraz to find the alleged criminal within 12 hours, a landing party encounters a man with supernatural powers who claims to be the Aztec god Quetzalcoatl. Quetzalcoatl does not believe his actions have endangered peace and, in a fit of rage, transports the landing party into a dangerous forest. By the time they make it back to him, he sees the Enterprise crew are worthy of his trust and realizes as his intentions with the peoples he has visited did not come true, he does not deserve to have the god-like powers he possesses. He asks the Enterprise crew to remove a gland responsible for his powers and his immortality. However, due to his interference in Klingon space, he is considered subject to Klingon law and has to be tried on Krakkour. When it becomes clear that the Klingon Admiral Vlict Kenka is trying to cover up his genocide on the population of Krakkour by punishing Quetzalcoatl as a scapegoat, the landing party is transported into a subterranean labyrinth, where they find the powerful native entity Bialbi. Bialbi declares Krakkour to be off-limits to Klingons and requires that Quetzalcoatl be released.

Commentary

This episode is quite captivating, not only due to its flow that spans two very different planets, but also because the multi-layered motivations of all involved parties are rather well explained. At first, it looks like the episode centers on Quetzalcoatl and the tests he puts up for the landing party. Then, the Klingons are in command, as is also decided by the Organians based on the current peace treaty, even though Kirk recognizes the Klingon admiral's perosnal motives. Finally, all parties involved get confronted with the entity Bialbi. Interestingly, Bialbi points out that Klingon archeologists had come close to its subterranean hideout. Beside this being one of a few rare cases where Klingons are mentioned who are not warriors, it is left open who built the control center around (the non-corporeal?) Bialbi, or who it was built for.

With this said, Quetzalcoatl is rather quick to accept that his original intentions have not led to the desired outcome, and thus to completely neglect his supernatural powers. It seems as if he had just been waiting for an excuse to honorably get rid of the supernatural gland. Also, he makes a point about humans not possessing the gland, implying that his species usually does. Are there more of his species, and if so, how and where do they use their powers?

Overall, however, this is still the most serious episode in the game so far. Fittingly, it does not end with the usual McCoy-Spock bantering, but with a more contemplative musing of Kirk that it did not end well for the dead on Krakkour.

Annotations

Rating: 8

 

That Old Devil Moon

Synopsis

The Enterprise is sent to Alpha Proxima to investigate unusual activity on an asteroid. The pre-warp inhabitants of Proxima III call the asteroid Scythe and interpret it as their god of war. In fact, it is an old missile base involved in a war that took place on Proxima III a millennium ago, which destroyed most of the planet's civilization, and much of its technological progress was forgotten. While the landing party is trying to disable the ancient missile base on the asteroid, the engineering staff on the Enterprise is trying to get rid of a computer virus.

Commentary

The episode starts with a sound background story, even though it appears somewhat formulaic, with the two ancient superpowers favoring individualism and communitarianism, respectively, which is apparently meant to mirror something like the divide between capitalism and communism on Earth. In any case, the rift between the two cultures must have run very deep, as they even favored different radices in their mathematics (3 and 4, respectively). In this case, it was the individualist Lucrs that installed missile bases (on the asteroid) to keep their opponents subjugated. During the episode, however, the background story mostly serves as a foundation for various of the tasks the crew has to solve while acknowledging base 3.

This is the first time in the game that a plot element actually gets recycled. After we have already seen a system that heavily relied on timed events, but measured time based on external factors rather than internally, we now see the ancient Lucrs were not any smarter than the Nauians. Rather than waiting forever, in this case the missile base misinterpreted 1000 years for a week. Come to think about it now, such a system design makes even less sense - imagine if your ink-jet printer counted days for starting its self-cleaning routine by registering daylight. The ink channels would completely dry up if you kept the printer in the basement!

The computer says the asteroid Scythe used to be a moon of Proxima III (pushed out of orbit during the war), and it must have been quite a massive moon. From space, the asteroid looks like a planet with bodies of water, and there is a breathable atmosphere on its surface. Still, the surface looks impressively exotic within the restrains of the game's graphics. It uses the TOS sound effect sometimes heard on uninhabited planets, combined with the slightly menacing music theme, which results in a convincing alien world mood. As the asteroid has an orbital period of 200 years, it has passed by Proxima III several times since the war, but this time, it registered unidentified radio waves from the planet for the first time, which triggered the missile base's activation. The final solution is "minimally invasive", in that the missiles still get launched, but at an incorrect time, so they will run out of fuel before they reach Proxima III. It seems, however, like this is the best the landing party can do for the moment, as the asteroid is worshipped as a god by the inhabitants of Proxima III and can thereby not be destroyed without violating the Prime Directive.

In general, the Prime Directive plays quite a role in this episode, and it is interpreted in a very different fashion than in TNG's "Homeward". Even though the inhabitants of Proxima III are subject to the non-interference clause of the Prime Directive, the Enterprise is supposed to save their world from whatever might happen due to the asteroid.

Annotations

Rating: 7

 

Vengeance

Synopsis

The Enterprise finds the destroyed U.S.S. Republic. Sensor records and the last surviving crewmember indicates the Enterprise had destroyed the Republic. The attack was conducted by the Vardainian Dr. Ies Bredell, who has managed to build an exact copy of the Enterprise to take late revenge on Kirk.

Commentary

The episode starts out with finding the wreckage of the Republic and almost everyone aboard dead. The mood remains accordingly somber throughout the episode, and the devastated interior of the Republic with debris and bodies lying around everywhere convincingly conveys the work of a ruthless aggressor.

While the desperate atmosphere is credible, it must be noted that the episode relies a bit much on common clichés. A completely devastated starship that is still intact enough for a landing party to walk around without spacesuits, a single survivor (who, how else could it be, is a former acquaintance of Kirk's - at least not an old flame of his, or maybe it was just not explicitly mentioned) who dies shortly after uttering some hints relevant for the plot (if we discount the red herring of the two survivors, one of which dies moments before the landing party arrives), an opponent obsessed with taking personal revenge and who has the means to somehow create an exact copy of the Enterprise, a fake distress call as a decoy to lure the Enterprise away - we have all had that before in one form or another.

This way, the story is not overly intriguing and the focus lies on the operational details of getting various parts of the ship to work, such as dysfunctional doors. When the main story is driven forward, it does not appear to be very focused. First, the Elasi want information about the 25 Elasi prisoners they already tried to free when capturing the Masada in "Hijacked". Then, Bredell turns up out of nowhere, trying to execute his revenge plan. But where has he been all the time? It seems he specifically wanted to destroy the Enterprise together with Kirk, but only if the other Elasi did not kill Kirk first while trying to extract the information about their captured comrades.

Bredell's background story does not become very clear, anyway. We learn that Kirk, while serving as a Lieutenant on the Farragut ten years before, helped expose "unethical practices" that Bredell was involved in. That, along with the fact that Bredell is referred to as a "doctor" and therefore must be a mad scientist, is apparently deemed to suffice to viewers. As an additional tidbit, Bredell is depicted as some sort of a cyborg with metal covering a part of his head and an artificial eye blinking in a menacing red. I would rather expect such an opponent in a non-Star Trek comic serial or maybe the Abramsverse, but not in any of the "old" Star Trek installments. Lastly, it is rather a letdown that the mission (and the game) ends by destroying Bredell's Enterprise-2. After several episodes where space fighting either did not occur at all, or was placed at the beginning of the story, making the final episode end with a decisive battle against an opponent that was barely introduced when the battle started, this ending feels too abrupt.

Character-wise, it is at least nice to see that, after the redshirts have steadily been somewhat vocal in one way or another (in contrast to the TV redshirts who often had very few or no lines), Ensign Kije even gets to be the hero in one aspect of the story, as it is him who beams to torpedo control and fixes the loading mechanism off-screen while reporting his progress.

Annotations

Rating: 4

 

Overall Commentary

25th Anniversary is a satisfactory experience, both in gameplay and storytelling. To some extent, it shows that the simplistic TOS style can be merged with more modern visuals. The TOS sound effects were a bit overused at first, but got toned down to an enjoyable level as the episodes progressed. The episodes were rather very short and thus could not reach the depth of TV episodes, but nonetheless did not feel rushed. Only the invariable combination of the landing parties, consisting of Kirk, Spock, McCoy, and a security officer (at least a different one every time!) was a bit repetitive, but that was fixed for the game's successor, Judgment Rites.

Gameplay-wise, the game provides a viable variant of common point-and-click control interfaces. Interaction with characters usually felt natural, and seeing Star Trek items such as tricorders or phasers in the inventory conveyed a true Star Trek feeling. Also, having Kirk or the others look at objects and scan them with the tricorder often provides interesting background information on the environment.

The space battles thankfully seemed somewhat realistic, as well, with weapons being restricted to phasers and torpedoes, as opposed to the elaborate fantasy weapons other more combat-oriented Star Trek games tend to invent. Given that the obligatory battles were rare and sufficiently simple to master, they also did not bother me too much as a distraction from the story-based adventure parts. The only exception was, as noted above, the final battle against Bredell and the Elasi, which could not even be rescued by giving orders to the familiar characters from TOS on the bridge.

Speaking of which, the game is sufficiently embedded in the Star Trek universe, although it fulfils barely more than the minimum requirements for that. The seven TOS main characters (Kirk, Spock, McCoy, Scotty, Uhura, Sulu, Chekov) appear, but secondary characters that could be aboard the Enterprise such as Janice Rand, Christine Chapel, or Doctor M'Benga are not even mentioned. This may have to do with the fact that, aside from the bridge and the quick (non-interactive) glances in the transporter room, no scenes in the game play aboard the Enterprise. At the same time, guest characters who are not supposed to be on the Enterprise (Carol Marcus, Harry Mudd) just show up a reasonable amount of times, as accidentally running into familiar persons all the time would be rather contrived. Lastly, while the Klingons and Romulans, as well as some other Starfleet ships appear, all other planets and civilizations are entirely new. This is not necessarily a shortcoming, but if the game consisted of more episodes, it would be desirable to further strengthen the ties to the established universe with more than just the few most prominent characters and races known from TOS.

Overall rating: 8

 


Back to Product Reviews index

TopShare
View as gallery