There are several alternatives, among them not doing the prolog at at all, and weaving in the explaination of the item, but I'm afraid that would appear to be a Deus Ex Machina kind of device.
Another alternative would be to have the story start with this prolog as chapter one, but then there would be a jump to six years in the future, which I can't see working.
Do any of you have any suggestions on how to introduce an item like this into a story, or do you think I should just drop the idea of an item all together, and rework the plot not to use something like this?
I'm not bugged by a six-year jump after the first chapter, and I don't read prologues.
Congratulations, you have a single data point.
It's really up to you on how you want to pass the information along. Not having read your story, it's hard for me to say if a prologue would be needed in your case or not.
Wow, I'm having a hard time wording things tonight. Maybe I should go to bed...
I agree that I don't mind a 6 year jump after the first chapter, especially if I've got some idea that time has passed. Seems like a safe way to do it.
But I also agree that not many people read them. Sometimes people skip right to the story and read for a while and are bamboozled as to why they're confused and what has happened, in my opinion, they're the ones at fault, not the author. But other stories may not really need to have a prologue, as the prologue information is contained within the actual novel.
I agree with Ray on his point about not having read you story, but your story may not really need a prologue at all. You could bring in your item into your story at any point in your story, as long as you have a built up plot as to why you have brought it in, it should be ok.
On the other hand I've read a number of novels that start with, what Christine calls, Chapter 0. A song for Arbonne by Guy Gavriel Kay is a wonderful example of this. A single pivotal event happened twenty years before the rest of the story. It was not back story. It was part of the main story but all the intervening years were not necessary. So, he wrote a Chapter 0.
It sounds to me like you probably don't need either of those, unless you need to show us what the object can do. It sounds like all you need is the character to think at some point about how he'd been carrying the darn thing around for six years and still had no idea what it did. I think you probably will need to give some hints about what it is capable of, but even if you don't that single thought would indicate to most readers that you have a gun on the mantle.
I love the idea of a Chapter Zero, on many levels. I hadn't seen that one before, and it provides you with a tempting alternative.
The only serious problem I see with prologues, in today's market, is that they are not good material for "partial" submissions. They usually are so far removed from the main story that an agent or editor has trouble judging the book when most of what they see in a partial is prologue. I think a lot of writers equate the word "prologue" with "detailed backstory" (otherwise known as "infodump"), and abuse the purpose of the device by writing something wordy, boring, filled with technical terms, and written from a POV that will never appear again in the book. These writers are the ones who have taught readers to skip prologues.
I've never really seen the point of dinking around with a prologue - just tell the main story without the throat-clearing and fake drama of most prologues. I've even seen a couple of short stories with prologues - what's up with that?
I would have felt...bothered...if it had been a dream sequence or a dialogue topic. Perhaps throwing it in while he uses it, or attempts to use it. Maybe story begins with him returning to where he stole it, secretly looking for what it was or how to use it. Then if he is caught, it can easily be explained.
Now if this hero is a meek, shy hero, one who is seen as a weakling, maybe he could use it as bragging rights in his local town/pub. It could show the story, and develop character. Use this to explain who this MC is. Give us a person!
But what do I know...
In your case, I think it would work quite well with a six year lapse. Your premise sounds interesting and I look forward to reading it in F & F.
Good luck with it.
If there is no prologue, I read the first part of the first chapter, depending on how long the chapter is, and sometimes the whole chapter. So if I were to pick up your book, it really wouldn't matter to me if there was a prologue or not, I would still get the basic idea.
Now that's just me, I know alot of people who don't read the prologue of books and for Terry Prachett fans reading 'Going Postal' that can be a very bad thing indeed! He has two prologues in that particular book which happen to be titled: "The Thousand Year Prologue" and "The Three Month Prologue". At least, I think it's three months. Both Prologues contain information that is not nessacarily vital to the story, but the book sure makes more scence if you read them!
So there's an idea for you.
But that's just me.
As many of you have alluded to, a prologue needs to provide information which is both relevant and yet not required for understanding. It should add an extra layer onto later events, without being necessary for basic understanding.
I've recently used a prologue to provide a scene that adds extra flavour to later characterisation, then skipped thirteen years to the main plot. As everything else in the book runs chronologically, it would feel stylistically jarring to have every chapter-break except the first to be directly continuous.
As it is, for the sequel I have avoided employing a prologue, because there is no major time-leapage (for want of a better term) to spoil the flow.
Teph
Also, to the OP, that plot sounds a lot like The Hobbit.
Thanks again for taking the time to comment on this.
I have two rules about whether I'll read a prologue. One has already been mentioned, that if it's densely packed with information or is a "dawn of time" type, as Christine mentioned. Those I don't read. Ever. They've actually persuaded me on occasion to not buy a book. They bore me, and, in my experience from when I used to read them, give way more information than I wanted about the world, let alone the amount of information I needed about it. It's too much, and too dry. If it's that relevant, it should be possible to work it into the story as it comes up somehow, imnsho.
The second is length. I really hate long prologues. Part of me says that, if there's that much happening, surely it could get put in with the rest of the stories. The rest of me wants to ask the writer if it's all really *that* necessary. Besides, I find that long prologues tend to be a bunch of little bits strung together in a sometimes untidy fashion (Jordan's prologues on later books in WOT, for example). However, I will definitely read short prologues, as they're generally to the point and only include the relevant stuff. Often, I even find them a like a good appetizer: They whet my appetite for the book itself.
Just my 2 cents on it.
If how he got the item is not a story worth of a chapter, just start in the 6 years later present and mention how he got it when the item first comes up.
Being a prolog, and epilog, reader I include them in my stories too, but now I have some doubts reading other people's opinions. Now I don't really know what I would do.
Maybe you could title your prolog: Chapter 0 (or the Prolog you really need to read)
In any event, if you call something a prolog, it needs to stay short. I can't stand huge prologs. Put no more in the prolog than is absolutely necessary, keep the writing short, concise and to the point. If the prolog is short and well written, you have a better chance of people reading it. If you can't keep it short and to the point, call it chapter 1 and rework the way the story/prolog is told to fit in with the general scheme of the book.
[This message has been edited by Jammrock (edited July 03, 2006).]
quote:
The only reason I can imagine that someone would skip a prologue is if they don't know the difference between that and an introduction or foreword or acknowledgement.
Perhaps the person is impatient and would rather read the story.
More often than not, a prologue is of the "from the dawn of time" type that's already been sufficiently ripped to shreds on this thread, or a "look at my cool milieu/ideas/characters/events!" prologue full of miscellaneous junk the author thought was nifty but couldn't or didn't cram into the story. Anything in the latter type is almost always as dry and boring as any of the former.
I was sort of exaggerating on my original reply, but not much. I only read a prologue if the first few words (I don't even give it a sentence) lead me to believe it'll be entertaining enough to be worth my time.
OSC usually advises against prologs. Yet Speaker for the Dead, one of the finest books I've ever read, has a prolog. And it's a good one.
In OSC's writing class this spring, he advised 2 of us to do something like prologs.
One: a very limited penetration account of a terrorist setting a bomb. The book then begins some 10 years before, so we know we're going to find out how someone becomes a terrorist.
Two: a single paragraph detailing the SF event that begins the story. (None of the characters know what happened until days later, but the reader gets to find out at once.)