This is a good article. Click here for more information.

FreeSpace 2

From Infogalactic: the planetary knowledge core
(Redirected from Freespace 2)
Jump to: navigation, search
FreeSpace 2
Freespace2box.jpg
Box cover art for FreeSpace 2
Developer(s) Volition, Inc.
Publisher(s) Interplay Entertainment
Designer(s) Dave Baranec
Jason Scott
Adam Pletcher
Programmer(s) Dave Baranec
Artist(s) Jasen Whiteside
Writer(s) Jason Scott
Mike Breault
Composer(s) Dan Wentz
Platforms Microsoft Windows
Release date(s)
    Genre(s) Space combat simulator
    Mode(s) Single-player, multiplayer

    FreeSpace 2 is a 1999 space combat simulation computer game developed by Volition, Inc. as the sequel to Descent: FreeSpace – The Great War. It was completed ahead of schedule in less than a year, and released to very positive reviews. Engrossing gameplay, excellent sound effects in addition to the inclusion of vocal talent such as Robert Loggia and Ronny Cox led several gaming sites to proclaim it as the definitive simulation game for 1999.

    The game continues on the story from Descent: FreeSpace, once again thrusting the player into the role of a pilot fighting against the mysterious aliens, the Shivans. While defending the human race and its alien Vasudan allies, the player also gets involved in putting down a rebellion. The game features large numbers of fighters alongside gigantic capital ships in a battlefield fraught with beams, shells and missiles in detailed star systems and nebulae. Free multiplayer games were available via Parallax Online which also ranked players by their statistics. A persistent galaxy was also available as SquadWar for players to fight with each other over territories.

    In 2002, Volition released the source code for the game engine under a non-commercial license. This code became the core of the FreeSpace 2 Source Code Project, which continuously improves it and enables new features. In cooperation with the FreeSpace Upgrade Project the game's graphics are kept up to date.[1] The improved game engine is also used by various mod projects, for example The Babylon Project and Diaspora which are based on the science fiction series Babylon 5 and Battlestar Galactica respectively.

    Gameplay

    A corvette and a destroyer attacking each other with beam cannons

    FreeSpace 2's gameplay involves the player piloting a starfighter using mounted weapons to destroy enemy starfighters, performing reconnaissance behind enemy lines, or escorting other starships.[2][3] Its flight model is based on a looser interpretation of space physics instead of realistic Newtonian physics.[4] Hence, the ships are weightless and feel more responsive, though they require constant application of engine power to move.[5] The result is that the game plays more like a "WWII dogfight simulator" unaffected by gravity.[6] Although joysticks are the recommended controller for this game, the mouse is a viable alternative.[7] Single player mode is executed in the form of a campaign, which follows a story as a linear sequence of missions are executed.

    The pre-mission briefing stage is where the player gets information on the background and objectives, and selects the ship and weapons.[8] The choices of ships and weapons increase as the player proceeds further along the campaign. Certain missions, however, will dictate certain ships and weapons to be used. Weapons can be classified into primary weapons and secondary weapons.[8] Primary weapons are kinetic and energy weapons, while missiles and torpedoes are classified as secondary weapons. Each weapon has its own specifications such as its rate of fire. They also inflict different damages on hulls (body of the ships) or shields (the protective energy fields surrounding the ships), or possess special effects such as shutting down specific electronic systems or propulsion.

    The player flies around in a fighter with a first-person, in-cockpit view with a fully customizable fixed head-up display (HUD) as the visual interface.[9][10] The HUD displays video communications and relevant data on the ship's status and performance, weapons, objectives, and targets. It can also warn players from which direction missiles are locking onto them from, thus becoming an aide for launching countermeasures or taking evasive maneuvers.[11] Players have to maneuver into position and shoot through both shields and hull to destroy enemy ships.[12] While hull damage is unrecoverable, shields recharge over time. With the game supporting force feedback technology, joystick players will find their controllers vibrating or putting up resistance when they engage the afterburners or collide with objects.[13] Similarly, certain events, such as engaging afterburners and firing powerful weapons, will shake the screen as a form of visual feedback.[11]

    FreeSpace 2 has many helpful features available. The player can target enemies attacking a protected objective or match speeds with them. Power can be shunted between shields, engines, and weapons, thereby allowing faster recharge of shields, afterburners, and weapons at the expense of other subsystems. These features can be ignored without any detrimental effects on gameplay.[14][15] The mission parameters are not rigidly fixed, as there is an allowance for the failures of some primary objectives.[11] When the mission is concluded, a post-mission briefing will be conducted to discuss the mission, and the performance of the player, before the next mission can be taken on.

    FreeSpace 2 allows multiplayer games to be played across a local area network (LAN) or over the Internet via the free services provided by Parallax Online (PXO).[16] The player can communicate with the other network players vocally through FreeSpace 2's own voice chat capability.[17] LAN play allows the players to play the standard player versus player modes such as deathmatch, or cooperate to complete multiplayer missions. They can even join in games which are already underway.[18] The same can be done over PXO but with the added incentive of having the players' statistics of kills and deaths being tracked on a ladder (ranking) system.[13] Players can also form up or join squadrons in SquadWar, an online persistent galaxy hosted by Volition on PXO, where squadrons fight each other for territories.

    Plot and setting

    FreeSpace 2 takes place entirely in outer space. The playing area is vast when compared to the small starfighters piloted by the player and the effective range they have. This space is populated with interstellar bodies such as stars, planets, asteroids, etc.[15][19][20] The implementation of nebulae as an interactive environment is one of the most distinctive and crowning aspects of FreeSpace 2.[21][22] Flying through a nebula involves impaired vision, and occasional disruptions to flight electronics. Nebulae have become known as an eerie and suspenseful arena of play.[3][6]

    Journeys between star systems are achieved by "jumping" through jump nodes and traveling through subspace, while shorter intra-system distances are done by "hopping" into subspace at any time.[23] All ships in a mission either "jump" or "hop" to make their entries and exits. The game's starship designs are clearly distinguishable between the three races.[15] Terran starships tend to be plain and practical, the Vasudans' starships are artistic with sleek lines and curves, and the enemies' ships—the Shivans—are sharp, pointy and asymmetrical in insidious black and red colors.[12] FreeSpace 2 also features humongous capital ships, hundreds of times larger than the fighters, and armed to the teeth with beam weapons and flak guns. These ships are commonly scripted to seek each other out and engage in massive duels.

    FreeSpace 2's story is brought out via narrative pre-rendered cutscenes, the pre- and post-mission briefings, as well as in-game chatter between non-player characters, and scripted mission events.[13][22] The structure for the story is linear without any branching paths for alternate storylines, though there are optional covert missions which can further flesh out the story.[11] The story can only be continued by clearing missions and progressing through the campaign. However, players are given the option to skip a mission if they have failed it five times in a row.[14] This gives those who are interested in the story, but less skilled, the chance to continue on with the story without frustration.

    Characters

    The player takes the role of a pilot in the ranks of the Galactic Terran–Vasudan Alliance (GTVA). While the appearance and name of the pilot can be customized by the player, the player never gets to personally interact with other characters in the game. The pilot is also never shown in the game's cinematics or any other media. This distant approach led to complaints of the game failing to motivate the player into the story.[24] However, the game's writer, James Scott, has stated the approach was to preserve the feeling of being a "nameless cog in the great machine" as per the first game.[25]

    Just like the player's pilot, most of the other characters are low-key. The non-player character Admiral Aken Bosch, however, plays a crucial part in moving the story. As a prominent antagonist from the start, he sparks off a rebellion which escalates the scale of action, and brings in the other antagonist force, the Shivans, into the story. The storytelling took on a character-driven approach with expositions taking the form of cutscenes in which Bosch gives out monologues, revealing the purpose and driving forces behind his actions. A few established voice actors were brought in to give a polished touch to the voices in the game.[22] Academy Award nominee Robert Loggia voiced the player's commanding officer, Admiral Petrarch, and Admiral Bosch was voiced by Ronny Cox. Kurtwood Smith and Stephen Baldwin participated in bit roles as well.

    Story

    The game begins 32 years after the events in Descent: FreeSpace. Following the end of the Great War, both the GTA and PVE cemented their alliance by combining together to form the Galactic Terran–Vasudan Alliance (GTVA)—a single entity formed to cement the alliance between the Terran and Vasudan races after the destruction of Vasuda Prime by the Lucifer and the subsequent collapse of all subspace nodes to the Sol system as a result of the superdestroyer's destruction inside the Sol–Delta Serpentis jump node.[14] Despite this alliance, however, opposition still exists to this union in the form of a faction of Terrans led by Great War veteran, Admiral Aken Bosch, who leads the rebel group under the banner of the Neo-Terran Front (NTF). The NTF's rebellion led to the faction gaining control over the Sirius, Polaris and Regulus star systems, while engaging the GTVA for 18 months, before launching attacks on the Vasudan systems of Deneb and Alpha Centauri.

    Seeking to stop the NTF from securing Deneb, the GTVA launch a campaign in the star system, though they are shocked to find Bosch within. An effort to stop him fails badly, and so the GTVA focus on securing the star system, with great success. Just as further engagements against the NTF are about to commence, an incident in the Gamma Draconis system leads to the 3rd Fleet of the GTVA being reassigned to the star system, where they learn that the Shivans have returned, along with the discovery of an artificial jump gate that leads to Shivan space. After securing the device and passing through it, the GTVA discover a nebula along with more Shivans, and a cruiser of the NTF, the Trinity. Despite efforts to secure and recover the cruiser, the Trinity is destroyed, and the GTVA fleet focus on dealing with the Shivans, before returning to Gamma Draconis for reassignment.

    The NTF rebellion soon becomes the focus of attention once again after attacks intensify, eventually leading the GTVA to quell an attack on a space station with their latest ship, the enormous capital ship GTVA Colossus. Dwarfing all other capital ships, this juggernaut-class ship's power proves more than a match to many NTF ships, defeating a major officer in the rebellion. Seeking to captalize on this, the GTVI (Galactic Terran–Vasudan Intelligence) organise an operation with their SOC (Special Operation Command) to investigate and uncover information on Bosch's ETAK project, which is nearly wrecked when a Vasudan admiral attempts to hit Bosch's flagship, the Iceni.

    Following the latest campaign against the NTF, GTVA forces re-engage Shivan forces in the nebula, while testing out new weapon and technology prototypes such as an AWACS cruiser that enables better vision in the nebula, a TAG missile that enables friendly capital ships to instantly lock on to the "tagged" enemy ship, and the Pegasus-class stealth fighter. With the aid of these new technologies, the Alliance destroys a Shivan Ravana-class destroyer. The 3rd Fleet soon return to GTVA space, where Bosch launches an assault to get the NTF to the Jump Gate. While the NTF loses many ships, the Iceni escapes with Bosch on board, thanks to sabotage preventing the GTVA Colossus from firing on it. While pursuing Bosch into the nebula, the GTVA attack Shivan nebular gas mining operations, only for the Shivans to retaliate with a juggernaut-class warship of their own, dubbed the Sathanas. The Sathanas enters Terran–Vasudan space, despite an effort to destroy the jump gate linking the nebula to Gamma Draconis; the node between the two system had stabilised at some point. With the Shivans encroaching on GTVA space, the Sathanas is engaged by the Colossus as it enters the densely populated Capella system and, thanks to the player's efforts in disabling its beam turrets, is destroyed in the engagement.[26]

    The Alliance Fleet soon resumes it efforts to track down Bosch, and discover that Bosch had built a device that enables him to communicate with the Shivans, which was the purpose of ETAK; the Alliance realise the jump gate was activated by Bosch, who had been stealing artefacts from archaeological sites looking into the Ancients, and had been hoping to meet and contact the Shivans. The Shivans respond to his transmission, and in turn board his command frigate, the Iceni, and capture him and fifteen other crewmen before attempting to destroy it. The GTVA manage to save the surviving crew of the Iceni and the ETAK device, but as they try to intercept the Shivan transport carrying Bosch, they discover a second jump gate in the nebula, which the Alliance destroyer, the GVD Psamtik, attempts to secure. However, it is destroyed by another Sathanas juggernaut shortly afterwards, forcing the GTVA to pull out. During this time, the GTVI and SOC launch a secret operation within the nebula, at great risk, to recover an operative and check the other side of the gate, discovering the threat posed to the GTVA by the Shivans is much greater than they had thought.[27]

    The Alliance devises a plan to halt the Shivan invasion while evacuating civilians and others from the Capella star system, by collapsing the two jump nodes from Capella to the rest of GTVA space. The Alliance plans to recreate the same conditions that collapsed the Sol jump nodes—namely a sufficiently powerful meson explosion, using a number of Great War-era destroyers, including the Bastion, which the GTVA send out to collapse the Capella–Epsilon Pegasi node by detonating its payload while it is within the node.[28]

    The plan works but it is pyrrhic victory, as the GTVA loses the Colossus, their only match for Shivan juggernauts, in a diversionary engagement at the other end of the Capella system. With not much left to do but escort the remaining evacuation convoys to the Capella–Vega jump node while a second payload is sent to the jump node, the GTVA soon begins to detect activity from the system's star, which is being bombarded with an intense subspace field by numerous Sathanas-class ships. This causes the star to goes supernova, destroying the fighting GTVA and Shivans in system. The player can choose to flee the scene when the warning is given or stay and die defending the remaining ships, which affects the ending slightly.[29] In the ending cutscene the player's commanding officer, Admiral Petrarch, delivers a speech about everything the Alliance has lost, speculating on the nature of the Shivans and why they destroyed the Capella star, and if the player decides to stay, a small tribute is paid to the player's heroic actions as Petrarch informs his wingmen of his sacrifice. The Admiral concludes by saying that the Alliance now has the means to recreate the Ancient subspace gate, implying that there's a chance the node to Earth can be restored and that this conflict didn't bring only sorrow, before signing off.

    Development

    The news of FreeSpace 2 being in development was confirmed in a chat on November 6, 1998. The Volition team revealed they had written up a deep story and will be targeting high-end hardware with dogfights for a greater number of ships and even larger and more deadly capital ships.[30] The team set themselves the goals of setting new standards for both single-player and multiplayer space combat simulations,[17] and started to modify the FreeSpace game engine for FreeSpace 2.[31] This team was the same team which had worked on Descent: FreeSpace, plus several new members. In order to flesh out the story, Volition hired Jason Scott as a full-time writer before work even started.[25][32] The linear mission structure was adopted as it was decided it would help the immersion factor of the story greatly.[8] As the relations between the Terrans and Vasudans dominated the first game, it was decided to scale the focus down to a personal level with Admiral Bosch and his decisions to rebel. Scott's close work with the designers, and co-ordination of the voice recording process helped to tightly integrate the story into the missions, giving a more sophisticated feel to the story.

    Due to time constraints, a lot of the initial ideas were dropped from the final version of the game, such as atmospheric battles, and new weapons types like a "subspace missile artillery strike". The team made major improvements to the same FreeSpace engine from the first game.[8] By revamping the core of the graphical engine, and adding 32-bit support, they sped up the interface screens and graphic processing.[33] Hardware acceleration for the graphics was also decided to be a requirement to target the high-end machines of 1999.[30] This allowed for a greater number of ships visibly active on the battlefield, satisfying the team's penchant of having great numbers of fighters and capitals ships duking it out in a big battlefield, instead of "multiple small-ass" battles.[30] The shifting of their target focus to higher end machines also fulfilled their top priority of having capital ships many times larger than fighter crafts.[31] The team also followed real world concepts for some of their designs. The Pegasus stealth fighter was modeled on the stealth technology of the 1990s for people to relate to it easily. The game was restrained from becoming too realistic by the team's recognition that most gamers only want believable worlds to have a blast flying around in and blowing things up.[4]

    Compared to the graphical changes, the artificial intelligence (AI) of the computer-controlled characters was only slightly changed. The justification given was that the team felt the AI worked very well for the first game. All they had to do was to tweak it a little and fix some bugs.[31] There was, however, a lot of work done in improving the multiplayer portion of the game. For FreeSpace 2, the player's personal computer was assigned a greater role in predicting the possible consequences for other players' actions. This reduced the amount of data needed to be transferred between the computers, which would result in a smoother playing experience. Beta testers were recruited to stress test and troubleshoot the multiplayer mode as well.[34] SquadWar was implemented as an attempt to establish a sense of continuity among the players in the form of a persistent online territorial fight, along with pilot statistics and ladder rankings. Volition hoped this concept would help to establish a strong, online community and build up the game's lifespan.[35] The process of fixing the bugs detected was even publicly published on the game's official website as the "Bug Fix of the Day" feature.

    FreeSpace 2 was released on September 30, 1999, one month ahead of schedule.[36] However, the team had to quickly come up with and release a patch (version 1.01) for a software bug which prevented recognition of a CD during the installation process.[37] Three months later, they released the next and final patch (version 1.20) to fix several other bugs.[38] The release of FreeSpace 2 was considerably muted compared to its predecessor Descent: FreeSpace.[39] Its publisher, Interplay, did not organize contests for it, nor did they generate pre-release hype up with the same drive as before. They also posted the incorrect system requirements for the game on their site. FreeSpace 2 was also placed on less-visible shelves than Descent 3. However, when GameSpot awarded FreeSpace 2 the "Sci-Fi Simulation of the Year" award, Interplay pushed out the "Sci-Fi Sim of the Year Edition" to capitalize on it.

    Despite Volition's interest and desire to develop add-ons and expansions for FreeSpace 2, Interplay told them to stop.[39] Volition was then acquired by THQ in 2000. As Interplay owns the rights to the FreeSpace series (as well as the Descent series) and Volition's owners, THQ, is only interested in pursuing development on what they own, Volition was unable to continue developing the FreeSpace franchise.[40] Faced with source code which became practically useless to them, Volition released the source code for only game engines to the public under a noncommercial license on April 25, 2002.[41][42] Mike Kulas, the President of Volition, said this was to give those outside the game industry a chance to look at the code of a commercial software product, a desire he and Matt Toschlog had when they were not yet in the industry. In the years since, no sequels to FreeSpace 2 have been made and Interplay has only published a limited re-release of it on February 2, 2004, to commemorate the company's 20th anniversary.[9] Interplay, by that time, was in financial trouble, failing to pay rent and wages to its workers. Seeking investors to inject it with funds, Interplay changed business strategies: instead of developing and publishing single-player games, it sold licenses to those games and looked towards developing massive multi-player online games.[43][44][45] Derek Smart, creator of Battlecruiser 3000AD, had casually mentioned his interest in the Freespace license, but nothing significant came out of this.[46][47] In 2013, Interplay acquired the remaining rights to the FreeSpace franchise for $7,500 after THQ went to bankruptcy court.[48]

    Reception

    FreeSpace 2 reviews
    Publication Score
    GameSpy
    92 / 100[10]
    GameSpot
    9.4 / 10[13]
    IGN
    8.9 / 10[14]
    GamePro
    5 / 5[49]
    PC Gamer
    93%[50]
    The Electric Playground
    8.5 / 10[16]
    Computer and Video Games
    8.5 / 10[6]
    FiringSquad
    90%[15]
    Eurogamer
    7 / 10[24]
    Compilations of multiple reviews
    Compiler Score
    Metacritic
    91 / 100[51]
    Game Rankings
    92.0%[52]
    Awards
    PC Player's Best Space Combat Game of 1999[53]

    Intelligamer 1999 Sim Game of the Year[54]
    CGW's 2000 Premier Award Winner[55]
    GameSpot's Sci-Fi Simulation of the Year[56]
    GamePower's Best Sim of '99[57]
    GameSpy's Sim Game of the Year[58]
    FiringSquad's Best Action Game of 1999[59]
    Computer Games' Sci-Fi Simulation of the Year[60]
    PC Player's All Time Top 100 Games[61]
    GameSpot's Greatest Games of All Time[21]
    The game's backdrops have received high praise from reviewers

    FreeSpace 2 has garnered high praise from most established reviewers. FreeSpace 2 received numerous "Game of the Year" awards for 1999, and was nominated for "Computer Simulation Game of the Year" in the 3rd Annual Interactive Achievement Awards, 2000.[62] Every review praised FreeSpace 2's graphics. From the ships to the backgrounds, the reviewers were pleased with the details Volition had paid attention to, such as the thematic differences in the ship designs between the races, the textures and clarity of the backdrops, and even the realism of the explosions, though FiringSquad pointed out explosions from torpedo strikes were lower in quality. The nebulae feature was also praised for its rendered atmosphere, which reviewers described as tense and paranoia-inducing as they keep expecting enemy ships to appear out of the gases in a deadly ambush.[10][15] Even though a couple of reviewers wrote that the nebulae made them dizzy, they still liked the feature.[2][18] Combatsim even claimed FreeSpace 2 was unrivaled among its space combat peers in the graphics department.[63] The graphical standards were such that when XGP reviewed the Anniversary Edition in 2004, Wehbi found the graphics to stand up quite well to the recent games then.[9]

    GameSpot felt FreeSpace's story was "both deeper and darker" than either the Wing Commander and X-Wing series, establishing invincible foes who never lost their stature despite the player learning of plausible ways to defeat them. Game Revolution felt the story was "first rate" for being able to "build several different conflicts into an unforgettable climax", nicely presented by the emphasis of story telling by means of in-game events.[22] While Eurogamer supported the story as intriguing, it also marked down its rating of the game for the way the story was told. The reviewer felt the "just a cog in the machine" story-telling approach left him apathetic towards the non-player characters and missions in the game. FiringSquad, however, said it created a "very believable military atmosphere," which helped to show how things revolve around big events, instead of just around a single person. Combatsim.com offered another angle; Reynolds said the gameplay elements of FreeSpace 2 are "light years beyond the competition" and more than offsets the loss of being personally immersed in the game's universe.[63]

    FreeSpace 2's key attraction is its dogfights. CNN.com said the close-ranged dogfights make for engrossing, and exciting skirmishes.[64] FiringSquad described it as a "total thrill" to be among 20 fighters flying in between opposing capital ships with beams, missiles, and flak all around and warnings going off, as they try to seek out and destroy their opposite numbers, a view which GameSpot agreed with.[21] The game's AI was judged adequate to provide for such fights, being cunning enough to trick others to crash into the walls of narrow openings, and good enough to detect and warn their wingmen of enemies coming up directly behind them.[16][20] There are those who expressed minor disappointments with the AI tending to collide too often with other objects.[13] While the dynamic mission objectives were celebrated for coming up with twists and turns to spice up the story,[12][14][22][63] there were a few who found these "in-game red herrings" overused instead.[3] Sharky Extreme praised FreeSpace 2 for having the enormous capital ships, as this burst the "trapped in a bubble" trend in Wing Commander- and X-Wing- type games.[20] Instead of the action simply coming to the player, it flows all around, and the player is the one who has to go and seek it. The scenes of these giant ships duking it out, with many gnat-like fighters swarming around in their little dances of death, have led reviewers to feel a sense of epicness,[6][13] comparable to reliving battles in science fiction series like Babylon 5 and Star Wars.[3][63] Similarly, PC Gamer praised the scaling of ships and battles and said that they "[came] as close to creating the feeling of a World War II naval battle in space as any game has ever come" and that "That's what fighter combat, in space or on Earth, should be all about.".[50]

    Opinions were generally favorable towards FreeSpace 2's multiplayer implementation.[12][15] SquadWar received favorable responses from the reviewers who were impressed by its persistent nature and statistics tracking.[11][13] While the required registration with PXO was considered a troublesome process by a few, the gameplay itself was a smooth experience with no lag at all.[16][20] Other reviewers' experiences with lag were different. Reynolds of Combatsim.com said Internet gaming was laggy with ships jumping places, but LAN gaming was smooth sailing.[63] GameSpy's reviewer said lag became more apparent on a dial-up connection during a multiplayer mission with four or more players. FiringSquad's reviewer's experience was similar but he said the lag was not enough to hinder his enjoyment of the multiplayer action.[10]

    GameSpot, in electing FreeSpace 2 as one of the "Greatest Games of All Time", pointed out that while most of the game's features could be found in its predecessor or peers, its "sheer quality of presentation and gameplay" was the key reason for their choice.[21] Computer and Video Games has acknowledged it as offering the best dogfighting among the space combat classics.[65] Ars Technica also posed FreeSpace 2 as the last significant stage in evolution of the space combat genre as of 2005.[66]

    Despite all the glowing reviews, FreeSpace 2 sold poorly. The April 2000 issue of PC Gamer stated that only 26,983 copies had been sold in the first six months of its release.[67] These figures were acknowledged as disappointing, and described as awful by Kulas. He, however, stated that as the team had stayed within budget by sticking to schedule, Volition should at least be breaking even with the estimated final sales of the game.[68] In NowGamer's interview with Jim Boone, a producer at Volition Inc., he stated that this could have been due to joysticks' being sold poorly because they were "going out of fashion" because more modern first-person shooters, such as Quake, were "very much about the mouse and [the] keyboard". He went further on to state "Before that, when we did Descent for example, it was perfectly common for people to have joysticks – we sold a lot of copies of Descent. It was around that time [when] the more modern FPS with mouse and keyboard came out, as opposed to just keyboard like Wolfenstein [3D] or something.".[69]

    Fans of the FreeSpace series have created modifications (mods) of FreeSpace 2. The first mods were just custom campaigns, with series of missions created through FRED2, the mission editor freely packaged with FreeSpace 2. One such mod which gained notability was Inferno, which sets its story decades after the conclusion of FreeSpace 2. Released in July 2003, the mod was hosted on established sites, such as GameSpot and CNET, as part of their FreeSpace 2 contents.[70]

    Source code project

    <templatestyles src="Module:Hatnote/styles.css"></templatestyles>

    Main article: FreeSpace 2 Source Code Project

    With the release of the game engine's source code, the possibilities of changing the game greatly opened up, and the fan community made use of the code to update the game using recent technology. Led by Edward Gardner and Ian Warfield, the FreeSpace 2 Source Code Project was formed to standardize changes and maintain a core engine for others to take advantage of. Using the new fan-updated engine, projects such as Beyond the Red Line, based on the new Battlestar Galactica, and The Babylon Project, based on Babylon 5, have become possible.[71] PXO, the free Internet gaming service handling SquadWar, was initially acquired by THQ in their 2002 acquisition of Outrage Entertainment (renamed as Outrage Games).[72] The service was continued until July 2003, when Outrage Games was dissolved and PXO terminated. The components of its website were, however, later handed over to the FreeSpace 2 Source Code Project to help them create a similar service in tracking statistics and rankings.[73]

    References

    1. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    2. ↑ 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
    3. ↑ 3.0 3.1 3.2 3.3 Lua error in package.lua at line 80: module 'strict' not found.
    4. ↑ 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.
    5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    6. ↑ 6.0 6.1 6.2 6.3 Lua error in package.lua at line 80: module 'strict' not found.[dead link]
    7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    8. ↑ 8.0 8.1 8.2 8.3 Lua error in package.lua at line 80: module 'strict' not found.
    9. ↑ 9.0 9.1 9.2 Lua error in package.lua at line 80: module 'strict' not found.
    10. ↑ 10.0 10.1 10.2 10.3 Lua error in package.lua at line 80: module 'strict' not found.
    11. ↑ 11.0 11.1 11.2 11.3 11.4 Lua error in package.lua at line 80: module 'strict' not found.
    12. ↑ 12.0 12.1 12.2 12.3 Lua error in package.lua at line 80: module 'strict' not found.
    13. ↑ 13.0 13.1 13.2 13.3 13.4 13.5 13.6 Lua error in package.lua at line 80: module 'strict' not found.
    14. ↑ 14.0 14.1 14.2 14.3 14.4 Lua error in package.lua at line 80: module 'strict' not found.
    15. ↑ 15.0 15.1 15.2 15.3 15.4 15.5 Lua error in package.lua at line 80: module 'strict' not found.
    16. ↑ 16.0 16.1 16.2 16.3 Lua error in package.lua at line 80: module 'strict' not found.
    17. ↑ 17.0 17.1 Lua error in package.lua at line 80: module 'strict' not found.
    18. ↑ 18.0 18.1 Lua error in package.lua at line 80: module 'strict' not found.
    19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    20. ↑ 20.0 20.1 20.2 20.3 Lua error in package.lua at line 80: module 'strict' not found.
    21. ↑ 21.0 21.1 21.2 21.3 Lua error in package.lua at line 80: module 'strict' not found.
    22. ↑ 22.0 22.1 22.2 22.3 22.4 Lua error in package.lua at line 80: module 'strict' not found.
    23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    24. ↑ 24.0 24.1 Lua error in package.lua at line 80: module 'strict' not found.
    25. ↑ 25.0 25.1 Lua error in package.lua at line 80: module 'strict' not found.
    26. ↑ Vasudan Commander: At 0345 hours, the GTVA Colossus destroyed the Shivan juggernaut Sathanas near the Gamma Draconis jump node in Capella. This victory proves without a doubt our technological superiority over our Great War nemesis. For the second time, the Alliance defeated a species which has annihilated entire civilizations across this galaxy. With the Colossus, we will have nothing more to fear. Lua error in package.lua at line 80: module 'strict' not found.
    27. ↑ Admiral Petrarch: Nine Sathanas juggernauts have now entered the Capella system, and Intelligence has sighted even more in the nebula, converging on the jump node to Terran–Vasudan space. We are on the threshold of a new apocalypse. Though the juggernauts have not engaged our warships, they have set course for the Capella star. We can only speculate about their intentions, but this development cannot bode well for the Alliance. Lua error in package.lua at line 80: module 'strict' not found.
    28. ↑ Admiral Petrarch: Preparations are now underway to collapse the Epsilon Pegasi jump node. A Great-War-era destroyer, the GTD Bastion, will contain multiple meson warheads that will detonate inside the node. Scientists believe an explosion of sufficient magnitude will cause this node to collapse, as evidenced by the destruction of the Lucifer 32 years ago. The detonation of the Lucifer's reactors sealed off the Sol jump node in Delta Serpentis and severed all contact with Earth. Lua error in package.lua at line 80: module 'strict' not found.
    29. ↑ Terran Commander: We are detecting a massive shockwave emanating from the Capella sun! All units, proceed to the Vega node! You are advised to leave the system immediately! Lua error in package.lua at line 80: module 'strict' not found.
    30. ↑ 30.0 30.1 30.2 Lua error in package.lua at line 80: module 'strict' not found.
    31. ↑ 31.0 31.1 31.2 Lua error in package.lua at line 80: module 'strict' not found.
    32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    37. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    38. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    39. ↑ 39.0 39.1 Lua error in package.lua at line 80: module 'strict' not found.
    40. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    41. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    42. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    43. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    44. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    45. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    46. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    47. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    48. ↑ Interplay Buys Freespace Rights For a Cool $7,500
    49. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    50. ↑ 50.0 50.1 Lua error in package.lua at line 80: module 'strict' not found.
    51. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    52. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    53. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    54. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    55. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    56. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    57. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    58. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    59. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    60. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    61. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    62. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    63. ↑ 63.0 63.1 63.2 63.3 63.4 Lua error in package.lua at line 80: module 'strict' not found.
    64. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    65. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    66. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    67. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    68. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    69. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    70. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    71. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    72. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    73. ↑ Lua error in package.lua at line 80: module 'strict' not found.[dead link]

    External links

    cs:Freespace fr:Descent: FreeSpace sk:FreeSpace

    Retrieved from "https://infogalactic.com/w/index.php?title=FreeSpace_2&oldid=4230342"