Star Wars Galaxies: Episode III Rage of the Wookiees
Released: May 5, 2005
Developed by: Sony Online Entertainment
Published by: LucasArts
Genre(s): MMORPG
  • ESRB: T </li></li>
  • The second expansion, Star Wars Galaxies: Episode III Rage of the Wookiees, was announced on March 9, 2005 and released to coincide with final Star Wars film, Revenge of the Sith. It added the ground planet of Kashyyyk and its corresponding space sector. Kashyyyk is different from the previous ten planets; rather than being 16 square kilometers of openly navigable area, it is divided into a small central area with several instanced "dungeon" areas, with no space available for open exploration. Other content added in this expansion included the ability to add cybernetic limbs to a player character.


    Rage of the Wookiees contains a large amount of content adapted from and associated with the film Star Wars Episode III: Revenge of the Sith. Other features included new starfighters, resource mining in space, and cybernetic limbs for player characters. The cybernetic limbs, however, were not due to the loss of an arm in combat. The player had to obtain the arm and then surgically attach it. Customers who purchased the expansion also received a limited-edition Varactyl pet as a player mount.

    The Rage of the Wookies expansion also added a few quests, one allowed the player to obtain a pet Bolotaur after going through several tasks. The Bolotaur is similar to the Veractyl but larger and brown.

    External linksEdit

    This page uses content from the English Wikipedia. The original article was at Star Wars Galaxies: Episode III Rage of the Wookiees. The list of authors can be seen in the page history. As with Lucasfilm Wiki, the text of Wikipedia is available under the GNU Free Documentation License.

    Ad blocker interference detected!

    Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

    Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.