Star Wars First Edition WEG - A Love Story
The 1E D6 Star Wars game has three rule versions.
First. There's the 1E Core rules, as described in the Core Rulebook.
Second. There is the Rules Upgrade. This was a four page set of additional rules that came with all 1E materials in the early days. You can view those four pages HERE or EVEN HERE.
Third. There is the Rules Companion. This book of supplemental rules came out during the 1E run, and once it did, the Rules Upgrade was no longer included with 1E purchases. This supplement included and expanded upon the Rules Upgrade.
What this post is about is:
The Rules Upgrade
...from the perspective of a GM who loves vanilla 1E, Core Rulebook style.
(Refer to the Rules Upgrade via one of the links provided above.)
DIFFICULTY NUMBERS
Sure! Use it! But, it's not really a rule change, per se. It's already in the 1E core rulebook but just not spelled out so clearly. There are optional modifiers charts at the back of the book that suggest changing difficulty for this and that. It's the same thing for the GM to modify difficulty for various reasons.
REVISED COMBAT SEQUENCE
From a pure 1E Core Rulebook perspective, this revised sequence is inferior to the original. First, the sequence requires that Reaction skills are declared and rolled at the start of the round, before any actions are resolved. This puts a straight jacket on the easy flow of actions in the very cinematic core rulebook combat sequence. It focuses the game more on dice rolls and less on incredible Space Opera action as described by the GM. In 1E Core, reaction rolls are never declared. A character can use them to "react" to another character trying to harm him. It's up to the player to use a reaction roll, and he doesn't have to decide until he's shot at--this is information that the attacker should not already know (as he does with this revised system).
Second, the revised combat sequence brings to the game the idea of Haste (which is elaborated upon in the Rules Companion). I have never liked the Haste concept as I think it just brings some chunkiness to a swift and clean system, mucking up the works for no real gain.
Third--and I really dislike this--the revised combat system, the damage roll from a hit is separated from the action roll that achieved the hit. This means that all actions in a segment take place, and if a blaster hit is scored on an enemy, the attacker must wait to roll damage after all characters in the combat round have rolled their actions. Then, you go back to the attacker that scored a hit and roll damage. So, if a character is hit, he still gets to perform his actions--all damage is rolled at the end of the sequence. I find this very unwieldy in a game and proof that upgrade rules are not always better rules.
Fourth, under 1E Combat, if a character is hit, the minimum that will happen to him is that he is stunned. That means that he will lose all his actions for the round if he has not yet acted. The hidden benefit to this is that this simple rule makes complicated combats very easy. The blaster bolts start flying, and early on, when people get hit, they can no longer act--thus the combat is streamlined. The new Upgrade Rules, where damage is considered last in a segment, keeps complicated combats rather complicated--because all combatants still act, no matter what, in that combat segment.
NOTE: That the Upgrade Rules also introduce two versions of Dodge: The Combat Dodge and the Full Dodge. The Combat Dodge is a roll of just the Dodge skill. The Full Dodge is what a dodge is in the 1E Core rulebook: You roll your Dodge and add it to the difficulty to hit you. Again, I think this is unnecessary and just complicates a fast moving game.
In 1E, the Dodge (called a Full Dodge in the upgraded sequence) is a powerful defense. It is what keeps the heroes alive. But, the 1E Core Dodge is only good for one segment. As with all multiple skill use, it degrades every time it is used. This, a player will have to balance that fact with skill use to keep his character safe.
And, the way it is used in 1E makes it not necessary to have to fiddle with Character Points (from 2E). The Dodge is weakened with the other options in the Rules Upgrade, which creates the need for Character Points. Simplicity is degraded, and the crunch feeds upon itself. Rules beget more rules. I prefer the quick, sleek fun of core 1E, unburdened by all this unnecessary extra.
More Complication: Look at the combat example given in the Rules Upgrade. It's just, flat-out, more complicated than that used in Core 1E. And, for what gain?
COMBINED ACTIONS
This is an interesting rule. It allows higher blaster attack values at the cost of lower damage rolls. For example, if two Stormtroopers roll an attack a the same target, both roll 3D for the attack. If a hit is scored, the blaster rifles do 5D damage.
This means that either trooper can roll a maximum of 18, and the damage potential for both hits is 5D twice.
With the combined action rule, you use the highest die code for the base then add +1 pip for every die code used in support. In the above example, the roll would be 3D +3. Now, the maximum roll is 21, and the average roll is skewed up 3 points to 13. Damage, though, is for the single weapon. So the likelihood of hitting increases, but damage remains with a single weapon.
This seems like a good rule to add to a game, but I caution you. This rule is very dangerous, and I would not use it.
First, consider that, in 1E, a character's main defense is his Dodge. He rolls his Dodge skill and adds that to his difficulty. Dodge is his armor--it keeps the character alive--it keeps the character from being hit and damaged. The Combined Actions rule is just going to make it easier for your Heroes to get hit.
Think about it. Five stormtroopers round a corner and fire on your PC. They each have Blaster 3D. Your PC rolls his Dodge and gets a total of 20. The PC cannot be hit this first segment (the PC is more vulnerable later in the round as his Dodge will degrade). This keeps the BIG **** HERO ALIVE!!!!
Now, with Combined Actions, those five strormtroopers coordinate fire. The attack roll becomes 3D + 12! The average roll is 22! The maximum roll is 30! We've gone from no possible hit (against the 20 Dodge) to a likely hit!
Think of Luke Skywalker swinging across the Death Star chasm with Princess Leia on his hip and a squad of stormtroopers blasting away at him. Which one of these scenarios better fits that heroic moment? The 1E Core rulebook version, where five stormtroopers start blasting away at our hero, but our hero escapes unharmed (and rather heroically!). Or, the second, combined fire version, where the hero is hit?
'Nuff said. I suggest strongly that you do not use Combined Actions in your 1E game.
STARSHIP COMBAT
As with normal fire combat, the new version of Starship Combat just mucks up the works and complicates an already graceful, fast and fun system in the 1E Core Rulebook. The changes mirror those in ground combat, and I think the Upgrade is not an improvement.
First. There's the 1E Core rules, as described in the Core Rulebook.
Second. There is the Rules Upgrade. This was a four page set of additional rules that came with all 1E materials in the early days. You can view those four pages HERE or EVEN HERE.
Third. There is the Rules Companion. This book of supplemental rules came out during the 1E run, and once it did, the Rules Upgrade was no longer included with 1E purchases. This supplement included and expanded upon the Rules Upgrade.
What this post is about is:
The Rules Upgrade
...from the perspective of a GM who loves vanilla 1E, Core Rulebook style.
(Refer to the Rules Upgrade via one of the links provided above.)
DIFFICULTY NUMBERS
Sure! Use it! But, it's not really a rule change, per se. It's already in the 1E core rulebook but just not spelled out so clearly. There are optional modifiers charts at the back of the book that suggest changing difficulty for this and that. It's the same thing for the GM to modify difficulty for various reasons.
REVISED COMBAT SEQUENCE
From a pure 1E Core Rulebook perspective, this revised sequence is inferior to the original. First, the sequence requires that Reaction skills are declared and rolled at the start of the round, before any actions are resolved. This puts a straight jacket on the easy flow of actions in the very cinematic core rulebook combat sequence. It focuses the game more on dice rolls and less on incredible Space Opera action as described by the GM. In 1E Core, reaction rolls are never declared. A character can use them to "react" to another character trying to harm him. It's up to the player to use a reaction roll, and he doesn't have to decide until he's shot at--this is information that the attacker should not already know (as he does with this revised system).
Second, the revised combat sequence brings to the game the idea of Haste (which is elaborated upon in the Rules Companion). I have never liked the Haste concept as I think it just brings some chunkiness to a swift and clean system, mucking up the works for no real gain.
Third--and I really dislike this--the revised combat system, the damage roll from a hit is separated from the action roll that achieved the hit. This means that all actions in a segment take place, and if a blaster hit is scored on an enemy, the attacker must wait to roll damage after all characters in the combat round have rolled their actions. Then, you go back to the attacker that scored a hit and roll damage. So, if a character is hit, he still gets to perform his actions--all damage is rolled at the end of the sequence. I find this very unwieldy in a game and proof that upgrade rules are not always better rules.
Fourth, under 1E Combat, if a character is hit, the minimum that will happen to him is that he is stunned. That means that he will lose all his actions for the round if he has not yet acted. The hidden benefit to this is that this simple rule makes complicated combats very easy. The blaster bolts start flying, and early on, when people get hit, they can no longer act--thus the combat is streamlined. The new Upgrade Rules, where damage is considered last in a segment, keeps complicated combats rather complicated--because all combatants still act, no matter what, in that combat segment.
NOTE: That the Upgrade Rules also introduce two versions of Dodge: The Combat Dodge and the Full Dodge. The Combat Dodge is a roll of just the Dodge skill. The Full Dodge is what a dodge is in the 1E Core rulebook: You roll your Dodge and add it to the difficulty to hit you. Again, I think this is unnecessary and just complicates a fast moving game.
In 1E, the Dodge (called a Full Dodge in the upgraded sequence) is a powerful defense. It is what keeps the heroes alive. But, the 1E Core Dodge is only good for one segment. As with all multiple skill use, it degrades every time it is used. This, a player will have to balance that fact with skill use to keep his character safe.
And, the way it is used in 1E makes it not necessary to have to fiddle with Character Points (from 2E). The Dodge is weakened with the other options in the Rules Upgrade, which creates the need for Character Points. Simplicity is degraded, and the crunch feeds upon itself. Rules beget more rules. I prefer the quick, sleek fun of core 1E, unburdened by all this unnecessary extra.
More Complication: Look at the combat example given in the Rules Upgrade. It's just, flat-out, more complicated than that used in Core 1E. And, for what gain?
COMBINED ACTIONS
This is an interesting rule. It allows higher blaster attack values at the cost of lower damage rolls. For example, if two Stormtroopers roll an attack a the same target, both roll 3D for the attack. If a hit is scored, the blaster rifles do 5D damage.
This means that either trooper can roll a maximum of 18, and the damage potential for both hits is 5D twice.
With the combined action rule, you use the highest die code for the base then add +1 pip for every die code used in support. In the above example, the roll would be 3D +3. Now, the maximum roll is 21, and the average roll is skewed up 3 points to 13. Damage, though, is for the single weapon. So the likelihood of hitting increases, but damage remains with a single weapon.
This seems like a good rule to add to a game, but I caution you. This rule is very dangerous, and I would not use it.
First, consider that, in 1E, a character's main defense is his Dodge. He rolls his Dodge skill and adds that to his difficulty. Dodge is his armor--it keeps the character alive--it keeps the character from being hit and damaged. The Combined Actions rule is just going to make it easier for your Heroes to get hit.
Think about it. Five stormtroopers round a corner and fire on your PC. They each have Blaster 3D. Your PC rolls his Dodge and gets a total of 20. The PC cannot be hit this first segment (the PC is more vulnerable later in the round as his Dodge will degrade). This keeps the BIG **** HERO ALIVE!!!!
Now, with Combined Actions, those five strormtroopers coordinate fire. The attack roll becomes 3D + 12! The average roll is 22! The maximum roll is 30! We've gone from no possible hit (against the 20 Dodge) to a likely hit!
Think of Luke Skywalker swinging across the Death Star chasm with Princess Leia on his hip and a squad of stormtroopers blasting away at him. Which one of these scenarios better fits that heroic moment? The 1E Core rulebook version, where five stormtroopers start blasting away at our hero, but our hero escapes unharmed (and rather heroically!). Or, the second, combined fire version, where the hero is hit?
'Nuff said. I suggest strongly that you do not use Combined Actions in your 1E game.
STARSHIP COMBAT
As with normal fire combat, the new version of Starship Combat just mucks up the works and complicates an already graceful, fast and fun system in the 1E Core Rulebook. The changes mirror those in ground combat, and I think the Upgrade is not an improvement.
WaterBob said:
Although I do not recommend using Combined Actions in your 1E based game, here are a few House Rule ideas to keep the rule in check.
COMMAND SKILL
Combined Fire must be directed by a commander. A commander can be the best shot among his stormtrooper, yelling out commands to his fellow soldiers. Or, the commander can be an officer directing fire. Or, the commander can be a forward observer or communications operator or squad leader. Whomever. A commander must be in contact with his troops.
The number of people that can be combined for fire is limited to the commander's Command skill (or his PER code if Command is not improved).
Thus, if a normal stormtrooper doesn't have Command, but has Perception 2D, then he can coordinate fire with himself and two other people. An Imperial Naval Officer, with Command 4D+2, can use the combined fire rule with himself plus 4 others, or just 4 others (if commanding is considered a skill use subject to the multiple action rule).
This makes the command skill very useful. As the multiple action rule kicks in, the commander loses his ability to effectively command as many troops. But, a commander can always command 1 other trooper.
COMMAND ONLY
If you want to be even more restrictive, you can reserve the combined action rules for characters who have Command skill. Those without the skill cannot use combined fire. Those that have the skill operate as described above.
OFFICER BASE
The rule typically works by taking the highest shot from among the group and then modifying that shot by the others. With this rule, the base attack is the Commander's Blaster skill (which may not be the highest Blaster skill among the group), if the commander is participating in the attack. If the commander is just giving orders, then the highest shot (or that trooper designated by the commander) acts as the base skill.
ROLL COMMAND
Another method that could be used is to have the commander roll his Command skill (or PER). He can command other to combine fire for every 5 points of the roll.
Thus...
5+ Command 1
10+ Command 2
15+ Command 3
20+ Command 4
And so on....
HANDLING MULTIPLE FOES IN 1E - THE HERO METHOD
You're running down the corridor, blaster rifle in your grip. Next to you is Chewie, keeping pace. The blast door before flashes open, and all of a sudden, you face 20 stormtroopers, fully armored and equipped, ready to come at you.
How do you handle this using the 1E rules?
First off, as GM, you're NOT going to roll 20 blaster shots at Han (Yeah, I know in the movie, they chased Han, but I need this to fit my example) to figure initiative. That would be a nightmare.
Go straight to the Declaration. "Han, Chewie? What are you going to do?"
"We're going to run as fast as we can in the opposite direction."
Again, I know that, in the movie, the troopers just chased the two. But, THESE troopers in THIS example are all going to raise their blaster rifles and fire at Han and Chewie.
To make it simple, I'll have 10 fire at Han and 10 fire at Chewie.
What about Initiative?
Use common sense. Han and Chewie are turning and running. The troopers are behind them. All troopers can get a shot as the pair run back down the hall.
So, all troopers fire first. Then Han and/or Chewie completes their movement.
In situations where logical initiative is not clear, simply allow the player to choose. Heroes have an edge. They're heroes.
Roll all those attacks?
Nope. You're going to use a house rule (that is suggested by the 1E core book) that is similar to but different than the Combined Actions rule--and this rule doesn't have the problems that the CA rule has.
Roll attacks normally, starting with the highest attack code, or, if all Blaster codes are the same, as is often the case with Stormtroopers, roll the closest attacker first.
You will keep rolling attacks until a trooper misses. And, once you have one miss, you consider that the rest of them miss. If you think about it, this is no more of a stretch with the rules than how the Combined Action rule works. If the first trooper misses, then all 10 end up missing.
"You're running down the corridor, heart pounding in your ears. Blaster bolts fly over your head and shoulders, exploding into the corridor walls, leaving smoking, burning divots."
If a trooper hits, then apply damage, but the rest of the shooters all miss (because the target is no longer where they aimed--the target is now writhing on the floor, collapsed from a stun, or worse).
You're running down the corridor, blaster rifle in your grip. Next to you is Chewie, keeping pace. The blast door before flashes open, and all of a sudden, you face 20 stormtroopers, fully armored and equipped, ready to come at you.
How do you handle this using the 1E rules?
First off, as GM, you're NOT going to roll 20 blaster shots at Han (Yeah, I know in the movie, they chased Han, but I need this to fit my example) to figure initiative. That would be a nightmare.
Go straight to the Declaration. "Han, Chewie? What are you going to do?"
"We're going to run as fast as we can in the opposite direction."
Again, I know that, in the movie, the troopers just chased the two. But, THESE troopers in THIS example are all going to raise their blaster rifles and fire at Han and Chewie.
To make it simple, I'll have 10 fire at Han and 10 fire at Chewie.
What about Initiative?
Use common sense. Han and Chewie are turning and running. The troopers are behind them. All troopers can get a shot as the pair run back down the hall.
So, all troopers fire first. Then Han and/or Chewie completes their movement.
In situations where logical initiative is not clear, simply allow the player to choose. Heroes have an edge. They're heroes.
Roll all those attacks?
Nope. You're going to use a house rule (that is suggested by the 1E core book) that is similar to but different than the Combined Actions rule--and this rule doesn't have the problems that the CA rule has.
Roll attacks normally, starting with the highest attack code, or, if all Blaster codes are the same, as is often the case with Stormtroopers, roll the closest attacker first.
You will keep rolling attacks until a trooper misses. And, once you have one miss, you consider that the rest of them miss. If you think about it, this is no more of a stretch with the rules than how the Combined Action rule works. If the first trooper misses, then all 10 end up missing.
"You're running down the corridor, heart pounding in your ears. Blaster bolts fly over your head and shoulders, exploding into the corridor walls, leaving smoking, burning divots."
If a trooper hits, then apply damage, but the rest of the shooters all miss (because the target is no longer where they aimed--the target is now writhing on the floor, collapsed from a stun, or worse).
TOOTHLESS STORMTROOPERS?
Sometimes it is argued that stormtroopers are under-powered. I argue that they're not. They're exactly the strength that they should be.
In Galaxy Guide 1 - A New Hope, a typical stormtrooper has Blaster 3D, after adjustment for armor. And, this is typical of all base-line stormtroopers in the game.
Luke Skywalker, the HERO of all HEROES, has Dodge 6D. And Dodge, in 1E, is computed by the Dodge roll + Range number.
So...troopers do look toothless, yes?
Let's take a deeper look. And, as we do, remember that the Heroes in Star Wars (original trilogy) rarely, if ever, got hurt, even though all the combats that they encountered. Luke had his hand chopped off, but that's a special case. Darth Vader did the cutting. And, the two droids were both blasted once each. C-3PO was blasted to bits at Cloud City. R2D2 took a bad hit in space combat during Luke's trench run. The only character actually hurt in blaster combat was Leia, when she was grazed on the Moon of Endor.
First off, Luke, as stated above, is the GALAXY'S HOPE! He's not your typical PC. Let's first compare a starting character, Roark Garnet, from page 8 of the 1E core rulebook.
Roark has Dodge 4D+1.
Now, let's put Roark in Luke's position on the Death Star. He's got his synthrope grappled around some piping. A princess is clinging to his kneck and hip. And Roark is about to shove off, crossing the chasm.
Behind Roark, 4 stormtroopers have gotten the blast door open, and they are ready to fire at him. Just above his destination are 4 more troopers gunning for him. Other doors open to ledges around the circumference of the shaft: there are 2 there, 3 over there, and 2 more there. All 15 stormtroopers are going to fire at Roark and the princess has he swings.
The troopers all have effective 3D Blaster skills. Range is Short, requiring a 10+ attack roll. And, Roark will of course use his Dodge, which is now effectively 3D+1 because he's got to use his Climbing/Jumping skill in order to swing across the chasm.
In effect, Stormtroopers are firing 3D vs. 3D +11. Chances are, Roark is going to swing across unmolested.
Unless...the troopers roll very high and Roark rolls very low. The chance is low...but there is a chance. The troopers could get lucky and roll a 16. And, Roark could get un-lucky and roll a 4. And that means at least one of the troopers will hit, spelling disaster for our hero.
That small chance is how it should be with heroes.
With a different game--a grittier, more realistic game--I might be arguing something different. But, man! THIS IS STAR WARS! Where Heroes are BIGGER THAN LIFE!
That, to me, is how it should be in D6 Star Wars.
And, it's not like GMs don't have other options. In GG1, Death Star Troopers are mentioned. These guys are elites. Their Blaster skill is 5D+1.
Sometimes, taking two shots will get the Dodge defense low enough for an attack.
If troopers have time, they can aim. This adds +1D to their attack codes.
If a PC gets action happy, taking too many actions, this lowers his Dodge defense due to the multiple action penalty.
And, let's not forget that stormtroopers almost always outnumber PCs, giving the troopers a lot more "at bats" to score a home run.
Sometimes it is argued that stormtroopers are under-powered. I argue that they're not. They're exactly the strength that they should be.
In Galaxy Guide 1 - A New Hope, a typical stormtrooper has Blaster 3D, after adjustment for armor. And, this is typical of all base-line stormtroopers in the game.
Luke Skywalker, the HERO of all HEROES, has Dodge 6D. And Dodge, in 1E, is computed by the Dodge roll + Range number.
So...troopers do look toothless, yes?
Let's take a deeper look. And, as we do, remember that the Heroes in Star Wars (original trilogy) rarely, if ever, got hurt, even though all the combats that they encountered. Luke had his hand chopped off, but that's a special case. Darth Vader did the cutting. And, the two droids were both blasted once each. C-3PO was blasted to bits at Cloud City. R2D2 took a bad hit in space combat during Luke's trench run. The only character actually hurt in blaster combat was Leia, when she was grazed on the Moon of Endor.
First off, Luke, as stated above, is the GALAXY'S HOPE! He's not your typical PC. Let's first compare a starting character, Roark Garnet, from page 8 of the 1E core rulebook.
Roark has Dodge 4D+1.
Now, let's put Roark in Luke's position on the Death Star. He's got his synthrope grappled around some piping. A princess is clinging to his kneck and hip. And Roark is about to shove off, crossing the chasm.
Behind Roark, 4 stormtroopers have gotten the blast door open, and they are ready to fire at him. Just above his destination are 4 more troopers gunning for him. Other doors open to ledges around the circumference of the shaft: there are 2 there, 3 over there, and 2 more there. All 15 stormtroopers are going to fire at Roark and the princess has he swings.
The troopers all have effective 3D Blaster skills. Range is Short, requiring a 10+ attack roll. And, Roark will of course use his Dodge, which is now effectively 3D+1 because he's got to use his Climbing/Jumping skill in order to swing across the chasm.
In effect, Stormtroopers are firing 3D vs. 3D +11. Chances are, Roark is going to swing across unmolested.
Unless...the troopers roll very high and Roark rolls very low. The chance is low...but there is a chance. The troopers could get lucky and roll a 16. And, Roark could get un-lucky and roll a 4. And that means at least one of the troopers will hit, spelling disaster for our hero.
That small chance is how it should be with heroes.
With a different game--a grittier, more realistic game--I might be arguing something different. But, man! THIS IS STAR WARS! Where Heroes are BIGGER THAN LIFE!
That, to me, is how it should be in D6 Star Wars.
And, it's not like GMs don't have other options. In GG1, Death Star Troopers are mentioned. These guys are elites. Their Blaster skill is 5D+1.
Sometimes, taking two shots will get the Dodge defense low enough for an attack.
If troopers have time, they can aim. This adds +1D to their attack codes.
If a PC gets action happy, taking too many actions, this lowers his Dodge defense due to the multiple action penalty.
And, let's not forget that stormtroopers almost always outnumber PCs, giving the troopers a lot more "at bats" to score a home run.
Joseph_RGG
First Post
Thanks for sharing this! I've not played d6 for at least two decades...it might be time to revisit.
delericho
Legend
Nitpick - Artoo was also blasted on Endor. It probably wasn't the best idea for Han to use him as cover while he was busy trying to open the bunker door...
Still. "I guess I could hotwire this thing."
A Starship Log for use in the game: CLICK HERE.
EASY WAY TO USE DODGE IN YOUR GAME
Sometimes new GMs to 1E Star Wars struggle with Dodge--when to roll it. It can get a bit unwieldy if, as the game book says, that Dodge must be rolled before an attack, but the attack roll is also used for initiative. Dodges don't have to be declared. They are reaction rolls, used in reaction to an attack, and Dodges are not penalized if they are rolled before any other actions during the segment.
So, here's my advice: Run your combat as if no character had Dodge. Don't worry about Dodge. Figure it when you check to see what the difficulty number of the shot will be.
The rules say to roll the Dodge before the attack, but this is only because the Dodging character has to decide whether to use his Dodge skill BEFORE he knows whether the attacker will hit at unmodified range.
The easy way I've found to play this is to assume a character will Dodge every time he is attacked. Even if the attack roll is made against the Dodging character before the Dodge is figured, the Dodger is committed. If the attacker fails to hit just by standard range, the Dodge must still be thrown.
A player may decide, though, that the default for his character is not to Dodge.
In either case, no matter if the default is to Dodge or not Dodge, the player must tell the GM that he intends to change his default (to not Dodge when the character's default is to Dodge) before an attacker makes an attack. Dicing the Dodge can come later, though.
A SIMPLE DODGE EXAMPLE.
We will assume that Sneaky Beet will Dodge (or Melee Parry) every time that he is attacked.
To make this very simple, Beet sees a Stormtrooper at Medium Range. Both Beet and the trooper have their blasters out and readied. Beet will take two shots, and the trooper will only take one.
We're not going to worry at all about Dodge. The default for both PC and NPC is that they will Dodge.
I like rolling real dice when I write these examples, so I will do that here. I don't know how this will play out.
INITIATIVE.
This is an initiative situation. We roll both shots at each other. The higher total is taken as the first shot. See how easy that is?
Sneaky Beet rolls Blaster 5D+1, but he's committed to two shots this round. That's -1D. Roll 4D+1 = 14.
Stormtrooper has Blaster 4D, reduced to 3D for armor. He'll roll 3D = 15.
YES! I rolled it!
SEGMENT 1.
This means that the trooper will act first, and Beet is committed to Dodge.
The trooper's attack is 15.
Beet rolls Dodge, now. Since Beet has technically already fired his blaster (he rolled for initiative), we've got to count that as a skill use. Otherwise, rolling Dodge will get wonky (the initiative roll will not match his attack roll, and that makes for uneasy figuring).
So, the Dodge is made at -1D. His full Dodge is 3D+1. So, he rolls 2D +1. Roll = 7. It takes a 22 to hit Beet.
The trooper's attack goes wide.
Now, it's Beet's turn to fire
He declared two actions, so that's -1D. And, he just used his Dodge, so that's another -1D. So, the second attack is made at -2D, which would be 3D+1.
The trooper is committed to Dodge.
Sneaky Beet rolls 3D+1 = 12.
We don't need to roll the trooper's Dodge because there are no more attacks against the trooper this segment. But, the use of Dodge is considered to have happened and counts as an action for Segment 2. Sometimes, we get to skip rolls this way--which makes the game go faster.
Segment 2.
The only thing that is happening this segment is the Beet is firing at the trooper, and the trooper is committed to Dodge.
Sneaky Beet rolls his second shot. He's at -2D (-1D for two actions, and -1D for using his Dodge last segment). He rolls 3D +1 = 7.
Again, we don't have to roll the Dodge for the trooper. Had Beet hit for regular range, then the trooper would roll it. Still, the trooper was committed either way.
End of combat round.
SUMMARY.
1. Don't worry about Dodge when you are rolling initiative.
2. Consider characters to be committed to Dodging (or default to not Dodging, if the player chooses), regardless of whether the actual Blaster attack would score a hit at range. This forces the target character to decide on the use of his Dodge before he knows whether the foe can hit him at just the range difficulty.
3. When rolling Dodge, penalize it for any skill rolls that were rolled before the Dodge (and the skill rolls used for initiative count), but don't penalize Dodge for any actions declared for later segments.
As in the above example, Beet's Dodge is 4D +1. When he first uses his Dodge, only the initiative throw is made, which is a skill use, which counts as an action for these purposes. Dodge is reduced by -1D. If Beet needed to use is Dodge in segment 1, then Dodge would be penalized further.
4. Note how the combat system allows you to speed up the game by bypassing some rolls, sometimes. Consider when a Rebel has initiative, fires, and stuns a troopers. Any actions that the trooper was going to perform are no longer rolled because the trooper is lying on the ground, in pain from the stun. He loses all actions for the round.
Sometimes new GMs to 1E Star Wars struggle with Dodge--when to roll it. It can get a bit unwieldy if, as the game book says, that Dodge must be rolled before an attack, but the attack roll is also used for initiative. Dodges don't have to be declared. They are reaction rolls, used in reaction to an attack, and Dodges are not penalized if they are rolled before any other actions during the segment.
So, here's my advice: Run your combat as if no character had Dodge. Don't worry about Dodge. Figure it when you check to see what the difficulty number of the shot will be.
The rules say to roll the Dodge before the attack, but this is only because the Dodging character has to decide whether to use his Dodge skill BEFORE he knows whether the attacker will hit at unmodified range.
The easy way I've found to play this is to assume a character will Dodge every time he is attacked. Even if the attack roll is made against the Dodging character before the Dodge is figured, the Dodger is committed. If the attacker fails to hit just by standard range, the Dodge must still be thrown.
A player may decide, though, that the default for his character is not to Dodge.
In either case, no matter if the default is to Dodge or not Dodge, the player must tell the GM that he intends to change his default (to not Dodge when the character's default is to Dodge) before an attacker makes an attack. Dicing the Dodge can come later, though.
A SIMPLE DODGE EXAMPLE.
We will assume that Sneaky Beet will Dodge (or Melee Parry) every time that he is attacked.
To make this very simple, Beet sees a Stormtrooper at Medium Range. Both Beet and the trooper have their blasters out and readied. Beet will take two shots, and the trooper will only take one.
We're not going to worry at all about Dodge. The default for both PC and NPC is that they will Dodge.
I like rolling real dice when I write these examples, so I will do that here. I don't know how this will play out.
INITIATIVE.
This is an initiative situation. We roll both shots at each other. The higher total is taken as the first shot. See how easy that is?
Sneaky Beet rolls Blaster 5D+1, but he's committed to two shots this round. That's -1D. Roll 4D+1 = 14.
Stormtrooper has Blaster 4D, reduced to 3D for armor. He'll roll 3D = 15.
YES! I rolled it!
SEGMENT 1.
This means that the trooper will act first, and Beet is committed to Dodge.
The trooper's attack is 15.
Beet rolls Dodge, now. Since Beet has technically already fired his blaster (he rolled for initiative), we've got to count that as a skill use. Otherwise, rolling Dodge will get wonky (the initiative roll will not match his attack roll, and that makes for uneasy figuring).
So, the Dodge is made at -1D. His full Dodge is 3D+1. So, he rolls 2D +1. Roll = 7. It takes a 22 to hit Beet.
The trooper's attack goes wide.
Now, it's Beet's turn to fire
He declared two actions, so that's -1D. And, he just used his Dodge, so that's another -1D. So, the second attack is made at -2D, which would be 3D+1.
The trooper is committed to Dodge.
Sneaky Beet rolls 3D+1 = 12.
We don't need to roll the trooper's Dodge because there are no more attacks against the trooper this segment. But, the use of Dodge is considered to have happened and counts as an action for Segment 2. Sometimes, we get to skip rolls this way--which makes the game go faster.
Segment 2.
The only thing that is happening this segment is the Beet is firing at the trooper, and the trooper is committed to Dodge.
Sneaky Beet rolls his second shot. He's at -2D (-1D for two actions, and -1D for using his Dodge last segment). He rolls 3D +1 = 7.
Again, we don't have to roll the Dodge for the trooper. Had Beet hit for regular range, then the trooper would roll it. Still, the trooper was committed either way.
End of combat round.
SUMMARY.
1. Don't worry about Dodge when you are rolling initiative.
2. Consider characters to be committed to Dodging (or default to not Dodging, if the player chooses), regardless of whether the actual Blaster attack would score a hit at range. This forces the target character to decide on the use of his Dodge before he knows whether the foe can hit him at just the range difficulty.
3. When rolling Dodge, penalize it for any skill rolls that were rolled before the Dodge (and the skill rolls used for initiative count), but don't penalize Dodge for any actions declared for later segments.
As in the above example, Beet's Dodge is 4D +1. When he first uses his Dodge, only the initiative throw is made, which is a skill use, which counts as an action for these purposes. Dodge is reduced by -1D. If Beet needed to use is Dodge in segment 1, then Dodge would be penalized further.
4. Note how the combat system allows you to speed up the game by bypassing some rolls, sometimes. Consider when a Rebel has initiative, fires, and stuns a troopers. Any actions that the trooper was going to perform are no longer rolled because the trooper is lying on the ground, in pain from the stun. He loses all actions for the round.
Similar Threads
