Fandom

Prince of Nothing

Anasûrimbor Nau-Cayûti

1,047pages on
this wiki
Add New Page
Talk0 Share

Nau-Cayûti (“Blessed Son” in Ûmeritic) officially was the youngest son of Anasûrimbor Celmomas II and his wife Suriala. But perhaps he was a bastard child of Seswatha and the Queen.

Nau-Cayûti was famed for his heroism and martial brilliance during the dark days after the fall of Aörsi (2136), when the nation of Kûniüri stood alone against the menace of the Consult. He rose to fame in the Battle of Ossirish, where he routed the Consult forces and personally killed the dragon Tanhafut the Red. After this, he became popularly known as Murswagga, the Dragonslayer. Many of his exploits are recounted in The Sagas.[1]

His last great deed was infiltrating Golgotterath itself, together with his mentor and possible father Seswatha, where they stole the mysterious Heron Spear. This daring exploit was motivated by Nau-Cayûti’s desperate desire to rescue his favorite concubine, Aulisi. Mandate commentators dispute the account found in The Sagas, where they successfully return with both Aulisi and the Heron Spear, claiming that Aulisi was never found.

Nau-Cayûti died shortly after the theft of the Heron Spear. According to The Sagas, he was murdered with poison by his wife, Iëva.[2]

However, visions into the past, received by Drusas Achamian through Seswatha’s Dreams, suggested that the poison merely paralyzed him. Iëva was in reality working for the Consult, and made sure to bury her husband alive rather than burning him.[3] Nau-Cayûti was then exhumed from his grave by Aurang and taken as a prisoner to Golgotterath.[4]

ReferencesEdit

  1. Encyclopedic Glossary, ‘Nau-Cayûti’
  2. Encyclopedic Glossary, ‘Apocalypse’
  3. The White-Luck Warrior, Chapter 12
  4. The White-Luck Warrior, Chapter 15

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.