Theoryland of the Wheel of Time

There is some division among readers regarding their favorite viewpoint character. One group chooses Raoden, but I think the majority go with Hrathen. All things considered, I think he's probably the best villain I've ever written. His personality comes off quite well in this first chapter, and I think he might have the strongest introduction—at least personality-wise—of the three.

Chapter three marks the end of the first "chapter triad."

The chapter triads are a major structural element of this novel. The viewpoints rotate Raoden-Sarene-Hrathen, in order, one chapter each. Each of the three chapters in the grouping cover pretty much the same time-frame, so they can overlap, and we can see the same scene sometimes from two different viewpoints. (Note the point in chapter two where Sarene sees Raoden being led to Elantris, wearing the sacrificial robes.)

We always follow this same format, going from Raoden, to Sarene, to Hrathen. Until, that is, the system breaks down late in the book—but we'll get into that.

And, you might have noticed that the Aons at the beginnings of the chapters stay the same for three chapters before changing. Each triad, therefore, has a different Aon to mark it. (I did a little bit of fighting to get this through at Tor. The final decision was theirs, but once they realized what I was trying to do, they liked the idea and approved it.) The placing of the Aons is a little bit obscure, I'll admit, but it might be fun for people to notice. (They also grow increasingly complex, built out of more and more tracings of Aon Aon, as the triads progress. There are some special Aons marking the beginnings of sections.)

I'll talk more on chapter triads later. You can read more about my theory on the format in the critical afterword to ELANTRIS (which should eventually be posted in the Elantris 'Goodies' section.) I might also do essay specifically about the format and the challenges it presented.

Anyway, back to Hrathen. My hope in creating him was to present an antagonist for the story who would be believable, understandable, and sympathetic. He's a good man, after his own fashion—and he's certainly dedicated. He doesn't want to destroy the world; he wants to save it. It's not his fault he's serving an evil imperial force.

Regardless, Hrathen certainly has the most interesting character progression in the story. Raoden and Sarene, despite many interesting attributes, are two of the most static characters I've designed. This book isn't about their growth as people, but rather their ability to overcome their desperate odds. Hrathen, on the other hand, has a real opportunity to grow, learn, and change. Perhaps this is what makes him people's favorite. It certainly made him the critic's favorite.

I can only think of two books I've written—out of sixteen—that use a literary 'timebomb' as strict as the one in ELANTRIS. Three months to convert the kingdom or Wyrn will destroy it. That's a pretty heavy motivator. Sometimes, timebombs can feel contrived, and I tried to make this one feel as realistic as possible.

Later, when we discover that Hrathen was never intended to succeed in his conversion, I think this three-month limit makes a lot more sense.

This third 'chapter triad' is the first one where I do a real intersection of the three viewpoints. Raoden sees Hrathen on the wall, Sarene and Hrathen spar, then Hrathen thinks about his run-in with Sarene on his way to the meeting with the noblemen.

I'm not sure if I'd ever want to use the chapter triad system again. It made all kinds of problems for writing the book. Almost everything else I've written has been strictly chronological—if you jump from one viewpoint, or one chapter, to the next, you're always progressing forward in time. By jumping backward in two chapters out of three, I gave myself some challenging pacing and coordination issues. For instance, the important events in each of the three storylines had to happen on generally the same days. Also, I had to rotate the chapters strictly, and so I couldn't just skip a character during a given time-frame. That meant I had to have important events happening in all three viewpoints all the time.

However, the benefits of this situation are moments like you see in this triad, where I could flow from one chapter to the next, having the timeframes play off of each other. You might have noticed from this triad that I had to fudge just a bit. Not all of the viewpoints happen at exactly the same time. The rule I set up for myself is that they had to all happen on the same day—preferably as close to overlapping each other as possible.

This chapter is one of the prime 'show Hrathen's competence' chapters. Most of what goes on here is in the way of character development for Hrathen. The plot of him swaying some of the noblemen is important, but not specifically so. However, I've always said that the stronger—and more clever—the villain is, the better the story is. By showing how Hrathen deals with the noblemen, I re-enforce his abilities, and justify him as a threat to the city.

There were a few small edits to this chapter. The biggest one was a change where I slightly-weakened Hrathen's treasonous talk. In the original, he told the noblemen that he was the gyorn assigned to Duladel before it collapsed. Moshe pointed out that this was a little too subversive of him to imply in the middle of a group of men who may or may not end up supporting him, so I made the change.

Sarene=Chaos

If you want to read more on this topic, read the critical afterword to ELANTRIS I wrote for inclusion with my Master's Thesis. (September's goodie—find it on the goodie page for Elantris) The short of it, however, is that Sarene is a force of change and chaos. Raoden, as mentioned above, is a master at working with what he is given. He manipulates his confines to the point that they are no longer binding.

Sarene, however, just ignores what she is 'supposed' to do. She is chaos. Not the 'evil' chaos usually used in fantasy novels—Sarene is simply unpredictable, a force that can't be measured as easily as others. One manifestation of this comes in the nature of this chapter. If you read closely, you'll notice that—for the first time in the book—I offer two viewpoints in the same chapter. We jump from Sarene to Raoden, then back to Sarene again. It's a little thing, perhaps—a silly thing, even, for me to put in. However, it is representative of the fact that the first time Sarene enters Raoden's world, she brings with her an uncanny ability to mess up his plans.

This book, as I've mentioned before, is a little less 'tight' than others I've written. There are chapters like this one, where nothing extremely important happens—I simply show life from one viewpoint, a state necessitated by one of the other two doing something very important. Still, despite it having very little to do with the overplot, I really like how this chapter turned out. Maybe I should force myself to do a strict triad system like this more often, for it forced me to have some chapters where the characters could just live. Sarene's light chapters center around her friends and family, giving us an opportunity to spend time with them and enjoy ourselves. The Lukel sourmellon exchange probably couldn't have happened in a book like MISTBORN, where the pacing is far more tense.

Anyway. . .I break triad here again. I'd forgotten about this one. Actually, you'll note that the closer I get to an action sequence or a climax, the more quickly I shift viewpoints. I do it half-intentionally, half-unconsciously. (If that's possible.) Logically, I know that quickly-shifting viewpoints give the scenes more tension and a sense of movement. Unconscious, I just know that it's good storytelling to keep things quick—and it's more dramatic when you can end with a cliff-hanger line, then switch to a new viewpoint.

I'll admit that this scene borders on being too melodramatic. A couple of things justify it in my mind. First, the scene is more about Raoden confronting how he'd made a mistake with Shaor's men than it is about Sarene discovering that she'd been betrayed. Second, Sarene's 'betrayal,' as explained in the next chapter, is really about her own prejudice. Inside, she was just waiting for something like this to happen. That's why she didn't give Raoden the benefit of the doubt—she never wanted to like him. It was almost like she was eager to be hurt, expecting it, since things obviously couldn't work out for her. (Or so she unconsciously assumed.)

So, in a way, they were both kind of expecting something like this to happen. When it did happen, they allowed it to. In my mind, this takes it from a 'silly misunderstanding' and changes it into a 'character-driven conflict.'

We have a nice little cliff-hanger at the end of this section. However, you have to remember the format of the triad system—when we go back to Sarene, we'll be jumping back in time a bit. That means that you won't immediately discover what is going on with the gate of Elantris. Dramatically, this is my favorite of the triad structures. We get to hold this cliffhanger for a long time, building it through the next chapter.

And, we finally get to figure out what is going on. As I said, this is one of my favorite triads because of the way it manages to string a cliff-hanger across three separate chapters. I've spoken often of how difficult it was, at times, to maintain the triad structure. However, scenes like these are the reward. We get to see from Hrathen's viewpoint the things spoken off in Sarene's viewpoint, and often (especially later in the book) we can see the same scene from different sets of eyes, seeing different opinions and thoughts manifest.

Another interesting note in this chapter is that we finally get to see what Raoden went through in chapter one. The washing process isn't all that exciting, but I have had several people remark that they were sad to have missed it. I guess that's just human curiosity. Well, for those who wondered what the process was, they finally got to see it in this chapter.

And, as for the ending lines—yes, I did it again. The same little cliffhanger-extension from before. I figured that it was fitting, since this structure threw Hrathen into the city. Why not use the triad system to do the same thing with his getting healed?

Ah, we needed some more Lukel. He hasn't been around enough lately. I'm glad I had the presence of mind to throw in a character to balance out Shuden and Eondel's solemnity. Lukel doesn't really have much part in the plot, but he's always there to throw in a nice quip or two. His annoyance at being told his face is too pink here is probably one of his best moments.

I brought in the Patriarch for a couple of reasons. Though Joshua wanted to cut him (my agent is quite the headsman) and suggested that I have Omin reveal the proclamation, I felt that I needed someone with a little more authority to fill that role. Plus, ELANTRIS is a book about religion, and I wanted to look at the idea of having a religious leader who isn't necessarily as. . .wise as his people would like. By giving the Korathi religion a man like the Patriarch at its head, I could show a different aspect of faith in the book—the idea that a religion is more than its leader, and faith is more powerful than one man. I think that for any religion to last, it needs to be able to survive IN SPITE of the people who run it, rather than just because of them.

By the way, in the original draft, when Sarene gives her "All of Arelon is blessed by your presence" line when the Patriarch is on the docks, the Patriarch originally said "I know." Moshe thought this was a little overdone, so I cut it. In my mind, however, the Patriarch IS overdone and cliché—that's part of his character. But, anyway, one other item about this scene is the storm. I threw it in so that I could fudge the time of the Patriarch's arrival—the triad structure requiring me to have had him on the boat longer than the trip should take. This might actually not be necessary any more—in the original, I had him leave before he found out about the king's death. (I'm. . .not exactly sure why. Something to do with pacing and the triad structure. However, it was always my intention to have him read the proclamation at the funeral, so I had to have the ASSUME that Iadon would be executed, then take off with the proclamation. Either way, I eventually fixed this, smoothing things out considerably.)

I did this triad a little differently. You might notice that the Hrathen chapter starts off right where the Sarene chapter ends. Again, I eventually decided to be more loose with the triad system than I'd originally intended. It would have been to limiting to force all three chapters to happen during the exact same time. So, instead I have them all happen on the same day, usually overlapping, but not always.

Anyway, this chapter was a nice little place for Hrathen to feel proud of himself. You may have noticed that the chapters are speeding up—getting shorter, things happening faster—as the book progresses. This is an aspect of my style, and while it's not quite so noticeable in my new books (I've tried to even out my climaxes and surprised better during the last few years,) ELANTRIS is an 'Old School' Brandon novel. My books tend to push toward the endings quite dramatically, and you usually hit a place my friends affectionately call 'The Brandon Avalanche.' Generally, my books tend to go haywire in about the last ten percent, the pace increasing drastically, the viewpoints going wild.

That hasn't happened at this point in ELANTRIS, but we're getting closer.

This scene where Raoden and Sarene meet on equal grounds is, I hope, something that people have been waiting for. I intended the moment when Sarene lets Raoden take her hand to be a major event in the book. The phrase 'For the first time' (I.e., she took his hand for the first time) was added at Moshe's suggestion. I'm personally not as fond of it as I could be—my opinion is often times, making a passage shorter actually emphasizes it more. However, I wasn't so set on those four words that I insisted on not putting them in.

These two chapters—forty and forty-one—are another sequential pair in a triad, like I did before. I wanted to push out of Raoden's viewpoint as quickly as possible here, because he's already seen Elantris and New Elantris. In these scenes, Sarene's view of things will be more fresh—and therefore more interesting. She can experience some parts of Elantris for the first time, and we can enjoy her realization and discovery.

So, why does Raoden keep his identity secret from Sarene? I think his explanation here is earnest—he wants to get to know her without the truth of his identity throwing a crimp into the relationship. He, of course, intends to tell her eventually. At the risk of giving a spoiler, however, you needn't worry that this is going to turn into a 'I'm mad at you for lying to me' plot. Those always annoy me too. (Chick flicks are famous for them. "Oh, you're really a rich prince? Well, I hate you for pretending to be a pauper to win my love!")

I'm a little bit chagrined at how much faking I have going on in this chapter. Sarene isn't telling Raoden about the outside world (a necessary plotting device because of the triad—three days have passed, and I had to have a reason why she hadn't told Raoden about events outside the city yet.) Raoden isn't telling Sarene who he really is. On top of that, I'm keeping the secret of Hrathen's potion from my own characters, and I have to do some more rationalizing in this chapter—explaining why Sarene has enough food, and why she can't do AonDor—to make it all work. Ah. . .why can't we all just be honest.

Anyway, back to the chapter. I planned from the beginning for Sarene to give Raoden this vital bit of information about the magic system. As I've said before, she represents chaos—and chaos isn't always a bad thing. She is able to give Raoden the one simple bit of information that, despite all of his studying, he hasn't been able to find.

I worry, now that we have the map, that the Chasm answer is too obvious. Jeff made the Chasm a lot bigger than I intended it to be. And, since we zoomed in on the map so much, the Chasm dominates a large section of what we see.

Fortunately, I think it's the very next Triad where Raoden figures out how to use Sarene's bit of information. We don't have to wait long for him to figure out the secret—so, hopefully, if the readers figure it out, they won't feel Raoden is too stupid for taking so long.

I think this final scene with Sarene in bed is much more powerful since I didn't show the actual conversation with Eventeo. Having it begin with a depressed Sarene, the Seon link disappearing, leaves an air of melancholy on the scene that is more telling than the sense of sorrowful confrontation that would have come from having Eventeo explain himself to Sarene.

Obviously, poor Eventeo isn't in a very easy position. I didn't want him to have an easy answer; I think this is a very difficult decision for him to make, and I don't really think there is an obviously right answer—even though Sarene thinks that there is. We'll see later that Sarene doesn't look at things the same way a person who actually has to be a leader does.

I wish I could have made Eventeo a viewpoint character—he goes through a lot of conflict and trouble in the book. Unfortunately, there's never enough room to do all the things that you want to, and I like how tight the book feels with only having the rotating viewpoints.

I use this chapter as a strict triad chapter—it covers the same space of time as the other two chapters. With Sarene and Raoden running around together now, the triad system has been easy to forget. While I still start each chapter with the correct character, I often let the viewpoints intermix after that.

Again, this is intentional. After this last Hrathen chapter, I have the triad system break down completely. It's supposed to be a subtle indication of the chaos of these last few chapters. I'll even start throwing in viewpoints that aren't of the core three, which I hope with give the reader a sensation that something different is happening. The world, even the narrative structure of the book, is breaking apart. None of the old rules hold any more.

I don't know if you've noticed this, but this chapter forms a mini-triad of its own. It shows all three characters in their traditional rotation. It's something fun I decided to, playing with my own format. The idea was to give an unconscious sense of urgency to the reader by giving them a whole triad compacted into one chapter. I don't expect anyone to pick up on it—actually, I don't want them to. For it to work right, the reader will be paying so much attention to the text that they don't consciously notice the speed up. However, I hope that it will make them read faster and faster as the book progresses.

I think I've noted that my viewpoints tend to speed up as I approach the endings of books. Well, ELANTRIS is a perfect example. We're hopping viewpoints like a crazed body-snatcher. At the risk of sounding redundant, I did this to increase pacing and tension. Quick-rotating viewpoints give a cinematic feel to the story, in my opinion—kind of like cameras changing angles. This keeps things quick and snappy, and keeps the reader reading.

It should be noted that writing and filmmaking are two completely different arts. What works in one doesn't work in the other—action sequences, for instance, have to be written completely differently in a novel than they would be displayed on screen. However, both storytelling forms try to evoke similar feelings in their audiences. So, you can't do the same things in writing as you can in filmmaking—but you can get a similar effect by using different tools. Here, I use viewpoint shifts, which is something a filmmaker can't really access without first-person voice-overs. Viewpoint is, in my opinion, one of the prime unique tools that we have as writers. That's why I think it's important to understand, and to manipulate.

If you're paying attention to such things, we actually get two complete—and well-rotated—viewpoint triads in this chapter. Again, this is to increase the sense of urgency and pacing.

FORM

From here on out, the chapters get longer. It's interesting to try and work with pacing. I think the shifting viewpoints achieve the sense of drama I want, and coupling that with lots of new chapters would be repetitive, I think. So, I waited for the most dramatic moments possible to end chapters. I think this ending counts.

The triad system breaks down completely here. Everything is falling apart, and we're getting wild viewpoints from all over the place. (Well, not exactly—we only add Galladon and Lukel. However, I think that after fifty-nine chapters with only three viewpoints, suddenly adding two more will be disorienting enough to have the effect I want.)

Part of the reason I add the viewpoints is so that I can show the breakdown of the form of the book. However, another—perhaps more important—reason is so that I can show what is happening in places that don't involve one of the three viewpoints. Raoden is off in his own little world of pain, and Sarene and Hrathen have gone to Teod. If I want to show what's happening in Arelon, I need some new viewpoints.

1) Most people who read the book find themselves gravitating toward one of the three characters. Which was your favorite, and why? Did you find yourself disliking the time I gave to other characters, and if so, which one was your least favorite?