Showing posts with label Epic. Show all posts
Showing posts with label Epic. Show all posts

Sunday, June 10, 2012

How a Geek Writes an Epic Fantasy part 2

In my previous post (How a Geek Writes an Epic Fantasy part 1) I introduced you to Magic Muse, my writing workbench.  But that's only a portion of my Epic Fantasy Writing tool set.  I also wrote an additional program that I call Visual Story.  (One day I'll merge the two into a single application.)  It has a number of uses, but I use it (loosely) as a storyboard or outline interface.

Essentially, the application consists of textboxes that can be sized and arranged on a large backdrop.  Each box contains one section for a title or heading and a second section for content.  Colors can be applied to each box's borders, titles and content.  I prefer setting the border colors according to plots.

I tend to wrap a complete chapter into a single box.  I list a description of the chapter's scene(s) and indicate which character's viewpoint is being used for each scene.  This works well for documenting chapters already written.  For planning, well, let's just say that this is about as close to true outlining as I get.

I've written a number of other applications over the years.  One served as virtual index cards that I intended to use for character bios, description of places and things, etc., but I've found that my scribblet in Magic Muse serves that purpose well enough for me.

But as much as I love my electronic tools, I don't rely exclusively on them.

Whiteboard
I have a whiteboard beside my desk at all times.  I've been known to draw on the whiteboard.  I sketched out the Hosiyin Citadel from my first book on it.  There were characteristics I knew I wanted, but I needed my eyes to see it so I could see it through a character's eyes.

I use the fine-tipped dry-erase markers so I can scribble loads of legible text.  I'll occasionally jot down the names of characters that need addressing in the story and how soon.  I'll work out plot mechanics for finding logical reasons for Character A to be in Location B so that Event C transpires according to plan.  I may write about dragons and magic, but even they must adhere to some form of logic.

Journal
When it comes down to fleshing out my world's settings, background, history and other such trivia that makes it into the manuscript only by--at best--a passing reference. Journals and diaries are great places for me to discover my world's history, back story.

I used this method for working out details of the last major war in my book, exploring treaty details, discovering the origins of races, even for writing short stories that serve no purpose other than enabling me to flesh out characters before they make it into the book.

The actual manuscript
I sometimes type quick notes, reminders, potential dialog or possible narrative snippets right inside the manuscript itself, usually at the end of the scene or chapter.  I do this when the snippet must be addressed or incorporated before moving too far into the next scene or chapter.

I've tinkered with index cards, college or narrow ruled spiral-bound notebooks, even loose leaf paper, but I really prefer a searchable, organized electronic means to store notes. And of course, I now have my Android tablet.  It's great for proofing what I've written.  The format and display is just different enough that I'll spot mistakes that I've overlooked a hundred times on the computer monitor.

What tools do you use?

Tuesday, May 29, 2012

How a Geek Writes an Epic Fantasy part 1

It's tough not to be a geek when you're male, a computer programmer and a lover of fantasy.  In fact, I'm so geeky that I wrote my own computer program to help me write my epic fantasy.  (That should rank me fairly high on the geek-o-meter, yes?)

My biggest challenge in writing epic fantasy is consistency.  Spend too many months "discovery writing" anything of that scope and errors are bound to creep into the manuscript.  Red hair becomes blonde.  A character is from Osek-Dahm in one chapter and suddenly from Jerok Thel in a subsequent one.  If you're not careful you may even forget which distant countries are at war with each other.

So I needed to find a quick and easy way to record these details and have them readily available when needed.  I searched the net.  I found some that had good features.  I found some that had marvelous interfaces.  But I didn't find one that tripped my trigger.  But hey, not a problem, I'm a software developer so there was really only one choice I could make.

Write my own!

And so I did.  I created Magic Muse, my very own, tailor-made, writing workbench.

This is a Visual Basic application I wrote many years ago to handle all the things that I felt I needed in a writing application.  I still use it for drafts.  It interfaces with MS Word for word counts, thesaurus, spell and grammar checking.  It even allows me to paste in maps and other diagrams.

All projects can be selected via a dropdown and each project can contain any number of cabinets, folders and documents displayed in the treeview on the left.  

I use the treeview to add, delete and reorder chapters and scenes.  Clicking a scene within the treeview opens it in the RTF (Rich Text Format) editor on the right.  Each scene is saved as an RTF document that I can load into MS Word, Open Office, MS Wordpad, etc.  When the book is finished, I can package its contents into a single RTF usable by those same word processors.  (Handy when you want to pump out a quick eBook using Word and Calibre for proofing on the Android tablet.)


Notes can be handled in one of two ways.  A cabinet can be created to hold all notes, which can also be broken down into multiple folders and documents.  My preference for most notes, however, is the scribblet.  That's the window attached to the bottom of the treeview and editor.  There are dedicated sections for things like characters, places, glossary of terms, etc.

The scribblet is collapsible.  To get items into the scribblet, I highlight the word I want to add, right-click it, and indicate which scribblet list should hold it.  I can then add all the generic information about the term and save it.  I can even "index" the term and Magic Muse will scan every scene and provide me with a complete list of where it was used.  (This is handy if I know I referenced the minor character Terrin, but don't recall which chapters featured him.)

I can do all the basic word processing tasks in Magic Muse.  And being able to quickly toggle between scenes instead of scrolling through a huge document is a massive plus for me.

In part two of this post I'll discuss additional ways I handle notes and plot lines, including my storyboard application that I, of course, wrote for myself.  I call it Visual Story and will leave you with a sneak peek at it.

Wednesday, May 9, 2012

It Happened...

At work, standing in the cafeteria lunch line, it happened.  A server left his station, walked to the serving station in which line I was waiting and asked, "Are you the one writing the book?"

I nearly fell in the floor!  I made him repeat the question, certain I'd misunderstood it.  "Are you the one writing the book?" he asked again.

Hiding my grin was impossible.  "Yes.  How did you know?"

"Jenn told me."

Jenn is a coworker of mine in another department.  I'd let her read my prologue the previous week.  She told me she liked it, but you know how that goes.  All your friends like what you wrote when they're talking with you about it.  Perhaps she really did.  Or perhaps she was just impressed that I had actually completed my draft.  In any event, it made me feel like a...ahem...writer.

And it felt good!

I don't even need to tell you what the next question was, right?  Anyone who has finished a book (even the first draft) knows the next question.  "What's it about?"

So there it was.  The question I've pondered answering for months.  I've wondered what I'd say, how badly I would answer and whether I'd leave them shaking their heads acting like they understood what I was telling them.

"Well, it's an epic fantasy."  Quickly, I moved to dispel the blank look already forming.  "It's kind of like Lord of the Rings."  Whew.  The nod of comprehension.  I don't need approval, but understanding is crucial.  This way, they can walk away with an inner giggle muttering, "Ha!  The guy thinks he's Tolkien."  That much is acceptable.

So, what makes it even better?  The other server joining the conversation and asking, "Is it like Eragon?"

"A little," I answered.  "It's got dragons."

"I loved Eragon," he told me with a smile.  "When you get it published I'll have to buy a copy."

Then it was my turn to smile.  Yes, folks, it felt mighty good indeed.


Do you have similar stories you'd care to share?

Thursday, April 19, 2012

An Epic Fantasy Map

What good is an epic fantasy without maps, right?  Well, I have an epic fantasy.  And I have maps.  Several of them.  Too many of them, yet not all I need.  No, I'm not going to tell you how many maps I've made.  Why?  Because it's embarrassing. 

The map below is one of them.  It shows where the first eight or nine chapters of my epic fantasy take place.  Please keep in mind that the actual size of the map is about 20-30% larger than what is displayed here.  That means that the names of places are much easier to read on the original.

First off, please accept my apologies if this thing doesn't scale or render well on lower resolution (or smaller) displays.  I have limited devices on which to preview it.

I have a couple questions I'd like to ask, so if you don't mind, give the map a gander and scroll down.

Land of Dramar Map
(This map depicts a tiny fraction of the Strands of Pattern series' world.)

I posted this map to ask a couple questions.  I would appreciate your thoughts.
  • Do you reference maps provided in books?
  • If so, do you want one big map or multiple detailed maps?

(For those who may be curious, I did this in Microsoft Paint under Windows XP.)

Sunday, March 18, 2012

The Hardest Part

I'm mere chapters away from completing the initial draft of my novel.  And I'm finding it difficult.  It's got to be perfect, you understand.  Believable.  Exciting.  Fun and engaging yet steeped in tension.  I intend to drive the reader to tears, to shouts of joy, to wondering why they've bitten all the nails off their fingers.  And of course, to pondering the inevitable woes to come.  I think, for me, the ending is the hardest part.

I know what has to happen.  The goal is clear.  The climax and its aftermath are not in question.  It's simply a matter of getting the setup just right.  The beginning was easy.  And writing the middle was loads of fun.

You see, I'm essentially a discovery writer and offer no apologies for it.  Were I to treat my outline like the Gospel According to St. John or the Pentateuch then writing would be a chore or a (gasp!) job.  (I already have one of those and it pays better in a month than I'll probably earn in my lifetime as a writer.)

Jean-Auguste-Dominique Ingres. (1842)
It amazes me.  All I need to start a story--even a novel--is a simple line of dialog, or possibly a stimulating opening statement without a clue where it will lead.  Two little words launched this current NIP (novel in progress) of mine.  Oh, if wrapping up all the loose threads were as easy.

This is the point in my writing where my muse goes on vacation.  She's done her job.  She inspired.  She dropped impressive vistas, titillating events and dynamic characters right into my lap and let me play.  She smiled as I did so.  But she doesn't write the book.  She doesn't dig plot.  She cares little for consistency.  And she despises grammar.  All that, she leaves to me.

I hear many say they can never get started or they become mired in the muddle in the middle. Some complain of writing themselves into a corner or of losing inspiration or enthusiasm.  I'm sure I'll experience all these hindrances at some point.  I haven't really done so yet with this book.  For the most part it's flowed like a serene stream.  At times it's been a rushing river.  Of course there have been times when I crawled and clawed my way through scenes or meandered at plot detours or fiddled with a setting until I could get it just so.

Now I must master the mechanics.  Now is when the skill must arise.  To reuse my previous metaphor, I'm at bat.  The bases are loaded.  It's a full count.  And the pitcher is winding the payoff pitch.  Will I choke?  Will I swing and miss?  Will I stand idly by and watch the ball sail perfectly through the strike zone?  I'm being sifted and measured.  Do I have what it takes to knock it out of the park?

My epic fantasy needs an epic climax.  Perhaps an epic climax requires an epic struggle on the part of the writer?  I think that before I'm finished, the fingertips without fingernails will be my own.

Is this a dilemma unique to Jeff-the-aspiring-novelist?  Care to enlighten this suddenly frightened writer?  Have any insights or recommendations you'd care to share?  I'll let you borrow my muse. :)