Thoras

If we use the Nightsister Acolytes' Coordinated Fire as an example, the requirement that the attack be a part of a combat action is not a part of the event, in the same way that the requirement of the attack coming from an allied Dathomirian Unit is not a part of the event. No, the timing that the trigger event occurs in or the time that the ability is used at doesn't define the trigger event itself. He can use both. Surely you can do better's event is that he is defending and Twice The Pride, Double the Fall's event is an attack.

Individual Tags can be combined together, but not deconstructed, to meet a Requirement.

Any given reactive superpower can only be used once per event triggering it, so the maximum this can reduce is 1 damage per source.

Yes. This is a timing reference rather than a requirement.

Characters don't actually have superpowers when dazed, so cold snap would not affect anyone.

This is still a requirement, yes. In the end, it must be a Galactic Republic Trooper or a Galactic Republic Padawan within range 3. Plo must also not be wounded

Yes Almost. They don't have to try to make an attack, the Unit can declare a combat action and then have the individual characters choose to not perform an attack. In terms of trying to declare the specific attack types, you need an enemy character in the appropriate Range/Engagement to do that.

Yes No

Page 15 of the core rulebook speaks to this interaction. When a rule that says something can happen conflicts with another saying it cannot, the cannot will take priority. The ability needs to provide permission to get around that core rule in order to override it.

Yes This is not correct, no. Some abilities don’t require a specific character or unit to have caused the wound, just that an enemy unit was wounded.

Yes

Yes, using this ability costs the Unit one of its two Actions and at least 1 Force This is one way in which it could resolve, yes.

Yes No. The damage is only suffered if one of the characters advanced.

Unless some other rule prevents it, yes. Yes, "this unit" always refers to the unit whose card the rule is on.

Those are different steps in the attack sequence, but not necessarily different events. The same event (depending on which event it is) can trigger at various different timing steps. Coordinated Fire also occurs at the start of step 5 rather than 3.

The damage is put into the damage pool of the ongoing attack in this situation, which is then applied as a "lump sum" for the entire attack. There is no distinction in terms of where different damage in the damage pool is coming from.

Conditions from an Expertise chart would be added in 10a or 10b of the attack timing chart (Feb 2024 version). If this involves applying a condition that a unit already has, it will instead become a damage and be applied immediately at that point.

It is an enemy effect to the unit being wounded, but no specific character or unit is considered to have caused the effect.

"Infinite loop" is too strong a term, but it would be "shuffled" into the otherwise empty deck and then be the only card available to draw next turn. In this scenario, he would be "shuffled" into the otherwise empty deck and then you could choose whether to draw him or play your card from reserve next turn.

The event that "Coordinated Fire" is reacting to is that an attack was made. There are further conditions on what type of attack/who it came from, but the event itself is an attack. The event that "I'm always first, kid" is reacting to is that a combat action was made. There are further conditions on what type of combat action/who it came from, but the event itself is the combat action. Rex cannot trigger his reactive in this situation, but not because its the same event (it's not). I'm always first kid can only be used with a Clone Trooper Supporting Unit's combat action, where as Commander Wolffe is a secondary character. This is possible now that its a supporting unit making a combat action, but Captain Rex is not reacting to the second attack, he's reacting to the overall combat action. It would go like this The unit starts its combat action The First character starts its attack (Wolfpack can then coordinated fire during that attack) The first character ends its attack The second character starts its attack The second character ends its attack The unit ends its combat action (CC-7567 Captain Rex can now "I'm always first, kid" at this point)

Yes

If you know ahead of time you can’t fit, you just don’t perform that rule. The placement is lost. If you go to move the model and only then find out you can’t place him, you put him back where he was as best as possible, following the margin of error rules from the challenger document

Yes

This depends on a lot of factors. In general, yes, but the specifics of the scenario are vitally important. The thing to internalize is that Strained will occur at the first possible instance it can, the first time a triggering action has hit the "after the effect is resolved" timing. Yes (Also, note, she doesn't get a Recover, she has Heal's on her combat tree). The Heals occur in Step 8 and Strained triggers/resolves in Step 10e in this scenario Yes. Life Drain occurs in step 10c of an attack and Strained would resolve in 10e (if nothing else that triggers it has occurred first) (Also, same note as above, it is a Heal rather than a Recover).

It does not. The attack generated by Mind Trick occurs before Mind Trick itself is fully resolved. You use Mind Trick, it starts resolving, the first attack is ended, the new attack is performed (and any other rules that re-actively occur as a result of that attack, etc.), then Mind Trick is finished resolving. We'd have to know which specific thread to fully clarify for you, but the general rule is Flipping your stance card is an "Any time" ability, which isn't actually available at literally any time. An "any time" rule can't be used when another ability or effect is resolving. Since the attack generated by Mind Trick occurs within the resolution of Mind Trick itself, you have an effect currently resolving and are thus unable to make use of "any time" rules.