Dichotomy said:
My apologies. I was waiting for "Skulk" to act before I did.
Ugh, I'll take the blame on this one, Dichotomy.
I guess I just made some assumptions that proved not to be valid. So, here are some basics about how we'll run combat.
When you guys get into a scrape, I'll first establish an initiative order. Then, you just need to let me know what your character's intentions are, using as many conditional qualifiers as you feel are relevant/appropriate.
For example: "Tordek will attack the orc with his waraxe until the brute falls, then move on to the next closest enemy and continue the assault. If he falls below 10 hp, he'll withdraw and move adjacent to Jozan in hopes of healing."
Now, obviously, there are plenty of unexpected occurences that might happen (an enemy spellcaster might cast a spell, new enemies enter the combat, etc.) which could disrupt those plans. If they do, I'll pause the action and ask for a new intended course of action. Still, these types of posts help me resolve combats faster, because they do give me a general idea of what your character wants to do.
I should also mention that this method of combat resolution works better at low levels, because there are fewer likely actions that a given character will take. At higher levels the combat becomes so complex that it really has to be resolved round by round.
In any case, there is no need to wait for another character (or enemy) to post his/her actions for a given round. Once I know everyone's intentions, I'll put it all together into a (hopefully) cohesive whole. If I see a sensible course of action that doesn't deviate radically from the PCs intent, and presents no serious drawbacks, I'll take the liberty (as I did in moving William to negate the skulk's cover advantage....in a face to face game, I assume Scotley would have done the same once he was reminded of that fact).
Well, that was long and rambly, but I hope it helps. Please let me know if there are any other questions.
-Krago