If you have that system That let's you decloak across obstacles, do you still take the effects of the obstacle?
A decloak isn't a manuver.
If you have that system That let's you decloak across obstacles, do you still take the effects of the obstacle?
A decloak isn't a manuver.
If you have that system That let's you decloak across obstacles, do you still take the effects of the obstacle?
A decloak isn't a manuver.
Neither is a boost or barrel roll action, but the consensus at this point is that you're meant to roll for damage any time a template or base overlaps an obstacle (via tractor beam, debris token, or Collision Detector-fueled action), despite the relevant rules only referring to maneuvers.
As yet unclear, we're hoping for an FAQ soon to clarify intent.
This is another instance where they would assist a lot by clarifying obstacles to not be directly tied to maneuvers. I think we can assume intent of 'any time you hit a rock or debris you take their effects' but currently there's no concrete rules evidence of such as written.
Edited by nigeltasticThis is another instance where they would assist a lot by clarifying obstacles to not be directly tied to maneuvers.
That would be the most simple way to deal with all these special cases, like Tractor Beams and such.
I think that's the intent, but there really is no clear cut rule in the FAQ that spells it out.
This is another instance where they would assist a lot by clarifying obstacles to not be directly tied to maneuvers. I think we can assume intent of 'any time you hit a rock or debris you take their effects' but currently there's no concrete rules evidence of such as written.
Currently, it's just "argument bait". I'd be fairly sure the next FAQ is going to rule that you suffer effects whenever you overlap an obstacle, based on how they've ruled with Tractor Beams. Personally I think the notion of "I didn't perform a manoeuvre, so nothing applies" just doesn't wash. That's rules lawyering to the nth degree in my book.
If you have that system That let's you decloak across obstacles, do you still take the effects of the obstacle?
A decloak isn't a manuver.
Neither is a boost or barrel roll action, but the consensus at this point is that you're meant to roll for damage any time a template or base overlaps an obstacle (via tractor beam, debris token, or Collision Detector-fueled action), despite the relevant rules only referring to maneuvers.
The tractor beam rules do specifically state you suffer the effects of the obstacle though. It's got nothing to do with the regular obstacle rules. Collision Detector hasn't yet been quite so elaborated on.
tbh i could understand decloak NOT suffering the effects unless they landed on it because decloak is technically the ship appearing in a slightly different spot than you thought it was, its not actually moving.
But, for simplicity's sake and it doesnt do that already, i'd rule it the same way people are viewing normal barrelrolls. You take the effects.
Collision Detector would be way too powerful for a 0pt sensor if it basically let you ignore rocks.
I'd also assume you roll for damage and take stress from debris.
You'd take the stress but collision detector means there's no need to roll for damage.
building on this I would also assume that you lose your action.
building on this I would also assume that you lose your action.
Not if you were using Collision Detector to allow you to perform a boost or barrel roll action over the debris.
building on this I would also assume that you lose your action.
Not if you were using Collision Detector to allow you to perform a boost or barrel roll action over the debris.
Apologies, I wasn't very clear. If you de-cloak or if you have further actions available (PTL/Darth) then you would lose them. Noting in the latter case you would likely take the action before attempting the boost/barrel roll.
I really hope they clarify this soon(before Worlds and our Regionals lol). I recently played against a buzzsaw Whisper and the ability to decloak over rocks and debris and suffer no ill effects was nasty and made him VERY unpredictable.
I can see the argument going both ways... an action is not a maneuver but then again you ARE placing a template down for barrel roll, boost, cloak etc...