1E "Initiative"

[boot]

One topic that often comes up from newcomers to 1E is the special version of initiative that is used in the game.  People are used to rolling initiative in other rpgs to decide the order of actions in a combat round.  Players are often confused when it comes to "initiative" in 1E because the game doesn't use a traditional initiative throw (though a traditional throw is used in 2E).

Initiative in 1E is extremely simple.  After I got the hang of it, it became one of the chief things that I love about first edition D6 Star Wars.

Let me show you...





1E INITIATIVE

In 1E, narrative is king.  The GM describes the opening circumstances in a combat round.  "Two stormtroopers approach, each casually holding their blaster rifles.  'You there!'  You hear from their mechanical voice boxes, 'Let's see some ID.'

Then the players react to that, telling the GM what they want their characters to do (this is the Declaration Segment).  Jon says, out of character, "We don't have any valid ID.  I'm going to draw on 'em.  I'll pull my blaster and fire at the one on the left."

Fred agrees.  "Yeah, my character will fire his blaster rifle at the one on the right."  

The Ref mentally notes that Jon's character is drawing while firing, while Fred's character already has his weapon in his hands.



Initiative is sometimes organic.  No type of roll is needed at all.  If it is clear, though the situation and the intended actions of the PCs and NPCs, then no roll will be consulted at all.  The Ref just directs the action as seems logical.



When one character can effect another character, as when one character is shooting a blaster at another, then some type of dicing is needed to see which character fired first.



In our situation above, the Ref will handle the combat in two stages.  Jon's character is firing at the left stormtrooper.  That will be handled separately from Fred's character firing at the right stormtrooper.  If the left stormtrooper were firing at Fred's character, then that would be a situation where all four characters would be regarded together.  But, as it stands, the Ref will resolve the Jon-->Left Trooper situation, then he will resolved the situation between Fred and the Right Trooper.



JON AND THE LEFT TROOPER

Jon is pulling his blaster from his hip holster and firing at the left trooper.  Mentally (the Ref does not inform the player), the Ref decides that the trooper will dodge and fire back at Jon's character.

Behind the screen, the Ref rolls the trooper's 4D Dodge.  He gets 6.  Range is Short, so Jon's target number is 16.

The Ref says to Jon, "As you turn, the trooper quickly raises his blaster to fire back."  This does two things.  It alerts Jon to the stormtrooper's action this round--the trooper is firing at Jon just as Jon is firing at the trooper (it's information that Jon's character could pick up in a split second).  Second, it gives Jon an opportunity to Dodge the trooper's shot.  (Jon doesn't declare a Dodge).

Behind the screen, the Ref rolls the trooper's attack.  4D blaster skill, -1D due to armor, -1D due to the Dodge.  2D are rolled, getting a total of 3.

Jon, the player, rolls the attack for his character.  5D+1 blaster skill, -1D for the draw.  4D+1 is rolled, getting a total of 17.

The rolls for the blaster shots serve two purposes:  As initiative, to decide who shoots first.  Then as attacks, to see if a shot is successful.

In this case, Jon's roll is higher.  Jon's character spins, pulls his weapon, and fires, hitting the trooper, before the trooper can lift his weapon and fire at Jon.  

Jon's shot is successful because his attack of 17 is higher than the trooper's 16 Dodge.

The trooper never gets off his shot (or, for effect, the GM could describe a shot that went wild, blowing a divot in the ceiling.

Jon's blaster bolt slams into the trooper, knocking him down, smoking his armor.  Damage from Jon's heavy blaster pistol is 5D.  Rolled, the damage is 19.

The trooper's defense is 2D STR +1D armor.  3D are rolled, getting 14.  This means the trooper is now Wounded.





FRANK AND THE RIGHT TROOPER

Frank has declared that he is going to raise his blaster rifle and fire at the right trooper.

The Ref has decided that the trooper is going to tongue his helmet comm to contact the patrol outpost and alert them to send back up for these Rebels.

So, we've got an initiative situation here.  Can Frank shoot the trooper before the trooper can contact the outpost?

In order to find out, we compare Frank's blaster attack total with the trooper's Mechanical throw to operate the comm.

Frank's blaster attack is 3D, getting a total of 8.

The trooper's throw to operate the comm is 2D, getting a total of 6.

So, what happens?  Frank's blaster attack wins initiative.  The shot happens first.  Range is Short, though, with a difficulty of 10.  So, the shot misses the trooper.

The allows the trooper's action to go through.  The comm roll is a 6, and the GM has set a difficulty of Very Easy to operate the comm.  Since 6 beats the 5+ required to operate the comm, the trooper's message goes through.





THE COMBAT ROUND

1.  2 Troopers Approach, asking for ID.
2.  Jon swings around, pulls his blaster, and blasts the one on the right.  He goes down with a smoking hole in his armor, wounded.
3.  Frank raises his blaster rifle but misses the other trooper.
4.  The standing trooper calls into the outpost, requesting back up troopers to this location.





INITIATIVE

What I like about this is a few things.  First, there is no extra initiative throw.  That makes the game move faster.  Often, it is obvious the way the action should flow, and the GM just describes the action in a logical order.

Second, when initiative is needed to see what event happens first, the character uses the skill appropriate to what he is doing.  If he's shooting, he uses his blaster skill.  If he's moving, he uses his Dexterity.  If he is using his helmet comm, then it is Mechanical.  Characters will be quick where they are skilled and not as quick in the areas where they are not as experienced.

New player confusion often centers around the dual nature of a roll used for initiative.  When Blaster skills is used, for example, the roll total is first considered as initiative and then the same roll is considered separately and secondary as a blaster attack.  It is sometimes confusing to those new to this system when a character rolls a blaster attack, loses initiative, is shot, and then his blaster attack is regarded as if it never happened.  This happened to the Left Stormtrooper in the above example.  Jon won initative with his higher roll, and the shot was successful.  Therefore, the trooper's blaster skill roll was only used for initiative and not as a blaster shot.  Jon shot and wounded the trooper before he could fire.


 









 

[boot]

IN SUMMARY


The GM should use his best judgement for who goes first and the order of actions.  No rolls needed.

When in doubt, as when two people are shooting at each other, simply have each side roll their skill.  The highest roll is taken first.  In this way, the skill roll serves two purposes.  First, it is taken as an initiative roll.  Second, it is taken as a skill roll as intended by the player.

Sometimes people get confused when Larl fires at a stormtrooper:  Both roll their blaster skills, and Larl has the higher roll (wins initiative) and hits and damages the trooper.  In this case, the trooper never fired.  His roll was strictly considered for initiative only.  He lost initiative, and thus was not able to fire back (because he got hit before he pulled the trigger).

And, sometimes, that same situation will happen to player characters, confusing the player.  They'll ask, "Now, I rolled my blaster skill...why was it again that I didn't fire my blaster."  You'll have to explain to them, "Your skill roll serves two purposes, first as initiative and then as a blaster attack throw.  Since you lost initiative, the trooper fired first, hitting you, which means that you cannot take any more actions during the round.  Your actual blaster skill roll never served as an actual attack."

The system is quick-n-easy, like most things First Edition.  I love it.  Once you get the hang of rolling your combats like this, you'll probably fall in love with it too.

It's just a little quirky feeling for some players used to rolling initiative for combat rounds, each and every round.  

You'll find that the 1E SW method uses a lot less rolls and speeds up the game.

It may not be intuitive the first time you use this initiative method, but after you get the feel for it, you'll all of a sudden why more games don't use the same method.  I find myself wanting to adapt the method to the other RPGs I play.

[Starbeard]

I think you really hit it here, Boot.

I learned on 2nd edition initiative, and the first time I read the first edition initiative rules I was unimpressed. It just seemed too ambiguous. But then, after going back and reading it again later, and then actually trying them in a few test fights, I discovered that I actually prefer them.

Most of the time, in most game systems, initiative order really doesn't matter to anyone except the two people attacking and defending. If three rebels are facing off against three stormtroopers, each trading shots, then there's no need to determine the exact order of events: just treat it as three individual duels, each happening simultaneously. If there's a fourth rebel who's running around the room trying to fix a computer console, as long as no one is shooting at him then that happens automatically and simultaneously as well. In fact, I'd go as far as to say that even in 2nd edition games where we would use strict initiative, we still defaulted to this kind of understanding, and sort of ignored the initiative rolls unless it actually mattered whether you'd get your action off before getting hit.

It also helps to solve the problem of many games, where you are supposed to declare actions and then roll initiative to carry them out. Even in games where you are supposed to do this (like D&D), almost all groups I've even played in will default to rolling initiative, then waiting to declare their action once it's their turn. It's just easier that way, instead of trying to remember everyone's intended actions, then rolling dice to put them in order, then executing them in initiative order. With first edition Star Wars, you just have everyone declare their actions and roll for it, and if once you've gone around the table there are conflicts of interest, the dice rolls already tell you who went first. Easy peasy.

The only time 1st edition initiative gets complicated is when you have a long chain of actions that affect each other (the number in parentheses will be their dice roll): Rebel A shoots at Imperial α (12); but Imperial α is shooting at Rebel B (15); but Rebel B is diving behind a crate (8) that Imperial β is also diving behind (24), and there's only room for one of them; and Rebel C is shooting at Imperial β (30), and Imperial γ is at a computer console trying to shut off the room's lights (16).

With a situation like that, it seems complicated when you right it out, but in play it still goes pretty fast. Just pick a character, any character, and ask the table, "Is anyone doing anything to this guy? No, great, let's see your roll and move on." Otherwise, if there is a conflict, just follow it down the line until you get to the end, and then you can adjudicate either of two ways: 1) have the two characters at the end of the line compare results to see who goes first, and then follow the line down from there, like a domino effect; or 2) look at everyone's rolls simultaneously and resolve them from highest roll to lowest roll.

Using method 1 (the more tactically interesting method, IMO):

1. Imperial γ (16) loses vs Rebel C (30), so Rebel C shoots and hits Imperial β before the lights go out;
2. Imperial β was shot and hit, so his manoeuvre to dive behind the crate is void;
3. Imperial γ (16) wins vs Rebel B (8), so the lights go out before he performs his action, and now his roll is low enough than he trips in the darkness and falls over, still exposed;
4. Imperial γ (16) wins vs Imperial α (15), so the lights go out before he shoots at Rebel B; he wins (15) vs Rebel B (8), and Rebel A (12), and so shoots at Rebel B before his manoeuvre starts, but because it is dark his roll misses;
5. Imperial γ (16) wins vs Rebel A (12), so when he shoots at Imperial α the lights have already gone out, and he misses.

Using method 2 (the easier method, IMO):

1. Rebel C (30) shoots at Imperial β and hits;
2. Imperial β (24) is hit, so his action is voided;
3. Imperial γ (16) shuts off the lights;
4. Imperial α (15) shoots at Rebel B in the dark and misses;
5. Rebel A (12) shoots at Imperial α in the dark and misses;
6. Rebel B (8) tries to dive behind the crate but trips in the dark.

You'll notice the effects of the round are the same, but Rebel B was able to act farther up the line using method 1, so depending on the situation which method you use can have a big effect on how the round plays out.

[boot]

Aug 6, 2018 17:58:54 GMT -6 Starbeard said:

The only time 1st edition initiative gets complicated is when you have a long chain of actions that affect each other (the number in parentheses will be their dice roll): Rebel A shoots at Imperial α (12); but Imperial α is shooting at Rebel B (15); but Rebel B is diving behind a crate (8) that Imperial β is also diving behind (24), and there's only room for one of them; and Rebel C is shooting at Imperial β (30), and Imperial γ is at a computer console trying to shut off the room's lights (16).

It's helps to match actions.

As you say, this is a complicated scenario.  I would just have everyone roll their skill and take it in normal initiative order.



Action 1:  

(Rebels)

Rebel A shoots at Imperial Alpha (don't know how to make those nifty symbols). 12.

Rebel B dives.  15.

Rebel C shoots at Imperial Beta.  30.



(Imperials)

Imperial Alpha shoots at Rebel B.  15.

Imperial Beta dives.  24.

Imperial Gamma shuts off lights.  16.





LESS COMPLICATION AS IT PLAYS OUT...

One thing to note:  These complicated combat rounds (that don't happen all that often in my experience) get a lot less complicated quick.

Watch what happens to this complicated scenario once the first actor, Rebel C, fires his blaster...



Rebel C acts first with his 30 blaster attack.  He's firing at Imperial Beta.  If Rebel C hits, then you are not going to have to worry about Imperial Beta and his contested dive with Rebel B.  That's because Imperial Beta will at least be stunned, using the 1E rules.  If he's hit, the minimum damage is stun.  And, he loses all remaining actions (in this case--all his actions).

And, that makes Rebel B's dive moot.  It happens (if the 15 beats the difficulty to dive, which I'm guessing it would).  The GM just describes this happening.

1.  Rebel C blasts Imperial Beta.  Beta is hit and goes down.

2.  Imperial Gamma shuts off the lights.

This could be the end of the round right here, if it is so dark that Rebel B can no longer see his cover that he would dive behind.  And, Imperial Alpha would no longer have a shot at Rebel B.  And, Rebel A would no longer have a shot at Imperial Alpha.

End of combat round.

Looked complicated, but like a house of cards, the complicated combat fell apart very quickly.  Simple.





If There Is Enough Light to Finish Actions...

1. Rebel C blasts Imperial Beta. Beta is hit and goes down.



2. Imperial Gamma shuts off the lights.
 GM now puts a penalty on dice throws requiring sight.

3.  Rebel B dives for cover (if the 15 throw beats the difficulty with the darkness penalty).  Ties go to the PCs, which is why Rebel B goes now.  And, with Rebel B completely covered, Imperial Alpha no longer has a shot at him.

4.  Rebel A shoots at Imperial Alpha while the trooper is tracking, with his weapon, Rebel B as the rebel moves.

Again, not as complicated at it first seemed.

[Starbeard]

Exactly. In my experience things rarely get that complicated, but even if they do, once you figure out the chain, the first one or two actions will un-complicate things very quickly, and the rest of the round takes care of itself.

It's a neat initiative system, and one that I'd consider porting over to other games, even D&D.

[boot]

One of the things integral to 1E combat is the minimum stun damage rule on a hit. Without it, the combat stay complicated.

People don't always realize this when they go fiddling with the damage system, using one of the other versions.

[Starbeard]

I agree. Whenever they changed the automatic stun rule (rules companion? 2nd edition?) was when the initiative system had to change too.

Even that I think could be ported over to other games. In the wargaming world it's not uncommon to have a rule like that: both sides roll for effectiveness, the side with the higher effectiveness wins the bout and damages the other side. In the RPG world, Tunnels & Trolls is a good example of the same thing: each round, either one side takes damage or the other does.

This is essentially the same. Whoever takes damage (even if just a stun) forfeits the turn. Their action was ineffective. Only one side gets to 'win' the round (unless, of course, you roll exactly the same number, then I'd argue for a simultaneous attack on both sides).

[boot]

Aug 8, 2018 12:01:27 GMT -6 Starbeard said:

Only one side gets to 'win' the round (unless, of course, you roll exactly the same number, then I'd argue for a simultaneous attack on both sides).

....But, you can have a situation where two Rebels are firing at one Stormtrooper.

Rebel 2 fires first, and misses.

Imperial fires at Rebel 2 and hits.

Rebel 1, who is closer to the Imperial, fires and hits.



Here, the Imperial got hit but was able to get his actions for the round done first.

[Starbeard]

Aug 8, 2018 17:36:24 GMT -6 boot said:

Aug 8, 2018 12:01:27 GMT -6 Starbeard said:

Only one side gets to 'win' the round (unless, of course, you roll exactly the same number, then I'd argue for a simultaneous attack on both sides).

....But, you can have a situation where two Rebels are firing at one Stormtrooper.

Rebel 2 fires first, and misses.

Imperial fires at Rebel 2 and hits.

Rebel 1, who is closer to the Imperial, fires and hits.



Here, the Imperial got hit but was able to get his actions for the round done first.

That's true. Again it goes back to the idea of the chain of events, which seems pretty central to the whole elegance of the system. I was oversimplifying it by just referring to the basic mano a mano initiative rule between two characters. But the nice thing is that the core premise still stands no matter how many characters you add. Each round, if there's a direct conflict, you either get to take your action or you don't, based on how well you roll compared to the other actions being taken against you.

[boot]

Yep. Total agreement.

The other thing I like about 1E's initiative system, besides the fact that sometimes initiative is organic and not rolled at all, is that the character, when rolling initiative, rolls the skill that he's using. If he's firing his blaster, then he uses his Blaster skill. If he picking a lock, then he uses Security. If he searching a terminal for the Death Star plans, then he uses Computer Programming and Repair.

A character may be quick with a blaster, but he may stumble a bit and take some time when operating a computer terminal.

I like this alot, when compared with the one-size-fits-all initiative of 2E and most other RPGs. I think this is a superior way to do it.