Finished...again.
So I think I finally wrapped up Firestar. I kept getting hung up on the last two chapters. There was a lot I wanted to put in (at one point it needed an extra chapter). But I finally bit the bullet, asked myself who the story was about, and what was the question, and did it.
I think Chapter 20 may be a bit weak. We'll see.
I finished it, now I have to do the synopsis, and fire it off to the agent. When I double-checked the address on his website, I learned that Steve Mancino has left the agency and moved to Philly. Okay.
On other writing subjects, I may have sold Spiked!. An anthology was looking for fantasy short stories with an ending that was a little spooky. Having the bad guy still alive when he's sectioned on a sawmill is spooky. And I was true to the legend of creatures like dryads (and mere-folk): as long as you are with them, nothing bad can happen to you. She left him, he gets cut to pieces.
The pay isn't great, but a writing credit is a writing credit, and that's important. Now I can start focusing on the rest of the dryad stories. And writing new ones. There's this idea of a spindizzy, and...
Saturday, May 31, 2008
Monday, May 26, 2008
Enthusiasms -
I fear I've fallen for temptation yet again. This last weekend was Enfilade!, the largest miniatures convention in the Pacific Northwest. It is organized/run by NHMGS, part of Historical Miniature Gamers Society, and includes people from Oregon, Idaho, Washington, and British Columbia. A lot of games are put on, and one can get enthused by some game you were in. This year was a good example of that.
As usual, I put on, or helped put on, two games, both of which I wrote the rules for. The first was Little Big Battles, 6mm Napoleonics where two 3-figure stands are a battalion, one 2-figure mounted stand is a pair of squadrons, and a gun with 1-3 figures is a battery. You can run multiple corps with these rules. We use a form of competitive die throw first done in DBA for combat. Things feel right with the way things go.
The other (in the evening) was King's War, pike and shot, 1640-1695. Jeff did this one, I just helped. It's set in 1672 at the start of King Louis' Dutch War. This is always popular, and we drew quite a crowd. The scenario needs work, but people had a good time.
While the King's War game was in progress I found myself going over to watch Bruce McFarlane's Torgau game using the Humberside Extensions of DBA.
The Battle of Torgau was a clash between the Austrians and the Prussians in 1760. It took place just outside of Dresden, and the Prussians narrowly won. Frederick the Great tried to do what the Austrians had been doing to him: converge columns on the Austrians from two directions. He had one clumn, and General von Ziethen had the other. Frederick attacked early, and was very bloodily repulsed. He was trying to reorganize his forces preparatory to a defense, and the Austrians had sent off a dispatch claiming victory, when Ziethen showed up. He put in his attack, and was actually bogging down when one of Frederick's subordinates got his men up for one more assault, catching the Austrians from the flank and rolling them up. It kicked the Austrians out of Saxony (again) for the winter, and was a major step towards making them seek peace. It was also one of the bloodiest battles of the Seven Years War (only Zorndorf was bloodier).
Tony Barr of the Society of Ancients wanted a set of Renaissance rules for DBA. So he added sections to the rules, and they are known as the Humberside Extensions. They take DBA, or a form of it, up to 1900. For 20th Century and later, both Tony and others suggest using HoTTs (Hordes of the Things), a fantasy set of rules. I've played them, and they work quite well (tanks are behemoths, artillery and air power are Gods, staff are wizards, machineguns are shooters, and so on).
One of the complaints about DBA (De Bellis Antiquitatis) is that they didn't account for attrition. Critics would point out that two lines of hoplites would shove each other back and forth until somebody was unlucky. That turned out to be the case with hoplite warfare, but the critics displayed their enormous lack of understanding about the period with their claims. Success in hoplite warfare depended upon flanking the enemy, which became common with the pike-armed phalangites. But DBA was originally meant for a campaign game. The competition gamers grabbed it because all armies are 12 stands, and vary in strength from 20-60 castings, something that even casual gamers can paint. BTW, serious competition gamers play only historical match-ups. I've seen both the serious and the unserious competition gamers, and I know the difference!
Bruce McFarlane decided to fix this, and introduced variable morale. This becomes necessary for musket period games as attrition is a serious consideration (though you win faster and with fewer losses if you can outflank the enemy). He tested it, liked what he was seeing, and went forward. In DBA, if you out-dice your opponent in one of the match-ups, the losing stand recoils. Bruce McFarlane put a limit on the number of recoils a stand could suffer before it was removed. Not all stands are rated the same, so you have better troops and poorer troops, and that gives you something else to ponder.
This is all the genesis of the Torgau game at Enfilade! Using a scale of one stand=one brigade, he prepared an Order of Battle. Following successful games of the Battle of Friedland at the Fall-In Con, he brought this game to the Red Lion in Olympia for Enfilade! Six players volunteered for it; I was involved in King's War, so I couldn't play. But I lurked. And I liked what I saw. In 2.5 hours they had a result that was believable (and historical, i.e. very bloody). And they were talking tactics at the end, not rules.
One of the measures I use for how well a set of rules works at a Con is what the players discuss in the bar afterwards. I saw this at a Dragonflight back in the late 80s or early 90s at Seattle University. I'd put on a game of Warfare in the Age of Reason, one of the best SYW sets of rules around (IMHO - and no, writing the siege module for the rules didn't effect my opinion; I wouldn't have written them if I thought the rules were bad). Afterwards we all retired to a Red Robin just down the street. The players at the next table had been in the game, and they were talking about the tactics they'd used, not how they'd manipulated the rules. I'd followed my principles of a good wargames convention game, and they'd had a lot of fun. I incorporated that into a measure of success as a games master.
The three rules for a convention game:
So since that game I've been researching everything I can about the Humberside Extensions, and even tried a solo game using my ACW troops. And I'm in a quandry that I hope to solve: what to base for them? My ACW troops, that's a given. But I've more or less made up my mind to base my SYW troops for Volley & Bayonet. But do I have any others? Funny you should ask that.
I have a veritable unpainted horde of figures for the 9 Years War. They look like Marlburians, but with floppy hats, not tricornes. So those'll go on DBA style stands. And still I'm tempted. Expect updates as I finally decide on what I want to rebase.
I fear I've fallen for temptation yet again. This last weekend was Enfilade!, the largest miniatures convention in the Pacific Northwest. It is organized/run by NHMGS, part of Historical Miniature Gamers Society, and includes people from Oregon, Idaho, Washington, and British Columbia. A lot of games are put on, and one can get enthused by some game you were in. This year was a good example of that.
As usual, I put on, or helped put on, two games, both of which I wrote the rules for. The first was Little Big Battles, 6mm Napoleonics where two 3-figure stands are a battalion, one 2-figure mounted stand is a pair of squadrons, and a gun with 1-3 figures is a battery. You can run multiple corps with these rules. We use a form of competitive die throw first done in DBA for combat. Things feel right with the way things go.
The other (in the evening) was King's War, pike and shot, 1640-1695. Jeff did this one, I just helped. It's set in 1672 at the start of King Louis' Dutch War. This is always popular, and we drew quite a crowd. The scenario needs work, but people had a good time.
While the King's War game was in progress I found myself going over to watch Bruce McFarlane's Torgau game using the Humberside Extensions of DBA.
The Battle of Torgau was a clash between the Austrians and the Prussians in 1760. It took place just outside of Dresden, and the Prussians narrowly won. Frederick the Great tried to do what the Austrians had been doing to him: converge columns on the Austrians from two directions. He had one clumn, and General von Ziethen had the other. Frederick attacked early, and was very bloodily repulsed. He was trying to reorganize his forces preparatory to a defense, and the Austrians had sent off a dispatch claiming victory, when Ziethen showed up. He put in his attack, and was actually bogging down when one of Frederick's subordinates got his men up for one more assault, catching the Austrians from the flank and rolling them up. It kicked the Austrians out of Saxony (again) for the winter, and was a major step towards making them seek peace. It was also one of the bloodiest battles of the Seven Years War (only Zorndorf was bloodier).
Tony Barr of the Society of Ancients wanted a set of Renaissance rules for DBA. So he added sections to the rules, and they are known as the Humberside Extensions. They take DBA, or a form of it, up to 1900. For 20th Century and later, both Tony and others suggest using HoTTs (Hordes of the Things), a fantasy set of rules. I've played them, and they work quite well (tanks are behemoths, artillery and air power are Gods, staff are wizards, machineguns are shooters, and so on).
One of the complaints about DBA (De Bellis Antiquitatis) is that they didn't account for attrition. Critics would point out that two lines of hoplites would shove each other back and forth until somebody was unlucky. That turned out to be the case with hoplite warfare, but the critics displayed their enormous lack of understanding about the period with their claims. Success in hoplite warfare depended upon flanking the enemy, which became common with the pike-armed phalangites. But DBA was originally meant for a campaign game. The competition gamers grabbed it because all armies are 12 stands, and vary in strength from 20-60 castings, something that even casual gamers can paint. BTW, serious competition gamers play only historical match-ups. I've seen both the serious and the unserious competition gamers, and I know the difference!
Bruce McFarlane decided to fix this, and introduced variable morale. This becomes necessary for musket period games as attrition is a serious consideration (though you win faster and with fewer losses if you can outflank the enemy). He tested it, liked what he was seeing, and went forward. In DBA, if you out-dice your opponent in one of the match-ups, the losing stand recoils. Bruce McFarlane put a limit on the number of recoils a stand could suffer before it was removed. Not all stands are rated the same, so you have better troops and poorer troops, and that gives you something else to ponder.
This is all the genesis of the Torgau game at Enfilade! Using a scale of one stand=one brigade, he prepared an Order of Battle. Following successful games of the Battle of Friedland at the Fall-In Con, he brought this game to the Red Lion in Olympia for Enfilade! Six players volunteered for it; I was involved in King's War, so I couldn't play. But I lurked. And I liked what I saw. In 2.5 hours they had a result that was believable (and historical, i.e. very bloody). And they were talking tactics at the end, not rules.
One of the measures I use for how well a set of rules works at a Con is what the players discuss in the bar afterwards. I saw this at a Dragonflight back in the late 80s or early 90s at Seattle University. I'd put on a game of Warfare in the Age of Reason, one of the best SYW sets of rules around (IMHO - and no, writing the siege module for the rules didn't effect my opinion; I wouldn't have written them if I thought the rules were bad). Afterwards we all retired to a Red Robin just down the street. The players at the next table had been in the game, and they were talking about the tactics they'd used, not how they'd manipulated the rules. I'd followed my principles of a good wargames convention game, and they'd had a lot of fun. I incorporated that into a measure of success as a games master.
The three rules for a convention game:
- Make the tactical problem relatively simple;
- Have players throwing dice no later than turn 2;
- Keep everything moving quickly so no one can possibly get bored.
So since that game I've been researching everything I can about the Humberside Extensions, and even tried a solo game using my ACW troops. And I'm in a quandry that I hope to solve: what to base for them? My ACW troops, that's a given. But I've more or less made up my mind to base my SYW troops for Volley & Bayonet. But do I have any others? Funny you should ask that.
I have a veritable unpainted horde of figures for the 9 Years War. They look like Marlburians, but with floppy hats, not tricornes. So those'll go on DBA style stands. And still I'm tempted. Expect updates as I finally decide on what I want to rebase.
Tuesday, May 20, 2008
Another Update --
It's that time, but first a plug. I know Liz Lyon. I met her at the Maui Writer's Conference and Cruise in 2004. She has a new book out: Manuscript Makeover. It is chock full of excellent advice on how to revise your manuscript.
The process of writing can be funny. Some people go all the way through a chapter or short story, then go back and revise. Others use revision as a way to get going so they can write the rest of the chapter. Some write the entire book before revising. Some write the book, and then start all over and write the book again. We writers sure can make a lot of work for ourselves.
I think I'm in the second category, kinda-sorta. I write the chapter, or most of it. I revise constantly. I add, I move things around, and I finally finish it. I send it off for feedback. Then I revise. Then I print it out and copy-edit the thing manually and add my revisions/changes. Then, finally, I print it out again and make copies for the writer's group. If it's Woodinville, it is probably a short story. If it is Phinney Ridge (though we meet at Northgate), it's probably 9-10 pages of a chapter. These latter are read aloud.
Later, much later, I go through it again, first on the computer, and then by hand with a printed copy. Then I collect it all in a copy that once again is sent off for the editorial review.
The members of your editorial review come in a variety of flavors. You must pick them carefully. You don't want "Gosh wow, that was the greatest thing I ever read!" That's nice to hear, but doesn't make you a better writer. You need someone to look at the overall thrust of the story, and you need someone to get into the nuts and bolts.
Look at Wingman. The original draft was terrible. I showed it to someone that I worked with, and he pointed out where I'd gone wrong. I rewrote, then rewrote again. This time it went to my own editorial team. Semi-colons, commas, spelling, split and unsplit infinitives, and ellipses later, I incorporated the changes I wanted. I sharpened the ending (it's subtle). THEN I finally sent it off to the editor/owner of the whole story cycle. He had things that I fixed. I read it to the B&N writer's group, and a couple of other things were fixed. I finally submitted it to Stories On Line. Since then I've made a few more changes to it, fixing minor things that had escaped every one's attention until it was available.
I've gotten almost as much feedback on Wingman as I did on Three Valleys - Sammi. Woof.
There's a lot of work involved in all of this. So it makes perfect sense that Firestar, which I thought was nearly done, is not.
I ran it by one of the editorial team. He pointed out that Corey is mostly an observer in the last two chapters. This is wrong. She has a problem to solve, and she has to solve it. That's what a protagonist does. So I cut scenes, I rewrote scenes, and I am rewriting the last bit of the book completely. That meant I had to rewrite earlier parts of the book, adding scenes, changing others. A lot of work.
However, it is coming together, albeit slowly. Part of Corey's problem is she knows how to beat the Idenux, but she has to convince others that her solution is the correct one. The Families are almost Medieval in their approach to things, and Corey has made some enemies. And she is a neophyte at the political aspects of command. She has to learn how to move and survive (and prosper) in the political environment of the Families where a lot of things are personal.
Then I have to set up the next book, Setosha. But where do I put K-303? That will be interesting.
Are there other things? Engage the Enemy More Closely is on hold. I got to chapter 4, and hit a wall (called Firestar). So I've been copy-editing Different World. I can see changes I need to make in the latter. I also saw where I was working myself into a box, and I think I've backed out from that approach.
In the meantime, Spiked! may have been bought! We'll see. Let's not jeopardize things by talking about it too much.
And after a prolonged absence (or at least it felt that way), I've returned to the world of The Construct. More on that later.
More on everything later.
It's that time, but first a plug. I know Liz Lyon. I met her at the Maui Writer's Conference and Cruise in 2004. She has a new book out: Manuscript Makeover. It is chock full of excellent advice on how to revise your manuscript.
The process of writing can be funny. Some people go all the way through a chapter or short story, then go back and revise. Others use revision as a way to get going so they can write the rest of the chapter. Some write the entire book before revising. Some write the book, and then start all over and write the book again. We writers sure can make a lot of work for ourselves.
I think I'm in the second category, kinda-sorta. I write the chapter, or most of it. I revise constantly. I add, I move things around, and I finally finish it. I send it off for feedback. Then I revise. Then I print it out and copy-edit the thing manually and add my revisions/changes. Then, finally, I print it out again and make copies for the writer's group. If it's Woodinville, it is probably a short story. If it is Phinney Ridge (though we meet at Northgate), it's probably 9-10 pages of a chapter. These latter are read aloud.
Later, much later, I go through it again, first on the computer, and then by hand with a printed copy. Then I collect it all in a copy that once again is sent off for the editorial review.
The members of your editorial review come in a variety of flavors. You must pick them carefully. You don't want "Gosh wow, that was the greatest thing I ever read!" That's nice to hear, but doesn't make you a better writer. You need someone to look at the overall thrust of the story, and you need someone to get into the nuts and bolts.
Look at Wingman. The original draft was terrible. I showed it to someone that I worked with, and he pointed out where I'd gone wrong. I rewrote, then rewrote again. This time it went to my own editorial team. Semi-colons, commas, spelling, split and unsplit infinitives, and ellipses later, I incorporated the changes I wanted. I sharpened the ending (it's subtle). THEN I finally sent it off to the editor/owner of the whole story cycle. He had things that I fixed. I read it to the B&N writer's group, and a couple of other things were fixed. I finally submitted it to Stories On Line. Since then I've made a few more changes to it, fixing minor things that had escaped every one's attention until it was available.
I've gotten almost as much feedback on Wingman as I did on Three Valleys - Sammi. Woof.
There's a lot of work involved in all of this. So it makes perfect sense that Firestar, which I thought was nearly done, is not.
I ran it by one of the editorial team. He pointed out that Corey is mostly an observer in the last two chapters. This is wrong. She has a problem to solve, and she has to solve it. That's what a protagonist does. So I cut scenes, I rewrote scenes, and I am rewriting the last bit of the book completely. That meant I had to rewrite earlier parts of the book, adding scenes, changing others. A lot of work.
However, it is coming together, albeit slowly. Part of Corey's problem is she knows how to beat the Idenux, but she has to convince others that her solution is the correct one. The Families are almost Medieval in their approach to things, and Corey has made some enemies. And she is a neophyte at the political aspects of command. She has to learn how to move and survive (and prosper) in the political environment of the Families where a lot of things are personal.
Then I have to set up the next book, Setosha. But where do I put K-303? That will be interesting.
Are there other things? Engage the Enemy More Closely is on hold. I got to chapter 4, and hit a wall (called Firestar). So I've been copy-editing Different World. I can see changes I need to make in the latter. I also saw where I was working myself into a box, and I think I've backed out from that approach.
In the meantime, Spiked! may have been bought! We'll see. Let's not jeopardize things by talking about it too much.
And after a prolonged absence (or at least it felt that way), I've returned to the world of The Construct. More on that later.
More on everything later.
Subscribe to:
Posts (Atom)