Friday, January 10, 2014

Booktalk – Wolves on the Border

While I have written a number of stories and been involved with several sourcebooks, my contribution is but a drop in the buck in the amount of stories and source books that have been written. I’ve decided to highlight some of these earlier works, and show how they are still relevant to day. These won’t be book reviews, but why I think they’re important.

I’ve decided to start with one of the first Battletech Novels: Wolves on the Border by Robert Charrette.



Many Battletech fans consider this the best Battletech novel ever written, and it’s hard to argue with that claim. This is the first novel that the reader sees large-scale warfare. In Decision at Thunder Rift, the main thrust is small-unit action, less than a company of ’Mechs involved. In the Sword and the Dagger, it’s political intrigue. In Wolves on the Border, it’s warfare.

Minobu Tetsuhara is a loyal officer in the Draconis Combine Mustered Soldiery. When he spares the life of an enemy, he is stripped of his position and reassigned as a liaison officer to a newly hired mercenary unit --- Wolf's Dragoons. He discovers that the enemy he spared was the Dragoon's commander, Colonel Jamie Wolf.

As he works with the Dragoons and Colonel Wolf, Tetsuhara find that he is more accepted by the mercenaries than he is by the Combine. Tetshura and Wolf becomes friends, finding common ground as warriors, As the Dragoons win victory after victory, Tetsuhara finds that their success is also his success.

He is given the task of training a new division of warriors, in the image of the Dragoons. But when Warlord Samsonov tried to trap the Dragoons into becoming a permanent part of the DCMS, the Wolves refuse, and Tetshura is forced to fight his friend Jamie Wolf and his Dragoons.

It’s our first good look at two important parts of the Battletech universe: The Draconis Combine and Wolves Dragoons. The Combine soldier as Samauri is established here, and the reader see it in Tetshura's actions and manner. We also see the power games and vicious backstabbing that hides behind the image. In the Dragoons, we see a highly profession unit of soldiers, with hints of a background that doesn't become known until twenty-five years later.

The story is solid, the action well-imaged, setting the standards for every other author that follows. The events have consequences far beyond the novel, and it's after effects felt for a long time. Several major characters are introduced in this novel --  Jaime Wolf,  Natasha Kerensky, Takashi Kurita, and The Bounty Hunter. Besides the Dragoons, this novel marks the first story appearance of the Sword of Light regiments, the Ryuken, and the Eridani Light Horse.

I consider this novel to be the most important novel in the fist several years of Battletech. It is one of the foundation stones on which the Battletech legacy is laid, and without it, the Battletech Universe would have been different.

Craig

Tuesday, January 7, 2014

Looking Back at 2013 and Forward to 2014

Well, for the second year in a row, I have the first Battlecorps story of the year! Unfortunately, that first story in 2013 was my only Battlecorps story in 2013....

Last year was way off for my story writing. I did write other things for Battletech – several entries in the 3145 TROs, a couple of scenarios that were attached to stories The scenarios came first: the stories were written to fit the scenario, not the other way around.), and I was the lead writer on FR2765: DCMS. So, what I wasn’t active in the Battlecorps end of things, I was busy,.

Operation Red Lion makes my twentieth published short story for Battletech, all in less than five years. But I think it’s time I pushed myself back into the short story arena. So, here are my goal when it comes to Battlecorps:

I want to publish a minimum of six stories on Battlecorps in 2014. I had six stories in both 2009 and 2010, my first two years of being a Battlecorps author. So, the goal is not unreachable.

So, what does that mean for this blog?

I intend on updating this blog at least twice a week, on Tuesdays and Fridays. As to what I’m going to write about, well, that’s going to be up in the air beyond writing about Battletech. I have a few ideas, and there might be a few surprises along the way.

In addition to this blog and my other blog (for my non-Battletech writing), I will be writing, or more accurately, finishing stories I’ve started. The number of half-finished stories on my tracking spreadsheet is large, so I intend on whittling down that number this year. I also have a couple of experimental things that may or may not go well. Things on my list include a sequel to Operation Red Lion, a third Gazael story, and a few other stories of interest.

Of course, this all depends on Jason the editor deciding the story is good enough to buy. We shall see if I can do it....

Craig

Friday, November 1, 2013

Contracts and "Work for Hire"

I mentioned Contracts in a few entries, but I think it's time to talk about them a little more and the concept of "Work for Hire"

Contracts are a vital part of being a freelance writer. CGL's contracts are three pages, of which the last one is just when you sign. It details what the freelancer will do, what the company will do, the price the freelancer will be paid, and who has what rights. The contract is basically the same one, with details like what the contract is for, how much the writer will be paid for, and the due date for the payment.

The process goes like this: Once a story is accepted, I get a contracted Emailed to me. I read it over, print it out, sign it and either email or fax the contract back to CGL, who then signs it and emails me the complete copy for my records. Once the product has been published, I send CGL an invoice for the published work and I get a check for the work. The entire process can take months, so don't expect the check if you need the money for something.

There is something I must stress; All the work I do for CGL is "Work for Hire." It means that in return for being paid, I give up all rights to the work. Any stories, TRO entries, or sourcebook work I do for CGL becomes CGL's property. I get the credit as the writer, but I have no other rights over the story.

 What does that mean? It means that everything in the story -- all characters, units, and situations are CGL's property. They are no longer mine. If someone in CGL wants to use them, they can (hopefully, with the original author's input, if he or she are still around) Unlike my own original universe writing, I can't publish any Battlecorps story I written. CGL can, and has done so with the Onslaught anthology I wrote for. If you get a CGL contract for something you did, read it over so you know what is expected from you as a freelancer. Then deliver it.

Craig

Wednesday, October 30, 2013

A long due update.....

I know I'm not the most active of bloggers, but I have been neglecting both my blogs over the last several months, and that is totally my fault. I need to blog more and I intend in fixing that failure through the rest of the year.....

Now, the update. The other two stories I mentioned in my last post that were up in the air? Both accepted, and I'm waiting for the contracts on them. I'll go into contracts in a later post, but I'm happy. I've finished up another story which, if I can get it off the ground, will become a series of stories in the same vein as the Cobalt Coil stories from the Battletechnology Magazine. We'll see how that goes....

I also am working on something, that, if Jason accepts it, will be a new chapter in my writing growth. If not, it will be a crash and burn and I will have to move onto the next project. I can't dwell on failures....

Craig

Sunday, June 23, 2013

Updates on Submissions

This morning, I found four emails in my mailbox from Jason on the four BattleCorps stories I submitted in the last month. It's a mixed bag -- One's been accepted for publication, one's been rejected, and the other two are still up in the air. I wrote an email on one of the two up in the air, while I won't hear a final decision on the other one until the end of July, after the fact-checkers go through it.

I have mixed feelings on the results. I'm pleased that one was accepted, but that joy is offset by the disappointment about the one was rejected. As for the other two, more waiting.....

For anyone reading this, you can take two things from it: First, just because I've written nearly two dozen stories for Battlecorps, that doesn't give me a free pass on any story I send in. My stories are subject to the same criteria as a new author's.

Second, your author's skin has to be as tough as 'Mech armor. Not every story is going to make it -- in fact, I could end up with three out of the four stories I sent in being rejected. That doesn't mean I send a hate-filled Email to Jason, and stomp off into the night, and never being heard from again. It means I need to get back to work and write more stories.

That is the way of the Writer. Rejection is part of the Way. If you can't accept that, then you will never be a writer of any sort.

As for the rejected story, Jason didn't say there was anything wrong with it per say, but it came down to a choice between this story and another, and he liked the other one better. Maybe it was just that they came in close together -- had I sent it six months from now, who knows?

That's it for now. I'll let you know what happens with the other two when I hear about it.

Later!

Craig

Tuesday, June 11, 2013

Sequels – The Good and Bad

Well, just before I posted this, I sent my fourth story in as many weeks to BattleCorps, a personal record for me. I haven’t heard back from Jason yet, but if he does think they’re good enough to be published, you’ll see them. If not, we’ll see....

But I’m not resting on my laurels. I have several more stories in various state of being written. As I look over the list, I find that three of them I have half-written are sequels.

Most BattleCorps stories are one-shots – the characters appears in the story and are never heard from again. With the size of the Battletech Universe, there’s no need to use the same characters over and over again. They have their time in the spotlight, then they disappear back into the larger universe, their story told. Some characters are only good for one story.

But a few still have stories that need to be told. These few have enough force to carry a second story, a sequel. Some are even strong enough to carry several stories. Sometimes, readers want to see more of these character, while sometimes, the author has a story that is right for the characters.

On the plus side of writing a sequel, it’s expanding on the characters and their dynamics from the first story, adding more to them. It allows the writer to add another layer to the character and situations. A supporting character in the first story might get some more screen time, or we learn more about one character’s background. Events or things mentioned in the first story might be explained in a second or even third story. It’s like sitting down and talking with an old friend.

On the minus side. . . . well, how many movie sequels were as good as the first? Not too many. When writing a sequel, you have to get into the same mental zone you were in when you wrote the first story. If the first story was a lighthearted farce, the second story has to close to that tone. If the first story was dark and serious, the sequel cannot be at the other end of the spectrum. Striking the balance between the new storyline and the old characters is difficult; Too much of one hurts the other.

Sometimes, writers feel they have to top the first story with the sequel. Bigger story, more action, higher stakes sort of idea. But I think trying for that will result in a failed sequel. A sequel has to have ties to the original story, but it can’t be a clone of the first. It also depends on how final the first story ends. Some stories end and are not easy to continue; characters die, the situation ends in a way that makes it difficult to continue, or the characters have nothing more to offer.

But sometimes, the characters do have something more to offer and it’s simply finding a place and a plot where they can be used. Maybe the background still has some good fodder for stories, or there are a few loose ties from the first story that can be explored.

I have found a couple of my characters who have both something more to say and who can continue. One is Precentor Gazeal, the Manei Domini precentor. He’s not finish having his say, not even after my second story about him. Assuming I can work it out, Evacuation will not be the last time Gazeal appears in one of my stories. There are a couple of more characters that seem interested in staying around; again, if I can work it out they’ll be back.

And now I must get back to writing....

Craig

Tuesday, April 23, 2013

Rewriting and Editing

I spent all of last week rewriting and editing three BattleCorps stories I got feedback on from the workshop. I plan to send them to the workshop for a second round of look-overs before submitting them to Jason Schmitzer and BattleCorps. A fourth story is going to need more work done to it before I can send it back to the workshop.

Which brings me to the subject of today's posts: rewrites and editing.
I don't plot out short stories in any detail before I start. Instead, I start with an idea, a couple of scenes in mind, and maybe an ending. The result is I'm not always certain of the ending or how I get there. Stories tend to wonder, or have a plot that needs some work. Rewrites and editing are a must for a writer to know and use, because the number of authors who can write a perfect story in one draft are very few. I'm not one of those....

I always let the story sit for a while -- days, sometimes weeks -- before I start going through them again. It allows the details to fade from my mind, so i can look at it with fresh eyes. It's amazing what you find when you're not up to your eyebrows in writing a story. And since I have several other stories being written at the same time, it isn't hard to leave stories alone for a while.

When I rewrite/edit a story, I concentrate on four things:

1) Word Count -- I always write a bit long, so trimming is a must. That means going through and cutting extra words, compacting diolougue, and rewriting sentaces so they have less words than before.

2) Misspelled and misused words, and grammer. -- It's amazing the things I see when I go through a story I'm rewriting. Misspelled words, wrong verb tense, fragmented sentences, and other little grammer goofs are easier to spot after letting it sit for a while.

3) Plot holes and weaknesses -- This takes up most of the rewriting. Plots needs to be simplfied, characters eliminated, scenes fully explained and described. Does each characters actions make sense in the story's context? Does the plot hold together? Are there any plot points I missed?

4) Continuity and style check -- are there any stupid continuity mistkes? (Wrong rank, 'Mech not available during the time of the story, wrong planet) Are all the style guidelines being followed ('Mech names italicized, epigraphs [The time-place section that appears at the start of scenes] are in the right place, use of meterics)

Depending on how badly the story needs work, it can take anywhere between a couple of days to a full week to complete a rewrite of a story. I also tend to do these in groups of two or three stories, so I can stay "In the grove" instead of bouncing back and forth between rewriting and writing. Once I finish with all three, I'll send them back to the Workshop, and if there are no other major problems, send them to Jason before the end of the month.

That's all for now -- back to work!

Craig