Behold, the Opening Chapters of CURSE OF A DARK GOD

For your reading pleasure, I have posted the current version of the first 12 chapters of Curse of a Dark God below. (And there was much rejoicing, yea.)

Read and enjoy!

CURSE OF A DARK GOD draft 3 chapters 1-12 reader 

Note: these are draft chapters and may change in the final version.

If you would like to be part of a test audience, please open the document and begin reading just as you would any book that you picked up because it looked interesting. Stop where you normally would. Then email me by clicking on the Contact John link under my photo up on the left. I’ll send you a couple of questions. Please make sure you don’t ask for the questions before you’ve given the bit above a go (I don’t want the questions to affect your reading). Also, don’t put any critique hat on. Just read as you normally would. 🙂 The deadline for test audience responses is January 15th.

Share

Similar Posts

  • Curse of a Dark God is Finished!

    I finished the 10% edit, going from 205,000 words to 185,000, this morning and emailed the finished manuscript to Super Agent Caitlin who will perform various incantations before sending it off to ye Editors for review. 

    While that’s happening, I will be switching gears and starting the thriller. I’m looking forward to this.  Not only am I having fun developing the ideas, but unlike these epic fantasies I’m writing with a gajillion story lines, this is going to have one story line (okay, with maybe, maybe two subplots), one point of view (instead of three or four), and a limited cast of characters like six (as opposed to close to twenty). I’m preparing to reach  escape velocity. I’ll tell you what jupiter looks like when I get back.

    Share
  • Awful Intent Update: Chapter 26

    I have now moved from the struggle into the resolution. It’s all down hill from here.  I expect the novel to be 70-80k words. The shortest novel I’ve written yet. But I always seem to add on most of my revisions. I hope to keep it shorter, but we’ll see.

    Now you may ask, hey, how does that compare with other thrillers? Well, here are the lengths of a few of James Patterson’s.

    Title Words
    Honeymoon 65,572
    4th of July 68,000
    Lifeguard 71,634
    Mary, Mary 72,426
    Judge and Jury 74,288
    Doublecross 70,753

    And here are some more by some other authors.

    Author Title Words
    Lee Child Gone Tomorrow 146,000
    Lee Child One Shot 124,000
    Lee Child Killing Floor 162,000
    Lee Child Persuader 164,000
    Michael Connelly The Brass Verdict 145,000
    Ridley Pearson Cut and Run 114,000
    Robert Crais The Watchman 82,000
    Robert Crais Taken 84,000
    Robert Crais The First Rule 76,000
    Robert Crais The Sentry 82,000
    Brad Thor Full Black 117,000
    Brad Thor Athena Project 102,000
    Dean Koontz The Good Guy 93,000
    Dean Koontz The Husband 94,000
    Share
  • |

    Awful Intent Update: The power of having the electric ladies read to you

    Everyone says you cannot copyedit your own work.

    You’re an idiot if you try.

    Because you’re mind auto-corrects eorrs, and fills in missing punctuation or words like “of” “the” and “a”.  And often doesn’t care or know the house rules for capitalization. Etc.

    (Did you catch all the errors in that paragraph?)

    Except the brains of copy editors play this trick as well. That’s why some read the manuscript backward and others use arcane WordText code to suss out issues. And some change the font face. And some make multiple passes over a section, looking for dialogue issues the first time through, capitalization the next, and something else the third time. And despite all their work, you still find errors in the text.

    I’m not saying editors aren’t any good. I’m just saying that our brains, for the most part, don’t care about the details. They just care about the communication, and they’re very good at ignoring the rubbish. And when it’s just the brain and the eye working together, the brain makes sense of the text, even when something’s wrong or missing.

    So one trick to force the brain to see what’s actually on the page is to read your text out loud to yourself. It’s an excellent practice, except a human brain is still involved, and it sometimes still plays tricks. And sometimes we get lazy and start to read too quickly, and the next thing you know we’re subvocalizing and whipping along, missing all sorts of stuff.

    So what can you do?

    Well, a few book releases ago, I stumbled onto something. I invited an electric lady to help. And she was dynamite. (You can invite a man if you prefer the sound of those voices.)

    I’m talking about inviting your computer to read aloud every word of your manuscript to you. And highlight the words as it goes.

    I can tell you I’m never going back. These ladies have simply helped me see too many errors that were invisible to me and my beta readers who had editorial chops.

    I use WordTalk, a free plugin for Microsoft Word for this kind of reading. The University of Edinburgh created it to help kids learn how to read. It allows you to select from the text-to-speech voices you have on your computer, set the reading rate, and it highlights the word it’s reading so you immediately see where the error is.

    I set it at a slightly faster reading speed so my mind cannot wander during the reading and use the quick keys so I can start and stop and make my edits easily. And I always, always, always have my electric friend re-read any fixes I make because I can’t tell you how many times I’ve adjusted a sentence or paragraph and introduced more errors that I didn’t see, even though they were staring me in the face.

    I must admit that the electric ladies can’t do everything. Having them read to you cannot help you spot errors you don’t know are errors in the first place. If you don’t know, for example, the conventions for capitalization of personal titles or the conventions for numbers (is it a “.44mm” gun or “forty-four millimeter”?) If you don’t have your own house rules for the many areas where you have a choice like in an epic fantasy (do you use “Dreadman” or “dreadman”?) If you don’t know any of that, you’ll blithely skip over a host of errors and only see the issues you know like the misuses of “rise” and “raise” or “lie” and “lay.”

    So you have to learn the conventions or find someone who does (an editor). Or both.

    Also, doing this type of reading will not help you see if what you’ve written is actually translating the scene in your head clearly and vividly to the page for someone new to your story. Only a fresh set of eyes can tell you where your story isn’t clear, believable, or interesting (at least to that one reader).

    But for helping you spot the issues you do know, I haven’t found anything better. Give it a try.

    Oh, and the update on Awful Intent–Zira and I are almost finished with the copy edit! Which means the release is only days away.

    Share
  • Curse of a Dark God draft 2 finished!!!!

    Rejoice! Sing! The draft is done!

    Hallelujah.

    Based on my records I spent:

    • 48.5 hours on the pre-draft for this book
    • 503.5 hours to finish draft 1
    • 130 hours to finish draft 2
    • A total of 682 hours of work to this point

    If I’d been working full time on this that would be roughly 17 weeks. That’s about 4 months. I don’t think that’s so bad, considering this book clocks in at 230,000 words. Not bad at all. But no wonder just finishing a novel is the thing that filters most would-be writers out. That’s a freaking huge amount of time. I hope as things progress I get faster.

    Here’s what I focused on in this draft.

    • Sugar’s story. It was a mess and the biggest problem with draft 1. I had to rewrite or massively revise about a dozen of her chapters. In fact, I ended up added three chapters to her story: White Tower, Withers, and Loyalties. I’m very please, however, with the result. I think it works very well.
    • The Gnolum. I had purposely left the seeding chapters for these giants out (seeding as in I can’t just have them show up at the end without laying some groundwork). I had to add 2 chapters for them to this draft.
    • Early Argoth chapters. The first two chapter of Argoth’s story needed to be totally rewritten. The second needed major revising.
    • Chapter titles. For titles in draft 1 I used the name of the main pov character in the chapter and a short summary of what was happening. It helps keep things clear. So those are now out and the chapter titles in.
    • Rough stuff. In many of the early chapters I was still feeling my way into the story. Yes, I had an outline, but I just can’t get the whole story until I begin to write. So there were many chapters with notes to myself or blanks to fill in. Some things no longer worked because of later chapters. All this I had to fix.
    • Reordering chapters in the last half of the book. About halfway through the book Talen’s story breaks off from Sugar’s and Argoth’s. So when I was originally writing them, I found it easier to just write all of Talen’s story and then all of Sugars and Argoth’s until the three met up again. Well, this created some time gaps. I fixed those. I also had long stretches of one pov. For example, I had Talen’s story running for 14  chapters without any break to the other viewpoints. All this had to be fixed.

    So I’m very pleased with this draft. Here are the first three chapters for your enjoyment: CODG draft 2 beginning for readers. Remember: feedback from my wife, agent, editors, and other early readers will change it. You’re welcome to contact me with any comments you might have about it.

    Share
  • |

    Killer Story Workshop to be held at CONduit

    I will conduct The 3 Things You Must Learn to Write Killer Stories workshop at CONduit this year. It’s being held at the downtown Raddison hotel. Here’s my schedule.

    Friday, May 22nd

    • Culture-Building in F&SF:  3:00  PM  (with Lee Modesitt, Roger White, Dave Wolverton, Elisabeth Waters, & Brandon Sanderson)
    • The 3 Things You Must Learn to Write Killer Stories Workshop: 8:00 pm – 10:00 pm

    Saturday, May 23rd

    • Mike Oberg asks questions from the audience: 4:00 PM (with Dave Wolverton, James Dashner, & Larry Correia)
    • Reading of Servant of a Dark God: 6:00 PM
    Share
  • Does anyone going to LTUE want “What Comes Next?”

    LTUE didn’t have enough slots to include the presentation in the schedule, but I’m willing to give it in the chat area by the lobby to folks who are interested. Probably on Saturday.

    So in “What Comes Next?” I share two tools I use that help me figure out where to start my stories and, well, what comes next all the way to the end. The second tool encapsulates, for me, the core of what story is all about.

    If you’re interested, let me know

    EDIT: I’m targeting 8-9 am on Saturday.

    Share

7 Comments

  1. Awesome! I went ahead and linked this on readandfindout.com. It’s always refreshing to see authors put their stuff out there.

  2. John, finished SoaDG last night. Writing my review today. Also read these 12 chapters. But when I try clicking the link to email you it won’t give me the link. Help?

  3. Harm,

    Thanks for the heads up. I upgraded to the newest WordPress version and forgot to reactivate. It should be working now. Look forward to your review. I’m going to email you the test audience questions.

  4. John, I am perusing the Life the Universe and Everything site. You’re not on the list of authors attending. What gives?

  5. Hezekiah,

    I think they just haven’t updated. As far as I know I’m slated to be on panels etc. I received an initial email from the organizers, but haven’t heard anything yet as to official schedule etc. You might want to contact them directly to see if they have info I haven’t received yet. I believe the email is on the site.

  6. Okay. Because, you know. If you weren’t there, why bother going? I need to get SoaDG signed, after all.

  7. Indeed, cause those other folks coming, like Sanderson, Modesitt, Farland–chumps 😀

Comments are closed.