Home ยป Forum ยป Author Hangout

Forum: Author Hangout

Flashback

PotomacBob ๐Ÿšซ

In my work in progress, there are occasions where I think I need to use a flashback.
In some stories on SOL, there is nothing to indicate that a flashback is about to begin. It's just the next paragraph that comes next. Some stories have a dash or some sort of marks or something that indicate there's a scene change coming.
I'm thinking about inserting words at that point, probably within parentheses. Something like (FLASHBACK TO THE SPRING OF 2016).
Who has an opinion about the use of such a device? Would it help or harm or do nothing?
I saw something like that once a good many years ago when I got to look at the script of a movie being filmed in my home town.

tendertouch ๐Ÿšซ

@PotomacBob

It all depends. If you've set the stage by noting the year/season previously then I'd probably just lead with an ellipses then break it with something like {Spring 2016}. If you haven't then you might just do a horizontal separator that's typically used to delineate scene changes and make it clear in the text that it's earlier.

I'm not fond of including FLASHBACK in the note โ€” just giving the time as sometime previous to the most recent you've noted should give that information.

Dominions Son ๐Ÿšซ

@PotomacBob

Another device that could be used is to end the previous scene with the protagonist starting to tell the story of the flash back.

"I remember, it was the winter of 94..."

scene break

I was digging my car out of the snow....

Mushroom ๐Ÿšซ

@PotomacBob

The one I used them the most was in Bohica.

And every few chapters it would start as a flashback, each time the main character narrating it as if was a dream. This helped me go straight into them without any leadup, and when they woke up I could continue the story.

Switch Blayde ๐Ÿšซ

@PotomacBob

Something like (FLASHBACK TO THE SPRING OF 2016).
Who has an opinion about the use of such a device?

I don't like it.

You transition into and out of a flashback.

The tense of the flashback is important. In a present tense story, the flashback is written in past tense. In a past tense story, the flashback is written in past perfect tense.

However, a lot of past perfect is hard to read. The reader can only handle so many "had"s. So if a past perfect flashback is of reasonable size, begin the flashback in past perfect and end it in past perfect but then have the middle as simple past. How much of the beginning and end? Up to the author, but at least the first one or two paragraphs and the last one or two.

Marius-6 ๐Ÿšซ
Updated:

@PotomacBob

In one of my stories I have a flashback. Since I use a Location and Time/Date in Bold to identify my sub-chapters, I used it for my flashback.

My MC (Main Character) doesn't recognize a young female former Marine who is now an FBI agent, since he is in uniform, and she is told his name before he sees her, she knows who he is the chapter before.

So, I have (something like):

In the air between Joint Base Andrews and Buckley AFB
0630 Hours EST 15 September 2010


Dialog between characters. The bereaved Gunnery Sergeant suddenly realizes he knew this woman 6 years before...

FOB Chosen, Iraq
2200 Hours Local, May 15th 2004


How the MC and at the time young female Marine meet, and become intimate.

The flashback is a much better way to Show why she initiates a sexual liaison with the MC, and, even though the readers are aware the MC is going to Colorado to deal with a death in his family, why he might agree to renewing the relationship.

If I had started the story six years before with what is essentially a "hook up" and that neither character ever expected to see the other again it would have started the story on the wrong track.

Nor did I want a long exposition of what had occurred years previously. It would have been awkward for the characters, and they are on a government aircraft with a bunch of Federal Agents...

Letting the readers witness events let's them draw their own conclusions. But I don't tell the readers. Reading further interactions of the characters Is a Plot Point. I Show things in the flashback that readers may use to put further events in context. But I don't Tell them, which would spoil the readers opportunity to make their own opinions.

Also, if I "Told" then some future plot twists would be spoiled.

Thus, in this circumstance, I believe a flashback is the best way of presenting events.

akarge ๐Ÿšซ
Updated:

@PotomacBob

What REALLY annoys me is writers that use NO scene transition clues. So you are reading along and suddenly you have different people talking, and they seem to not know things that have already happened in the story and WAIT, that person who is talking just DIED, a chapter ago. Oh, it's a flashback! Wait. Now I have to reread that and get my timeline staight! Has he gone back to the present yet? #%=_&^

Replies:   Grey Wolf
Grey Wolf ๐Ÿšซ

@akarge

For whatever reason, I had significant disagreements with two editors about using scene breaks (implemented with horizontal rules, which SoL processes perfectly well, and if/when I convert to HTML/EPUB they'll work fine).

I just finished reading a long story where the reader does not use scene breaks (and/or they were implemented in such a way that SoL / SoL's EPUB generator fails). Each scene shift was a bit like a speed bump.

I also had a minor kerfuffle trying to get a blank line between the date and the body of the first scene within a day. I understand the objection there - screen readers and other assistive technology tend to gloss over blank likes - but in this case the blank line is exactly the same as no blank line for readers using those tools while giving a slight distinction between metadata and content for visual readers. I can't think of a good way to format it for screen readers and such that isn't horribly intrusive and repetitive, so the blank lines will continue :)

Replies:   akarge
akarge ๐Ÿšซ

@Grey Wolf

Blank lines are fine.

They rarely have any typos.

๐Ÿ˜

Replies:   Grey Wolf
Grey Wolf ๐Ÿšซ

@akarge

Lazeez isn't a fan, but not bitterly opposed, either.

The most common 'blank line' typos that I have are accidentally getting an extra one where I didn't expect it. It's rare, and since each blank like requires manual handling, I always catch it before publication.

Missing one, though, is something that I won't catch until someone notices it.

Replies:   Dominions Son
Dominions Son ๐Ÿšซ

@Grey Wolf

I've had one, in the middle of a sentence even.

I use OO/LO and keep the master document as ODT, I save as HTML when preparing to post.

I had one case, were there was a paragraph break in the posted chapter in the middle of a sentence.

I checked my master file and there was no visible break at that location in the master. Then I looked at the HTML file in a browser and the break was there.

I have since taken to skimming the HTML file before posting.

I still have no idea what caused a line break like that in the HTML but not in the master, but I've caught a couple more cases of it before posting.

Replies:   storiesonline_23
storiesonline_23 ๐Ÿšซ

@Dominions Son

I still have no idea what caused a line break like that in the HTML but not in the master, but I've caught a couple more cases of it before posting.

That is grounds for a bug report: file it here

Paladin_HGWT ๐Ÿšซ

@PotomacBob

I have resorted to using:

Location
Time and Date

I found that using a: Break its just br inside the "arrow" (greater than/lesser than) symbols. Prevents the hard stop after the Location, being treated as a paragraph.

That method is unambiguous, and seems to work in all formats.

However, on rare occasions, either the Break, or the Bold didn't work. When I make spelling or grammar changes, I find that the issue is resolved without me making any changes. Why I don't know.

That is mostly an appearance issue. Using

Location
Time

Creates an easily identifiable scene break.

YMMV

Back to Top

 

WARNING! ADULT CONTENT...

Storiesonline is for adult entertainment only. By accessing this site you declare that you are of legal age and that you agree with our Terms of Service and Privacy Policy.


Log In