FANDOM


Tab-canon-white  Tab-legends-black 
"From the Battles of Rashfond, to the Peacekeeping of Parliock, to our very own Clone Wars, the lightsaber is a Jedi's only true ally. But how do they work? Hmm? Yes, you have brought me crystals, but they're all useless unless you give them life. Do you know how to awaken the Force within the crystal? No? Then I suggest you listen and learn, until you think of a question this droid cannot answer."
―Huyang, to a class of Jedi Younglings[src]

Huyang was a Mark IV architect droid professor based out of the Jedi vessel, the Crucible, who for a thousand generations had taught Jedi younglings (one of them being the future Grand Master Yoda[3]) how to build their lightsaber following the Gathering.[1]

BiographyEdit

By the time of the Clone Wars, Huyang was over a thousand years old, and had helped many Jedi younglings in the construction of their lightsabers. His purpose was to accompany the young trainees to the planet Ilum, and once they would retrieve the kyber crystal that called to them through the Force, he would aid them in fashioning the weapon for use.

During the Clone Wars, in 20 BBY, Huyang accompanied Grand Master Yoda, Ahsoka Tano, and a group of younglings to Ilum, where they would begin their journey toward Padawanhood. During this time, with Tano there with him to supervise the kids, their ship was boarded by Weequay pirates led by Hondo Ohnaka. Tano fought off the pirates, and Huyang was disabled, but the younglings reassembled parts of him. Tano was captured by the pirates, but the younglings managed to get away.

Droid stub This article is a stub about a droid. You can help Wookieepedia by expanding it.

Behind the scenesEdit

Huyang was voiced in Star Wars: The Clone Wars by former Doctor Who actor David Tennant.

AppearancesEdit

SourcesEdit

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.