would sound as sweet.
Let’s have a chat about prologues. In the writing community, there seems to be a divide on this topic. One faction is the prologue haters. They seem to think that prologues are evil, disgusting, vile things – an excuse for lazy authors to give an info dump in a fantasy novel, or worse, a character waking up and going about her day without anything happening! *gasp* How boring! How predictable! How unnecessary! *hiss* Bad! Bad!
Then there’s the other side of the argument, the “I don’t really give a shit but make it good” faction. I’m more of a member of this faction.
You don’t always need a prologue. In fact, most books without prologues do very well, even in the fantasy genre. Look at Harry Potter; it starts right at Chapter One with no prologue in sight. The Lord of the Rings is another good example of a fantasy book without a prologue (although we all know how much Tolkien wrote in the Appendices of that book. And one could say that The Hobbit is technically a prologue to LOTR.)
Another amazing fantasy book without a prologue is my very own The Crown and the Mage. *insert shameless plug here*
Now that that’s out of the way… Let’s look at when you should include a prologue.
If I read a book and it’s got a prologue, this is what I expect to see, as a reader and as a fellow author.
1. Your prologue should have a purpose.
This is the most important aspect of a prologue. If your character wakes up, eats breakfast, hits the gym for a quick workout, goes to work, attends a meeting, makes a presentation, has a tuna sandwich for lunch, works some more, goes home, and goes to bed, that’s boring. Yawn. In fact, if that’s your prologue, I won’t even get to the part where he spreads the butter on his toast while his morning coffee brews.
However, if your prologue sees the main character attempting a rescue mission of a kidnapped infant but then he gets captured by the enemy and needs to find some way to escape, depending on how you write it, that’s a pretty interesting prologue and I’ll stick around to read it. (by the way, that’s the prologue I’m writing for my next book) Your prologue should either relate to the main plot of the story or else have its own mini-plot.
Let’s look at another example of a well-done prologue: Sabriel by Garth Nix. The first book in the Abhorsen cycle sees a band of traveling nomads trying to assist a woman in labor. We meet Abhorsen, a strange necromancer, and we see him use his powers to save his newborn daughter. We also meet an ominous character in Kerrigor, who is later revealed to be the main villain of the book. And in addition to meeting some of the main cast of the story, we also get to see a lot about the setting of the story and the worldbuilding, like the construction of the Wall and the difference between the Old Kingdom and Ancelstierre. (and wow I can’t believe I spelled that right without looking it up first.)
I occasionally write prologues. As mentioned above, my current manuscript has a prologue. And while it’s still not perfectly polished and ready for publication, a lot of critique partners have said that it works and it’s a good prologue, so I’ll be pointing out some aspects of my prologue and why it works. I’ll also use some other various prologues I’ve read as examples.
2. Your prologue should not be an info-dump.
If you want to use your prologue to reveal worldbuilding information (for those who are unfamiliar, worldbuilding is usually specific to fantasy novels and refers to how your fantasy world works, like its political system, its currency, its educational system, etc.), that’s perfectly fine, but don’t just give us a huge info-dump as to your world’s economy, politics, and geography. A prologue needs to have some element of story to it, including conflict, character, and emotional impact. My good friend Krisna is writing a novel at the moment called Dragons of Atlantea, and it’s got a prologue. I was given the opportunity to read and critique her first three chapters, and I think her prologue works very well in this aspect. It contained a lot of worldbuilding information about the story world and how it works, but there was also a plot about a princess trapped in a tower and forbidden magic and people getting turned into dragons, making it interesting to read.
3. Your prologue should not just be “Chapter One”
The purpose of a prologue is to introduce some aspect of the story or scene that does not fit in the timeline of the main story. So for example, Krisna’s prologue was set hundreds of years before her “chapter one,” in which Mer, a cripple, is living as a servant in a mansion and is trying to earn a scholarship to escape her situation and go to school. The same with my prologue, and with the prologue in Sabriel. My prologue takes place twenty-some years before the main story happens, so it doesn’t really make sense to label it as “Chapter One” because then it would just confuse the reader. And in Sabriel, the prologue happens when Sabriel is a newborn, and then we meet her again in Chapter One when she’s eighteen.
But do all prologues have to take place “before the story?” Not necessarily. Eragon by Christopher Paolini has a prologue that takes place almost instantaneously as the first chapter: Arya is captured by the shade Durza and sends the dragon egg with magic. In chapter one, Eragon is tracking some deer and finds the dragon egg in the forest. We later learn that Arya was captured by Durza the moment Eragon first held the egg. So sometimes your prologue doesn’t have to be “before the story.”
4. Keep in mind that some people skip the prologue entirely.
This is an optional aspect of a prologue. Sometimes you’ll run into people who skip your prologue entirely, simply because “it’s a prologue and I hate those.” I think of a prologue as the equivalent of having an appetizer or an alcoholic beverage before a meal. Some people enjoy snacking on chips and salsa at a Mexican restaurant while waiting for their food. Some people don’t like chips and salsa. Both are justified in their reasoning. For the people who don’t enjoy chips and salsa, they can still enjoy the meal without having them. It isn’t as if the rest of the meal hinges on the person eating the chips and salsa beforehand. And the people who do have the chips and salsa before the meal can also enjoy the meal itself in a different way than can the no-chip people.
It’s the same with prologues, in my opinion. When I write a prologue, it’s something that’s its own mini-story and that definitely deserves its place in the book, but will also please the no-chips people, aka the prologue haters. The people who don’t read the prologue can still enjoy the story just as much as someone who does. The type of enjoyment is different – people who do read the prologue will experience the story differently than those who don’t. Yet neither will feel like the story is lacking in any way.
Again, this is just an optional part of having a prologue. If you want to write a prologue that introduces crucial information to the plot that can’t be skipped, you’re absolutely within your right to do so. It’s not your job to please the prologue-haters. (Come to think of it, I might be too nice sometimes…)
I sometimes see beginning authors ask “Do I need a prologue in my story?”
No, not in the least. If you don’t think your story needs a prologue, you shouldn’t write one. If you think you might want to write a prologue, feel free to try it. These are just some tips I tend to give to beginning authors who ask this question. I definitely do not agree with the prologue haters who think that all prologues are evil and a mere device for lazy authors, but neither do I advocate for them in every situation. If your story calls for a prologue, then write one. If it doesn’t need a prologue, don’t write one. It will depend on your story’s needs and your needs as an author.
That’s all for today. What do you think is the most important aspect for a prologue to have? Comment below! 乙女