Fantasy research – creepy in fantasy (Coraline)

One of the lovely things about writing is that often your research involves reading other stories. Not to lift work, of course, but to understand tricks of the trade, analyze what worked, or didn’t, and try to figure out why. One of the key things War of Shadow needs, in certain parts, is an element of creepy. I want the setting to feel slightly uncomfortable as the characters move through the landscape. So, in an effort to understand how other writers do it, and discover tricks to how it might be adapted for my ow purposes, I started by picking up Coraline by Neil Gaiman. There are other books in the queue, but that was the first. It’s a book I should have picked up a long time ago. I did see the movie just after it came out, and thought it was very good and pretty darn creepy.

First off, my opinion of the book – Inside the first couple chapters, I felt as though it was more of a sketch, and left me wanting. However, the story really picks up the second time Coraline goes into the world in the other flat. All throughout, the imagery is very good, and the writing excellent. As I went through, I’m not sure I felt particularly unsettled, or creeped-out. The last few chapters were just suspenseful enough, not overdone, and I was compelled to go on to the next page.

From the perspective of a writer, if I take only one thing away from the book, is the suspense at the end. That said, I did read it for the creepy, and I have to say that I don’t know what I was expecting to feel while reading the book. Perhaps that I’d lose a bit of sleep thinking about a disembodied hand because I’m waiting for it to scrabble out from under the bed? Maybe find my self thinking twice about opening a locked door in case I might find button-eyed mockeries of a loved one? No, I didn’t feel any of that. But was that the point? Probably not.

In verbally ruminating upon the story, my wife reminded me that Coraline was meant to be for younger readers. From that perspective, had I read this when I was a child, it probably would have kept me from sleeping. However, as an adult not so much. The reason, I think, I didn’t find it as creepy as I may have been expecting is because Coraline does not, except for one place, seem to be in any imminent danger of certain death from the Beldam. It sort of feels like this is a possible outcome, at some distant point in the future, not an immediate threat. I sort of wonder if that distinction doesn’t tend to temper the ‘creepy’ for me. I also wonder if this was not by design, to make the story a little less horrifying for young readers.

After having read this book, did I learn anything about writing creepy?

I think so. First off, you need to rely on the principle of “things aren’t what they seem.” I can see this being difficult for the writer to pull off in a fantasy novel because the reader already isn’t familiar with the world. I think it’s one of the reasons I’m having some trouble with it. There are so many things being introduced, this concept can be a bit of a challenge to really highlight. How does the reader know that we’re dealing with something that’s not quite right? In urban fantasy, where the world is generally the same as the one we’re sitting in, you can rely on that familiarity to set the bar for ‘normal.’ In this case, unexpected things are going to seem unusual to the reader, and the character only needs to react in a manner generally consistent with things not being as they should be. I think the same trick can be used when you have an unusual world. The reader will have to rely on cues from the characters. Elements of the world that are mundane to the characters should read that way. When things are supposed to be creepy, they should be contrasted with things that the character takes as normal, as well as what the reader would consider normal.

Another thing that I was reminded of while reading this book is the choice of words used for imagery. In one particular example from Coraline, Neil Gaiman uses the look of a spider to describe the color of the other mother’s skin. What he did there was use something generally regarded as uncomfortable (I mean who likes spiders, really?) in the description when other descriptions would suffice. Of course, this is just how it’s done, although it’s also easy to lose sight of when you’re trying to manage some 100K words of text. Think about any particular story that has a bit of creepy to it. Inevitably there are sentences about slithering snakes and the jerky motions of spiders and the like. However, I also think that this can be overdone.

For now, I’m not quite ready to begin going back and polishing in this particular flavor, I’d like to finish a few other books for research, and I’d rather focus my attention on finishing up the first drafts of the last 2 – 3 chapters of War of Shadows (I really need to start working out a name that I plan to use, or this is going to stick.) and also finish fixing up the bits that need help.

Thinking about the act of killing

10523887934_57fbc8091e

Before I start this blog, I want you to know it may be disturbing, and might even be slightly offensive. So, if you’re not familiar with hunting or the farming life, you might skip this one.

I had to kill a duck last week. Perhaps you might be asking why? Well, there is a point when enough of an animal’s insides are on the outside that death is inevitable, and though not incapacitated, or in a state of irreparable pain, the end is in sight -and will likely be a drawn-out and painful ordeal. Furthermore, I’m a pragmatic person. We had originally gotten the duck to eat, and even though we had changed our mind, once it became apparent the duck was facing a deadly affliction, we concluded the best thing to do was end the situation soon, and salvage some of the meat.

Have you ever had to kill anything? Even for something you intend to eat, unless you do it professionally, it’s not an easy thing to do. I’m not even talking about killing a human, I’ve never been in such a position and I hope that this is never a topic I even become remotely knowledgeable about. There is no nice way of ending an animal’s life. With skill and a sure hand, you can do it reasonably easily -make it as quick and complete as possible, but the act is necessarily violent and final. I find that when I’m hunting, the identification and trigger pulling is compressed into just a handful of seconds. It turns to instinct. There is no thinking about it, just doing. If your shot placement is good, and hopefully it is, the animal succumbs quickly. A dead rabbit or fish or grouse is easy to deal with. At that point you’re handling something more recognizable as food than as an animal.

The story gets more complicated when it’s an animal you know. Say a duck or chicken you have raised from a chick for example. You’re not simply catching sight of an animal and shooting it. No, you are picking it up, and deliberately ending it’s life with your own two hands. It is a very stressful thing to do. For me, it’s stressful because I want the end to be quick and humane. Butchering our chickens and ducks is something I do not look forward to. The act of killing them makes me feel vaguely ill. Sure it passes in the span of a few moments before it’s time to get down to business, but I still feel it. Every time. It’s not at all like the movies where you see single gunshot ending it before the person/animal hits the ground. No, it’s not like that. If you can sever just the right part of the spine, of any creature, everything seizes and it’s over. That said, most of us don’t have have such a sure hand. Most other methods result in thrashing and a struggle for survival, even though it’s over.

Now, with that in mind. Imagine being put into a position of killing another human being. I’m going to assume you’re not a psychopath who enjoys such things. Let’s, instead, assume you are in a fight, any kind of fight, where it is your life or an enemy’s life at stake. How would you feel? More precisely, how should your character feel? Unless s/he is a psychopath, s/he is going to be feeling the flight/fight response rather keenly, likely in the form of an intense adrenaline rush. Once the threat has been lifted, they are going to feel slightly shaky and vaguely ill. This is partly the after-effects of the adrenaline, but it’s still a physical response. In a long drawn-out battle, your character probably won’t have time to stop and think about each kill. It’s the sort of thing that happens after the fact -once the air has cleared and the danger has lifted.

I think the point I’m trying to make is that very often you read about epic battles and mighty blows dealt to ugly foes, and yet you rarely see what it actually feels like when you kill something. Even for something as inconsequential as a chicken, it can be a very singular adrenaline rush. Your protagonist might be a farmer and butchering chickens isn’t much of a problem, but being so intimate with the death of another human being at close range is going to have an effect on that person. Considering that your protagonist, if following a typical fantasy arc, is probably not a well seasoned warrior, this is going to have a dramatic effect on him/her – even when they didn’t cause the death directly, and even when the death was necessary for their own survival.

So. When you have your character, perhaps a fighting noob, off a bad-guy, think about that adrenaline rush, the shaking of hands, the vaguely ill feeling. It’s not much to add to a story, but it’s authentic, and adds something to your character.


 

photo credit: crime-scene-murder-weapon.jpg via photopin (license)

Another story idea

Procrastination. Really, that’s where I’m at. I have so little left before I finish the first draft of War of Shadows, and I’m avoiding it at every turn – stupid really, but I just can’t help myself. Today, I spent most of my writing time with a new and different story idea. I don’t know where it’s going, the characters hopped into my mind, and I’m already in love with them. Someday I’m going to turn this into something, but maybe not right now. Anyhow, here it is in all its drafty glory (what do you think? Is it going somewhere or were you done before you got to the end?):


 

Thittlebod the Great

She looked at the little old man, bent over some unknown conglomeration of cogs, gears, springs, and flywheels. Thittlebod the Adventurer he was called or Thittlebod the Maker, Thittlebod the Secret Stealer, and sometimes Thittlebod the Great. Once she had even heard Thittlebod the Terrible. He wasn’t any of those things. As she stepped fully into the room, he looked up and removed his goggles, blinking at her with small eyes, watery from concentration. He ran his hand through his wispy white hair.

“My dear Bel,” he said with a toothy smile. “You’ve arrived just in the nick of time.”

Bel-atter was her proper name. She hated being called Bel, she was not one of those prim and brainless bimbos that flitted about the courts of the moneyed. No, that wasn’t her, never would be. Their story was always the same. There was no fairytale ending for them.

She let out an exasperated sigh. “You know I don’t care for the name.”

“Ah, yes, of course, my dear. You prefer Att. Might you see fit to forgive an old man in his dotage.”

Thittlebod’s eye sparkled at this. Whatever he was, he wasn’t dotty. Att knew he thought of her as a Bel, always had. She had been a princess in his home even since she was a small child.

“Oh, my dear,” Thittlebod said, embracing her tightly. “It is so good to see you. I am glad you have come down all this way.”

“I am pleased to have the excuse,” Att said, taking a step back and looking him over more closely. She was disappointed to see that age was beginning to catch up with him. “To what do I owe the honor of your invitation?”

“Your help, my dear, your help.”

Att raised her eyebrow. “What sort of adventure are we on now?”

Thittlebod waived his hand. “No, my dear, I’m too old for that now. Too old. No, I’ll show you.”

After fiddling with the mass of gears and what-not on his workbench, he turned crank, counting aloud to ten, then he dropped a brilliant blue gem into the mess, and clicked a panel into place over it. He took a few steps back.

“A dozen heartbeats, my dear,” He said.

True to his word, a dozen heartbeats later, the mass began moving. This time Att took a step back and reached for her pistol.

“No, no, my dear, he’s safe,” Thittlebod said, holding his hand out to stop her.

Att could feel her eyes growing wide. “He?”

They watched as the mass, sat up on the bench, stretched, and turned to face them, just as if it were getting out of bed. Att actually un-holstered her pistol and pointed it at the thing. As much as a mechanical thing could, it took on a look of surprise and held up it’s hands in a clear sign of fear.

“That’s not necessary, my dear, you’re frightening him,” Thittlebod said.

“What is this Thits?” Att said.

“It’s okay Rundis. She means no harm,” Thittlebod said to the thing, Then turning To Att. “Please, my dear, put that away. It’s not necessary here.”

Att complied, slowly lowering her weapon. “Please tell me what you’ve done now.”

“Rundis here is the world’s first auto-winding automaton.”

“Perhaps you mean the world’s first automaton?” Att corrected him.

“Details,” Thittlebod said vaguely.

“Why have you made it?”

Rundis stared at them with unblinking, glass eyes. Two little flaps, Att took to be eyebrows were raised in an expression reminiscent of surprise or curiosity, she couldn’t tell which.

Thittlebod frowned. “Why have I made him? Well, that’s why you’re here isn’t it?”

Att’s mouth fell open in an effort to find words to respond. These kings of enigmatic statements were one of the peculiar things about Thittlebod.

“I suppose you’ll be wondering what that is my dear?”

“It had crossed my mind.”

“Have I a role?” Rundis said in a metallic, echoing voice.

Att jumped back. “It talks.”

Thittlebod looked from Rundis to her, squinting. “Well, of course it does, my dear.”

Att took a deep breath, then another. “I need a very stiff drink Thits.”

“Of course you do, my dear,” Thittlebod said kindly.

“May I do a drink?” Rundis asked, cocking its head slightly.

“Two, actually,” Att added.