You're missing how this works: Reset doesn't require LOF so you can speculatively declare it preemptively and it becomes legal during resolution if someone tried to Spotlight you. And afterwards it's raining Templates which are fine to Dodge or Reset against.
Speculative declaration is gone as of this morning! You now have to wait and declare Reset once the Spotlight gives you an ARO. But it's the same result.
Don't think that's in the FAQ, was specifically looking for it too. Mind pointing me to the bit that has changed?
@Teslarod you are missing the big change. You can no longer Dodge ARO against out-of-ZoC Spotlight attacks. Previously you could make an interpretation that you could do that. This allowed you to Dodge out of repeater hacking area (or perhaps next to Repeater*). After FAQ1.1, your guy will simply stand there until he gets Spotlighted or enemy runs out of Orders. * Standing next to enemy Repeater prevents Guidebot attacks, because Repeaters are friendlies for the enemy and template attacks are cancelled if friendlies are in the template area.
Ah that's a use case I was missing. Not quite sure it's a huge loss given you eat an unopposed Spotlight for your efforts. No interpretation required with the now "old" Dodge requirements: "In the Reactive Turn, they have a valid ARO." Could definitely do that till now.
The FAQ rewrites the Order Expenditure Sequence entirely. All the stuff about having a valid or invalid ARO is gone. Now we just check at step 2.1 whether a trooper "can declare an ARO" (which we now know with certainty at that step, thanks to ZoC premeasuring.)
Yes, I was proven correct on that case. Reset ARO is still wonky. You can Dodge and BS attack ARO against non-LoF (smoke) and non-ZoC non-template attack, but can't press a button to Reset your powersuit? Only against flamers you manage to find that all-important button.
While in FAQ 1.0 your guy would declare a lot but wouldn't get to execute them until he gets Spotlighted or enemy runs out of Orders. So, like QueensGambit wrote; it's the same result. I mean, the FAQ is a huge change, but not for this topic ;)
Templates are cancelled if they hit "allied or neutral Troopers." Deployable repeaters aren't Troopers. You could at least force them to blow of their own repeaters in the course of blowing you up, which was something anyway. (Edit: but only prior to FAQ 1.0).
Uhm, Requirements do not have to be met until (5.) Resolution. That hasn't changed, so what are you referring to? The new stuff is "you know if you have ZOC" related only. The problematic cases are "I Declare Non-LOF-Skill-X with the first Short Skill and then fulfill the requirements with my second Short Skill". Meaning stuff like "speculative CC Attack" is still very much a thing
@QueensGambit are you sure? I got an impression that deployables count as friendly/enemy troopers for all purposes. I mean there is bound to be stupid rule somewhere if they aren't. If they aren't friendly troopers, can you target your own deployables with template weapons?
On the other hand, the rules for attack says otherwise and isn't directly counter-said by what's written under template weapons. We know a lot of rules need to consider an attack to be declared against secondary targets as well in order for the rules to work, so... get close to the enemy Repeater to be safe(ish) from Guided https://infinitythewiki.com/Labels#Attack Attack The use of this Special Skill or piece of Equipment is considered an Attack. Remember that you cannot declare attacks against allies or Neutral elements, whether represented by Models or Markers.
Hmm. Right, per the other thread, speculative CC attack may be allowed (provided the active trooper is in your ZoC). I can't think of any other speculative declarations that would still work. You can no longer declare while outside ZoC and LoF of the active unit, which was the basis for most speculative declarations. Am I missing one? You're right that the Requirements check still happens at Resolution, so in theory there could still be speculative declarations, I just can't think of any other than CC that would still work.
Why not? ONLY LOF based declaration is impossible to begin with without meeting the requirements. The very first entry of the FAQ makes that still entirely possible: Nothing stops you from happily declaring a Jammer against something clearly outside of your ZOC and then walking up to it afterwards. Knowing you have ZOC or not does nothing to reign in or address the interaction "problem" for "speculative CC Attack" and other non LOF SkillsShenanigans.
Oh interesting, you mean speculative declaration by the active trooper. Yes I think you're right, the active player can declare it in that order. But I don't see the benefit in that example. The target will just declare Reset as their aro once you move into their ZoC for your second short skill. Is there a case whether the active trooper gains a benefit from a speculative declaration? Other than CC Attack, which may or may not still be prevented by ijw's interim ruling.
It might be important for the enemy to advance. By declaring (possibly) speculative (non-LoF) BS attack (Deploy mines, Jammers, hacking etc.) during 1st part of the order, he can ARO bait enemies into declaring Dodges. During 2nd part of the order, he moves into LoF. Similar trick can also be used with Dodge.
Reactively it prevents the use of CC Attack vs Guard (which is annyoingly prevented by the interrim ruling). But that's honestly more Guard being a badly designed gotcha mechanic of a Skill.
