Fandom

Wookieepedia

Rescue at Jundland Station

135,506pages on
this wiki
Add New Page
Talk0 Share
Atticon

This article is about an Easter egg.

This article covers a subject that was included as an Easter egg in a Star Wars Legends source and may not have been considered canon within the Legends continuity.

Atticon

This article is non-canon within the Star Wars Legends continuity.

This article covers a Star Wars Legends subject that was published under the Infinities label or that Lucasfilm otherwise declared to be non-canon within the Legends continuity.

In 4 ABY,[2] the Naboo people orchestrated a rescue of Queen Padmé Amidala after she was somehow captured by a group of Tusken Raiders stationed at Jundland Station.

The rescuers came in the form of two Jedi Knights, who after befriending an Ewok named Simon , proceeded to attack Jundland Station, and rescued the Queen before she was beaten to death. They then escorted the Queen back to her J-type 327 Nubian royal starship, also killing the bounty hunter Aurra Sing, who tried to stop them in the process.

Upon arriving back at the ship, Darth Maul ambushed them, although the trio managed to vanquish him.[1]

Behind the scenesEdit

This mission was an optional mission that can be played during the Liberation of Kashyyyk mission of the Wookiee Campaign in Star Wars: Galactic Battlegrounds and its expansion pack, Clone Campaigns. It can be accessed by using "Forcesight" and "Forceexplore" and then accessing the East Corner of the Map. The mission leaves it ambiguous as to whether Jundland Station took place on Tatooine or on Kashyyyk.[1]

Until proven otherwise, that mission is considered non-canon, since it features several characters[1] that were long dead by 4 ABY, such as Padmé Amidala[4] Obi-Wan Kenobi[5] and Qui-Gon Jinn.[6]

AppearancesEdit

Notes and referencesEdit

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.