Celebrating Fantasy: The Chosen One

This may be a controversial view, but I enjoy “Chosen One” stories. A lot of them are cliched, yes, but when you run across a great one, it can be a very rewarding reading experience. It’s all a matter of how the author executes it.

A sufficiently talented author knows how to write this kind of story without losing the tension. The big thing it comes down to is making any prophecies open-ended. Don’t have the prophecy spell out everything that’s going to happen. Don’t tell us that the Chosen One is going to succeed. That takes all the suspense out of the story.

One of my best examples for this is the Harry Potter series.

SPOILERS AHEAD IF YOU HAVEN’T READ THE SERIES YET.

 

Rowling handles the Chosen One trope very well in my opinion. For one thing, you don’t find out until the fifth book that Harry is the Chosen One. Even then, the prophecy you’re given is open-ended. Harry can defeat Voldemort. There’s no guarantee that he will.

Instead of taking away tension, this introduces more tension. Now you know that Harry is the world’s best chance of defeating Voldemort, but you don’t know that he’ll succeed. As the reader, you feel the pressure Harry feels as he struggles to find a way to defeat Voldemort. It’s an unimaginable amount of pressure.

This works even better because the prophecy is not his sole motivation. At this point, he’s suffered so much because of Voldemort, and he’s taken it upon himself to defeat Voldemort regardless of the prophecy. And that’s the beauty of a well-done Chosen One story. The hero is not doing things solely because prophecy says they should. The prophecy is just one piece of what motivates them.

 

Similarly, you can look at The Wheel of Time for a Chosen One story done very well. In this case, Robert Jordan accomplishes it through the creation of a deep and complex world and throwing a great deal of ambiguity into the prophecy and the outcome of the final battle. Even if you think Rand will defeat the Dark One at the end, you don’t know how it’s going to happen, or if Rand will survive the battle.

Then there are all the other characters. These prophecies say nothing about what they’re supposed to do. By having a cast of so many characters you care about, it takes a lot of focus away from the direct Chosen One/prophecy narrative. It’s a story of a prophecy, but it’s also a story of all these other characters connected to the prophecy, some more directly than others. And that makes it very enjoyable (despite a bit of a slog through the middle portion of the series).

 

There are countless other examples, but these are two of the most prominent that come to mind. I’m not going to talk much about the Belgariad, for example, because I don’t think Eddings handled the prophecy aspect of the story quite as well. It’s a fun, light read, but I never felt any doubt about the final outcome.

What about you? What are some of your favorite Chosen One stories?

A Slight Change in Plans

I’ve decided to make a small change with my editing process and publishing schedule.

First, I’ll address the editing process. I’m currently hard at work revising The Gilded Empire, book 3 of World in Chains. I’m not sure when I’ll finish editing it, but I still think I can get it out there this spring. That may be delayed, however, because of the changes I’m making. Instead of revising just book 3, I’m also going to do some work on book 4 before, The Winds of Time, before releasing The Gilded Empire.

I don’t anticipate this taking that long. It’s mostly to refresh myself on all the craziness that happens in the fourth book before finishing up my edits of the third. This is necessary so that I deliver two books that don’t contradict one another. I did veer a bit away from my original plan in the fourth book, and I need to make sure those changes are reflected in the third.

I may end up doing something similar with the second and third books of Sunweaver. It’s one of the dangers of writing more by the seat of your pants. You can come up with some amazing twists you’d never think of while outlining, but it can make things a bit messy when it comes time to revise. That’s why I prefer writing an entire series before publishing any of it. I’m hoping I can get better at planning, though.

 

Now, on to the publishing schedule. I think it’s a better idea to publish the final two books of World in Chains before returning to the second and third books of Sunweaver. Part of this is my desire to get a finished series out there. Another part is that the worlds of World in Chains and Sunweaver are loosely connected. Anyone who’s finished The Shadowed Land and read Sunweaver might have noticed this.

The second book of Sunweaver does contain very minor spoilers for the ending of my World in Chains series. I don’t think this would result in anyone enjoying the ending of World in Chains any less, but I know some readers don’t like anything to be spoiled.

Personally, I think it can be enjoyable either way. If you read book 2 of Sunweaver, you’ll know that a certain character from World in Chains has survived the events of the series, but you won’t know how. So it’s a matter of which you’d prefer as a reader. Do you want to worry for the life of this character, or are you okay figuring out the mystery of how they end up in a completely different world?

In the end, I don’t think it’s a problem to read the series in whatever order you wish. I just thought I’d get the information out there and update everyone on why I’m changing my publishing schedule a little bit.

Based on these changes, I’d expect The Gilded Empire around April and The Winds of Time around July. After that, Fireweaver will probably come out around October and Sunlord near the beginning of 2019.

I may be able to speed up this schedule, but even these dates are tentative. There are a lot of other things on my plate between work and school and family commitments, and I can make no promises.

Thanks again for reading. If you want to be the first to know about new releases, you can sign up for my mailing list at the top right of the sidebar.