Fandom

Wookieepedia

Unidentified Tarisian noble

134,567pages on
this wiki
Add New Page
Talk5 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.

"I can trace my lineage back five generations to one of the founding houses of Taris."
―The noble[src]

This male Human was a Tarisian noble. Among his ancestors was a member of one of the founding houses of the planet Taris.[1]

After Revan gives Christya 20 credits to buy the two of them drinks, she goes talking with this noble, he begins to brag to her about his rich heritage. Eventually, the two of them leave the cantina together, leaving Revan 20 credits short.

Behind the scenesEdit

This noble's first canonical appearance was as a non-player character in the Star Wars: Knights of the Old Republic video game, in which the player, Revan, can interact with him. However, the nature of the conversation is such that it does not progress any plot, nor does it change the player's alignment. Therefore, it is undetermined whether Revan ever interacted with him at all.[1]

The same noble also appears in Davik Kang's estate when the player is there at the same time, however, the player can persuade the noble not to take action for him entering his room, the noble is convinced that he works for Davik Kang, so gives the player a 5 credit tip, but the player can later choose to reveal himself to the noble, resulting in the noble attacking the player, resulting in the noble's death.

However, if the noble has already interacted with Christya in the Cantina, his corpse is left on the floor in his room when the player opens the door to his room, not holding any remains for the player to take.

AppearancesEdit

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.