Star Trek: Bridge Commander

From Infogalactic: the planetary knowledge core
(Redirected from Bridge Commander)
Jump to: navigation, search
Star Trek: Bridge Commander
File:Star Trek - Bridge Commander Coverart.png
Developer(s) Totally Games
Publisher(s) Activision
Designer(s) Bill Morrison, Tony Evans, Jess VanDerwalker, Derek Chester, Dorothy Fontana
Engine Gamebryo
Platforms Microsoft Windows
Release date(s)
    Genre(s) Space combat simulator
    Mode(s) Single-player, Multiplayer Online

    Star Trek: Bridge Commander is a space combat simulation video game, published by Activision and Totally Games in 2002, based in the Star Trek universe.

    The plot revolves around a newly promoted captain who is assigned to investigate an explosion of a star in the Maelstrom. Throughout the mystery, the player will often encounter characters from the Star Trek universe, including Captain Picard and Commander Data. The captain and his crew take command of the Galaxy-class USS Dauntless (NCC-71879) as well as the USS Sovereign (NCC-73811) to combat a new threat to the Federation.

    The game allows two different styles of gameplay: storyline mode and quick battle mode. Quick battle mode allows for customized scenarios within a "simulated" environment, allowing the player to pick their allies/enemies, system, etc. With the advent of modding for Star Trek: Bridge Commander, custom missions and even campaigns have been made possible through this engine.

    Gameplay

    Main game screen, viewing from bridge.

    There are several game play modes in Bridge Commander, with the main two means of control being the bridge view and the tactical view. While the bridge view has the player control the movements of the ship by interacting with members of the bridge crew, the tactical view changes to an external view allows the player to have direct control over the starship. A variety of shortcut keys work in the same manner in both modes. Additional modes in the game include the map mode and the cinematic mode, which removes the interface from being displayed and also switches to an external view of the ship.[2]

    In the bridge view, most game functions are carried out by selecting an individual bridge officer, and selecting from a set of commands or options in order to control that individual's set of responsibilities.[3] In this way, the game simulates being in command of a starship. For example, a player could issue the command to intercept a fleeing starship through the Helm menu, or order Lt. Felix Savali, the tactical officer to destroy an enemy ship. An AI would then pilot the ship for the player.[4]

    Bridge Commander incorporates a Quick Battle mode which is a combat simulation that allows the player to control any ship encountered during the course of the game. There is also a selection of a system which on rare occasions, incorporates their own unique hazards.[5] The multiplayer mode is no longer operated by GameSpy, but is now hosted by 333networks, allows for a maximum of 8 players over the internet to compete in one of four modes; Deathmatch, Team Deathmatch, UFP vs Non-UFP Deathmatch and Defend the Starbase.[6]

    Players also have the option to switch to an external ship view, and carry out many piloting and weapons functions themselves. In this view, they are able to view various tactical indicators.

    Storyline

    The USS Dauntless is in orbit of planet Vesuvi III. Her captain, Robert Wright, is piloting a shuttle to a research station orbiting the planet when the star goes supernova, destroying the planet, killing the captain, and severely damaging the Dauntless. After several months of repairs and refits, the Dauntless' first officer becomes her new captain, and after a brief resupply mission to the surviving Vesuvi colonies, an investigation into the star's destruction begins.

    The Dauntless crew is later given the USS Sovereign, the USS Enterprise-E's sister ship, for the investigation. They also undergo a shakedown cruise to check for bugs in the ship's systems which results in a simulated battle against the USS Geronimo and two Birds of Prey. Additionally, Lieutenant Commander Data from the Enterprise is temporarily assigned to the Sovereign to assist in the investigation. Initial hostilities with the Romulans briefly lead the crew to suspect them as the culprits, but further evidence reveals a renegade faction of Cardassians are responsible. They are led by Legate Matan, the game's central villain.

    Matan is assisted by a new race of aliens called the Kessok whom Matan exploited and lied to in order to gain their cooperation. While searching for the technology that destroyed the Vesuvi star in the Alioth system, the Sovereign is ambushed and forced to leave Data behind on the surface of the system's sixth planet.

    The revelation of the Cardassians' responsibility for the destruction of the Vesuvi star leads to a full-scale war between the Federation and Matan's faction.[7] The Federation is at first at a disadvantage, having underestimated Matan's forces; however, they are able to repel an offensive against Starbase 12 and destroy Litvok Nor, a Cardassian space station identical to Deep Space 9, and rescue Data. Additionally, a Federation–Klingon–Romulan alliance is formed to put an end to the war in the game's final missions.

    Shortly after Data's rescue and the formation of the alliance, the Sovereign is ordered to destroy the remaining Kessok technology that destroyed the Vesuvi star. During an encounter with a Kessok heavy cruiser, which makes no hostile movements and is unshielded, the player is presented with a choice: destroy the Kessok ship and the remaining device or hail it. If the player fires on the Kessok ship, two smaller vessels will de-cloak and assist the heavy cruiser. The final mission will also be more difficult as the Kessok forces will initially side with the Cardassians. Hailing the vessel will open a dialog with the Kessok and reveal the Cardassians' exploitation of them.[8]

    The game's final mission involves destroying the remaining Kessok device in the custody of Matan before he can use it to destroy a newly founded Kessok colony. The final confrontation with Matan occurs near the star of the Omega Draconis system. The game ends with Matan's ship falling into the star and the beginnings of formal diplomatic relations with the Kessok. Captain Picard wishes the player good luck on their journeys, and the Sovereign warps away.[9][10]

    Development

    In late 1998, publishers Activision made contact with Totally Games for the start of development of Bridge Commander. Employees working for Totally Games spent six months on research, design and testing to keep the game within the bounds of the Star Trek universe.[11] At E3 2001, the Multi-Player mode originally to be included was dropped in favour of Single-Player. This announcement was reversed several days later.[12]

    Reception

    Reception
    Aggregate scores
    Aggregator Score
    GameRankings 80.11%[13]
    Metacritic 82[14]
    Review scores
    Publication Score
    GameSpot 8.2/10[15]
    IGN 9/10[16]

    Star Trek: Bridge Commander received positive reviews from critics, scoring 80.11% and 82 out of 100 on the review aggregator sites GameRankings and Metacritic respectively.[13][14]

    Ivan Sulic for IGN said that Bridge Commander was "the single most engaging Star Trek experience yet in gaming" and the "undisputed king of all that is starship combat",[16] but appreciated that some players may feel that it isn't as nonlinear as they might like. He added that the missions were well paced, although complained of the difficulty of a stealth based level.[16]

    Citations

    1. Lua error in package.lua at line 80: module 'strict' not found.
    2. Rodriguez y Gibson (2002): pp. 8-9
    3. Rodriguez y Gibson (2002): p. 10
    4. Rodriguez y Gibson (2002): pp. 17-18
    5. Lua error in package.lua at line 80: module 'strict' not found.
    6. Lua error in package.lua at line 80: module 'strict' not found.
    7. Lua error in package.lua at line 80: module 'strict' not found.
    8. Lua error in package.lua at line 80: module 'strict' not found.
    9. Lua error in package.lua at line 80: module 'strict' not found.
    10. Lua error in package.lua at line 80: module 'strict' not found.
    11. Lua error in package.lua at line 80: module 'strict' not found.
    12. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
    13. 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found.
    14. 14.0 14.1 Lua error in package.lua at line 80: module 'strict' not found.
    15. Lua error in package.lua at line 80: module 'strict' not found.
    16. 16.0 16.1 16.2 Lua error in package.lua at line 80: module 'strict' not found.

    References

    • Lua error in package.lua at line 80: module 'strict' not found.

    External links