• Welcome to the Fantasy Writing Forums. Register Now to join us!

How much should we explain existing mythology in our stories?

Nikos

Dreamer
Greetings everyone,

My name is Nikos. This is my first post here and I thought I would go with a question that I have thought quite a few times while writing:

When weaving existing mythology into a story, how much explanation do you think the writer owes the reader?

On one hand, a detailed explanation of the myth can provide context and depth, especially for readers who aren’t familiar with it. On the other, there’s a risk of bogging the narrative down or drifting into info-dump territory.

Some writers assume readers will be curious enough to look things up themselves, while others prefer to retell or reinterpret the myth within the narrative.

Personally, I’ve been experimenting with mythological structures and symbols in my own writing, and I often wonder: is it better to leave some mystery, or to guide the reader more directly through the mythic background?

For example, in one of my projects I include the three fates from ancient Greek mythology, and during the story I include a few of their characteristics but I never invest time into their entire lore. My characters due to the nature of the story are simply aware of what each fate represents as soon as they meet her.

How do you approach this balance in your own worldbuilding?
 

pmmg

Myth Weaver
Howdy Nikos,

Initially, my own writing would reveal the the lore and mythos only when the characters of the story had need to reveal it, which was rare, cause for the most part, my characters don't care, or it not very present on their minds. But it did slowly start to leak out, even in book 1. But as time went on, and the story grew, some of the back story did make its way into flashback scenes, but not enough to reveal the entire pantheon and their stories. And, as my story expands, the world become more diverse and different belief sets also appear.

I do have supported material which reveals more of this, but it will probably not make it into the actual story. In that case, I will likely post it to my website when it becomes a good time to do so. Right now, it contains spoilers I prefer not to reveal.

I dont think there is a single answer to this. The way it is revealed needs to fit the story its being told in. Only you know your story, so only you know if its a good fit or not.
 

Incanus

Auror
This is one of several areas of exposition that I have been struggling with mightily in my WIP.

My current answer is: I don't know.

However, my current solution is: include the material as best you can in the text, and then see how readers (alpha, beta, whoever) respond to it. And then, adjust accordingly.

A lot of mythological elements certainly feel like backstory or exposition, but then, these things have a part to play in character motivations and worldviews. At least, that's how it is in my story.

Good luck, and if you find a decent answer to this, I hope you'll share!
 

Saigonnus

Auror
I would say: If it's important to the story; as in central to the plot, character development etc, then it should be explained well, with as much detail as made necessary by the story. With that in mind, no one really like infodumping, so perhaps you could use a sprinkle here and there to impart the mythology so the readers don't have wade through a page-and-a-half biopic of this god, or that god, or this belief system.

If not that important, or it is simply "window dressing", or "world-building", then a more minimalistic approach would be better. Writers have to be careful we don't add things to a story that could muddy the water, distract from the story, take away from the character development, etc.
 

Nikos

Dreamer
Greetings everyone,

My name is Nikos. This is my first post here and I thought I would go with a question that I have thought quite a few times while writing:

When weaving existing mythology into a story, how much explanation do you think the writer owes the reader?

On one hand, a detailed explanation of the myth can provide context and depth, especially for readers who aren’t familiar with it. On the other, there’s a risk of bogging the narrative down or drifting into info-dump territory.

Some writers assume readers will be curious enough to look things up themselves, while others prefer to retell or reinterpret the myth within the narrative.

Personally, I’ve been experimenting with mythological structures and symbols in my own writing, and I often wonder: is it better to leave some mystery, or to guide the reader more directly through the mythic background?

For example, in one of my projects I include the three fates from ancient Greek mythology, and during the story I include a few of their characteristics but I never invest time into their entire lore. My characters due to the nature of the story are simply aware of what each fate represents as soon as they meet her.

How do you approach this balance in your own worldbuilding?
Thank you for your answers, we seem to be of similar mind. The work I had in mind as I was writing the question, is written in a poetic form ( meaning in rhymes) so there is very little space for extended world building through exposition. The idea came to my mind about using a song for instance within the narrative, but it felt kind of expensive, if that makes sense and it would draw the reader's attention away from the main plot.
 
I feel that a few important questions to ask for any scene are:
1) What does the reader need to know right now?
2) What needs to be foreshadowed or hinted at for later developments?
3) What do the characters need to know right now?

Figuring out how to organically add information might be one of the hardest tasks, but it is well worth it, if only to avoid the dreaded 'As You Know' dialogue.
"As you know, the dark lord Generic the XVI was sealed away 100 years ago by the legendary hero and his trusty sword, which was forged at McGuffin Industries."
"I'm his grandchild, why are you telling me what I've known for most of my life?"
"Oh. Um. How about I tell you my tragic backstory instead? No pets were harmed, I promise!"
"Go away."
 

Miles Lacey

Archmage
Mythology is how groups explain things from why the length of daytime varies during the course of a year to why a woman having her period is considered unclean. Below are a few examples of how I've introduced mythology into my writing without an infodump or a "As you know..." introduction.

"The taniwha has stirred!" Hunia cried out as the ground shook. "Priestess! What have we done to offend it?"
"Taniwha get stiff and sore from being idle for so long, my boy!" The Priestess shouted back. "The ground will cease shaking when the taniwha is comfortable again!"

"The days get shorter when the sun forgets why Maui trapped and beat it so long ago," Aroha's father explained. "Soon enough, Maui will need to beat the sun again so it will slow down and the days become longer."

"We don't eat this type of mushroom," Mama told me as she pointed to a pretty red mushroom covered in white spots. "It is cursed by Honare, the god of the undergrowth. If you eat it, you will die."


I used Māori mythology as the inspiration for the first two examples. Note that details are kept to a minimum and, in the second example, I avoided the "As you know..." thing by simply having a father explain something to his daughter by recalling a story from their mythology that is summed up in two sentences.

In most cases the only times I think it's okay to go into the details of a mythology is:

1. If the character(s) discussing the mythology in detail are in the clergy, academics or elders/teachers passing on knowledge or having a debate.
2. If a main character is some sort of prophet or destined to go forth on their journey because the mythology states that this person is the chosen one.
3. There is a major deviation from what most people would consider to be acceptable in a real world situation.
4. The characters are killing time while resting. Seriously, who would'n't love a good story while sitting at a campfire after spending the day saving a village from a bunch of bandits?

I hope this answers the question.
 

Malik

Auror
If you mean extant mythology in our world that you're working into your fantasy novel, unless it's common knowledge, you're going to need it explained.

If it's mythology that's unique to your fantasy world, you're definitely going to need to explain it.

The novel I just published has a whole thing n which the world the characters find themselves transported to

is ruled by leaders called Vallas. They refer to their world as Vallala, Land of the Vallas. "Valhalla" needs no explanation, although the MC, a Norse researcher, has to painstakingly explain to a slower person that it's likely a similar portal opened up in Scandinavia thousands of years ago and this could explain where Norse legends come from--elves, trolls, dragons, gods.
 
Do we actually know to what extent people believed in the mythology being told? Were they accepted as truth or were they just stories that were useful to remember certain things, like which plants were safe to eat? Or something in the middle?
 

xena

Troubadour
You don't need to explain every part of a myth, just enough so readers can follow the story. If it's just background, a brief mention is fine. If it's important to the plot, drop the details in naturally through dialogue or lore.
 

minta

Troubadour
As long as readers understand what’s happening without needing to look it up, you’re good.
 

Gurkhal

Auror
I shall offer another suggestion. If you feel that the reader needs to know some extensive mythology but you don't want to do an info dump or can't find a way to deliver the information into the story. Consider using an appendix for it. As long as you don't go overboard with it and still keep that appendix concise and to the point with the relevant information I think it could work.
 

Mad Swede

Auror
I've been following this thread for a few days, and it strikes me that we may be missing something. The challenge is how we convey the mythology to the reader in a situation where the characters probably already know it and don't need it explained. The Lord of the Rings is an interesting example, in that the story is full of hints about the history and mythology of Middle Earth (eg when Tom Bombadil mentions the Men of Westernesse after he's rescued the hobbits from the barrow, or when Aragorn half-seriously accuses Bilbo of cheek for writing verse about Eärendil in Elrond's house), but it is rarely fully detailed or even explained. If you read the appendices you get most - but not all - of the picture.

My approach to the mythology of my setting is not to explain it to the reader. I do have it worked out, because I need that for the characters to be able to refer to it in their conversations. But I don't feel the readers need it, I prefer to hint at it all as a way of both gving depth and as a way of leaving some things unexplained. Some readers like this, some don't.
 
Top