FANDOM


Ill13

Roark aiming to attack Cyrilus in a bar in the town of Quarlen.

Highborn of the town of Amory, Roark is tall with bushy black eyebrows, dark eyes, an aqualine nose and jet black hair. He is a pompous figure who Lone Wolf encounters several times.


AppearancesEdit

The Kingdoms of TerrorEdit

Roark and Lone Wolf first cross paths in The Kingdoms of Terror when the Kai Lord intervenes in a tavern dispute to spare the life of an innocent man.

Roark vows revenge for this intrusion and later attempts to carry out his threat when he draws Lone Wolf into an ambush, summoning "from the Pit of Eternal Pain" an entity he refers to as Tagazin. Roark barely escapes this ambush with his life, as the resulting summonation goes awry and results in the deaths of the riders accompanying him. Should Lone Wolf make the mistake of visiting Amory in the course of the story, however, the Kai Lord does not live to tell the tale.

Combat StatsEdit

The Dungeons of TorgarEdit

The next appearance of Roark comes in The Dungeons of Torgar. On the Isle of Ghosts, Lone Wolf learns that Roark is not merely a hostile noble but is in fact a secret member of the Cener Druids, and that "Tagazin" is a demonlord who ordinarily resides on the Plane of Darkness. The subsequent confrontation pits Lone Wolf against Tagazin and, upon its conclusion, leaves Roark's fate uncertain.

Dawn of the DragonsEdit

We finally learn the fate of Roark in Dawn of the Dragons, when Lone Wolf's travels again take him through the Stornlands and provide a second opportunity to visit Amory. What was years earlier a thriving town is by this time nothing more than a ghostly ruin, haunted by the spirit of none other than Roark himself. The destruction of his evil spirit removes the shadow from the ruins of Amory, ushering in new life and closing the chapter on Roark's tale.

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.