Category Archives: character

Never tell me the odds… er, backstory

I don’t think it’s controversial to say that fictional characters are most interesting when they’re doing something.

And yet, there is a school of thought that says that a character needs backstory and background, and that a character who’s already done something is more interesting.

This school is wrong. This school is teaching that the Earth is flat, that 2 + 2 = ham and that Blade Trinity was a better film than Blade 2. (For god’s sake, people, Blade 2 had Ron Perlman and Blade Trinity had Triple-fucking-H. What are you huffing?) This school needs its teaching license revoked, and then the school buildings razed to the ground.

Entirely made of awesome
Entirely made of dicks


Anyway, having talked a bit about why backstory is bad for narrative, I’d like to move on to why it’s bad for characters in general. This comes, in part, from the Continuum panel on roleplaying and storytelling that I was on last month, where I ended talking a lot about how character influences play and shapes story, and about how the actions of characters in play is what drives a game. That left me thinking afterwards about character and how to portray it, and I’m going to write about that next weekend. This post is a bridge, taking us from the negativity of last week to the positivity of next week over the broad river of moderately-negative-but-not-that-much-honest. Well, okay, it’s pretty negative, but that’s just because I like writing the word ‘fuck’.

There are two reasons why backstory is poisonous for characters. First, it’s because backstory exists outside the narrative, as I ranted about last time. Events that happen before the current narrative can’t be experienced by the reader as part of that narrative – you either summarise them, which is boring (‘That was the week I saved the President and was awarded the Medal of Honour for a fourth time, Ginger!’), or you set up a second narrative stream to play them out, which pulls the reader from the narrative they actually want to explore (‘Before we defuse the bomb, let’s have a flashback to how I graduated from bomb defusing college!’). Both of these are tell-not-show errors, because you’re not demonstrating character within the narrative, you’re writing directly at the reader and dumping the information in their heads. And that’s boring.

The second reason, which is subtler, is that backstories don’t have conflict, and conflict – the need to meet and overcome obstacles to reach goals – is what drives stories. Backstories shunt conflict offstage so that those obstacles have already been overcome (or failed, I guess, though that’s vanishingly rare) before the narrative starts. And perhaps that’s one of the main reasons why gamers love backstory so much – it’s a way of setting up interesting conflicts for your character, with none of the uncertainty of whether they’ll actually have to work to overcome those problems. Same for writers, I think – working through a conflict can be hard and demands a strong development of character and story. It’s much easier to have them worked out ahead of time and present them to the reader, forgetting that what’s actually interesting about a conflict is the process of working through it, rather than the actual outcome. That’s why failure can make for a strong narrative, because exploring the process of that failure is way more readable than just learning about another success after the fact.

I’m not saying that every character should be a tyro, novice, farmboy or 1st-level adventurer (pick whichever description you like). Experienced characters are interesting because they carry with them the weight of authority and confidence, and can justify the skills and abilities they possess by dint of that experience. But they, like the farmboy, are starting this story at the beginning.

I'm cooler than the hero. That's my fucking backstory.

Look at one of genre’s most beloved characters, Han Solo – there’s an experienced character that shows off his skills and background from the moment he appears on screen, without the need to stop and tell us about how he learned them. When elements of his background come up, they’re story rather than backstory – he gets hunted by Jabba the Hutt and sold out by Lando Calrissian (shit, sorry, spoiler warning) within the narrative, rather than flashing back to the events or describing them in detail to other characters.  No, those conflicts got referenced briefly in story to create new conflicts that drove the current story – and then, I imagine, they got described in intricate and tedious detail in prequel novels that fans read out of duty. That’s what backstory leads to – prequel novels and fanfic. AND NO-ONE NEEDS THAT.

So how do you portray interesting, engaging, experienced characters without delving into (or ‘revealing’) backstory? Let’s talk about that next weekend.

If you agree, disagree, or want to tell me how awesome Han Solo and Hutt Girls Gone Wild was, get in there and leave a comment.

And if you want a double dose of me being opinionated out of all proportion to any intellectual authority I might possess, head on over to today’s LiveJournal post, where I talk at great and tedious length about Captain America comics, of all things.