Five Star Trek eras squeezed into one clumsy budget arcade shooter
Written from the published record (critics' reviews, the developer's documentation and the game's history), not a hands-on playthrough. How these are written.
A Star Trek license turned into an arcade shooter
Scottish studio 4J Studios built Star Trek: Encounters for Bethesda Softworks. It came out on PlayStation 2 in October 2006 as a budget-priced title. The year after, the studio went back to the license with Star Trek: Conquest.
The big change here is the genre. Encounters isn't a bridge simulator or a slow fleet tactics game. It's an arcade-style shoot 'em up with short missions and quick fights. It keeps the surface of Star Trek: ships and characters from The Original Series, The Next Generation, Deep Space Nine, Voyager and Enterprise, plus the Enterprise-E from Star Trek: First Contact. Phasers, sensors and photon torpedoes are all in.
Critics agreed that the surface is about all it keeps. Juan Castro of IGN wrote that it played more like a game about radio-controlled cars "with a Star Trek skin." He called it Star Trek "only in name." Metacritic put it at 51 from 17 critics, and a later count across 53 reviews landed at 5.8/10.
Six storylines with nothing tying them together
The story mode has six sections, one for each series plus one for the Enterprise-E. Each section tells its own self-contained plot. Some of the setups are strong:
- Enterprise: stopping a Xindi planet-destroying weapon and the orbs that build its parts.
- The Original Series: set between The Wrath of Khan and The Search for Spock, ending with a run from the shockwave of the exploding Genesis Planet.
- The Next Generation: a Romulan wormhole into Federation space, then an escape from inside a giant "living" weapon.
- Deep Space Nine: missions set during the Dominion War.
Star Trek: Legacy connected its eras with one overall story. Encounters doesn't, and critics named that as a common problem. They also flagged events that didn't fit established Star Trek canon. Greg Damiano of Game Revolution said William Shatner's introductions were "muted" and that text boxes did the rest. Missions played out with no radio chatter at all. Damiano also pointed to a planet-killer boss that never actually kills a planet, so the threat never feels real.
Why the flying wears thin
The biggest complaints were about the controls and the pacing. Benjamin Turner of GameSpy described lock-on and firing split across R2 and R1. Holding one while tapping the other got painful enough that he changed how he held the controller.
Kevin VanOrd of GameSpot went further. His review described:
- long stretches of flying from one point to another with nothing new to see;
- a warp-trail chase that ends the mission if the trail is lost for a few seconds;
- minefields along that path that cause cheap deaths.
VanOrd did credit some objectives, such as beaming crew elsewhere or towing a damaged ship to safety with a tractor beam. Those are the moments that use the license for something other than shooting. He still called the game a "budget-priced fiasco" and told waiting fans to keep waiting.
Skirmish is the better half, with the same flaws
The skirmish modes drop the empty travel, and that probably makes them the strongest part of the package. Head-to-Head is a one-on-one duel to a frag limit you set, and it can use unlocked enemy ships. Battlefest sends a group of three ships against another three, with each side bringing in its next ship as the last one falls. Onslaught gives you a Starfleet ship against endless, tougher waves, sometimes with orders to destroy a Romulan Nestar Station.
All of it runs on the same controls Turner described and the same combat Castro called "less than riveting." Skirmish removes the padding critics complained about. It doesn't fix the basic flying and shooting.
Sources
- Wikipedia: Star Trek: Encounters en.wikipedia.org
- Wikidata: Q7600975 wikidata.org