Also gotta give it a little bit of time to be out in wild before there can actually be Frequently Asked Questions to be had. Why create one FAQ and then have to do another one a few weeks later when players find new interactions to deal with.

Did have one come up I'd like to see, If Quickdraw takes enough damage to push through shields and takes a crit and draws blinded pilot, will he get his attack from his ability before he gets the crit or will blinded pilot kick in and that attack clears the crit?

The biggest issue I can think of is dropping rigged cargo chute on someone's head when they dialed in a red maneuver, so it was legal when dialed in, but illegal when they got o execute it, so their opponent gets to pick their move.

Well, you can (perhaps intentionally) RAW around that.

"Its effects are applied immediately"

"1. Execute the maneuver as normal, but assign a stress token to that ship after the "Check Pilot Stress" step.

2. The player rolls one attack die. On a [crit] result, the ship suffers one critical damage"

Step one has a clearly delineated window in which it takes effect (after you check your stress), and a ship that has not moved is not in that window. Worst case scenario in RAW you get a second (or third, depending on whether the template hits the debris) stress after executing your red maneuver.

Did have one come up I'd like to see, If Quickdraw takes enough damage to push through shields and takes a crit and draws blinded pilot, will he get his attack from his ability before he gets the crit or will blinded pilot kick in and that attack clears the crit?

Our Nationals are this coming weekend and our TO has ruled that Collision Detector does not mean that you avoid any of the effects of the obstacle. He justified this by saying "it would be too powerful for a zero cost card" and just ignored what the rules state about the effects triggering on maneuvers. Even a pre-FAQ ruling on this would be great from FFG as this has the potential to become a nasty debate at our Nationals.

Is there a specific build that could be very dangerous with collision detector? I can't see a reason not to use a 0 point upgrade, but I'm curious if there is a strategy that capitalises on it.

I was practicing with Whisper with CD and after getting used to it found it immensely handy. I wouldn't put CD on if it suffers effects because it actually becomes detrimental. Because it says "can boost, barrel roll, decloak . . . " rather than "may", you can no longer see if you fit with a barrel roll or decloak, and if you don't then have to chose something else. You would HAVE to do it because you can. So you could barrel roll onto an obstacle to your detriment. It actually ends up weakening the phantom rather than strengthening it. Imagine all the times you would have barrel rolled onto an obstacle but were saved by the rules. Decloaking and then taking stress or damage and losing your action is just too great a price to pay.

Our Nationals are this coming weekend and our TO has ruled that Collision Detector does not mean that you avoid any of the effects of the obstacle. He justified this by saying "it would be too powerful for a zero cost card" and just ignored what the rules state about the effects triggering on maneuvers. Even a pre-FAQ ruling on this would be great from FFG as this has the potential to become a nasty debate at our Nationals.

I actually agree that the intention of collision detector is to still suffer the effects of boost/br/decloak onto an obstacle, it just allows to to actually do it if you choose to do so. The ruling on effects only triggering on maneuvres is already iffy due to things like tractor beam and rigged cargo chute. I do think an FAQ would be good to clarify which way they intend though.

TB and Rigged cargo are exceptions because they explicitly state on the card that they trigger obstacles. If they did not state it on the card, obstacle effects would not happen because the rules only say you suffer effects when performing a maneuver that overlaps an obstacle. RAW, Collision Detector does not trigger obstacle effects because boosting, barrel rolling, and decloack get over obstacles are not maneuvers. They may FAQ it, but for now, CD avoids rolling for obstacles.

Would you care to quote the section of the rules that explicitly state that ONLY AND EXCLUSIVELY Manoeuvring over an obstacle triggers it's effects?

You can't because it doesn't actually say that. the rules were written prior to tractor beam, rigged cargo and collision detector so it obviously doesn't reference them, all the rules say is when you maneuver over an trigger the effects. We now have other means of flying through or overlapping obstacles, triggering their effects. Simple you take the effects

@SkyWarp "Did have one come up I'd like to see, If Quickdraw takes enough damage to push through shields and takes a crit and draws blinded pilot, will he get his attack from his ability before he gets the crit or will blinded pilot kick in and that attack clears the crit?"

Quickdraw's card states "Once per round, when you lose a shield token...". If she's losing shields as a result of an attack, this is a unique time for her ability to trigger: during step 7i of the attack timing chart. So, she'd be hit, lose a shield, get her pilot ability free attack, then (after her free attack is complete and all results resolved) the original attack resolves, resuming where it left off in step 7i: removing shield tokens to cancel hit results.

This results in a few interesting timing quirks:

1. Even if Quickdraw takes 4-5 damage and explodes, as long as there was a shield token on her she gets to take her shot before further damage is dealt and she's removed from play.

2. If she's attacked by Whisper (VI, FCS, ACD) and loses a shield, she could fire back before any of Whisper's post-attack abilities trigger, as those all occur in step 8 of the attack timing chart.

This is my first post, and I could be missing something, but it seems logical when I think through it. I'm loving Quickdraw: putting her at range 1 of ships your opponent doesn't want you to hit is great insurance against getting shot down quickly.

Our Nationals are this coming weekend and our TO has ruled that Collision Detector does not mean that you avoid any of the effects of the obstacle. He justified this by saying "it would be too powerful for a zero cost card" and just ignored what the rules state about the effects triggering on maneuvers. Even a pre-FAQ ruling on this would be great from FFG as this has the potential to become a nasty debate at our Nationals.

I actually agree that the intention of collision detector is to still suffer the effects of boost/br/decloak onto an obstacle, it just allows to to actually do it if you choose to do so. The ruling on effects only triggering on maneuvres is already iffy due to things like tractor beam and rigged cargo chute. I do think an FAQ would be good to clarify which way they intend though.

TB and Rigged cargo are exceptions because they explicitly state on the card that they trigger obstacles. If they did not state it on the card, obstacle effects would not happen because the rules only say you suffer effects when performing a maneuver that overlaps an obstacle. RAW, Collision Detector does not trigger obstacle effects because boosting, barrel rolling, and decloack get over obstacles are not maneuvers. They may FAQ it, but for now, CD avoids rolling for obstacles.

Would you care to quote the section of the rules that explicitly state that ONLY AND EXCLUSIVELY Manoeuvring over an obstacle triggers it's effects?

You can't because it doesn't actually say that. the rules were written prior to tractor beam, rigged cargo and collision detector so it obviously doesn't reference them, all the rules say is when you maneuver over an trigger the effects. We now have other means of flying through or overlapping obstacles, triggering their effects. Simple you take the effects

The reverse can also be asked of you : please quote the part of the rules that says you suffer obstacle effects when you land on one in ALL other circumstances that aren't maneuvers. You can't because it doesn't exist.

FFG has had ample opprtunities to FAQ this part of the rules since Tractor Beam but hasn't. The fact that the tractor beam rules are specifically stated on the reference card makes me rhink FFG doesn't want a blanket rule on non-maneuver effects

Our Nationals are this coming weekend and our TO has ruled that Collision Detector does not mean that you avoid any of the effects of the obstacle. He justified this by saying "it would be too powerful for a zero cost card" and just ignored what the rules state about the effects triggering on maneuvers. Even a pre-FAQ ruling on this would be great from FFG as this has the potential to become a nasty debate at our Nationals.

I actually agree that the intention of collision detector is to still suffer the effects of boost/br/decloak onto an obstacle, it just allows to to actually do it if you choose to do so. The ruling on effects only triggering on maneuvres is already iffy due to things like tractor beam and rigged cargo chute. I do think an FAQ would be good to clarify which way they intend though.

TB and Rigged cargo are exceptions because they explicitly state on the card that they trigger obstacles. If they did not state it on the card, obstacle effects would not happen because the rules only say you suffer effects when performing a maneuver that overlaps an obstacle. RAW, Collision Detector does not trigger obstacle effects because boosting, barrel rolling, and decloack get over obstacles are not maneuvers. They may FAQ it, but for now, CD avoids rolling for obstacles.

Would you care to quote the section of the rules that explicitly state that ONLY AND EXCLUSIVELY Manoeuvring over an obstacle triggers it's effects?

You can't because it doesn't actually say that. the rules were written prior to tractor beam, rigged cargo and collision detector so it obviously doesn't reference them, all the rules say is when you maneuver over an trigger the effects. We now have other means of flying through or overlapping obstacles, triggering their effects. Simple you take the effects

The reverse can also be asked of you : please quote the part of the rules that says you suffer obstacle effects when you land on one in ALL other circumstances that aren't maneuvers. You can't because it doesn't exist.

FFG has had ample opprtunities to FAQ this part of the rules since Tractor Beam but hasn't. The fact that the tractor beam rules are specifically stated on the reference card makes me rhink FFG doesn't want a blanket rule on non-maneuver effects

Sure lets break it down one sentence at a time shall we, here is the relevant section from the RRG:

OBSTACLES

Obstacles acts as hazards that can disrupt and damage ships. When a ship executes a maneuver, if its base or maneuver template overlaps an obstacle token, it executes its maneuver as normal but suffers an effect based on the type of obstacle:

• Asteroid: The ship must skip its “Perform Action” step this round. After skipping the “Perform Action” step, it rolls one attack die. On a Boom result, the ship suffers one damage; on a Kaboom result, it suffers one critical damage. While a ship is overlapping an asteroid, it cannot perform any attacks.

• Debris Cloud†: After the “Check Pilot Stress” step, the ship receives one stress token. After the “Perform Action” step, it rolls one attack die. On a Kaboom result, the ship suffers one critical damage. The ship can still perform attacks

Let dissect shall we:

Obstacles acts as hazards that can disrupt and damage ships.

A clear indication that obstacles are meant to deal damage when you fly through them or land on them.

When a ship executes a maneuver, if its base or maneuver template overlaps an obstacle token, it executes its maneuver as normal but suffers an effect based on the type of obstacle:

This seems to be the bone of contention, this is what you call an "inclusive" clause, that is to say here is how you "can" trigger "Something" when you meet either of the 2 conditions stated. it is not an "exclusive" clause, it is not the "only" way to do something as if it was it would have said so.

At the time of the RRG's guides writing, these were the only 2 ways that you could trigger obstacles. There are now more ways to trigger them

now to reiterate this clause:

but suffers an effect based on the type of obstacle:

The next 2 sections labeled Asteroids and Debris indicate the "effects suffered" of triggering Obstacles.

the simple fact is that the precedent set by rigged cargo and tractor beam should be enough evidence to prove this.

here is another analogy showing why not taking damage doesn't make sense. currently you cant shoot in the activation phase, but soon you have snapshot. I couldn't previously be shot in the activation phase so that meant i couldn't take damage from being shot in the activation phase so snapshot cant hurt me. sound ridiculous right?

the simple fact is that the precedent set by rigged cargo and tractor beam should be enough evidence to prove this.

here is another analogy showing why not taking damage doesn't make sense. currently you cant shoot in the activation phase, but soon you have snapshot. I couldn't previously be shot in the activation phase so that meant i couldn't take damage from being shot in the activation phase so snapshot cant hurt me. sound ridiculous right?

If this is what FFG intended, why haven't they FAQed the obstacle rules to remove the maneuver reference ? They've had ample time to do so (2 FAQ versions after Tractor Beams IIRC).

Your Snap Shot example is also stupid, as there's no rule srating you can only attack in the combat phase.

the simple fact is that the precedent set by rigged cargo and tractor beam should be enough evidence to prove this.

here is another analogy showing why not taking damage doesn't make sense. currently you cant shoot in the activation phase, but soon you have snapshot. I couldn't previously be shot in the activation phase so that meant i couldn't take damage from being shot in the activation phase so snapshot cant hurt me. sound ridiculous right?

If this is what FFG intended, why haven't they FAQed the obstacle rules to remove the maneuver reference ? They've had ample time to do so (2 FAQ versions after Tractor Beams IIRC).

Your Snap Shot example is also stupid, as there's no rule srating you can only attack in the combat phase.

And there no rule that says you ONLY hit asteroids when you maneuver across them.

No where in the obstacle rules does it say "Only when you maneuver over an obstacle do you trigger it's effects"

the simple fact is that the precedent set by rigged cargo and tractor beam should be enough evidence to prove this.

here is another analogy showing why not taking damage doesn't make sense. currently you cant shoot in the activation phase, but soon you have snapshot. I couldn't previously be shot in the activation phase so that meant i couldn't take damage from being shot in the activation phase so snapshot cant hurt me. sound ridiculous right?

If this is what FFG intended, why haven't they FAQed the obstacle rules to remove the maneuver reference ? They've had ample time to do so (2 FAQ versions after Tractor Beams IIRC).

Your Snap Shot example is also stupid, as there's no rule srating you can only attack in the combat phase.

And there no rule that says you ONLY hit asteroids when you maneuver across them.

No where in the obstacle rules does it say "Only when you maneuver over an obstacle do you trigger it's effects"

The way I understand the rules of a game, any game, you do what the rules tell you to and you don't do anything the rules don't tell you to.

The rules tell you to suffer obstacle effects when you overlap as part of a maneuver, so you suffer them. The rules don't tell you to suffer obstacle effects when you overlap as part of a barrel roll, so you don't.