How do I know when and if a character requires a backstory?Should I change POVs in the following case?Will what worked 'back then' work today? (Novels)When do I successfully kill off an important secondary main character… in a series of five books?Explain character dynamics without giving away too much backstory?How to add depth to primary female character that contrasts well with primary male charactersStory that's too depressing?How to portray a character with gender dysphoria?Can the prologue be the backstory of your main character?Many sexual situations, but no actual sex scenes?How do I show and not tell a backstory?
Why do dragons like shiny stuff?
what can you do with Format View
If someone else uploads my GPL'd code to Github without my permission, is that a copyright violation?
Vectorised way to calculate mean of left and right neighbours in a vector
What is it exactly about flying a Flyboard across the English channel that made Zapata's thighs burn?
Volcanic 3D masyu
What's "halachic" about "Esav hates Ya'akov"?
How do people drown while wearing a life jacket?
Programmatically drawing sinusoids with tikz
C# TCP server/client class
Meaning of ギャップ in the following sentence
How to call made-up data?
Need reasons why a satellite network would not work
Is the first page of a novel really that important?
Piece de Resistance - Introduction & Ace and A's
Awk to get all my regular users in shadow
State of a Robot
How does Geralt transport his swords?
Accurately recalling the key - can everyone do it?
Why is the Vasa Museum in Stockholm so Popular?
…down the primrose path
Does the problem of P vs NP come under the category of Operational Research?
would a winged human/angel build like this be able to fly? (see image below)
Is it possible to use reference type alias with pointer operator to declare a reference to pointer?
How do I know when and if a character requires a backstory?
Should I change POVs in the following case?Will what worked 'back then' work today? (Novels)When do I successfully kill off an important secondary main character… in a series of five books?Explain character dynamics without giving away too much backstory?How to add depth to primary female character that contrasts well with primary male charactersStory that's too depressing?How to portray a character with gender dysphoria?Can the prologue be the backstory of your main character?Many sexual situations, but no actual sex scenes?How do I show and not tell a backstory?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom: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'?
creative-writing character-development backstory
add a comment |
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'?
creative-writing character-development backstory
add a comment |
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'?
creative-writing character-development backstory
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'?
creative-writing character-development backstory
creative-writing character-development backstory
edited 6 hours ago
Cyn
28.2k2 gold badges62 silver badges130 bronze badges
28.2k2 gold badges62 silver badges130 bronze badges
asked 11 hours ago
cool_bodhicool_bodhi
7272 silver badges17 bronze badges
7272 silver badges17 bronze badges
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
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 just 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 related 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.
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.
add a comment |
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.
add a comment |
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.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "166"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwriting.stackexchange.com%2fquestions%2f47126%2fhow-do-i-know-when-and-if-a-character-requires-a-backstory%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
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 just 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 related 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.
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.
add a comment |
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 just 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 related 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.
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.
add a comment |
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 just 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 related 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.
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.
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 just 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 related 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.
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.
answered 10 hours ago
AmadeusAmadeus
71.3k7 gold badges96 silver badges234 bronze badges
71.3k7 gold badges96 silver badges234 bronze badges
add a comment |
add a comment |
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.
add a comment |
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.
add a comment |
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.
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.
answered 9 hours ago
GalastelGalastel
43.6k6 gold badges134 silver badges243 bronze badges
43.6k6 gold badges134 silver badges243 bronze badges
add a comment |
add a comment |
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.
add a comment |
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.
add a comment |
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.
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.
answered 8 hours ago
AshAsh
8,84812 silver badges48 bronze badges
8,84812 silver badges48 bronze badges
add a comment |
add a comment |
Thanks for contributing an answer to Writing Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwriting.stackexchange.com%2fquestions%2f47126%2fhow-do-i-know-when-and-if-a-character-requires-a-backstory%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown