Fandom

Wookieepedia

Star Wars Adventures 3: The Hostage Princess

135,114pages on
this wiki
Add New Page
Talk0 Share

Star Wars Adventures 3: The Hostage Princess was the third installment of Scholastic's Star Wars Adventures series.

Cargo Bay summaryEdit

Mace Windu and Kit Fisto investigate the sudden siege of a Fondor spaceport by droid forces. The capture of a Nallastian noble leads the Jedi on a pursuit [...] they must act quickly to save the life of the captive princess.

Plot summaryEdit

Behind the scenesEdit

Jedi Knight Bultar Swan's comment to 18-year-old Padawan Anakin Skywalker at the Skull Queen's fortress that "Jedi don't have nightmares"[1] serves as a precursor reference to Anakin's identical line of dialogue with Padmé Amidala as he stands on the east balcony of the Naberrie family's Varykino lodge (in both Star Wars Episode II: Attack of the Clones novel and screenplay[2][3]) that appears to directly quote Swan from Skywalker's memory of their discussion about 'Jedi dreams' during their mission to Fondor some months earlier.
Help

Over here! Help! Please, help!

This article's plot summary is in need of attention. It may be missing or require expansion.

Please improve the plot summary however you can and remove this notice once finished.

AppearancesEdit

By type 
Characters Creatures Droid models Events Locations
Organizations and titles Sentient species Vehicles and vessels Weapons and technology Miscellanea

Characters

Creatures

Droid models

Events

Locations

Organizations and titles

Sentient species

Vehicles and vessels

Weapons and technology

Miscellanea


See alsoEdit

External linksEdit

Notes and referencesEdit

  1. Star Wars Adventures 3: The Hostage Princess
  2. Star Wars Episode II: Attack of the Clones (novel)
  3. Star Wars: Episode II Attack of the Clones

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.