Fandom

Hegalia

Kharyrll

269pages on
this wiki
Add New Page
Comments0 Share
This article is about the historic site of modern day Canifis. For teleport spell see Kharyrll Teleport.
File:Kharyrll as it appears today.png

Kharyrll was a fortress controlled by Zaros during the Second and early Third Ages. It was destroyed during the God Wars, although by whom remains a subject of debate. Lord Drakan's invasion of the Hallowland in the Fall of Hallowvale of the early Third Age was, until recently, the only conflict theorized to have caused the fortress's destruction. However, the Jagex-made Armies of Gielinor game, featured on FunOrb, suggests that the fort was destroyed by independent werewolves, who renamed the area Cave Canem and occupied it until being defeated by Drakan in the invasion. The game's application of canon, however, is inconsistent.

The area was occupied for several hundred years by the Lordship of the North Coast during the late Fourth Age. In the Year 20, the area was settled by Morytanian werewolves subservient to Lord Drakan, who established Canifis. Werewolves feel at home at this town in these days, pretending to be humans. Any of Kharyrll's remains have since been destroyed or lost.

To enter the site where Kharyrll once stood, one must have done the "Priest In Peril" quest.

If the player has access to the Ancient Magicks spellbook, the Kharyrll Teleport once used by Zarosians can be used to teleport directly into the Hair of the Dog pub, using 2 law runes and 1 blood rune (66 Magic required).

In addition, a player with 50 Construction can build a Portal Chamber in their player-owned house, and a Kharyrll portal to modern-day Canifis may be assigned without needing the spellbook set to Ancient Magicks. (requires 200 law runes, 100 blood runes, and 66 magic)

ReferencesEdit


{{{header}}}
{{{body}}}

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.