I'm not sure why, but these thoughts came to me today as I was driving home. So I thought I'd share them...

The Top 10 Mistakes Potential Fantasy Writers Make

1. Not having any idea of how big a whole world is. Think for a moment about how big planet Earth is. Now, pick a hero, send him on a quest. Oh, and while you're at it, take away all but one continent, two or three countries, all languages but one, give Earth a temperate climate all over said lonely continent, with maybe some snowy regions a few days from the one of the only three cities you have left, and populate the entire animal kingdom with only horses, dogs, the odd cow and no insects. And when you get your MS back with "thanks, but no thanks" scrawled across it, take a moment to wonder what the editor meant when they said your world building lacked "depth"?
2. Trying to copy someone else's plot. This is a double-edged sword. You can be totally unoriginal and make bucket-loads, provided you can present an old idea in a new way. It takes talent, however, to do this, so be very careful before you try it.
3. Trying to be too original. There's innovation... and there's being so far off the rails nobody but you and the three friends you were sharing the bong with when you thought up your epic storyline get what you mean. Be original, by all means, but do it sensibly.
4. Forgetting epic fantasy needs more than one plot. Big epic trilogies tend to need big epic plots with multiple characters and intersecting plot lines. By all means, have a major thread running through your story, but you'd better be a cross between Shakespeare and Elmore Lenard if you think you can squeeze a three book deal out of a publisher for a story about two people alone on a raft looking for the magic talisman that's going to save the world at the end of book 3.
5. Forgetting pack/transport animals need to eat, drink, and rest occasionally. Trust me, even if you manage to get this past an editor, you will not get it past the various animal experts out there that populate the world of fantasy readers. They will know. And they will scoff at your ignorance. Loudly. To everyone they meet.
6. Assuming everything you see in the movies is true. I had a young writer assure me once that you could knock a person unconscious by simply tapping them on the head because that's what they do in movies. Let me assure you this is not the case. I know this because I once (accidentally, of course) dropped a 15lb bowling ball on my ex's head from about 6' off the ground and it didn't even crack his skull, let alone knock him out. Nor do people ride at a gallop for miles with a bullet wound in their leg, win a fist fight after being shot in the shoulder, or solve complex mathematical problems in their head, ten minutes after being brought back from the dead. Physical violence has consequences. And not just bad guys die from it.
7. Thinking that because fantasy is all you read, you'll be able to write it, too. I was asked once, at a con, what was the best thing a fantasy writer can read to help them write better fantasy. My answer was: a newspaper. Sad, but true, kiddies. How can you write a convincing imaginary world, if you have no idea what makes the one you live in work? Without exception, all the successful fantasy writers I have ever met are grounded, practical people capable of holding a conversation just as easily about politics, religion or current affairs as they are about magic. In fact, most of them prefer to discuss politics, religion or current affairs (except Trudi Canavan who prefers to talk about knitting). And not a single one of them believes in magic. But damn, they can write about it well.
8. Breaking your own rules. In it's own way, magic is a force like any other. It has certain rules and you have to stick to them, even if you're the one making up the rules. If your magic is lunar, then you'd better not have anyone working it by day. If you've said it's impossible to make pigs fly in chapter 1, you'd better not have your enemies launch an airborne pig attack in chapter 57. Make up your own magic rules, by all means, but don't go changing them half way through the story because you'd discovered flying porkers would be handy, after all.
9. Stereotyping. JK Rowling has made poo-loads of money writing what is, essentially, a story about a kid in boarding school. What separates her bank account from the wannabe's is that she found a way to make her hero different. Isn't her first chapter of Book 1 titled "The Boy who Lived"? Enid Blighton never thought that one up. Fantasy with a drop-dead gorgeous virgin princess who needs rescuing from an evil sorcerer by a handsome goat-herder (who is really a lost prince) and his amusing sidekick will get you nowhere. It's not that you can't use the plot, but you'd be better off with the amusing princess and her drop-dead gorgeous sidekick rescuing the evil sorcerer from the psychotic goat-herder... you get the idea? It's not the plot, it's the done to death characters that'll kill your epic every single time...
10. Overwriting. There is absolutely no need to ever use the words "very", "really" or "suddenly" in your narrative (you can use them sparingly in dialogue if you promise to be careful). Nor should you need to qualify your dialogue with adverbs. In fact, try not to use anything other than "said". And watch out for redundant writing. Things like 'the end result" or "hesitating for a moment". And read every single sentence with the word "that" in it. And then read it again leaving out the "that". You will be amazed.

When proofing, I always say that's not a good idea. Take that out, I say to myself.

... In fact, try not to use anything other than "said".

I've always found it very amusing how successful writers always seem to say this and yet I remember being told by teachers years ago never to use "said" and try to find different variations of it when writing. This may explain why I'm not a successful writer and refuse to subject people to it in the first place. :)

that = dat in my native tongue. used in different ways. sorry about THAT.

Jade, it took me a while to come around to the "use nothing but said" position, because like you, I was taught in school to avoid it like the plague.

I still think "asked", "suggested" (sparingly) and a few other inoffensive words like that are OK. The killers are things like "he reminisced" or "he extrapolated", "he ventured", "he digressed"... Oh the list goes on... and some of them are truly woeful.

High school English teachers have a lot to answer for...LOL

Occasionally I'll receive an email from a reader who berates me for having bad real-life things happen in my books, because she (always a she, for some reason) only reads fantasy as an escape from the real world.

It could be worse. I could substitute bad real-life things for descriptions of knitting techniques.

That'd be a purler.

Hi Jennifer

Now that I've seen your comment, I am more in agreement with you. But when I read your blog post a couple of days ago, I was going to leave a comment about "said" controversy disagreeing with you. I just lost track of it when I got busy doing something else.

I just read a Robert B. Parker book and discovered that he uses nothing but "said" in his writing. I didn't even realize it in the first book of his I read, but when I read a couple of passages from his new book out loud to my wife, it was *really* annoying. After that, I couldn't read the book without that tendency irritating the heck out of me.

I do agree with you that too many authors bend over backwards too much to avoid using "said," and that gets annoying as well. But using nothing but "said" gets on my nerves too.

After thinking about it, I wonder if the reason it annoys me is because of Parker's writing style, which is very dialogue-driven. I may not notice it as much if there are actually paragraphs of description among the dialogue sentences. I don't know. I'll have to keep an eye out. This is probably why, if you don't use anything but that word, I probably haven't noticed. :-)

Dave

The best written dialogue has no descriptors at all, because it's so seamlessly integrated into scene it's not needed.

One day, I'll figure out how to do that all the time:)