Recent changes Random page
GAMING
Entertainment
 
Star Wars
Star Trek
Transformers
 Muppet Wiki
Digimon Wiki
Marvel Database
See more...

Star Wars: Empire at War

From Wookieepedia, the Star Wars wiki.

Jump to: navigation, search
Star Wars: Empire at War
Developer(s)

Petroglyph

Publisher(s)

LucasArts

Game engine

Alamo

Release date

February 16, 2006

Genre

Real-Time Strategy (RTS)

Modes

Single player, multiplayer

Rating(s)

ESRB: Teen (T)
OFLC (AU): M
USK: 12

Platform(s)

PC (Windows), Mac OS X

[Source]

Star Wars: Empire at War, (sometimes abbreviated to simply EaW), is a real-time strategy (RTS) game that takes place in the Star Wars universe. Promising to end the mediocrity of past Star Wars RTS games (namely Star Wars: Force Commander), Empire at War started from the ground up.

The game was developed by Petroglyph, comprised of many former members of Westwood Studios (known for the Command and Conquer series). This company has developed a completely new engine specifically for EaW known as Alamo. It uses several higher-end shader effects such as soft shadows, specular lighting, and particle effects for dust clouds and explosions.

The game spawned an impressive mod community, and was followed-up by a successor, Star Wars: Empire At War: Forces of Corruption, taking place between the aftermath of the Battle of Yavin and the Battle of Endor.

Contents

[edit] Gameplay

The environment plays a significant role in Empire at War.
The environment plays a significant role in Empire at War.

The game features a brand new style of play to make things a bit more realistic. Instead of building workers, gathering resources, and recruiting individual units, players are granted resources based on how many planets the player controls. Controlling worlds increases a player's cash flow and provide unique bonuses depending on the planet (ex. Armor increases, discounted prices, special unit production.)

Targeting an enemy's starship hardpoints to destroy that hardpoint is an essential to destroying the vessel.
Targeting an enemy's starship hardpoints to destroy that hardpoint is an essential to destroying the vessel.

Battles are carried out both on a planet's surface and in orbit. Whoever controls the planet's surface, controls the planet itself. There are different factors to keep in mind depending on your status as an attacker or defender. Attackers must secure Landing Points to increase the number of units they deploy, while Defenders may deploy up to 10 "units" on a planet immediately. Attackers have their advantages, though. They may call in bombing runs if they have Bombers in orbit. Likewise, ground-based installations (like the ion cannon and Hypervelocity gun) can fire upon units in orbit during space tactical battles. Unlike in Star Wars: Galactic Battlegrounds, shields will form an actual physical barrier that must be penetrated and protect bases from artillery and bombing runs. Assorted building pads litter the playing field in both space and land battles. These pads allow the player to build useful structures (ex. Turbolasers which can easily destroy enemy mechanized units.)

An Alliance Space Station under attack.
An Alliance Space Station under attack.
AT-AT Barges as seen in the game.
AT-AT Barges as seen in the game.

EaW takes place during the time between Episode III and Episode IV, concluding with the construction and possible destruction of the Death Star. Empire at War features three factions, although only two are playable. These factions are the Rebel Alliance, the Galactic Empire, and the Black Sun (playable with XML modding, see below.) Units in this game are a mix of Clone Wars-era and New Order-era. The Empire's advantages include powerful ships and swarms of TIE Fighters, while the Rebels, on the other hand, must rely on swifter ships and Raid Fleets (Small ground troop fleets that can bypass space defenses.) Like many RTS games, Empire at War features a "Rock-Paper-Scissors" unit usage style—for every unit there is a counter-unit. Brett Tosti, the LucasArts producer, has stated that this encourages players to create diverse armies and fleets with units that counter other units, as opposed to building a bunch of "super units".

Players are also able to call on reinforcements during battle, including heroes like Darth Vader and Obi-Wan Kenobi. Players can also construct planet-borne ion cannons, factories, and space stations. Over forty locales are featured including Yavin 4, Tatooine, Dagobah, and others from the movies and Expanded Universe.

[edit] Appearances

This list is incomplete; you can help by expanding it.

[edit] Planets

Map of the planets in Star Wars: Empire at War.

Bothawui as seen from space

Shola, an original planet.

Polus, another original planet.


[edit] Other locations

[edit] Species and Creatures

Hutts facing a horde of stormtroopers.
Hutts facing a horde of stormtroopers.

[edit] Heroes

[edit] Imperial

[edit] Rebel


[edit] Other characters

[edit] Ground Units

[edit] Imperial

[edit] Rebel

[edit] Other

[edit] Space Units

[edit] Imperial

[edit] Rebel

[edit] Other

An immense swarm of X-wings.
An immense swarm of X-wings.

[edit] Special Weapons

[edit] Imperial

[edit] Rebel

[edit] Buildings

[edit] Imperial

[edit] Rebel

[edit] Other

[edit] Organizations and titles

[edit] Events

[edit] Miscellaneous

[edit] Hidden Items

The following are units and planets that were removed for the final version and are hidden or mentioned in the internal game files. Some have been unlocked via XML and MEG editing.

[edit] Planets

[edit] Heroes

[edit] Land Units

[edit] Space Units

Imperial Naval Troopers unlocked for EaW.
Imperial Naval Troopers unlocked for EaW.

[edit] Missions

Master Qui-Gon, more to say, have you?

It is requested that this article, or a section of this article, be expanded.

See the request on the listing or on this article's talk page. Once the improvements have been completed, you may remove this notice and the page's listing.

[edit] Rebel

Final box cover art
Final box cover art

[edit] Imperial

[edit] Endings

There are two different endings to Empire at War's campaign mode depending on the side the player chooses to fight for. The end of the Rebel campaign closely follows the canonical ending of Episode IV. A cutscene shows Luke Skywalker's X-Wing destroying the Death Star and the award ceremony that follows afterwards. However, this ending should not necessarily be treated as canonical, as the final battle with the Death Star can take place over any planet in the game. Moreover, it is still possible for the Rebellion to "win," even if the Empire destroys other planets besides Alderaan, including Yavin IV.

The end of the Imperial campaign is non-canonical, as it is intended to be more of an "alternate history" in the vein of the Infinities universe. The ending cutscene depicts Darth Vader leading a ground assault on what is presumed to be the main Rebel base. The Rebel defenders are quickly crushed as Vader orders his troops to move in. Afterwards, a shuttle is seen flying to the Death Star, flanked by two TIE Fighters. In a scene reminiscent of the Emperor's arrival in Episode VI, an assembly of Imperial troops is shown waiting in one of the battlestation's hangars for the shuttle to land. As the shuttle deposits its contingent of Royal Guards, the Emperor disembarks, greeted by a kneeling Lord Vader. Palpatine congratulates Vader, claiming that the last Jedi (presumably Obi-Wan) and the Rebellion are defeated, and that it is all as he had foreseen.

Two other non-canon endings can be seen in Galactic Conquest mode. If the Rebels defeat the Empire without destroying the Death Star, the ending cutscene depicts a pitched space battle over a ecumenopolis, presumably Coruscant. A Rebel fleet closes in on an Imperial Star Destroyer with Darth Vader on board. As the Imperial defenses crumble, Vader chokes the Star Destroyer's captain for his apparent incompetence and escapes in his TIE Advanced x1 moments before the ship is destroyed. From there, the same award ceremony cutscene follows that was in the campaign ending. Also, if the Empire destroys the last Rebel planet/one with Mon Montha on it, the battle will be replaced by the Death Star destroying a planet, followed by the Death Star cutscene.

[edit] Modding

A screenshot from the Empire at War map editor.
A screenshot from the Empire at War map editor.

As was revealed in early press releases and interviews, EaW is marginally open-source—with much of the game being controlled through text files (*.txt), XML files (*.xml), DAT files (*.dat), and LUA (*.lua). Anyone with the knowledge and software needed to alter these files can do so. The text files are easily edited in most text-editing programs (though Notepad is often the default editing program on the Windows platform) and control the unique ship names that appear on many of the capital ships as well as a fair amount of the stories used throughout the Galactic Conquest mode. The XML files control much of the data responsible for the appearance and behavior of units and buildings. These files are often, by default, launched in a web browser which allows for viewing only. For the purposes of editing XML WYSIWYG web editors (ie: Microsoft's Front Page and Adobe Macromedia's Dreamweaver), text-editors such as Notepad, or proprietary XML editors can all be utilized (though the latter two are most common due to their relative ease of use).

A wireframe TIE Interceptor from the fanmade ALO viewer.
A wireframe TIE Interceptor from the fanmade ALO viewer.

DAT files require the use of software capable of reading the information embedded within. In Empire at War, DAT files are used to store almost all of the text found within the game. Lastly, the Lua files are used primarily for high-level scripting and AI. The decompiled files come with the Map Editor, and can replace the scripts in the EAW directory without having to compile them.

It is now possible to create new ground and space maps with the map editor released by Petroglyph. Included in the map editor download is a plug-in for 3ds Max 6 that can export models into .alo format used by the Alamo engine. However, 3ds Max 8 users that patch their software to the Service Pack 3 version are able to use the separately released 3ds Max 8 exporter in conjunction with the shaders provided with the map editor. Modified shaders created by EaW modder Mike.nl fixes an issue where the models in the viewports using Rskn shaders are invisible. 3ds Max 8 SP 3 is also necessary in order to use the exporter included with the Forces of Corruption map editor.

The community has been pressing forward in terms of modding, going so far as to implement diplomacy, create new particles, and even have detachments of transports assigned to a specific fleet in Galactic Conquest mode. There exist some fan-made programs to assist with the editing of what can be edited, as well as a .alo file viewer. Such tools include a particle editor and an .alo model importer, but controversy over the creation of the importer exists over possible model theft and the lack of an effective way to combat it due to some concerns over the relative age of the Empire at War modding community.

[edit] Mod Projects

There are many large mod projects now in the making, huge mod projects that add entire timelines.

[edit] PC Requirements

The following are the minimum requirements for the PC version of Empire At War.

Computer Required: 100% DirectX 9.0c compatible computer

CPU:

  • Required: Intel P3 1.0 GHz or AMD Athlon 1.0 GHz
  • Recommended: Intel P4 2.0 GHz or AMD Athlon XP 2.0 GHz

Memory:

  • Required: 256 MB RAM
  • Recommended: 512 MB RAM

Hard Drive Space:

  • 2.5 GB

Graphics Card:

  • Required: 32 MB 3D Graphics card with Hardware Transform and Lighting (T&L) Capability
  • Recommended 64 MB 3D Graphics card with Hardware Vertex and Pixel Shader (VS/PS) Capability

Sound Card:

  • Required: 100% DirectX 9.0c compatible PCI, USB, or Onboard Audio Device
  • Recommended: EAX 2.0 compliant Audio Device

CD-ROM:

  • Required: 8X Speed CD-ROM drive
  • Recommended: 16X Speed CD-ROM or DVD-ROM drive

Input Device:

  • Required: Keyboard and mouse

[edit] Expansion pack

Star Wars: Empire at War: Forces of Corruption Expansion.
Star Wars: Empire at War: Forces of Corruption Expansion.
       Main article: Star Wars: Empire at War: Forces of Corruption

An expansion pack was announced at E3 May 9, 2006. It adds 40 new units, 13 planets, a new side and new warfare and features. It was released October 24th in the U.S.A and came out October 27th in Europe.

[edit] Inconsistencies with established canon

Some of the following inconsistencies could be considered an issue of game balance or mechanics.

  • Ackbar was discovered during the siege of an Imperial space station over Corulag.
  • A-wings are in use in the early Galactic Civil War. The R-22 Spearhead retcon partially reconciles this frequent inconsistency.
  • Antilles, R2-D2 and C-3PO all partake in a mission to Wayland, the Emperor's secret storehouse. No one in the Rebellion had even heard of the planet, much less operated on it, until Thrawn's campaign.
  • Imperial troops deploy from the AT-ATs bottom rather than the sides.
  • Several Ship armaments and hard points don't match up with the descriptions of the ships i.e. the batteries on the side of the superstructure of an Imperial-class Star Destroyers are mostly made up of turbolasers. Corellian gunships are stated in the game to have 4 banks of concussion missile launchers and 2 laser cannons when they really have 8 heavy turbolaser turrets, 6 quad laser turrets and 4 concussion missile launchers.
  • Also several ships seem to have more fire power than they should such as the EF76 Nebulon-B escort frigates have 2 turbolaser and 2 laser cannon batteries to a Victory-class Star Destroyer's 2 turbolaser and 1 ion cannon batteries.

[edit] Trivia

Original box art for Star Wars: Empire at War.
Original box art for Star Wars: Empire at War.
  • The in-game description for Maximilian Veers's personal AT-AT Blizzard 1 says his AT-AT cannot be toppled by Rebel Snowspeeders. However, in one of the recent patches, they stated that it was a bug and removed the feature.
  • In several sources, Fondor is misspelled as "Fonfor".[1]
  • Some sources also make the mistake of using the callsign "Base One" for Admiral Ackbar's Home One.[2]
  • The music was written by composer Frank Klepacki. The entire Empire at War soundtrack is available to listen to on his site.[source?]
  • The locations of many of the planets ingame are not exact. An example is the population of the Unknown Regions by well-known and canonically established planets, such as Taris and Thyferra. Differences such as these are due to game mechanics and are thus considered non-canon.
  • When choosing a side to play in the campaign, between the Empire and Rebellion buttons there is a sentence written in the Aurebesh. When translated, it reads "At Petroglyph we are dedicated to making top quality games that are extremely fun and innovative".

[edit] Reaction

Empire at War was well received by fans, and many considered it the best of the Star Wars RTS games. Gamespot called the game "The RTS fans had been waiting for." Others were disappointed that a sequel to Rebellion had not been made. However, some critics, at the worst, claimed the game to be shallow and repetitive, whilst others considered it fun but basic.

[edit] See also

[edit] External links

Retrieved from "http://starwars.wikia.com/wiki/Star_Wars:_Empire_at_War"
Rate this article:
Share this article: