Category: Who

            This week’s blog title is from a future Asylum movie for SyFy.  It’s not in development or anything, as far as I know, but I’m pretty sure just by writing that online I’ve caused it to happen.  It’s the internet butterfly effect.

            And speaking of that geeky reference to a geeky reference…

            What that title really comes from is a note from a friend of mine, the editor at a sci-fi/ science site called Giant Freakin Robot (check it out—it’s fun and educational).  He was explaining what kind of movies and television shows the site covered.  To paraphrase, if the zombies have biochemical or viral origins, GFR will cover them, but not if they’re raised by voodoo spells or curses.

            Over the past few years, a lot of genres have really blended together.  In books and movies, it’s not uncommon to see strong action, drama, or even comedy threads mixing in with sci-fi, fantasy, or horror.  Nowadays it’s just as common for protagonists to fight the undead as it is to run from them, and in doing so writers and readers have created dozens of subgenres.

            Personally, as I’ve mentioned before, I’m a big fan of this.  I think any story that stays too much in one vein tends to get dry pretty quick.  There’s almost always some humor in every situation, even incredibly dark ones.  It’s not uncommon for men and women to have inappropriate thoughts at really inopportune times (or to act on them).  Hey, I grew up on Doctor Who, so in my mind it makes perfect sense for religion-obsessed barbarian tribes to be descended from intergalactic survey teams or for aliens to be controlling the Loch Ness Monster.

            Now, sad but true, there aren’t a lot of firm rules on mixing these things.  Every story is different, so the way mystory blends horror and comedy is going to be different from the way yourstory blends them.  Ten of us can use the same basic plot, but we’re each going to end up with our own unique story.  My characters won’t react the same way as yours, hers will make different decisions than his.

             As such it’s hard for anyone to say which amount is right or wrong without having all the context.  To use one of my frequent cooking analogies, it’s kind of like if I asked “is this too much sugar?”  It’s an impossible question to answer without knowing what I’m cooking, what are the recipe standards, what are my preferences, and what are the preferences of the people who are going to be eating it.  My own skill level in the kitchen matters, too, on whether I should be trying a fried Alaska, death by chocolate, or maybe just a bowl of Captain Crunch.

            However… all that being said…

            I think when these mixed genre stories go bad, a lot of folks tend to look at the small issues and ignore the big ones.  Something isn’t bad because it mixed androids and artificial intelligence with Arthurian legends, or because it introduced a lot of comedy into the Cthulhu mythos.  Those are just the easiest targets, so they get the criticism first. 

            What I’ve come to realize is that most bad genre stuff tends to be bad for the same three reasons.  Granted, there’s always going to be someone who tries to write a sexy mutant cockroach story (or something worse), and there will always be people who just load up on basic mistakes like spelling or flat characters or incoherent plotting. In my experience, though, most genre stuff goes wrong in three basic ways—whether my story is one pure genre or several overlapping ones.

            The firstand often biggest mistake is when authors try to make their stories too fantastic.  If I have an idea, it gets included in the story.  No matter what it is, I’ll cram it in there.  If you’ve ever watched old slasher movies, you know most of them just devolved into creative ways to kill people, and sometimes there are excess characters for no other reason but to allow for more inventive deaths.  Most of us have probably read a sci fi novel that went to great lengths to explain how the weapons, shoes, uniforms, food, transportation, education, and economics are all very different on that other world or in that not-so-distant future.  I read a book recently that had to do with… well, everything.  No, seriously.  Government conspiracies, bio-engineering, super-soldiers, angels and demons, secret identities, zombies, aliens from Neptune, extraterrestrial dragons, thrill-killers, child abuse, sadism, torture porn, regular porn, and lost civilizations in the Amazon.  All of these things were major threads and elements in one average-length novel.  Heck, I’m tempted to say it was even on the shorter side.

            The problem with writing a story like this (book or screenplay) is my audience has nothing to connect with as they’re overwhelmed with all these unfamiliar elements.  The people are different.  The setting is different.  Motivations are different.  I may have created the most amazing post-apocalyptic matriarchal feudal society run by a supercomputer (and its secret android army) that’s ever been seen, but my readers need to be able to understand those characters and that society and relate to it right now while it’s on the page in front of them.

            This is closely related to the second problem—when the writer tries to explain everything.  Bad enough that I felt the need to include the secret android army, but now I’m also going to write about how they were first developed by the Mysteridroid Corporation three hundred years ago, how they see the world, and even how they recharge in various situations.  I think most people reading this have read a story or two that suddenly deviated into exposition like that.  Edgar Rice Burroughs had an awful habit in his Mars books of having his characters stop and explain various aspects of Barsoomian technology (one midnight walk with the Princess famously spun into a discussion of how radium bullets are manufactured and used).  A few recent horror films have gone to great lengths to explain why their antagonist turned out the way he or she did, even though that mystery was part of the character’s strength.

            What this often leads to is stories that feel very exotic and detailed, but very little ever actually happens in them.  Page after page of explanation can add up really fast, and no matter what my chosen format is, there’s only going to be so many pages.  Suddenly a third of my book is just… details.  And while I’m going over those details, my characters are just sitting around twiddling their thumbs, waiting for something to happen again.  This can also lead to a bit of resentment from the reader as I’m spoon-feeding them all this information.

            As it turns out, problem number three is the flipside of two.  It’s when the writer doesn’t explain anything.  I’ve gone through whole chapters of a book trying to figure out which character was Kristo.  Mystery Science Theater 3000 once had a running gag about a mystical object (or maybe it was a person…) called “the Sampo.”  We’ve all seen stories where people ride “twyrfels” and we’re left wondering what the hell a twyrfel is (an animal? a vehicle? some kind of transporter beam?).

            There’s also the folks who hide motives and actions to create a sense of mystery.    Characters will appear, make a mysterious statement or three, and then vanish from the story.  Creepy messages will be found on walls, sidewalks, or computer screens and we never learn how they got there.  Disturbing objects are found in the cellar, but never discussed again.  Ever.

            There are two general causes behind this, in my experience.  In the first case it’s when I’ve sunk so far into my fictional world and spent so much time there that I forget the reader isn’t quite so familiar with it.  I can tell you the whole history of the twyrfel as transportation, so I forget that you don’t even know what one looks like.  In the second case, they’re trying to duplicate the tone of books like House of Leaves or shows in the vein of LOST or Person of Interest, but they don’t really understand how those stories achieved that tone.  This is especially frustrating when there’s clearly no real mystery, just a bunch of withheld information.

            So, there’s three big, common mistakes in genre fiction.  Sci-fi, horror, fantasy—we could probably give an example of each failing for each genre.  We could even make a chart.

            Or we could go over a few simple ways to avoid these issues…

            For that firstproblem up above, my story needs to have something my audience can immediately relate to in some way, and it’s best if it’s the main character.  Someone who hates their job, who wants something they can’t have, or maybe who just feels like an outsider.  Simply put, a person with a universal need or desire. 

            I’ve mentioned once or thrice that believable characters make for believable stories, and that’s especially true here in the genres.  Seriously, pick a popular genre story and I’ll bet the main character has a very humble, relatable origin.  Dan Torrance is a nursing home orderly before he’s forced to confront the True Knot.  Katniss Everdeen is just trying to put food on the table when she’s forced to fight for her life in an arena.  John Anderson (a.k.a. Neo) was a cubicle drone who was dragged into a war between humanity and sentient machines.  Dana, Marty, Jules, and their friends were regular college students before they decided to spend their vacation at that old cabin in the woods.  Hell, even in Pacific Rim, one of the most over-the-top movies of the year, our hero Raleigh is working a construction job when we catch up to him in the present, still shaking off the death of his brother.

            I think there’s two ways to deal with the second problem, too much information.  One is a concept I’ve talked about here in the past—the ignorant stranger.  If things are going to be explained, I should have an actual, in-story reason for that explanation.  Yakko may know all about the secret android army, but Dot doesn’t.  This gives him a valid reason to talk about the Mysteridroid Corporation for a page and a half.  I just need to be sure this really is an ignorant stranger situation and I’m not falling back on the dreaded “as you know…” crutch.

            But is it necessary to the story, or is it just there to help push things deeper into my chosen genre?  It’s cool that my hero has an energy sidearm that uses ultrasonic beams focused through a blue quartz crystal to set up a harmonic vibration in the target’s cells which causes extreme pain and eventual molecular disruption, all powered by a cold-fusion microbattery… but in the long run is this any different than just saying he has a blaster?  Or a pistol?  I may have the most inventive take on teleportation ever, but if there’s no point to teleportation technology in my story except to show off this idea… why bother?  If the plot flows along fine without it, why take up space on the page with it?

            The thirdproblem, not explaining anything, is a little tougher.  On one level, it’s just a matter of skill and practice.  I need to be a good enough writer to know how my plot’s shaping up and to empathize with my audience. 

            A friend of mine gave me a great rule of thumb once—my main character should mirror my audience.  If my main character’s angry about something, the reader should be angry about it.  If my protagonist is puzzled, it means the audience should be puzzled. And if my hero is annoyed because he still doesn’t know what’s going on… well, that’s probably a sign I should have a reveal or two in the immediate future.

            The other way to deal with that third problem is to be sure my story actually has a real mystery, not just the sense of one.  Tying in to what I just mentioned, nothing will aggravate my readers more than to stumble through a story alongside my hero and then discover I’m not revealing a single thread of my mystery.  Or, worse yet, they might realize there isn’t a mystery at all—I was just stringing them along with some nonsense clues.  I need to know what the secret is going to be and work backwards, making sure my characters are smart enough to uncover it or honestly motivated to hide it, depending on which side of the mystery they’re on.

            Are these three the only problems that might crop up in my genre writing?  Not by a long shot.  But these are the ones I see cropping up again and again, so they’re worth looking at and considering.  And fixing.

            Next time, the last post before Christmas, I’d like to share a little holiday conversation I had with the writer-director of Iron Man 3, back when he was just the guy who did Kiss Kiss Bang Bang,

            Until then, go write.

            Pop culture reference, long overdue.  Hopefully you get it.  If not… you’re missing out.

            If you’ve followed this collection of ramblings for a while, you know that I worked in the film industry for a number of years before I stepped away to start writing about it.  In that time I worked on a lot of television, but also did some low budget movies.  And as time went on, something became very clear to me, and once I realized this it changed my attitude a lot.  And I came to realize you could always spot inexperienced (or plain ignorant) people on set by this lack of clarity.

            Y’see, every member of the crew—for at least for one moment every day—is the most important person on set.  Not just the actors and the director and the assistant directors—everyone.  The makeup artists, the dolly grip, the on-set dresser, the clapper-loader, the assistant prop master, and even the production assistants.  At some point during a given day, they will be the most important person on set for one reason or another.

            What’s the proof of this, you ask?

            Well, the film industry is focused on money.  For all the stories you hear about Hollywood wasting money on things, the truth is most producers squeeze every penny they can out of a film shoot.  If someone doesn’t need to be on set—and drawing a paycheck—they just wouldn’t be there.  Their job would’ve been eliminated or rolled into someone else’s.  Or sometimes just handed off to a production assistant, or even an intern.  It’s a regular thing on film sets to have temporary crew members who work a day or two, then vanish until they’re needed again. 

            If they don’t need to be there… they’re not there.

            Now, I gave you that little insight so I could tell you this story.

            Back in the early ‘90s the X-Men were taking off and mutant characters were the flavor of the decade at Marvel.  Every new character was a mutant.  Any old character who’d never had a specific origin became a mutant.  Needless to say, most of these new creations were tissue-thin with nothing interesting about them except their random power or ability.

            One of those characters was a guy named Guido.  He was a very over-muscled, bespectacled guy with super-strength who’d originally been created as a bodyguard (mutant, of course) for another character (mutant, of course).  Guido ended up on the new, government-sponsored X-Force team (in the same-titled comic written by Peter David) and he was there when the team was introduced at a press conference.

            Problem was, Guido never picked a code-name.  Their NSA liaison couldn’t exactly introduce Havok, Polaris, Quicksilver, Wolfsbane, Multiple Man, and… Guido.  Confusion ensued for a moment, during which Guido wandered out on stage in his uniform, seven feet tall and about eight feet wide.  And one of the reporters at the press conference said..

            “Wow!  He must be the strong guy.  Every group’s got a strong guy, it must be him.”

            To which Guido grinned and proudly announced, “Yes, that’s me.  I’m Strong Guy!”

            Much giggling ensued.  For about two years.

            Anyway, there’s a keen little observation there, and it’s why I used this comic book as my example.  Almost every superhero team doeshave a strong guy because, at some point or another, every team needs a strong guy.  X-Force needed Guido.  The Avengers needed the Hulk.  The crew of Serenity needed Jane.  SG-1 needed Tylk.  You can trace this all the way back to Grimms’ Fairy Tales, when a wandering man would gather a group of friends who were fast, keen-eyed, sharp-hearing… or extremely strong.

            And, much like the film crews, these groups have a strong guy because at some point they’re going  to need a strong guy.  The whole point of having someone like the Hulk on your team is that eventually there’s going to be some kind of giant space war-snake that needs to be taken out with one punch.  If I wasn’t going to have going to have a key moment like that, I wouldn’t bother to include a strong guy.  

            This doesn’t just hold for the strong guy, of course.  It holds for all the characters.  If I’m going to have a super-smart, deductive character in my story, there needs to be an intellectual problem for him or her to solve.  If I’m going to write in the greatest sniper in the world, at some point something’s going to need to get shot with pinpoint accuracy. 

            Is this all starting to make sense now?

            Simply put, characters need a reason to be in my story.  Sure, there’s always going to be those nameless folks there to bulk up the mob, fill in the ranks, or just serve as cannon fodder. Thing is, though, I shouldn’t be putting a lot of effort into someone who isn’t actually going to be doing anything.  All my characters should be propelling the plot and/or story forward.  If they’re just standing around not affecting anything… why am do I have them there?

            If Yakko’s just standing around not taking part in anything, odds are he’s going to get in the way.  We’ve all dealt with people like that, right?  The ones who just stop moving in the middle of a walkway or stand in front of a door.  They’re just hindering everyone else from getting things done, and the common response to them is anger or frustration.

            I’ve mentioned a bad habit before, the tendency to name every single character in a story or screenplay.  That idea has a lot of ties with this one.  Naming someone is a clue that this person is going to be important one way or another and that the reader might want to keep track of them.  So when I’m giving names to the waitress, the security guard, the cab driver, the homeless guy in the alley, and the woman jogging by the diner… well, it’s going to cause chaos in the reader’s head because they’re going to assume all these people are important somehow.  It’s the character equivalent of Chekhov’s phaser on the mantle.

           Then it’s going to cause frustration because none of them are doing anything.  They’re just standing around (or sitting, or jogging by outside), getting in the way of the story.  They’re wasting time and space that could be spent on the plot or on developing the characters who are actually doing something. And my readers are going to resent them for that.  And resent me.

            One last example.  The title one, in fact.

            When Russell Davies relaunched Doctor Who for the 21st Century, fans were almost instantly united on one point.  Mickey Smith was the most useless recurring character ever.  He was introduced as the on-again-off-again (mostly off) boyfriend of Rose, the Doctor’s companion, and for a year and a half that’s all he was.  He showed up, moped, grumbled, and then got left behind again as Rose and the Doctor took off for new adventures.  He had no personality and no real purpose.

            But in the second season, something happened.  Mickey realized he had no purpose.  He decided to stop standing around and to become part of the story.  In fact, after a few episodes Mickey even decided he needed to have his own story, one that didn’t involve Rose and the Doctor.  The next time we saw him, Mickey had become a confident, dimension-hopping resistance fighter.  And at that point, we couldn’t wait until the next time we saw him.
            Mickey went from annoyance to cool, just like that.  He was so cool that he turned down an offer from Torchwood and became a freelance alien hunter.  Hell, in the end Mickey hooked up with one of the Doctor’s other companions, Martha Jones, and we all knew she was way cooler that Rose.

            No, come on.  Admit it.  Martha was cooler than Rose.

            Anyway…

            Y’see, Timmy, there needs to be a reason for a character to be in my story.  At some point, just for a moment, they need to be the most important person in the story, the one who’s making things happen.  If they don’t do that—if they don’t advance things somehow—they shouldn’t be there.

            Next time… well, I’m taking Halloween off, so next time I’ll get to the scary stuff a little early.

            Until then, go write.

            The first chapter is titled “Zefram Cochrane.”

            Geek reference.

            Anyway…

            Well, for a couple months now I’ve promised that I’d blather on about structure.  I’ve actually got a bit of time now, so let’s do it.  I’ll warn you all right up front, this is probably going to be spread over two or three posts because it’s a big topic.  I also may be using terms a bit loosely and in ways your MFA professor may not approve of.  But I’ll do my best to make it easy to understand, despite that.

            When we’re talking about structure in stories, it really means the same thing it does when we’re talking about architecture or biochemistry or auto engineering.  It’s the underlying framework that helps us figure out how things go together.  Different structures work for different projects, so just because something worked when we were building One World Trade Center doesn’t mean we should use it when we’re building a house.  Or a motorcycle.

            Now, there are three types of structure in stories, and they all interact and work with each other.  Just like a house or a skyscraper, if two elements are strong and one is weak, a story won’t be able to support itself. So it’s important to have a good grasp of all three and understand how they work.

            First up, the one we’re going to deal with this week, is linear structure.  Simply put, the linear structure of a story is the chronological timeline the characters experience.  There’s a Russian literary term for this called fabula. I’ll prattle on more about this in just a bit.

            Next isnarrative structure.  This is the manner and order my story is told in.  Put another way, it’s the way my audience experiences the story.  A flashback is part of the narrative structure, as are prologues, epilogues, and “ten years later…”  Again, if you studied (or over-studied) this sort of stuff in college, you professor may have used the term syuzhet.  I’ll talk more about this one next week.

            Last but not least, there’s dramatic structure.  This is the way linear and narrative structures work together to form a coherent, enjoyable story.  Dramatic structure is why tension builds, why mysteries intrigue us, and why twists and reveals surprise us.  I’ll talk a little more about this on the 26th, if all goes well.

            For now, though… linear structure.

            As I mentioned a few moments ago, linear structure is the order your characters experience the story in.   Another term you may have heard for this is continuity, or maybe cause and effect.  Day comes before night, which leads to another day.  People start young and then get old (Benjamin Button and Doctor Who excepted).  Turning a key in the ignition starts my car.  Or, sometimes, sets off a bomb.

            Now… check out this list

            These are five random events from a life.  Now, despite the fact that I started the list with Yakko’s death, we all inherently understand this is not the first event in his life.  In fact, I’m betting most of you reading this can put that list in linear order in just a few seconds.  That’s because linear order is the most natural structure for all of us—it’s the one we experience all the time, every day.

            This is also why linear structure is so important.  Most of us are experts on it.  We’ll notice when effect comes before cause, even if we’re getting them out of order like I just gave them to you.  A good way to think of linear structure, as I mentioned above, is a timeline.  When you see detectives breaking down the clues of a crime, them may discover them out of order, but it doesn’t change the order they actually happened in.  If I’m writing a story—even if I’m telling the story in a non-linear fashion—there still needs to be a linear structure. 

            A good way to test the linear structure of my story (a method I’ve mentioned before) is to pull everything apart and then arrange all the flashbacks, flash-forwards, recollections, frames, and so on in chronological order.  They should still make logical sense like this, even if they’ve lost some of their dramatic weight this way (again, more on this later).  If my story elements don’t work like this (if cause doesn’t come before effect, or if the same thing is happening multiple times), I’ve done something wrong.

             Which brings us to time travel.

            Time travel stories depend a lot on linear structure.  If I don’t have a clear then and now, before and after, then time travel means nothing.  I need to be able to see that linear structure so I can see how my traveler’s timeline moves back and forth along the world’s.

            Check out this little diagram.  Here’s a pair of timelines featuring two characters from Doctor Who—the Doctor himself and his friend, Jack Harkness.  There’s kind of a big spoiler in here (or not, depending on which fan theories you subscribe to) which I’ll try to avoid, but if it makes things too confusing just say so.

            Jack’s life is pretty straightforward, for our purposes here.  A is when young Jack first meets the Ninth Doctor and decides to travel with him for a while.  B is when he later encounters the Tenth Doctor, and C is when they briefly meet again to stop the Daleks.  They meet again (D) much, much later in Jack’s life.  And E is when Jack finally dies at the ripe old age of about five billion or so (no, seriously).  All in all, this personal timeline isn’t much different than the one I showed for Yakko up above.

            Now… look at the Doctor’s timeline.  This the linear structure of the show because we (the audience) are following the Doctor around.  He travels in time a lot, so he actually meets Jack in kind of an odd order.  But it’s still a logical order for the Doctor—he’s still living on his own timeline A-B-C-D-E, just like Jack.  A and B are the Ninth Doctor, C through E are the Tenth.

            In fact, this linear order creates a big twist for the Doctor (and the viewers, since we’re following him).  He doesn’t realize the person he first meets at D is the same person he later meets at A (as I mentioned, a lot of time passes for Jack).  But this isn’t a twist for Jack because he’s following his own linear story.  That’s why he can address the (somewhat confused) Doctor as “my old friend.” 

            Make sense?

            Y’see, Timmy, no matter what order I tell things in, the characters are experiencing the story in linear order.  If halfway through my book one of my character flashes back to what happened a week ago, this isn’t new information for him or her—it happened a week ago.  So all of their actions and reactions up until the flashback should take that into account.

            It sounds pretty straightforward and it really is.  Linear structure is going to be the easiest of the three forms I blab about over the next few weeks because overall it’s logical and objective.  But, alas, people still mess it up all the time.  And the mistakes are usually because of narrative structure.

            But we’ll talk about that next week.

            Until then, go write.

            I don’t have cable, as I’ve mentioned here and a few other places.  When everything went digital it was a big thing for my lovely lady and I because we suddenly had about two dozen more channels and access to a lot more programming.  Granted, this is exactly why we didn’t want cable, but… well, I’ve become a big fan of Svengoolie.

            One of our channels shows lots of old movies from the ‘30s and ‘40s, and I happened to catch the opening of a little film called Chain Gang.  It’s from 1950, written by the very prolific Howard Green.  That date’s important because it’s the height of the Hays Code, a very restrictive set of guidelines that prohibited showing—or even discussing—a number of things on film.  Sex, violence, language, pretty much anything that could be considered immoral by somebody.  All the stuff  Family Guytakes for granted today.  Because of this, screenwriters of this era had to either write the blandest material possible or become masters of subtext.

            Early in Chain Gang, two reporters—a man and a woman—are having lunch at a burger shack across from the courthouse.  Since they’re from rival papers, they’re not actually talking to one another, they just keep asking rhetorical questions to the cook which are intended for each other.  And the clever subtext of the very quick and witty conversation—or set of conversations–goes something like this…

Him:  Well we can see where the trial’s going.  Let’s blow this off and go back to my place for a few hours.

Her:  I don’t think it’s so open and shut.  And besides, I’ve got a job to do.

Him:  I’ve got a job for you.

Her:  And I’d be more than willing to do it for you if I didn’t have this one already.

            Keep in mind, they weren’t saying any of this.  They were asking the cook about the time, relationships, work, and numerous other unrelated topics.  And after three or four minutes the cook asks “Look, are you two going to order or not?”

            The male reporter looks at his counterpart in a happy, slightly naughty way and says “I’ll have a burger—hold the onions.”

            The woman chuckles, shakes her head, and says, “Make that two burgers, Joe—and you can put onions on them.”

            Any question who won that unspoken discussion?

            Subtext is the art of the conversation beneath the one your characters are having out loud.  It’s the flipside of on-the-nose dialogue.  That hidden meaning doesn’t have to be miles beneath the spoken one.  It also doesn’t have to be rich and elaborate and layered with exquisite meaning.  But in good dialogue, it’s almost always there.

            Here’s a couple of suggestions for some methods that can bring your dialogue up to the level of an sixty year old movie…

The Reverse—One of the simplest ways to use subtext is for a character to declare the exact opposite of what they really mean.  I’ve mentioned the show Keen Eddie a few times, where the two main characters would constantly yell “I hate you!” back and forth at each other.  At one point or another, we’ve all probably been in the position of saying something along the lines of “It’s okay, I really didn’t want the promotion.  It was too much work, anyway.”

            A lot of times the reverse is just sarcasm, because sarcasm is all about subtext. Odds are all of us have made a suggestion where one of our friends has rolled their eyes and said “Oh, yeah, I’d love to do that.”  There’s a bit at the start of Roxanne (a movie loaded with subtext) where Daryl Hannah’s titular character is locked outside of her house wearing… well, nothing, and has to sneak her way to the nearby fire station for help.  When fire chief Charlie (Steve Martin) asks if she wants a coat or a blanket, she gives a nervous laugh and says “No, I really wanted to hang out nude in this bush in the freezing cold.”

The Friend— How many times have you read a story or seen a show where someone goes to the doctor and talks about the embarrassing problem “their friend” has.  Or maybe my character knows a guy who got really confused by how to install that Space Marine videogame patch, and was wondering if you could explain it in simple terms he could tell this guy next time they hang out.  This is another easy form of subtext, because I’m pushing all the emotions and thoughts onto another character altogether—even if it’s a nonexistent character.

The Blank—Kind of like the reverse method, the blank is a slightly trickier way of doing subtext.  It’s when a character demonstrates their opinion on something by offering no opinion.  Sometimes they do it by ignoring the topic, like when Yakko asks his brother Wakko’s opinion on Phoebe and Wakko instead wonders aloud how much the DJ gets paid at this club.  Other times Wakko might just dance around it, saying he doesn’t know Phoebe that well or giving a very vague non-answer (“Well, how well can you really know anyone, right?”)

The Next Step—If you’ve ever read about someone ordering a double or triple drink before they break some bad news to their tense friend, you know this method.  It’s when a character shows they’re one or two steps ahead.  I’m not thinking about now, I’m thinking about fifteen minutes from now.  Through their words or actions, the character’s saying “I know where this is going and I know how it’s going to end, even if no one else does.”  If you’re a Doctor Who fan, you might recall that in the Eleventh Doctor’s premiere episode writer Stephen Moffat packed an incredible amount of subtext into the single word, “run.”

The Metaphor—All of us have been in a conversation where what we’re talking about is not what we’re really talking about.  This method of using subtext is a huge part of flirting.  If you ever watched Seinfeld, you probably remember the time George misread a woman’s invitation to come up for coffee at the end of their date, said goodnight, and drove happily away (and then spent days on the phone leaving messages explaining that he thought she was talking about coffee, not coffee, because he would’ve loved to have coffee with her).  Eddie Izzard played with this one, too, and explained that “do you want to come up for coffee” is essentially the universal code for “sex is on!”  You’ve probably seen this method used in organized crime stories, too.  Characters in these tales will discuss “disposing of assets” and “making a definitive statement” or “preparing a welcome home party.”  I bet just by tying these statements to crime, the implied subtext has sparked a predictable set of images in all of your minds.

            And there’s five ways to create subtext.

            It’s worth mentioning that all of these methods need a bit of skill and practice, because sometimes people yell “I hate you” because… well, they hate you (sorry).  Every now and then we really do have a friend who needs help with something.  And if the Minister of Burundi asks if you want coffee, well… don’t start unbuttoning your shirt. 

            The trick with subtext is making sure it’s clear what I really mean.  So I can’t be so blunt that I’m not really hiding anything, but I also can’t be so subtle that people think my characters are just saying what they mean with no subtext at all.  It’s a fine balancing act, and it’ll take a few tries to get it right.

            Heck, I know this one guy who couldn’t pull off good subtext for years.

            Next time, I’m thinking about doing a big piece on structure again, because I got a nice bit of praise recently for the last time I did it.  But I might have something quick to say before that about crossing genre lines.

            Until then, go write.