Fandom

Wookieepedia

Roan Shryne's first Padawan

135,126pages on
this wiki
Add New Page
Talk1 Share
Queicon

The title of this article is conjectural.

Although this article is based on official information from the Star Wars Legends continuity, the actual name of this subject is pure conjecture.

An individual was the first Padawan of the Jedi Master Roan Shryne during the waning years of the Galactic Republic. In 22 BBY, the Padawan and Shryne were part of task force assembled to rescue Jedi Knight Obi-Wan Kenobi from execution on the planet Geonosis and Shryne's Padawan was killed in the ensuing battle.

BiographyEdit

A Force-sensitive individual lived during the last years of the Galactic Republic. At some point before the outbreak of the Clone Wars[2] in 22 BBY,[1] the individual was chosen as Padawan by the Jedi Roan Shryne.[2] In 22 BBY,[1] Jedi Knight Obi-Wan Kenobi, was captured by forces of the Confederacy of Independent Systems during a mission on the planet Geonosis. Jedi Master Mace Windu assembled a strike team to rescue Kenobi from execution. The Padawan, Shryne and Shryne's former master Nat-Sem were part of this strike team.[2]

The rescue mission turned into a full-scale battle against the Separatist Droid Army and the Padawan was killed in the battle alongside Nat-Sem and many other Jedi. Shryne survived, but the loss of his pupil and his former master, coupled with the death of another student later during the war, led to the Jedi Master losing his faith in the Force and the Jedi Council.[2]

Behind the scenesEdit

The Padawan was first mentioned in the 2005 novel Dark Lord: The Rise of Darth Vader written by James Luceno. In 2008, the Padawan was briefly mentioned in Shryne's entry in The Complete Star Wars Encyclopedia.

AppearancesEdit

SourcesEdit

Notes and referencesEdit

In other languages

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.