Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

How do I know when and if a character requires a backstory?

+0
−0

In my novel, at the point where the MC meets her would-be boyfriend, Rufus, I have added a small backstory about his job. Later on, the story is almost entirely focused on the MC and what happens to her with a very little mention of Rufus' backstory.

Now, IMHO, being a lead character, his backstory is something the reader would like. Three chapters after meeting Rufus they fall in love, and then the story is almost focused on the adventure they go on together from the MC's POV.

I am unable to understand, which characters need a backstory, wherein the story it should be introduced. Are backstories 'word fillers'?

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

This post was sourced from https://writers.stackexchange.com/q/47126. It is licensed under CC BY-SA 3.0.

0 comment threads

4 answers

+1
−0

Ultimately audiences don't need a lot of details about most characters' history, what they do need, in order for the story to make sense and be immersive, is justifications for their actions. If a character has clear (stated) motives, reasons for being in the tale and doing what they do that is enough. You as the author will generally know far more than you ever put on the page about where characters come from and their true motives. Rufus needs a reason to attach himself to the MC and the two of them need reasons to bond, backstory may form the basis for this, but equally the events of the narrative may be sufficient without a detailed history of the characters coming into it.

Note that stated motives and true motives need not be the same thing, the friction between the two can be a source of dramatic tension.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

This post was sourced from https://writers.stackexchange.com/a/47132. It is licensed under CC BY-SA 3.0.

0 comment threads

+1
−0

I disagree with @Galastel. Not every character needs a backstory.

Many minor characters in fiction only need to appear consistent with their context and the purpose they have in the narrative. When the protagonist shops at a supermarket, takes a bus, or asks for directions on the street, the clerk, bus driver, and passerby only need to behave in the manner that we are familiar with from our own everyday experience of similar situations. And even if the bus driver pulls a gun to shoot at the hero, you don't need a backstory for him before the hero shoots him, you only have to make it plausible within the logic of the narrative that a henchman of the antagonist would be placed in that position. What made the bus driver become a bus driver or the henchman a henchman is completely irrelevant if they only appear briefly to be paid or shot.

Backstory serves to makes the behavior of a fictional character consistent.

If you can accomplish consistency in another manner, you don't need backstory.

I never even do the full character interview and what else is recommended to "become familiar with" my protagonists. I only flesh out their backstory as much as I am interested in it, and that is usually enough for my readers to be happy. What I do is create a psychological profile. That is, I sketch out their personality, their needs, their fears, their interests, and so on – but again, only insofar as these are relevant for the story that I have outlined and want to tell.

Using your example, I would ask myself:

  • What makes your main character fall in love with her love interest?

  • What makes the love interest behave in the way he does?

If the job he has is relevant to the answers to those questions, then I would think about what job he has. If not, not.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

This post was sourced from https://writers.stackexchange.com/a/47175. It is licensed under CC BY-SA 3.0.

0 comment threads

+0
−0

A backstory needs to matter to the story; in this case it probably matters to the MC; few people fall in love with a person they know nothing about. They fall in lust, certainly, and that lust can lead to true love by compelling them to pursue the object of their lust and thus get to know them personally. But lust isn't love -- If in getting to know the object of their lust they find repellent ideas, cruelty and selfishness, disgust with the personality can defeat both love and lust.

In that sense, you may want the Rufus backstory mostly told to the MC, to create sympathies and understanding for Rufus with her, supporting the cause of her falling in love with Rufus. It becomes more convincing to the reader if they share in the MC's experience of Rufus, instead of them being told something the MC doesn't really know. And story wise, this is more efficient: If you tell the reader something the MC doesn't know, and then later Rufus needs to tell her all about it, then as an author you are repeating yourself and boring the reader, because when they read this second passage, the reader is not learning anything new at all. (Of course somebody besides Rufus could tell the MC, and Rufus not talk about it.)

There is some magic in romantic love, some undefinable qualities are necessary, but there are also some commonalities we expect to be present for true romantic love, as opposed to similar motivators like lust, or chivalrous honor, or heroism in protecting the weak. One of these commonalities is spending time together and getting to know each other, personality is an important component of love, but not so much the similar motivators listed; we can lust after a beautiful body without knowing a thing about the person inside it. Or pull such a person out of a car crash, or intervene to prevent a bully from beating them.

Romance demands a fit of two personalities, usually one with synergy, so the two together are "better" in some sense to each of them, than they are alone. That synergy is the magical part that you, as an author, can assert as feeling.

But if you want them to fall in love, they do need to get to know each other, even if much of that is off-screen, you have to make sure the reader understands they are spending time together and learning about each other. Wherever you engineer your story for these conversations to take place, that is a good time for backstories.

These "times for conversation" often occur in transitional times within the story; for example while traveling somewhere, or on a stake out, or in an office setting working on a project, or while one of them is in the hospital recovering from injury, etc. Avoid a "talking heads" scene, make it so they are doing something (or things are going on around them) that doesn't require a lot of mental attention and allows them time to have a conversation.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

0 comment threads

+0
−0

First and foremost, every character requires a backstory in your mind. You need to know who they are, why they act in a certain way, how they would respond to new situations, etc.

Once you have that backstory, you can decide how much of it will be revealed to the reader, at what point of the story, and whether directly or indirectly. Bits and pieces of a character's backstory can be strewn throughout your story, coming up when they're relevant. It might be that some element would be revealed when this would create the most dramatic effect. Or it might be that the backstory remains entirely in the subtext, never getting officially "revealed".

Look for example at Hemingway's The Sun Also Rises: the novel starts with the backstory of one character, Robert Cohn. The backstory of another, Brett, is revealed in bits and pieces - here we learn that she's getting married, there - that she's getting divorced first, much much later - why she's getting divorced. As for the MC, we learn very early on that he suffers from impotency, or something similar, due to an injury suffered during WW1. We never learn any more. His backstory is all subtext and no text.

Or, look at The Lord of the Rings. Boromir tells us his backstory right upon arrival: who he is, where he came from, why, his family, his position in society - everything. Aragorn, on the other hand - it takes several chapters between his appearance as "Strider the Ranger" and the revelation that he is Isildur's heir. Of Legolas's and Gimli's backstory we know little save where they came from, since that's irrelevant; and Gandalf's backstory is a deliberate mystery. But Gandalf's story does exist, it just never gets told. You find out more about him in the Unfinished Tales.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »