Foreshadowing
People have been asking me to expand on that essay , though it was written (originally) to be part of a series I did on writing The Way of Kings . I never had the time, however, and that was the only one that was fleshed out, so my assistant suggested it might be a good fit for a Scalzi guest blog. However, I do worry that some of the ideas are unformed, as it was written to come after several other essays I was planning.
The short answer to your first comment is a yes, you are right. The realization I came to while working on The Way of Kings was that I was so accustomed to writing self-aware fantasy in the Mistborn books that I was searching to do the same with Kings . While anyone can enjoy Mistborn (I hope) it works best as a series for those who are familiar with (and expecting) tropes of epic fantasy to come their direction. That allows me to play with conventions and use reader expectations in a delightful way. But it also means that if you don’t know those conventions, the story loses a little of its impact.
But this is an interesting discussion as to the larger form of a novel. Is it okay, in an epic fantasy, to hang a gun on the mantle, then not fire it until book ten of the series written fifteen years later? Will people wait that long? Will it even be meaningful? My general instincts as a writer so far have been to make sure those guns are there, but to obscure them—or at least downplay them. People say this is so that I can be more surprising. But it’s partially so that those weapons are there when I need them.
It often seems to me that so much in a book is about effective foreshadowing. This deserves more attention than we give it credit. When readers have problems with characters being inconsistent, you could say this is a foreshadowing problem—the changes, or potential for change, within the character has not been presented in the right way. When you have a deus ex machina ending, you could argue that the problem was not in the ending, but the lack of proper framework at the start. Some of the biggest problems in books that are otherwise technically sound come from the lack of proper groundwork.
In the case you mentioned, however, I think I would have cut the creature. Because you said it was slowing things down. There’s an old rule of thumb in screenwriting that I’ve heard expressed in several ways, and think it works well applied to fiction. Don’t save your best storytelling for the sequel. If your best storytelling isn’t up front, you won’t get a sequel. Of course, once you’re done, you do need to come up with something as good or better for the sequel, otherwise it might not be worth writing.
For The Way of Kings , I’ve had to walk a very careful balance. I do have ten books planned, but I had to make sure I was putting my best foot forward for the first book. I had to hang guns for the later novels, but not make this story about them—otherwise readers would be unsatisfied to only get part of a story.
Question for you, then, Brent. Have you ever planned out a story to be a certain length, then ended up deciding there just wasn’t enough there to justify it? I had trouble learning this balance as a younger writer, and some of my readers know that I wrote two failed books (one called Mistborn , the other called The Final Empire ) in which neither one had enough material to form a novel. It wasn’t until I combined the ideas and story together and wrote Mistborn: The Final Empire that everything worked.
If you are viewing this on github.io, you can see that this site is open source. Please do not try to improve this page. It is auto-generated by a python script. If you have suggestions for improvements, please start a discussion on the github repo or the Discord.