In my recent game against spry this came up one time.

He grenaded Tulak (who was adjacent to Zannah). He made Tulak roll first, he failed took damage and then teleported away to a new square adjacent to some other guys. We played it that since Zannah was no longer adjacent she no longer had to make a grenades save, and since there were now more characters adjacent that hadn't yet rolled for grenades that they had to make grenade saves.

We think this is correct based on the wording of grenades

Grenades 30 (Replaces attacks: range 6; 30 damage to target and to each character adjacent to that target; save 11)

and the lawnmower ruling precedents.

If this is indeed the case then Sith Reflexes is extremely powerful...it makes it so that you have to be extremely careful when targeting Tulak with Missiles or Grenades, because you could end up taking them in the face.

I'm not a rules lawyer, but FWIW, this ruling sounds wrong to me. Aren't all of the targets of the grenade/missile set when the target is declared, similar to how all the targets of a Blaster Barrage are set once the BB is declared?

Ok, I recognize that there's a difference between BB and area effect stuff. I do think that it's a really bad thing for the game if entire area-effect abilities can be re-located because of Sith Reflexes. Would this work for Force Lightning 2, so that Tulak teleports beside 2 enemies, so that Palpatine zaps Tulak and those 2 allies of his, rather than the 3 enemies he originally targeted? Or Splash 10...does Tulak get to move after taking damage so that he's beside several enemies before splash damage is rolled? If this is the case then I think we need a change to Sith Reflexes.

.




Ok, but what about as Trevor said lightning where you don't choose order because there isn't a save to make? IMO we need to change Sith reflexes to specifically state that teleporting happens after all damage from the attack/ replaces attack ability is resolved. Yes there may be a precedent about choosing order of resolution, but it would simplify the issue because who in their right mind would ever want their opponent to control who gets targeted by forgetting to resolve Tulak last in an important moment. Simple is better IMO FWIW.

Peanut gallery checking in! (Ignore me if I'm a moron).

1.) Once damage is resolved against Tulak (and he teleports) he would no longer be considered a target correct? So then you wouldn't need to factor where he lands and you can move on to whomever was ORIGINALLY beside him. I'm thinking this way based on how it would play based in (loose) reality. If a grenade detonates in front of a group and one guy catches shrapnel, then teleports, that doesn't stop the other guys by him from catching their share of the shrapnel right? Meanwhile, who cares about the guy who end up near the teleporter post 'port? They were no where near the original grenade.

2.) Quoting gholli69 "Ok, but what about as Trevor said lightning where you don't choose order because there isn't a save to make? IMO we need to change Sith reflexes to specifically state that teleporting happens after all damage from the attack/ replaces attack ability is resolved. Yes there may be a precedent about choosing order of resolution, but it would simplify the issue because who in their right mind would ever want their opponent to control who gets targeted by forgetting to resolve Tulak last in an important moment. Simple is better IMO FWIW."
- I agree with this.

No quick access to a rulebook at the moment nor do I see it stickied in the Rules section.

Please remind me as I'm second-guessing: What is the order of steps in an attack?

Certainly no expert here, but my thinking would be that the characters originally adjacent to Tulak would still have to make the save.
This is purely based on the fact that if Tulak was first to save and failed, and he had 30 or less Hit Points remaining and was therefore defeated, all adjacent characters would still have to save.