Should foreshadowing be close to the main event?
This question is a followup to my earlier question.
Continuing the dialog with my one critic, I wrote back that I believed that certain "foreshadowing" was necessary. Then I added something like, "But I take what I believe to be your main point, which was that Chapter 2 was too early for this material, when other matters were more pressing." I now believe that this foreshadowing scene should be in Chapter 10 or 11, because the main scene takes place in Chapter 12.
Is this a good way to look at things? Could it have been that the real problem was that the scene was in the wrong place, even though necessary?
This post was sourced from https://writers.stackexchange.com/q/35664. It is licensed under CC BY-SA 3.0.
3 answers
"The Wheel of Time" is an excellent use of foreshadowing. Most of his foreshadowing was done in just a sentence here and a sentence there. It was a huge series and therefore had a lot of things to foreshadow.
I think that some of the foreshadowing was a game by the author. He would deliberately give small amounts of information to the reader and see if they could guess the outcome. For example, one character "died" but many readers believed she'd come back because it was foreshadowed that she would marry another character. And eventually (it was a 13-book series with large books) she was rescued.
I agree with @Amadeus that foreshadowing should be done as early as possible.
I believe that foreshadowing aids in specific events or intentions. Again, in the Wheel of Time, one of Rand's lovers (not at the time) had a true dream of the future (this was her power) where she, along with two other young women, were standing very sad at his funeral. This foreshadowed the even of his death, and that he would have the three women who loved him. However, it did not foreshadow that Rand would love any of them back.
Please don't think I'm recommending the Wheel of Time for reading purposes. It was too long and over bloated, and Robert Jordon died three volumes before completing the series. Brandon Sanderson did well on his first two volumes but IMNSHO the last book felt like a parody of the series.
This post was sourced from https://writers.stackexchange.com/a/35669. It is licensed under CC BY-SA 3.0.
0 comment threads
I don't think it is universally true that foreshadowing should be close to the event. For example, Frodo's inability to cast the Ring into the Cracks of Doom is foreshadowed by his inability to cast it into the fireplace in Bag End, right in the beginning of the Lord of the Rings. Or, another example: the end of Jim Butcher's "Changes" is foreshadowed from chapter 4 onwards, and by the beginning of chapter 11, I no longer had any doubts. The book has 49 chapters.
However, key to the discussion is your statement that
other matters were more pressing.
You cannot foreshadow everything all at once, and the foreshadowing should be organic, sitting within what you're telling at the moment. It shouldn't stick out, it shouldn't have a large "this is foreshadowing" spotlight pointed at it. If that means you should move a scene to a different place, go ahead and do so.
Remember also your story doesn't need to be linear. You can even tell of an event in a way that suits a development of a particular idea, and then some chapters later return to the same event (by means of a character remembering it, for example), and add some more information about it, following a different idea this time, foreshadowing additional things. For example, Naomi Novik's Uprooted, chapter 6:
Unfortunately, the willingness to learn magic wasn't the same thing as being good at it. [..] After another three days of letting the Dragon set me at healing spells, all of which felt as awkward and wrong as ever, I marched down to the library the next morning with the little worn journal in my hand and put it down on the table before him as he scowled. "Why won't you teach me from this?" I demanded.
And in chapter 7 there's a return to the same incident, from a different perspective:
I hadn't seen anyone from Dvernik since the beacon night. Danka had sent the fire-heart back to Olshanka, with an escort gathered grimly from every village of the valley [..] They looked at me and saw someone out of a story, who might ride by and be stared at, but didn't belong in their lives at all. [..] That was the day I had taken Jaga's book down to the library, and demanded that the Dragon stop pretending I had any more gift for healing than I did for any other sort of spell, and let me learn the kind of magic that I could do.
The first instance follows the logical line of the MC learning magic. The second follows the logical line of the MC's relationship with the place she came from. The different focus allows to add information, and foreshadow different things, instead of cluttering all at once. In a way, it's examining two threads of the story separately, though they might be twined together, instead of allowing them to become a tangled mess where you can't follow either one.
0 comment threads
+1 Cloudchaser, I'd go further and say foreshadowing should NEVER be close to the event. But it doesn't have to be on page 1, or page 50.
As I said in my answer to your previous foreshadowing question if you have THIS MUCH foreshadowing you probably have too much of it.
Foreshadowing should be a scene or incident that the reader is likely to remember, but it must fit into the narrative where it appears so the reader does not notice it is foreshadowing.
Perhaps we have a miscommunication in terminology:
Foreshadowing is NOT just information the reader needs.
Foreshadowing is a taste of something that is to come; it is a mini-version of a scene that will happen later, often only similar to what happens later. Much as a shadow can reveal a person is present but does not reveal the full image of the person and their nature; it reveals a distorted but later recognizable shape of the person. Foreshadowing shows the reader the shape of what is to come, not precisely what is to come.
An actual quote IRL, using it correctly:
"By comparison, he said, and as the students would later read in class, a major Moscow media outlet was raided right after Vladimir Putin became president, foreshadowing the government’s control of Russian media."
Washington Post, Mar 18, 2018
I.E. a mini-version: The raid on one media outlet heralds Putin's subjugation of all media outlets; the illegal raid heralds the future illegalities of assassination, murder, blackmail and corruption and election fixing; the single dictatorial act heralds many dictatorial acts throughout Russian society.
You are not "foreshadowing" to inform the reader:
that magic is possible in a world, or
that a machine that accomplishes XYZ exists, or
that homosexuality is widely accepted in your fantasy world, or
that "Chicago" and "Los Angeles" are now the names of planets in different star systems founded after the destruction of Earth in 11238, or
that your peasants practice good hygiene for disease prevention (as IRL some early cultures did, whether they understood germ theory or not).
That stuff is just information, and as always you should avoid info-dumping. If your real problem is info-dumping, there are many tricks to avoid info-dumping and you can search our site for suggestions. Briefly,
Some information is not necessary because it has no consequences in the story or does not have any great influence on the plot or character emotions. When that crap is included it is world-builder's disease; basically showing off an invention that has no purpose but you think it's cool.
Some explanations are not necessary because the reader isn't going to question them; if your scifi Bond character has a nuclear powered belt buckle with a hidden laser that can cut through three feet of solid steel, maybe with all the other tech in your universe the reader doesn't care exactly how you fit a safe nuclear reactor in a cubic centimeter.
Some info can be conveyed in dialogue; some can be shown-not-told. I don't have to tell you Amy is homosexual if she wakes up next to her wife in the morning.
It is not "foreshadowing" to inform the reader machine X exists, even if you are doing that to avoid a Deus Ex when your hero is saved by machine X. That is still just information. The more implausible it is the more important it is to disclose it early. if it is not implausible at all, it can be used with impunity: I worked three years in a hospital and there are many machines there for which I do not know the purpose, but presume others do. They need no explanation. It will help your story if when it is time for that machine you use the authentic terminology, but it wouldn't have to be revealed early to the reader unless you are inventing it to levitate yourself out of some impossible corner you have painted yourself into.
Foreshadows cannot be frequent or they stop working. They are spice, they cannot overwhelm the reader. They must be remembered and the reader's capacity for remembering things is limited; they are not going to read your book twenty times and memorize every nuance; most readers do not read the same book twice. It works in one pass or it doesn't work at all, and that is how editors and publishers and reviewers will see it too.
Information about how the world works must necessarily be done throughout, and avoiding boring info-dumping is a difficult skill to learn. I suspect that is your real problem, a confusion of these two terms. The rules for them are similar, but they serve different purposes. Information conveyance is necessarily frequent, foreshadowing is necessarily sparse.
0 comment threads
0 comment threads