Hero origin stories are told in a few ways: following right from the start, flashbacks, catching the last of the most important parts, and simply referred to in dialogue or commentary. The question the author must answer is, does the audience need to know? Does the audience need to see everything? What are the important parts of the origin, and what can be safely left out? The much maligned Star Wars prequels (Episodes 1-3) got me thinking a lot about this, because you can make a very strong case that Darth Vader didn't even need an origin story. Sometimes it's best to leave things in the dark, unknown and pulling mysterious strings.
For the audience, origin stories explain where the hero came from, what motivates them, and what fears they may have. Batman's origin story is likely the best known (possibly because it's the most believable) and explains all of those things. Usually the hero is the main character, so an origin story can be very helpful to the audience. On the other hand, it's nice just to step into a story already underway and learn little things all through, so the audience is more likely to pay attention than when it's thrown out in one shot.
For the author, origin stories are a time to create the suite of emotions needed to make the hero into the character desired. It's incredible how powerful emotions become when attached to a specific event in the formation of the hero. So, the question is, do you want the audience to know this all in advance or as things require explanation? Audiences do like mysteriousness, and it's fun putting together the pieces of why a hero is who they are (so long as it's not impossible). Whatever the choice, make sure your audience isn't left behind. If an origin story is needed, make absolutely sure you don't do it halfway.
- M
No comments:
Post a Comment