April 2022 Irregular Update

It’s been about seven months since my last update post. I do believe these posts will continue to pop up irregularly, but getting at least two major updates out in a year seems like a fair minimum to reach for. So, here’s how it’s been going.

Where are you on Red Watch 3?

Some mixed news here. Shortly after revisiting the project, reading through what I’ve written and my outline, I ended up making some major revisions. I caught on to some glaring pacing issues, restructured how I was planning to present the chapters, and ended up with an entire storyline that proved to be too much for the book. I hope not to leave that hook hanging, though. When I’m getting my completed draft into the hands of beta readers, I might work on that plotline as a companion novella – something similar in scale to Thuna, but it likely won’t be included in the book for Red Watch 3 as a collection. I’m still adjusting some stuff, finding out what I need to rewrite in the new draft, and more challenges could end up coming down the pipeline, but I’m making progress.

It’s undoubtedly the most ambitious thing on my plate. I’m needing to be more considerate of how to keep the plates spinning with all that I set up in the first two Red Watch books and bringing everything forward in a satisfying way. I’m hoping to get a draft in the hands of my beta readers this year. I’m sorry that the wait for this book is proving so long, but I haven’t surrendered. Thank you for your patience, everyone.

How’s the blog going?

I’m enjoying it more than I thought I would. Being upfront about just writing about anything I wanted helped me open myself up to it, for sure. I’ve always been a quiet person socially, just felt like I didn’t have much of value to add to most conversations. But, building my own little soapbox on my website worked, since anyone who doesn’t want to hear from me can just … not be here? Easy enough.

When I was starting the blog, though, my hosting service had a system for comments to be left on each entry and I was sad to see that disappear. I’m interested in some entries serving as a conversation starter, but I’m not trying to cross-post every entry here on every social media site. I never cared for them much – getting me to log onto my Facebook is like pulling teeth, and I use it specifically for book promotion.

All to say that it’s good. I’m like the pace of getting out two entries a month, and I think I’ll at a minimum manage at least one. I will say most of my ideas right now revolve around D&D, and despite my passion for the hobby I don’t want that to be the blog. I’ve been working to ensure I don’t do too many posts like that back-to-back.

Anything else?

I’m planning to run a sale on all three of my books in May. I’ll, naturally, be mostly promoting Ebonskar as my newest book, hoping to get it into more people’s hands. So, if you were waiting for a sale to pick them up for yourself or as a gift, it’s right around the corner. Tell your friends! (If you want to.)

As a more sore subject however, I decided to make another revision to A Tide of Bones earlier this week. Smaller in scope than what occurred before the release of Legacy, but something I’d been unhappy with for a long time. I’ve changed a lot as a writer and person since I worked on Tide and an early scene in the book wasn’t sitting right with me.

I’m speaking, of course, about the scene with Lytha and the thieves. In the original version of the scene, there’s an implication of intent that I have now removed. The exchange is explicitly only about the money, now. The story ultimately was not improved by including that implication and in fact, likely worse for it. It’s something I have expressly forbidden from occurring in my tabletop games, and it didn’t sit well with me that it existed as an introductory moment for this character.

As I understand, the change applies retroactively to the kindle version (unless you have the downloaded version and are offline on the device, perhaps?) but, naturally, old print copies of the text will retain the original scene. I include the mention here as almost a bit of future proofing – for if someone discovers the discrepancy of the scenes and wonders what happened.

That’s about it.

Thank you for reading.

Comments

Leave a comment