What constitutes misleading the reader
I'm as novice a writer as one can get so please bear with me. I have read many times that a writer shouldn't mislead the reader otherwise the reader will lose trust in the author and lose his engagement to the story. Near the very start of my book the protagonist, passes out from blood loss and poisoning, after which he dreams of waking up fine uninjured and continuing on his way. As he progresses things start to slowly deteriorate and the dream slowly turns into a nightmare leading to him eventually waking up right where he passed out initially.Here comes my problem, I handle the transition from reality to dream like normal wihtout informing the readers of what is happening exactly, somewhat like that. (not what i'v actually written just a hasty example)
Sitting in the side of tree, he sowly closes his eyes to rest for a few minutes.
A drop of water fell to his bare hand jolting him up from his sleep. Scared he jumped up to check his suroundings........
Would this constitute tricking the reader since I dont specify that he wakes up in his dreams?
Also in the next chapter I do something similar with the introduction to another protaginst to draw a parallel between them. Even if it alright to do it the first time, would using two dream sequences in such close proximity alienate the readers?
This post was sourced from https://writers.stackexchange.com/q/29311. It is licensed under CC BY-SA 3.0.
3 answers
To add to the excellent answers already given, here's a simple way of thinking about it:
As long as the reader knows just as much about what's going on as the point of view character does, it isn't misleading.
For example, if the character is in a dream, and doesn't know they're dreaming, and the story is written from a limited point of view, there's no reason for the reader to know that the character is dreaming either. It's fine for there to be confusion about that by the reader, because the character in the story is experiencing the same thing.
On the other hand, if there are things that the characters know about that the reader doesn't, or if the reader has been led to believe something that the characters know isn't true, that would be misleading the reader. If the point of view character knows something, and it's pertinent to the current story, the reader should know that thing as well.
This post was sourced from https://writers.stackexchange.com/a/29319. It is licensed under CC BY-SA 3.0.
0 comment threads
"Don't confuse the reader" is one of the rules that exist to be broken. As usually, "when to break the rule? When you know what you're doing."
In this case, straighten it out immediately after he wakes up.
No branch, no tree, no sky. Just murk of the cavern, drip of water.
He shook his head to get rid of the last of sleep, and tried to recall the scraps of the dream, fleeting from his mind rapidly.
Deceiving the reader for no good reason is not good. But a small deceit that goes right hand in hand with protagonist's confusion, straightened out as soon as confusion vanishes, is good to improve immersion. A big deceit may make for a great plot twist, but it must be carefully engineered, both with foreshadowing and with clear reason. Definitely don't deceive the reader if the reader is the only one getting deceived - you may follow up with the same deceit the rest of characters fall for, but if there's an elephant in the room and everyone can see the elephant, don't inform the reader it's a gazelle, and then at the end laugh "ha ha, it was not a gazelle in the first place, it was always an elephant!"
This post was sourced from https://writers.stackexchange.com/a/29312. It is licensed under CC BY-SA 3.0.
0 comment threads
"Don't confuse the reader" is not a rule, but it is an action with consequences. You can decide to break a rule, but you cannot decide to exempt yourself from consequences. The consequence of confusing the reader is a confused reader. The probable consequence of a confused reader is an abandoned book.
However, there are circumstances in which the reader may enjoy being confused. In a certain type of whodunit mystery (most mysteries are not really whodunits these days) the reader is expecting to be mislead and misdirected and much of their pleasure comes in trying to see through the misdirection. If the writers does succeed in fooling them honestly, however, they will regard it as a game well played and be pleased with the experience. If the writer fools them dishonestly, however, by outright lying, for example, rather than misdirection, then they will not be pleased with the experience at all.
So, the question you have to ask yourself is, what pleasure are you preparing for the reader by being unclear about whether the protagonist's experience is waking or dream? At some point, presumably, you will have to make the reader aware that that experience was a dream. So why? What is the payoff for the reader in having that information revealed only then? How will it seem satisfactory to them, rather than a cheat, or simply outright confusion? Unless you have a very clear idea about these things, and are very confident in your ability to pull it off, confusing the reader about the protagonist's dream sequence is only likely to annoy them.
And remember, while you may have the entire arc of the story fully in your mind as you write, the reader is mostly enjoying the story they way you enjoy scenery from the window of a train. The experience is enjoyable in the moment but in not necessarily retained. Making any long back-reference in a story is likely to leave the reader scratching their head unless you have taken extraordinary measures to make that event memorable -- which is the very opposite of what you do when you obscure the dream/waking distinction. How can the reader remember the dream if they were not told it was a dream at the time?
So, while not a rule, it is good practice to be as clear and transparent as you can at all times unless you have a very good reason -- a big payoff for the reader -- for doing otherwise, and are very confident in your ability to pull off the deception.
0 comment threads
0 comment threads