Chapter one (part 1): Overused Plots and Clichés in General
As I said in my introduction, I have read over 600 stories that were submitted to a publishing company I was once a part of. When you add those as well as books from published authors that I've read, you can imagine I have gained an understanding of what I see over and over.
I should start by talking about how our rating system worked. We didn’t have time to read through an entire book if we didn’t think it’d make it. On one occasion, I rejected a story after reading the first page and a half. It seems brutal, but I’ll explain the reason one may be rejected in a snap in a later post.
There were a few things a story could have that would give it bad marks. Getting these marks didn’t mean it’d necessarily be rejected, but it shot down the odds like a tumbling boulder on a mountainside.
1. Prologue that could not be absorbed into a different section of the story.
Prologues are a tough subject. Publishing companies do not like them. I don’t even like them. You need to be some writer to get away with a prologue. Such as, Brandon Sanderson.
What reason do we have to dislike them? That has a lot to do with the fact that I can’t remember a single prologue that was at all good or needed in those 600 books. Whether the prologue was something from the past or a jump in the future, it just seemed like a waste of space.
There was one occasion where a prologue I read wasn’t bad, but the author didn’t realize the opportunity he’d have if he had decided to slip subtle hints of the past in the present of his story. It’d add a sense of thrill, mystery and excitement. After reading the prologue, the rest of the story was dull and underwhelming. We asked him if he’d be willing to forgo the prologue and leave those hints. Sprinkle it throughout his story instead. (We sometimes gave writers a second chance after revision.) He refused. He wasn’t published through us. (After researching, it seems it still isn’t published, but I’m unsure.)
By far the worst prologue I have ever read was from this female author. It began with a girl main character hearing a knock on her front door during the night. She opened it and beyond the entrance was a beast that attacked her. And then, it jumped into chapter one. The first issue, she had that underwhelming feel as the last guy. The second issue? It was nighttime during the first chapter. The MC was writing at her desk, got ready for bed and then it hopped to her being attacked. The prologue she wrote showed the future of the FIRST chapter.
There are a few more problems that we run into with prologues. Overall though, ask yourself if it is a must. Would it be better if the story told the prologue? Would it be better to show it through emotions of other characters? Etc..
2. Info dumps. In the corners, in the crannies, at the beginning, anywhere.
If there is one thing we disliked more than prologues, it was info dumps. Mostly because majority of prologues were only info dumps.
What is an info dump?
Just like it sounds. You dump a load of information to your readers. Almost any reader will close a book out of sheer boredom when it comes to info dumps. That doesn’t mean you can’t have a paragraph of information, but you shouldn’t have an entire page.
Everything I mention always has exceptions. I am a symbolic writer. When I take the time to describe something or an event, it is likely because there is a message in it that needs to be deciphered. Edgar Allan Poe often does this as well. There is a difference between purpose and wanting to shove information at a reader.
Well, how do you defeat the dreaded info dumps? You need to divulge information to your reader somehow. You must tell them about a certain war. They gotta know about the sub-character's past, right? RIGHT?
WRONG, sort of… This falls into the category of, "show don’t tell". If there are two characters that have a rocky past, don’t tell the reader that information. Show the discomfort they have around each other. Show them buttheads. Show them scheming to bring the other down until the past surfaces.
There are far superior ways to teach the reader information from your book without it becoming monotonous and mundane.
3. The mirror scene.
You want to describe how a character looks like? Well, why not have them look at themselves in the mirror and describe their appearance to the reader? Don't do that. Frankly, we hate almost every appearance description. We don't want a jotted down list of all their outward appearances and emotions.
Eyes - Green
Hair - Chestnut brown
Smile - enchanting
Height - 5'5
Skin - Fair
Clothes - Pink skirt with a loose white top
Personality - Cute with a side of boring
Characters aren't grocery lists. It is rare to take considerable note of someone you just met. (Character sheets are NOT the same thing. This is for writing in general.) The best way to describe a character is by using interactions of nature and man/woman to mold them.
Examples:
The hem of her white dress danced with the wind as she stared out into the open sea.
He couldn't help but grace the back of his hand against her fair skin. Her breathing was harsh and scratchy. Even her brown hair appeared to dull in color.
(Or a more body build description.)
When the man heard the news, a buzz flared between his ears as his brow furrowed. He clenched his teeth and poured into a sprint. Each footfall was quick, direct and his strides were long.
From those descriptions we know a character is wearing a white dress, another is sick with brown hair and the last man is athletic with a possible anger problem.
4. The Star Wars, Lord of the Rings, anime syndrome.
I'll be explaining this more in the cliches during part 2. But I'll touch up on it now. We don't want knock off Star Wars, LotR or anime. However, we do welcome twists on such things. I could spend an entire chapter on anime, and I likely will. I am a fan of anime, I've loved the stuff since I was nine, but I am as well an animator who would never animate anime for specific reasons.
So, let's focus on Star Wars and LotR. Should I even try to count how many stories were just rip offs of the originals? No, I shouldn't. That would be impossible. There were far too many and it became ridiculous. We forced an immediate rejection when one author decided to even name their world, Middle Terra. Like I said, when I open up with part 2, I'll better explain how you can knock the syndrome out of the ballpark while still keeping all your favorite attributes of either one.
For now, consider how much your story may resemble the two.
That's it for part 1.
LazyDaze (I will tag you for part 2 as well.)
As I said in my introduction, I have read over 600 stories that were submitted to a publishing company I was once a part of. When you add those as well as books from published authors that I've read, you can imagine I have gained an understanding of what I see over and over.
I should start by talking about how our rating system worked. We didn’t have time to read through an entire book if we didn’t think it’d make it. On one occasion, I rejected a story after reading the first page and a half. It seems brutal, but I’ll explain the reason one may be rejected in a snap in a later post.
There were a few things a story could have that would give it bad marks. Getting these marks didn’t mean it’d necessarily be rejected, but it shot down the odds like a tumbling boulder on a mountainside.
1. Prologue that could not be absorbed into a different section of the story.
Prologues are a tough subject. Publishing companies do not like them. I don’t even like them. You need to be some writer to get away with a prologue. Such as, Brandon Sanderson.
What reason do we have to dislike them? That has a lot to do with the fact that I can’t remember a single prologue that was at all good or needed in those 600 books. Whether the prologue was something from the past or a jump in the future, it just seemed like a waste of space.
There was one occasion where a prologue I read wasn’t bad, but the author didn’t realize the opportunity he’d have if he had decided to slip subtle hints of the past in the present of his story. It’d add a sense of thrill, mystery and excitement. After reading the prologue, the rest of the story was dull and underwhelming. We asked him if he’d be willing to forgo the prologue and leave those hints. Sprinkle it throughout his story instead. (We sometimes gave writers a second chance after revision.) He refused. He wasn’t published through us. (After researching, it seems it still isn’t published, but I’m unsure.)
By far the worst prologue I have ever read was from this female author. It began with a girl main character hearing a knock on her front door during the night. She opened it and beyond the entrance was a beast that attacked her. And then, it jumped into chapter one. The first issue, she had that underwhelming feel as the last guy. The second issue? It was nighttime during the first chapter. The MC was writing at her desk, got ready for bed and then it hopped to her being attacked. The prologue she wrote showed the future of the FIRST chapter.
There are a few more problems that we run into with prologues. Overall though, ask yourself if it is a must. Would it be better if the story told the prologue? Would it be better to show it through emotions of other characters? Etc..
2. Info dumps. In the corners, in the crannies, at the beginning, anywhere.
If there is one thing we disliked more than prologues, it was info dumps. Mostly because majority of prologues were only info dumps.
What is an info dump?
Just like it sounds. You dump a load of information to your readers. Almost any reader will close a book out of sheer boredom when it comes to info dumps. That doesn’t mean you can’t have a paragraph of information, but you shouldn’t have an entire page.
Everything I mention always has exceptions. I am a symbolic writer. When I take the time to describe something or an event, it is likely because there is a message in it that needs to be deciphered. Edgar Allan Poe often does this as well. There is a difference between purpose and wanting to shove information at a reader.
Well, how do you defeat the dreaded info dumps? You need to divulge information to your reader somehow. You must tell them about a certain war. They gotta know about the sub-character's past, right? RIGHT?
WRONG, sort of… This falls into the category of, "show don’t tell". If there are two characters that have a rocky past, don’t tell the reader that information. Show the discomfort they have around each other. Show them buttheads. Show them scheming to bring the other down until the past surfaces.
There are far superior ways to teach the reader information from your book without it becoming monotonous and mundane.
3. The mirror scene.
You want to describe how a character looks like? Well, why not have them look at themselves in the mirror and describe their appearance to the reader? Don't do that. Frankly, we hate almost every appearance description. We don't want a jotted down list of all their outward appearances and emotions.
Eyes - Green
Hair - Chestnut brown
Smile - enchanting
Height - 5'5
Skin - Fair
Clothes - Pink skirt with a loose white top
Personality - Cute with a side of boring
Characters aren't grocery lists. It is rare to take considerable note of someone you just met. (Character sheets are NOT the same thing. This is for writing in general.) The best way to describe a character is by using interactions of nature and man/woman to mold them.
Examples:
The hem of her white dress danced with the wind as she stared out into the open sea.
He couldn't help but grace the back of his hand against her fair skin. Her breathing was harsh and scratchy. Even her brown hair appeared to dull in color.
(Or a more body build description.)
When the man heard the news, a buzz flared between his ears as his brow furrowed. He clenched his teeth and poured into a sprint. Each footfall was quick, direct and his strides were long.
From those descriptions we know a character is wearing a white dress, another is sick with brown hair and the last man is athletic with a possible anger problem.
4. The Star Wars, Lord of the Rings, anime syndrome.
I'll be explaining this more in the cliches during part 2. But I'll touch up on it now. We don't want knock off Star Wars, LotR or anime. However, we do welcome twists on such things. I could spend an entire chapter on anime, and I likely will. I am a fan of anime, I've loved the stuff since I was nine, but I am as well an animator who would never animate anime for specific reasons.
So, let's focus on Star Wars and LotR. Should I even try to count how many stories were just rip offs of the originals? No, I shouldn't. That would be impossible. There were far too many and it became ridiculous. We forced an immediate rejection when one author decided to even name their world, Middle Terra. Like I said, when I open up with part 2, I'll better explain how you can knock the syndrome out of the ballpark while still keeping all your favorite attributes of either one.
For now, consider how much your story may resemble the two.
That's it for part 1.
LazyDaze (I will tag you for part 2 as well.)
Last edited: