Theoryland of the Wheel of Time

Dakhor. One of the better words I came up for this book, I think.

Be patient with me—I'm going somewhere with this whole Dakhor monastery thing. We'll get there eventually. For now, enjoy Hrathen's visions. Or, rather, be disturbed by them. (Dakhor, if you haven't noticed, isn't a very friendly place. . . .)

I made certain to throw in lots of references to the Arelene Market. You'll find another one in this chapter. Obviously, the market itself is important. Since the Dakhor are going to pop out of the tents, readers need to understand that they're there.

Ah, and Hrathen's three month timebomb. It's always nice when you can have a timebomb go off early. Hrathen thinks in this very chapter about how he's got a month left on his deadline. However, I suspect that readers will look at the book and realize that there's less than a hundred pages left. Hopefully, with these chapters—Raoden crowned king, Hrathen apparently beaten—I invoke a sense of confusion in the reader. They'll be expecting something big, something they weren't looking for.

The arrival of the Dakhor monks is it. You'll get some more explanation of this later, of course. Anyway, now you know why I kept mentioning the Arelene market and how unprofitable it seemed. The merchants there weren't even really merchants.

In the first draft, I had the monks hiding on the merchants' ships. In a later rewrite, however, I realized that this wasn't as powerful as if I had them actually playing the part of the merchants. If I had them on the ships, I had to have Hrathen follow Dilaf all the way to the docks. In addition, those monks would have had to spend weeks cooped up in the holds of a bunch of merchant ships. So, I changed it so that the monks were impersonating the merchants themselves—a better plan, I think, on their part. This lets them infiltrate the city, move around and scout the area, and essentially hide in plain sight.

My only sadness concerning the Dakhor is that I had to wait so long to reveal them. I think that visually, they are very interesting. The concept of a group whose bones have been twisted and deformed by powerful magics brings interesting images to mind.

The Dakhor aren't majorly deformed, however—they still have all the pieces in the right places. Their bones have simply been. . .changed. Expanded in places, simply twisted to form patterns in others. Because of this, of course, they have to run around shirtless. It's more dramatic that way. Besides, we spent all this money on special effects—we might as well show them off.

Of all the things in the book, this one worries the most with its sudden appearance. I really did try to foreshadow this as best I could. If it's still too sudden for you, I apologize. My suggestion is to just sit back and enjoy the ride.

So, this is where the book turns a little violent. You can read some of my earlier annotations on the topic. I was a little bit worried about putting any strong violence in this book, since it was generally focused around politics and other, more subtle methods of building tension. However, I decided to go with contrast instead. So far, nearly everything in the book has been surprisingly peaceful. We didn't even see Shaor's men kill many people.

Now things are going very wrong. An evil that nobody was expecting has come against the city, and it's controlled by a demented, hateful creature. I don't see how we could get around having these scenes be particularly dark. I think there is an element of realism here too, however. This is what happens with all of the politics and the maneuvering breaks down.

I've only mentioned Gragdets a couple of places. Hrathen never thinks much about them, since he doesn't consider them part of the traditional Derethi structure. In truth, they aren't—but they do have authority over a Gyorn in their own small sphere. I don't think that the reader needs to understand the entire social structure of the religion, however. Hrathen understands what is happening, and knows that he should probably let himself be under Dilaf's authority. That should be enough for most readers.

And, yes, Dilaf always had bones that were deformed. That's why I mention that they're not terribly disfiguring—they would be quite easy to hide under robes. And I often pointed out in the book that Dilaf was wearing his enveloping robes.

Hopefully, these moments—Dilaf's unleasing—have been building for you through the entire book. By now, you should have realized that Dilaf was always the main villain of the story. He's the one with true hatred, and true instability. Hrathen is an antagonist, but he's no villain. Dilaf, however, has been built-up as someone who can do some truly terrible things. Now he's unleashed, and he has an army of demonic monks at his control.

And yes, we'll get to more about how Dilaf was able to imitate an Arelene later.

Kiin gets a little over-confident here by letting the two of them go on top. However, he doesn't know how powerful the Dakhor are. He assumes that his roof is unscalable.

In addition, he realizes how difficult a situation he is in. Dilaf has an army—Kiin's fortress house, no matter how well fortified, can't defend against them for long. He needs to do something, and thinks that maybe the negotiations will offer a way. So, he takes the chance.

Whoops.

LUKEL

Lukel isn't as interesting as Galladon, but I still enjoyed giving him a viewpoint. He has the perfect personality to show what I wanted in these chapters. He's not a warrior—like Kinn—or a king—like Raoden. He's just a regular person caught in a nightmare.

I wanted to deal a little bit with prisoner mentality in this scene. People allow terrible things to be done to them in situations like this. Part of it is because they fear what COULD happen more than they fear what IS happening. In this case, hope proves their enemy. The Dakhor stop killing the people and start rounding them up instead. The reason for this is simple—after seeing and hearing such terrible things, the people would run and fight. However, if the Dakhor back off, the people can hope that the worst is over. For this reason, they let themselves get rounded up and gathered in Elantris.

It may seem convenient that the soldiers wait to kill the people, but I think it makes sense. You want to gather everyone in an enclosed place, where they will be trapped, before you begin your slaughter in earnest. That way you can be certain there are no escapees. The only one I fudged here was Kiin. A Dakhor probably should have killed him. However, I've had enough corpses in this book. Randomly killing off Kiin seemed like too much. (Some readers are already in rebellion over the people I've killed—or, rather, will kill shortly. . . .)

Anyway, I get past part of this concern by throwing in the 'purification rites' line. This hints that there is some sort of ritual that needs to be preformed before the people can be killed, and therefore explains why the Dakhor don't just slaughter them immediately. (I still think that control is the greater reason, however.) Another explanation of why the slaughter starts is mentioned by Lukel. Most of the Derethi left in Arelon are regular soldier-monks, not Dakhor. They don't have the same. . .zeal for destruction as Dakhor.

DILAF'S BACKSTORY

I hope that Dilaf's explanations about his past are suitably creepy. I also hope they give some explanation. He is a man who betrayed his religion when he thought it would save the woman he loved—only to find himself, in turn, betrayed by the Elantrians. His wife became Hoed, and he himself burned her. This would have something of an effect on a man's psyche, I think.

Now, recall that Elantris was at the height of its power when Dilaf took his wife in to be healed. I mentioned her earlier in the book, in a Raoden chapter. He found a story in one of his textbooks about a woman who was improperly-healed, and it turned her into what the Elantrians now are. This is Dilaf's wife. (Go re-read Chapter Twenty-Five for the story.) I find this little item beautifully circular.

Anyway, we now have an explanation for Dilaf's instability and his hatred. I really like how Dilaf, normatively, grows into being the prime villain for this book. He comes to it slowly, kind of stealthily, while the reader is focusing on Hrathen. Yet, Dilaf is there from the first Hrathen chapter, always dangerous, always trying to destroy Elantris, always making his own plans. I worked hard to bring about his rise to power in the book, and I hope that it worked. Puling off the Dilaf/Hrathen reversal was one of my main goals in the story.

DAKHOR MAGIC

I actually didn't plan to use the 'teleportation' aspect of the Dakhor magic. However, I wrote myself into this chapter, then suddenly realized that I needed to get the group Teod in a real hurry. I couldn't let days pass while Sarene, Hrathen, and Dilaf sailed to the peninsula as I'd originally intended. (I have no idea what I was thinking.) So, I added in teleportation. It ended up working out very well in the book, as it let me add another dimension to the Dakhor magic—that of having it cost a life to create some of its effects.

This, more than anything, should instill in the reader a sense of disgust regarding the Dakhor. I particularly like Hrathen's story about Dilaf making someone die so he could travel to a place fifteen minutes away. It characterizes Dilaf perfectly while at the same time giving a clue to how strict and obedient his order is. This isn't a group of people you want to mess with. It's the ultimate exaggeration of Derethi beliefs on loyalty and structure.

HRATHEN AND SARENE

There is some good, if terse, exposition here with Hrathen sorting through his feelings. I don't think he really wants to come to any answers right now. Logic has lead him astray before, and now that he's doing what he feels is right, he doesn't want to pause to give himself a chance to consider the ramifications of what he's done.

Again, Sarene has fulfilled her purpose in the book. She's thrown chaos into Hrathen's otherwise-orderly life. However, her chaos here—just like the chaos she caused in Elantris with her food—eventually proves to be a good thing. It inspires change for the better, even though that change is painful.

And, of course, I remind the reader here that there is something odd about Hrathen's arm. I've only mentioned it in a couple of places, so I don't expect people to remember what is going on here. I actually forgot to have the sleeve in the original rewrite. I didn't even think to notice that his Dakhor arm would be exposed to Sarene in this scene. . . .

THE SALVATION OF ELANTRIS

Yes, Raoden lets the Dakhor monks go. That's the sort of thing that happens in this book. If you want something more gritty, you can read MISTBORN. (Which is gritty for me, though nowhere near the genius sadism of George R. R. Martin's books.)

I like having this scene from Lukel's viewpoint. If nothing else were gained from his other sections, I think the scene of the Elantrians emerging from the flames would be enough to justify his viewpoints in these last few chapters.

So, anyway, that's one major plot line finished. Elantris has been restored. Most fantasies, however, are about characters more they are about plot. I love great twists and revelations—but the book isn't over until the characters are fulfilled. So, onward.

THE DAKHOR MONKS

In the original write of the book, the Dakhor broke and ran before the Elantiran attack. My thought was that the Dakhor always been so much more powerful than their opponents that they didn't know what to do when faced with someone more powerful than they were. In a rewrite, however, I changed this. I'd spent too much time establishing that he Dakhor were fiercely loyal. I see them as fanatics—people who were either originally like Dilaf, or who became like him through their conditioning. They wouldn't break before a superior force—they'd attack it, even if it meant getting slaughtered.

This revision works far better for me—especially since I can have the scene where Dilaf wishes he could join them. Death is not something that scares a group like this.

RAODEN AND SARENE VS DILAF

There's really only one way this battle could have ended—Dilaf had to win. Raoden might know his Aons, but Dilaf has been a Dakhor for decades. Sarene has practiced fencing, but Dilaf is a warrior monk with a supernaturally fast and powerful body. It makes sense to me that this little battle wouldn't even be much of a contest. Both Sarene and Raoden are people who succeed not based on their ability to beat up their enemies, but on their ability to manipulate their surroundings. By having the heroes defeated in combat by the villain at the end, I think I give a final nod to my desire to write a book that didn't use violence as the solution to problems.

(Oh, and if you caught the reference to the word 'Skaze,' then good for you. The Skaze are a group that will appear in the sequel, when and if I get around to writing it. They're pretty much evil Seons.)

HRATHEN

So, Hrathen wasn't really dead. (Ironically, while many of you are probably saying 'yeah, yeah. That was obvious,' I actually didn't have him appear here in the first eight drafts of the book. I'll explain later.)

I think this is my favorite scene of this chapter. Not only is it written a little better than the rest of the book (I added it quite late—just this last summer) but it gives final closure to the Hrathen-Dilaf relationship. It uses Hrathen's time in Dakhor as an ironic twist against Dilaf. In short, it is a pretty good scene. Fulfills character, plot, and theme at the same time—while giving us a nice image to boot. (Though I do hate to do the "Hey look, a guy we thought was dead is really alive" twist.)

The story behind this scene is pretty recent. One of the original rewrites Moshe asked for was a fix of the ending, which he thought was too Deus Ex Machina. (Which, indeed, it was.) I don't think I'll go into the entire original version here—it was quite different. You can read the alternate ending in the deleted scenes section, when I throw it up next month. The short of it, however, is that Ien (Raoden's Seon) showed up to save Raoden and Sarene from Dilaf. I used a mechanic of the magic system that I have since pretty much cut from the novel (since it was only in the book to facilitate this scene) that allowed Ien to complete his Aon, 'healing' Dilaf. Except, since Ien's Aon was broken, it turned Dilaf into an Elantrian instead. (A non-glowing Elantrian. One like Raoden the group used to be—like Dilaf's own wife became after she was improperly healed in Elantris.)

I know that's probably confusing to you. The scene, over all, was just kind of weak. It relied on a barely-explained mechanic mixed with a tangential character showing up at just the right moment. When Moshe asked for the change, I immediately saw that I needed to bring Hrathen back to life for a few more moments. Letting him die on the street just wasn't dignified enough (though originally I wanted him to die this way because it felt more realistic.) I wanted a final confrontation between Hrathen and Dilaf, since it would give most people's favorite character a heroic send-off, and would also let me tie in the aforementioned Dakhor irony.

In the end, I was very pleased with the rewrite. It's good to have an editor.

LOOSE THREADS

You'll notice, therefore, that I pile on the lose threads here. The most important one, of course, is the concept that Fjorden has gained access to the Dor (presumably recently.) The Dakhor are a newer development—Wyrn was just getting ready to use them against Elantris when the city fell on its own. (Dilaf wasn't the only Dakhor plant inside Arelon. But, those are stories for another time.) Anyway, I think I gave myself plenty of sequel room here. There are the questions about the Dor, about Fjorden, and about the Seons.

That said, I can't honestly promise that I'll do an ELANTRIS sequel. When I was writing during this period of my life (some seven years ago now), I was trying to create as many first books as possible. I was sending them all off to publishers, trying to get someone to bite on one of them so I could start a series. However, since I was a nobody, I had to write each book as a stand-alone as well. Publishers, I was told, like to get books from new authors that could stand alone or launch into a series. That way, they're not committing to anything drastic, but can monopolize on popularity if it comes.

ELANTRIS turned out to be one of the best stand-alones I did. I kind of like how it doesn't really need anything more to make it feel complete. And, I've got so many stories that I want to tell, I don't know that I'll be able to get back to this one. I guess it will depend upon how well ELANTRIS sells, and whether or not Tor pushes me toward writing more books in this world.

Anyway, I've got plenty of things I could talk about if I do come back.

9) Speaking of sequels, here's what I'M planning. A book that takes place ten years after the events of ELANTRIS. It would occur in the capitol city of Fjorden, and would star Kiin's children as viewpoint characters along with a Seon viewpoint character. The plot of the book: Wyrn has declared that Jaddeth, the Derethi God, is going to finally return. (A new interpretation of the scriptures says that he'll return when everyone east of the mountains converts, so they don't have to worry about Teod and Arelon.) Kiin's family, ambassadors to the Fjordell state, has to deal with the chaos of this announcement, and investigate the truth behind the Dakhor magic. Thoughts?

This book is quite a bit more violent than ELANTRIS. I worry about that, sometimes. I hope I don't put people off who enjoyed my first novel. Several things save me, I think.

First off, though people initially don't think of ELANTRIS as a gruesome book, it really does include quite a few disturbing elements. The brutality of the people in Elantris, for instance, or the slaughtering done by the Dakhor monks. In chapter one of Elantris, we see a boy with his throat crushed, seeping blood. So, really, there isn't anything in MISTBORN that stands out THAT much.

The difference is, I guess, that one of the heroes is himself a killer. Also, we have scenes like this one, which are just plain disturbing.