Lance Alvein (paraphrased)
Can you give us an idea when the Prelude to Stormlight Archive is with respect to Elantris?
Brandon Sanderson (paraphrased)
Found 94 entries in 0.218 seconds.
Can you give us an idea when the Prelude to Stormlight Archive is with respect to Elantris?
Raoden failed in finding ways to defeat Shaor's gang on two separate occasions. First, there was the original infiltration with Galladon (in which Raoden hoped to convince Shaor to stop attacking.) This excursion was informative, but not successful. The second failure was in dealing with the wild men who were trying to get to the carts. Raoden's decision to simply cut them off from the courtyard was eventually a failure. I'm not sure what else he could have done, but he still failed. Saolin's death, among other things, was the cost.
I knew that Raoden had to have more difficulty dealing with Shaor's band than he did with the other two. "Defeating" Karata and Taan happened quickly, and with relative ease. If Shaor's band hadn't presented a problem, then I felt that the entire "three gangs" plot would have been unfulfilling.
So, in these chapters, I stepped up the danger from Shaor and the crew. In the early drafts of the book, this danger wasn't present enough. (In fact, this was one of the main comments that Tom Doherty, CEO of Tor, gave me when he read Elantris.) So, I increased Shaor's numbers–by giving them a larger percentage of Taan's men, not to mention a larger number of men to begin with–and made them more dangerous in the way they attacked.
Time for my second favorite chapter! (The first, if you recall, was the one where Raoden led Karata to the king's palace.)
There are so many things going on in this chapter that I don't quite know where to start. I guess I'll begin with the Mysteries. I drew part of this religion, including the name, from the mystery cults of ancient Greece. I added the ritual sacrifices to give them a bit of zing. You'll get a little bit more of an explanation of the Mysteries, and why someone might decide to join one, in a later Sarene chapter.
As I've noted before, religion–especially its dark side–is a theme in this book. I don't think I could have covered this subject well in the book without including a look at cult mentality. Now, I'll admit that "cult" is a word we bandy about too frequently in religious discussions. It has been noted that Christianity started out as a kind of cult, and it seems that many consider any unorthodox religion to be a "cult."
To me, however, a cult is something that twists who you are, changing you into a shadow of what you used to be. I firmly believe that you can judge a religion by the effects it produces in its practitioners. Does it make them better people? If so, then there's a good chance that the religion is worth something. Does it turn them into people who sacrifice their own servants in an effort to make evil spirits come and kill their daughters-in-law? If so, well. . .you might want to stay away from that one.
Anyway, the Mysteries were–in my mind–a natural outgrowth of the Mystical Jesker religion. Like Galladon is always saying, they're NOT the same religion. The Mysteries are a perversion and simplification of Jesker teachings. Jesker looks to the Dor–the power behind all things–and tries to understand it. The Mysteries treat the Dor like some kind of force to be manipulated. (Which actually, is what AonDor does. . . .)
There's a tie for best line of the chapter, in my opinion. The first one goes to Sarene, and it's in her thoughts. " 'The problem with being clever,' Sarene thought with a sigh, 'is that everyone assumes you're always planning something.' " This was an original line from the first draft, and it's always struck me as a rather true statement. The other line goes to Roial, and it was actually added in one of the last drafts. "Mean young men are trivial, and kindly old men boring."
Another short, but powerful, Hrathen chapter. This is the head of Hrathen's character climax for the first half of the book. He has been questioning his own faith ever since he first met Dilaf. It isn't that he questions the truthfulness of the Derethi religion–he just has become uncertain of his own place within it. I wanted this moment, when he's semi-consciously watching the eclipse, to be the moment where he finally decides upon an answer within himself.
This is a major turning-point for Hrathen. His part in the book pivots on this chapter, and the things he does later are greatly influenced by the decisions he makes here. I think the important realization he realizes here is that not every person's faith manifests in the same way. He's different from other people, and he worships differently. That doesn't make his faith inferior.
In fact, I think his faith is actually superior to Dilaf's. Hrathen has considered, weighed, and decided. That gives him more validity as a teacher, I think. In fact, he fits into the Derethi religion quite well–the entire Derethi idea was conceived as a logical movement.
This spy conversation is a remnant of things left over from a previous version. I'll talk more about it later. However, if it looked like I was foreshadowing something. . .well, I was. Unfortunately, the thing I was foreshadowing got cut. Again, I'll talk more about it later.
So, this section marked one of the biggest changes to the text during the revision process. In the Mad Prince version of the novel, the soldiers who ride up to Kiin's house were members of the Mad Prince's army. They arrested Raoden–he went willingly–and tried him for the death of their leader. This took the better part of two chapters, and ended with Raoden almost getting beheaded.
Overall, I kind of happy to lose the scene. The trial was a big distraction, and I'm not sure that I ever pulled it off narratively. There were a few interestingly tense moments, and it did let Raoden show his honor in his defense (he accepted the judgments of the army assuming they promised to make Sarene queen.) However, I sense that the scene in general was just over-written.
It's interesting that this book would be the first one I publish. Many of you know that when I finally sold Elantris, I was working on my thirteenth novel. By the time Elantris was released, I'd written fifteen separate novels. Very few of these are sequels, and of the fifteen, Elantris is actually number six.
One of the things I pride myself on as a writer are my magic systems. I spend a lot of effort and prewriting on them, and I strive very hard to make them feel like nothing a reader has ever experienced before. Mistborn, the book that will come out a year after Elantris, is a very good example of this.
Elantris, however, is very interesting in that I don't actually get to spend much time with the magic. Or, at least, I don't get to spend much time showing it–the magic of this book is broken, and so while we find out a lot about it (and I think it's distinctive in its arrangement) we don't get to see it.
In the end, when the magic finally gets restored, I think it actually loses just a bit of charm. I developed this magic system to be an interesting and original puzzle–and so, when you finally see it working, I think there's a fulfilling payoff. However, in its actual form, it isn't generally as distinctive as some of my other magic systems.
Another interesting thing about this book, however, is that the setting includes a mixture of magical wonder itself–kind of as a balancing factor to the fact that we don't get to see the Aons doing anything. I think the problems associated with being an Elantrian, mixed with the interesting setting inside of the city, create an interesting magical ambiance for the book, one that seons serve to heighten.
Will you be posting what you change in the Elantris 10th year anniversary re-release like with how you changed the Words of Radiance ending? Also thanks for writing amazing books!
We'll try. The changes are, on one hand, way more pervasive--but on the other hand, far less substantial. There is a lot of cleaning up language, and a little of moving about the locations of buildings and the like for the sake of continuity.
If I may ask another thing, did you decide what come earlier in the Cosmere's Timeline between Elantris and White Sand ?
White Sand is earlier. I was pretty sure on this, but I wanted to be able to glance at the timeline and make sure I hadn't made any changes. (And I haven't.) It's pretty solidly locked into that place because of certain events around the cosmere, so you can assume it won't change.
Another big nod of thanks goes out to my thesis committee for their suggestion regarding this chapter. I'm not sure how I missed it, but in the original drafts, Raoden and company never acknowledge the fact that Hrathen had been healed. They never even mentioned it, and they certainly didn't give their thoughts on why it happened.
The fix was an easy one–you can read it in a few paragraphs in this chapter. However, the fact that it hadn't been there before was indeed a problem. Moshe was dumbfounded when I mentioned the oversight to him.
So, thanks Sally, Dennis, and John. You saved me from some embarrassment.
I like the explanation that Raoden gives here for Hrathen's healing. It seems like it would make sense to the Elantrians, and it saves me from having them suspect what was really going on.
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 him ASSUME that Iadon would be executed, then take off with the proclamation. Either way, I eventually fixed this, smoothing things out considerably.)
Originally, I had the steps leading up to Elantris from the outside be a construction put there by the people of Kae. I knew I wanted a large number of scenes on the wall–it is such a dominant visual feature of the book that I thought it would make a good stage for scenes. However, I quickly realized that it would be the people of Kae–not the Elantrians–who controlled the wall. The Elantris City Guard grew from this idea, as did the set of steps constructed on the outside, leading up.
As I worked more and more on the book, however, I came to realize that the pre-Reod Elantrians wouldn't have needed a city wall for protection.Obviously, to those who've read more, there is a good Aon-based reason for the wall. However, there is more to it than that, as well.
The wall of the city is a symbol–it's part of the city's majesty. As such, it made more and more sense that there would be plenty of ways to get up on top of it.
When we got the cover art back from Stephen, we were amazed by its beauty. A few things, however, didn't quite mesh with the text. One of these was the set of steps–they were so ornate, so beautiful, that it didn't fit that they would have been designed by the people of Kae. At that point, things kind of fell together, and I realized that there was no reason why the Elantrians themselves wouldn't have put a large staircase outside the city leading up to the wall.
And so, in the final rewrite of the book (the ninth draft) I changed the staircase, and the general feel of the wall, to give the proper sense to the reader. The staircase was placed by the Elantrians as a means of getting up on top the wall. The wall itself became less a fortification, and more a wonder–like the Eiffel Tower. It is there to be climbed and experienced.
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.
Chapter Forty-Six - Part Two
As I've said before, I worried about the Sarene-Raoden plot falling too much into "romantic comedy" stereotypes, so I took measures to try and make them act more honestly. In this chapter, Raoden tries to push Sarene away–but, of course, she doesn't believe him. Honestly, I think people in a lot of such plots TRY to find ways to misunderstand each other. That's the only explanation I can give for why such ridiculous things occur.
In cutting the Mad Prince, this section in the Sarene/Raoden chapters was one of the things I was sad to change. As I mentioned in a previous annotation, in the Mad Prince version of the book, Sarene thought that Raoden had returned with an army to try and take the city. I started this chapter out with a scene of Raoden thinking about the problems Sarene's realization caused. I’ll just stick it in here:
One side effect of her mistaken supposition was that she hesitated in regards to their own relationship. He could see the conflict within he–the two of them had grown very close over the last five days, acting on the feelings they had both been forced to hold back during the weeks of Sarene's food distribution. Yet, now, Sarene thought that her husband might actually be alive and, a truly devout daughter of political necessity, she felt that getting any closer to Raoden would betray her vows. With surprise, Raoden realized that he was competing with himself–and losing.
I really hate to lose that last line. It always struck me as ironically clever. However, there was another loss that was even tougher to lose. It comes in where Raoden and Sarene are at the city gates:
Raoden fell still. He wanted her to stay–he longed for her to stay. But, at the same time, he knew he had to do whatever it took to get her out of Adonis. The city was death. As much as it pained him to think of her leaving, it pained him more to think of her staying.
"He will be there," Raoden said enticingly, his voice suddenly growing quiet. "Raoden. The man you love."
Sarene's hand grew slack, and she waved uncertain eyes towards the Elantris city gate. "No," she finally said. "That's not what I want any more."
I think the reason I hated to lose this scene is obvious. Right here, Sarene gets to choose "Spirit" over the images she has in her head of the perfect Prince Raoden. It's an opportunity for her to show that she really does love him, despite what he is, despite what the other options might be. It's love offered against logic and against wished-for dreams. In other words, it's realistic love. Of all the scenes I had to cut, these few paragraphs make me the saddest to lose, I think.
Moshe and I agreed on just about every edit or change made to Elantris. There is one small thing, however, that we kind of went the rounds about. The word Kolo.
Galladon's "Kolos" are, in my mind, an integral part of his personality. I characterize him a great deal through his dialogue–he doesn't really get viewpoints of his own, so everything I do for him at least until the ending I either have to do through Raoden's thoughts or through Galladon's own words. When I was coming up with Galladon's character, I realized I would need a set of linguistic features that would reinforce his culture's relaxed nature. So, I went with smooth-sounds, and gave their dialect a very "chatty" feel. The Dula habit of calling everyone "friend" came from this–as did their habit of softening everything they say with a question tag. Linguistically, questions are less antagonistic than statements, and I figured a culture like the Dula one would be all about not antagonizing people.
A number of languages in our own world make frequent use of similar tags. Korean, the foreign language I'm most familiar with, has a language construction like this. Closer to home, people often make fun of the Canadian propensity for adding a similar tag to their own statements. I hear that Spanish often uses these tags. In many of these languages, a large percentage of statements made will actually end in a softening interrogative tag.
Anyway, enough linguistics. I'm probably using the standard "literary" posture of falling back on facts and explanations to make myself sound more authoritative. Either way, I liked having Galladon say "Kolo" a lot. In the original draft, the tags were added onto the ends of sentences, much like we might ask "eh?" or "understand?" in English. "It's hot today, kolo?"
Moshe, however, found the excessive use of Kolo confusing–especially in connection with Sule. He thought that people might get the two words confused, since they're used similarly in the sentences. Simply put, he found the kolos distracting, and started to cut them right and left. I, in turn, fought to keep in as many as I could. It actually grew rather amusing–in each successive draft, he'd try to cut more and more, and I'd try to keep a hold of as many as possible. (I was half tempted to throw a "kolo" into the draft of Mistborn, just to amuse him.)
Regardless, we ended up moving kolo to its own sentence to try and make it more understandable. "It's hot today. Kolo?" We also ended up cutting between a third and a half of the uses of the word, and losing each one was a great pain for me. (Well, not really. But I'm paid to be melodramatic.) So, if you feel like it, you can add them back in your mind as your read Galladon's lines.
We that there are spren that are partially of Honor, partially of Cultivation, and Odium. Can there be spren made of any combination of Shards?
Yes. Well, you would have to call them... Under that definition if you call a seon a spren, then yes. If you don't call a seon a spren, if you define a spren as, "On Roshar, related to the natural world of Roshar," then no. Theoretically yes, but it wouldn't really work. But it depends on how you define spren. If a Shard were to come and reside on Roshar like the other ones have, then you could theoretically see other new spren appearing out of them.
Could there be a spren of all 16 Shards combined all at once?
*hands out RAFO card*
How did you come up with Shardpools and travel between the worlds?
...So, what happened is (close as I can remember; it's been a long time now), close as I can remember, I wrote Elantris in, like, 1998 or 1999, and I, at that point, didn't really have the cosmere in place. I knew I wanted to do some sort of grand epic, I knew I wanted to do some sort of thing, but I just wrote that book-- Elantris is mostly a discovery-written book, rather than an outlined book. And I wrote this book, and that's when I started a lot of these ideas. I stepped away from it, and I started writing a book called Dragonsteel, which was Hoid's origin story. And then I kinda got into the dark age where I was trying to be George R.R. Martin for a while. And then when I came out of that, I wrote The Way of Kings [Prime]. And during those days, I was really looking for these tying agents. When I put the first Shardpool in, I had-- I'm just like "Here's a well of power. I don't know what this does." I was discovery-writing the book. By the time I sold Mistborn and Elantris, I sold those two in a deal in 2003, that's when I'm like, "All right, now I'm gonna do this for real." I've had all this trial run-- I'd written thirteen novels at this point, and I'd sold #6 and #14, Mistborn not being written yet... So, I sat down with Elantris, and I built out the cosmere, and I built out these things, like "Why do I have this pool of power? What am I gonna do with the pool of power in the next book? I want this to be a theme." And I started building out the cosmere from there. So, part of it was organic, part of it was by design.
In these chapters, I had to be very careful during the Sarene viewpoints. As I was writing, I had a habit of accidentally referring to Raoden by his real name, rather than calling him Spirit. Sarene, of course, doesn't know who he really is. I found one place where I called him "Raoden" that somehow lasted all the way to the final edit–hopefully, that was the last one.
Hum. I forgot how short many of these chapters got. Usually, I don't let my chapters get this short in a book. I like longer chapters, and tend to be pretty stable in my chapter lengths. Elantris, however, is an aberration. It has a good twenty chapters more than my average book, despite being shorter than many of them.
Sarene used to tap her cheek a lot more than she does in this draft. It was a quirk I designed for her at the beginning–a nervous habit I thought indicative of her personality. However, a lot of people found it distracting. They seemed to think that tapping the cheek was an odd behavior. (Just as a note, when she taps her cheek, I'm thinking of her folding her arms, with one hand raised contemplative, index finger resting on her cheek. I've been known to sit that way some times.)
Anyway, I took out many of the references. As Moshe said, "There's just too much tapping going on!"
So, in the original version of the book, Raoden and Galladon saw Eton's army outside the city when they went up to the top of the wall. This shocked and concerned them, which is why they went searching for Sarene to get news about the outside world. More on the Mad Prince later, however.
Originally, when Raoden and Galladon got to the top of the stairwell, they hacked their way through the door with Seolin's sword. When I got to this point, I'd completely forgotten that I'd already established that there was at least one axe in Elantris. In the rewrite, I put that in instead.
Do you think that if Ashe had seen Ien in Elantris while he was there...Do you think he would have recognized him?
Okay, now, I know you're going to laugh at me here. However, I suppose you deserve to know the whole story of this book. After all, I told you about the whole "Adonis" thing.
Well, the thing is, the first version of the book included about two pages of poetry from Wyrn the King. I think every prose writer goes through a stage where we think, for some reason, that we have a talent for poetry. It's doubly bad in fantasy, where we've all read Tolkien, and felt like adding poems, songs, and the like to our stories.
The thing is, most of us aren't very good at it. Wyrn the King was a narrative alliterative poem patterned after Beowulf, and it was TERRIBLE. I might be masochistic enough to post it in the "deleted scenes" section of the website. I'm honestly not sure yet. (Actually, I wrote the poem as a college assignment. I wiggled out of doing something research-oriented by somehow convincing my teacher that I deserved to do a creative project instead. When I finished, I felt a little bit obliged to stick it in my current book, as I'd told my teacher I would. Sorry, Dr. Thursby, but. . .uh. . .it didn't make the final cut.)
Anyway, there was a point behind sticking the poem in the text, even if I completely overshadowed it by including so many lines of poetry. This section is really all we get in the book itself about Fjorden's past. As I've explained in the annotations, Fjorden switched to Shu-Dereth to do its conquering, relying on religion rather than armies. When they did so, they went back and rewrote many of their great classics. (Orwell would be proud of them.)
This is actually based on some events in our world. Some scholars think that Beowulf underwent similar revision, the monks who copied and translated it adding Christian symbolism to the text. After all, no great artist could possibly have been a true pagan. Everyone knows that Aristotle was a Christian–and he died before Christ was even born!
Cutting the Mad Prince forced me to rewrite a bit of this chapter. As I mentioned, in the original draft, Raoden and Galladon saw Eton's army crouching outside the city. At first, Sarene didn't know what to make of this news. She decided it couldn't be a Fjordell army–one could have never arrived so quickly. She knew it wasn't Teoish.
The chapter used to end with a startling realization from Sarene–she decided that the phantom army must belong to Prince Raoden. She decided that he hadn't died or been killed, but had instead fled to raise an army to take the throne from his father. I thought this was a very clever twist, and it was one of the things I was most sad to lose by cutting the Mad Prince.
You'd be surprised how much can be said about the title of this book. Naming books is one of the most frustrating, and most fulfilling, elements of writing. I'm more fortunate than some authors I know–for most of my books, the names came easily. Sometimes, I even came up with the title before I wrote the book. (This has actually only happened once, when thought up the phrase "The Way of Kings," and thought "Man! That would be a great title for a book!")
Elantris has had several titles. During the rough draft phase, I simply called it "SPIRIT." I knew that the main character's name would be based on the character for Spirit, and that would also be the name he took for himself when he was in exile. I never intended this to be the final title for the manuscript, but it was what I named all the files when I was typing the work.
Those of you who've read the book realize the special significance of "Spirit" (or Aon Rao as it eventually became known) to the climax of the story. I'll talk more about this in a bit.
Well, as I was writing the story, I realized I needed a better title. The most obvious choice was to somehow work in the name of the fallen magical city that was the focus of the book. Now, I'm a little embarrassed to admit this, but the city "Elantris" was actually originally named "Adonis." I'm not sure what I was thinking. Sometimes, when you're coming up with a lot of fantastical names, you create words that have a certain, unforeseen connotations or connections. In this case, I wasn't even thinking of the Greek myth. "Ado" was simply the Aon I chose to base the city’s name around, and "Adonis" (Pronounced with a long "A" and a long "O") was the word that came out of that Aon.
So, I named the book The Spirit of Adonis, hoping to play off of Raoden's name.
It was, however, actually a three-fold pun. I included this line–"The Spirit of Adonis" at the climax, when Raoden realizes that the city itself formed an enormous Aon Rao.
I didn't realize what I'd done until my writing group met for the first time, and they said "I like the beginning of the book. I'm having trouble figuring out what this has to do with the Greeks. Is it because the god-like people were so arrogant?"
Then it hit me. Adonis, from Greek mythology, was a beautiful man loved by Aphrodite. The word has become a kind of paradigm for a beautiful–almost perfect–specimen of the male species. And I had unwittingly named my book after him.
Let's just say I changed that pretty quickly. However, I needed a new name for the city. I played with a number of different combinations of Ado, but somehow ended up trying up different sounds and combinations. Thankfully, I came up with the word "Elantris." As soon as I wrote it down, I knew this was my city. It sounded grand without being overbearing, and it had a mythological feel to it (hearkening slightly to "Atlantis".) I renamed the book "The Spirit of Elantris," and proceeded.</p>
Then came time to send out the manuscript. I had had some comments on the book–people liked "Elantris," but the "spirit of" was less popular. I tried several iterations, and even sent out some query letters calling the book "THE LORDS OF ELANTRIS." That just felt too cliché fantasy for me, however, and I eventually returned to "The Spirit of Elantris."
Finally, the book got sold. At this point, my editor (Moshe Feder) suggested that we shorten the title to simply Elantris. Remembering how other people had been unimpressed with the "spirit of," I agreed. Now that I've seen the cover lettering and worked with it as "Elantris" for some time, I'm very pleased with the change. The new title has more zip, and makes the book sound more majestic. I still get to have a reference to my old title, as Part Three of the book is called "The Spirit of Elantris."
Of course, even this title isn't without its problems. People have trouble spelling it when I say the title, and some think of the car named the "Elantra." At one panel, I even had one person miss-hear me, thinking the name of the book was "The Laundress." That would certainly be a different book...
Where were you in your writing process for Elantris-- I know it was your sixth book and you were on your nineteenth when you got it published or--
Yeah, good question.So, where was I in my process when I wrote Elantris and when I got published, which was my sixth novel. So what happened with my career, it's kind of a very weird thing. You find that everybody has a different path to success as a writer. I heard early on that your first five books are generally terrible and this was really relieving to me, because I--a part of my brain-- this would not-- someone else, this might've been the worst thing to tell them. But for me it was the best thing because my brain said, "Okay, good, you don't have to be any good at this for your first five books".
And so my first five books I experimented quite a bit in story and tone. I did a gritty cyberpunkish thing. I did a comedy. I did an epic fantasy. I tried a lot of-- I did a space opera. I did a lot of different things. And once I had done all that, I came back and said, "You know, my first love is epic fantasy, and it's what I really want to do." So I sat down to write book number 6, which was Elantris.
And at that point, I had gotten a few books underneath me. I kind of knew what I was doing, though I was not-- I hadn't figured out my process quite as well as I would have liked. Elantris and a lot of the books during that era I did a lot more discovery writing, and I naturally am better when I have a stronger outline. But that's where I was.
My biggest weakness as a writer at that point was revision. I had spent those five early books just trying different things, and that permission for me to not be good yet also kind of gave me the psychological ability to be like, "Well, I don't have to revise this one, because I don't have to be good yet." But what that meant is I didn't practice revision. So once I finished Elantris, I was not good enough yet to know how to take a good book and make it great. So it went the rounds in New York and got rejected; rightly so, because it was very flabby and had not been focused. And I know, from a guy who writes thousand-page books, focus is a weird thing to say. *laughter*
And so, when I actually sold Elantris to Tor, it was after it had gone through four or five drafts and I had finally sat down and kind of buckled down and said "I need to learn revision and learn how to make my books better". So I sold it right after-- right while I was working on Way of Kings in 2002, 2003, somewhere around there.
It seems to me that members of the [LDS] church generally like Elantris a lot more than people who aren't in the church and why do you think that is?
I haven't noticed that but if that were the case… boy. I don't know that whole Raoden just pushed through it has some sort of tying your spirit to it and that's definitely-- I could see that being relevant.
I've been told it's Hrathen's struggle with faith.
I think they like the whole-- the whole evil missionary thing would be something thing that members of the church would be like "Ahh evil missionary?! That's cool!" *laughter* So I think that's totally possible but I hadn't noticed that specifically. I think that it is also a book that is less focused on the action and fighting. Like Mistborn is more focused on that, and so I would expect that there's that relevant issue, perhaps, as well.
I'm a very sequential writer. When I write a book, I usually start with the prologue and write straight through until I hit the epilogue. Though I can't remember for certain, I'm pretty sure that this prologue was the first thing I ever wrote for Elantris.
Back in those days, I didn't outline as much as I do now. When I first put fingers to keyboard, I really didn't know where this book was going to go. I had some vague idea of what I wanted it to be, but I didn't know how I was going to get there. However, this prologue really helped solidify things for me.
I love how it works in the story. It's quick, descriptive, and gives a marvelous outline of the magical setting of the book. It's also one of the most heavily-edited sections of the book. Moshe didn't like my original draft of it because he thought it was over-written. The original first line of the book was "Whispered are the days when Elantris was beautiful." I kind of still like this line better, but it may just be nostalgia. The line kind of has a faint. . .flowing quality to it. An etherealness.
Regardless, "Elantris was beautiful, once" made for a nice compromise. I'll probably post the entire, first-draft version of the prologue in the "deleted scenes" section of the website, if you want to compare.
Despite my preference for the old first line, I like the other changes we made to the prologue. Over all, it became more descriptive and easier to understand. It's a nice springboard to the story, and we've used it several places as a kind of quick teaser to get people to read the book.
(Including putting it on the back cover of the hardback.)
Chapter Forty-Six - Part One
Raoden's reaction to Iadon's death is just a little bit cliché, but I think that cliché exists for a reason, so I wrote the scene this way.
Sometimes, I have difficulty in my writing because I try to be TOO original. I react pretty strongly against anything I've seen before, and don't want to include it in my books. This has served me well in some ways–Moshe bought Elantris partially because he found it refreshingly different from other fantasies on the market. I generally have a strong element of originality to my worlds, my magic systems, and my plot structures. This is part of what draws people to my work.
However, sometimes I go too far. If I see something written one way–even if that way is good–then I react against it, trying to find another way. I've stayed away from "Eternal Apprentice" plots (Thank you Craig Shaw Gardner for the name) even though they are extremely popular in fantasy–indeed, they are what got me into fantasy when I was younger. But, because of some things like this, my books can be more difficult to get into. The extremely steep learning curve of my works, the focus on strange settings and odd magic systems, might be off-putting for some readers. (Elantris, by the way, is only a hint at these kinds of things. Mistborn is a much better example.)
I try to walk a fine balance in my works. The trick is to write something that is original and new, breaking convention and tradition–yet at the same time have it FEEL like a fantasy. People read in the genre because they like the things it can do. I have to add the new, Sanderson, spin to things without tossing out all that is wonderful and resonant within the genre.
That's why you'll see some old archetypes showing up in my works occasionally. In a way, Mistborn is an old-fashioned "overthrow the evil empire" fantasy. When choosing my next project, I decided that I had enough sufficiently new material–both in setting and in plot–to tell the story in a way that would be fresh. I think it adds something to the genre, rather than just recycling what is there. So, I went ahead with it, hoping that the familiar and the original would work together.
Elantris is similar. I threw in odd (for fantasy) plotting structures, but I let the air of "standard medieval culture" remain in the book. (In fact, as I've noted, this is probably my most like-Earth book in that way.)
The balance between the new and the familiar. That's what it's all about.
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.
So, AonDor is super versatile and powerful.
Yes, but region-locked!
Yes, it is region locked, exactly. If a full Feruchemist using nicrosil were to create an unlocked medallion that allowed an Elantrian to store Connection to Elantris' location, would it let them use AonDor at full power as long as they were tapping that Connection?
Yes. That should work just fine.
Just understand that the medallion's going to have to be usable by everyone in order to work. You're going to have to jump through some hoops, but I think what you want there would work. And for those of you listening, that would be the harder way to unlock AonDor. There are easier methods.
This ending scene is where Hrathen and Raoden come the closest to speaking to one another. Hrathen stands there, looking down on Raoden. Then he leaves.
In case you were wondering, no. They never say a word to one another throughout the entire book. Sarene mixes with both of them, but Hrathen and Raoden barely interact.
Elantris to Emperor's Soul? Similar time period, Emperor's Soul is a little after.
Now we're getting into the most heavily-edited chapters of the book. From here, if you're curious about the Mad Prince version of the book, look in the "Deleted scenes" section. For the rest of the annotations, just realize that what the Mad Prince once did, Telrii now does. There is, of course, a lot of cut material–however, all of the essential elements of the plot still occur.
Basically, the Mad Prince gave aggravation and problems to Hrathen in these late chapters. He'd had so much success with his Elantris-poison plots that I knew I had to give him a few more wrinkles during these chapters. In the original draft, he instigated the arrival of the Mad Prince, then realized that he couldn't control what he'd unleashed.
These were all difficult edits. I still think the Mad Prince worked better in the role than Telrii does–however, the book as a whole works better without the Mad Prince in it. Sometimes you have to cut something good in order to achieve a better over-all effect.
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.
Is the cosmere, the thread connecting several of your series, something that came from the beginning, or something that kind of grew?
What a great question! So the cosmere, which is the thread connects a lot of my books together. All of my epic fantasies are connected in this world called the cosmere. Was that from the beginning, or was it something that grew?
So I had, I often point to the fact that I had those years not getting published as a big advantage, because while I was working on those books, I didn't write the first ones as a connected shared universe. It was after I had done a number of them, that I'm like, "Hey, there's something here! There's a thread that I can weave together." But by the time I got published, I knew all of that right?
And so, like when I wrote Mistborn, which was my, the first book I wrote knowing it would get published. Elantris was my first published, it was number 6 in those years. I sat down specifically with Mistborn and built the cosmere, using some of these unpublished books as the history of what had happened. So from the get-go of reading it, it was all interconnected. Elantris got retrofitted a little bit, to fit in with this. From Mistborn is where it all kind of starts working together and things like that.
I was inspired to do this by authors I had read who did this really well, that I liked. Stephen King did it. Michael Moorcock did it. It really kind of blew my mind when Asimov connected the Robots and the Foundation books. Of course, you know, comics have been doing it forever. But when I saw authors doing it is what made me really excited. I would count those as inspiration.
If you were wondering, most of the explanations we get in this chapter are true. The reason that Raoden was subject to the Dor attacks was because he spent so much time practicing with the Aons. He began to make a bridge between this world and the Dor, and because of that, he gave the Dor a slight opening into his soul. I imagine that he isn't the first one to suffer something like this during the ten years that Elantris has been fallen. Other Elantrians probably practiced with the Aons, and the Dor eventually destroyed them. When it was done, they simply became Hoed.
By finally using the Dor effectively, Raoden relieved a little bit of the pressure, letting the nearby buildup of the Dor (the one that he himself had created by practicing so much) rip through him and fuel that single Aon.
Originally, I had Raoden's conflict with the Dor continue on after this scene–I had it continue attacking him. In a later draft, however, I realized that I'd made a mistake. Raoden has other things to worry about in the upcoming chapters–he doesn't need the Dor attacks to create conflict and tension. So, after this chapter, the Dor attacks actually became distractions. I also realized that the way I'd set up the magic system, this chapter was probably the place where the Dor should stop attacking, since Raoden had fulfilled what he wanted it to do.
This is a different kind of Hrathen chapter. With it, I wanted to set the tone for the final section of the book. Only about 15% of the novel remains, and things are going to change for the last bit. You may have noticed a slight tone shift in this chapter–I made it a little darker, filling it with death imagery. (Incense, ash, darkness, Svrakiss.) I wanted to subtly get across that things are growing more dim for Hrathen and Arelon.
Originally, this scene happened outside, at the Mad Prince's pyre. I liked the death imagery there a little better–Dilaf sifting through the ashes of a funeral pyre made for a very interesting image. However, the visuals in this newer version have their own advantages. I was able to use the lantern to half-light Dilaf's, and the smells from the tent make a nice sensual addition to the section.
This is the dénouement to the denouement, I guess. We get to end with my favorite character, tying up some of the small loose ends that were related to her storyline. There is some good material here–she points out that Raoden is doing well as king, how Ahan is fairing, and gives a nice prognosis for the future of Arelon.
However, the important part of the epilogue comes at the end. I love the last line of the book, despite the fact that Joshua disagrees with it. (He wanted something else there–I can't quite remember now what his quibble was.)
Anyway, I always intended to end this book talking about Hrathen. He was their savior, after a manner–and he certainly was a dominant force in the book. I wanted to give him one final send-off–to honor him for what he did, both for Arelon, and for the story in general.
Chapter Fifty-Eight - Part Four
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 worked for a while on the last line of Part Two. Originally, Hrathen thought to himself "Well, this isn't good." However, Moshe disagreed with that line. First, he thought it was too quippish. He wanted something more serious here. Second, he didn't think that these events were actually bad for Hrathen. Telrii, a man who had been giving Hrathen serious troubles, and Eondel, one of his main enemies, had just killed each other. On top of that, Roial—the main rival for the throne—is dead. All in all, a lot of annoying people are dead.
Moshe had a point, though I did disagree a bit. I think Hrathen would see Telrii's death as a wasted investment. He was still hoping to control the man, and having Telrii on the throne and amiable to Hrathen would have been a much better outcome, since it would leave Hrathen looking less powerless before Wyrn.
However, I went ahead and changed the line. It now reads "So much for avoiding a bloody revolution." It gets across the same ruefulness as before, without being as flippant.
Also, "The Call of Elantris"—the name of Part Two—is probably the weakest of my three sub-titles. I liked "Shadow" and "Spirit" a lot, and I knew that I had to use something parallel. I named this one "Call" because of the way Hrathen and Sarene both end up getting tossed into the city, then end up using that event to their advantage. Raoden also deals with the "call" of the Dor inside himself during this section, overcoming that particular conflict
There are a couple of interesting things about this chapter. First off, it didn't originally start with Raoden waking up. When I first wrote the book, I threw Raoden directly into the city, line one. That original line was: "It wasn't until Raoden heard the gate swing closed behind him, booming with a shocking sound of finality, that he realized he had been damned."
While this line worked pretty well, I found I had to do an extended flashback showing him waking up and frightening the maid, etc. In the end, I realized that this was a bulky construction that didn't really speed the novel up–but rather slowed it down. So, I rewrote the first scene to have Raoden waking up, seeing Elantris, and then realizing he'd been taken by the Shaod.
My books tend to have what are called "steep learning curves." In other words, they take a little getting used to. Fantasy in general has a steep learning curve, and I don't tend to write very standard fantasies–I like to push the genre a little bit, introducing strange settings and irregular magic systems. Because of this, I have to be very careful at the beginnings of my books not to overwhelm the reader. This book was a good example–taking it a little easier, giving the reader a more cautious ease into Elantris, proved the better route.
Happily, I eventually managed to preserve the original line with its catchy feel. I don't usually do things like this–I don't believe in the standard "hook" idea. However, when I was thinking about this book, the first lines of the first three chapters were some of the first things that occurred to me. These three lines became the foundation for how I characterized the separate viewpoints, and they were part of what drew me to writing the book in the first place. If you go through and read them, I think they each have a little bit of zip, and hopefully invoke a sense of curiosity. These three lines introduce each character and one of their primary conflicts, and do it in a simple, clear way.
Maintaining this feel with the new first scene was important to me, even though it could be argued that the first line of chapter one is a bit of POV error. I'm revealing information that the viewpoint character doesn't yet know. I avoid these, but in this case, I felt that cohesion was more important than strict POV, right here.
I also did a second massive cut just after Raoden was thrown into the city. If you read the earlier draft, you'll see that he struggles with what has happened to him a bit more. There's even a brief section where he thinks about Ien and some of the seon's words of wisdom. I cut these sections because they just slowed the book too much. I figured Raoden's shorter soul-searching at the beginning, where he quickly comes to the decision to "look damnation in the face," helped the story move along. Again, I worry about my beginnings–perhaps too much–because they have a history of dragging just a bit. By pushing Raoden into walking through the city, I kept the pacing up.
Everything else in this chapter pretty much stayed the same. In the original draft, Galladon was actually named Galerion. I made the change because the name "Galerion" just didn't fit the eventual linguistic style I devised for Duladel. Again, I didn't do as much planning for this book as I do for books I write now, and I just kind of let the names and cultures develop as I wrote. In the end, Galerion's culture out-developed his name. I figured that the main Dula in the book needed to have a Dula-sounding name. Interestingly, Moshe–my editor–independently decided that he really didn't like Galerion's name. When I made the suggested change, he was very pleased. Originally, he didn't like Raoden's name either–but this came, mostly, because he had trouble pronouncing it. I actually really like the name, but understand that it can be difficult if you don't understand the Aonic language. Remember–two hard vowel sounds formed by the Aon, every other vowel is soft. RAY-OH-den. (Read the pronunciation guide for more.)
Galladon/Galerion originally spoke with a much stronger dialect in this chapter. However, these dribbled off after the first few chapters, and I decided I didn't want him to be quite as difficult to understand. So, I went back and cut them. You'll notice, however, that Galladon still hits the dialect pretty hard in this first chapter.
So, this chapter gets the grand prize for most edited and revised chapter in the book. There are other chapters that have more new material–but only because they were added in completely after the original draft. This chapter, good old chapter two, was the one that underwent the most tweaks, face-lifts, additions, and edits during the ten drafts I did of Elantris.
And, I think poor little Sarene is the cause of it.
You could say that she played havoc with the book in much the same way she did with Hrathen, Iadon, and Raoden in the story.
As I worked on the novel, Sarene as a character took on a much more dominant role in the plot than I had intended. Perhaps it's because she's the intermediary between the other two characters, or maybe it's because I liked her best of the three characters. Either way, in my mind, this book is about Sarene. She's the catalyst, the force of change.
In the end, she's the one that provides the solutions to both Raoden and Hrathen's problems. She gives Raoden the hint he needs to fix Elantris, and she gives Hrathen the moment of courage he needs in order to turn against Dilaf.
However, I've found that Sarene is many people's least-favorite of the three characters. I had a lot of trouble in the original drafts of this book, since many alpha readers didn't like her in this chapter. They thought she came off as too brusque and manipulative. It was always my intention to show a more sensitive side to her later in the novel, but I didn't intend to lead with it quite as quickly as I ended up doing.
The first edit to the chapter came with the addition of the Sarene-and-Ashe-travel-to-the-palace scene. This is the section were Sarene sits in the carriage, thinking about her anger at Raoden and her insecurity. This counteracts a bit of the strength we see from her in the first scene at the docks, rounding her out as a character.
The second big addition came in the form of the funeral tent scene. This was added as a tangent to one of Moshe's suggestions–he wanted us to have an opportunity to see Sarene investigating Raoden's death. In the original drafts of the book, we felt the narrative made it too obvious to outsiders that Raoden must have been thrown into Elantris. Moshe and I felt that it seemed silly that people wouldn't consider the possibility that Raoden wasn't dead. This wasn't what I wanted–I wanted most people to accept the event. Only someone as overly-curious as Sarene would have been suspicious.
So, I revised the story to downplay the suspicion around Raoden's death. Instead of having Iadon rush through the funeral (an element of the original draft) I added the funeral tent and had Sarene (off-stage) attend the funeral itself. These changes made it more reasonable that very few people would have suspicions regarding the prince's death, and therefore made it more plausible that people wouldn't think that he had been thrown into Elantris.
Other small tweaks to this chapter included the removal of a line that almost everyone seemed to hate but me. After Sarene meets Iadon for the first time, she is pulled away by Eshen to leave the throne room. At this time, I had Sarene mutter "Oh dear. This will never do." Everyone thought that was too forceful, and made her sound to callous, so I changed it to "Merciful Domi! What have I gotten myself into?" A piece of me, however, still misses Sarene's little quip there.
Raoden is an expert at manipulating his surroundings. This doesn't make him "manipulative," in my mind. (You can read about a real manipulator in my next book.) Raoden simply knows how to take what he is given and make the best from them. In a way, this is the soul of creativity. Raoden is like a master composer or an artist–except, where they take images or sounds and combine them to suit their needs, he takes the situation and adapts it to create something useful. Outside of Elantris, he took his father's edicts and turn them against the man. However, thrown into a terrible situation like the pit of Elantris, Raoden really has an opportunity to shine.
He's kind of like a magic unto himself. I've known people a little like him in this world–people who can defy convention and reality, and just make things work. Somehow, Raoden can make three out of two. He can take the pieces and combine them in new ways, creating something greater than most people thought possible.
In short, he's the perfect hero for this kind of book. When I was writing Elantris in the winter of 1999 and spring of 2000, I was finishing up my undergraduate degree at BYU. The book I'd written before it was called The Sixth Incarnation of Pandora–undoubtedly the strangest, most-un-Brandon-like book I've ever constructed. Pandora was a SFstory about a man made immortal though careful–and expensive–application of nanotechnology. The process slowly drove him mad.
Pandora was a dark, grisly book. The man character could withstand alarming injuries without dying. One prime theme of the novel was dealing with the psyche of a man who could slaughter thousands of people while being shot to pieces, then find himself reconstructed a short time later. It was a rather violent book–probably the most disturbing I've ever written.
When I got done with that book, I reacted against it by wanting to devise a plot that didn't depend at all on violence. Elantris was the result. I wanted to tell a story about a hero who could succeed without having to beat up on the people who opposed him. I took away his physical abilities and his royal resources, leaving him with only his wits and his determination.
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.
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.