So I've been looking over some old Sixth Sense threads to try and find an answer to this but had no luck. The situation in question would be, a model with SSL1 has 2 enemies activate by the same order, these could be link members or G:sync etc. Enemy A is within 8 inches, while Enemy B is outside 8 inches, allowing the trooper to delay their ARO as something activated within ZOC. Enemy B then shoots the SSL1 trooper, while Enemy A does not. Can the trooper in question validly shoot back at Enemy B, or have they restricted their ARO targets (much the same as when delaying against coordinated camo markers) by virtue of utilizing the ZOC proximity to delay? Obviously you can just forego the delay to resolve this but I'm very curious as to how this works out.
I believe yes as model A allowed the ssl1 model to delay and then model B creates a new aro in the second half of the order ( as long as the ssl1 model can fulfill the requirements to shoot back.)
This sounds like a pretty relevant precedent, not that precedents count for anything in this ruleset.
There's a crucial difference. When you delay against a camo marker, that's using the Camo Marker's rules specifically to allow the delay. That's why you get locked into responding to it--you're playing by the Camo Marker's rules at that point. When you delay using Sixth Sense L1, you're not committing your ARO yet. So you're not locked into responding to any particular trooper yet. But that's largely irrelevant because... No, you can't. Because Trooper B is making an attack outside of your ZoC. That doesn't trigger the response clause in Sixth Sense Level 1. Multiple activating models and the whole "only one ARO" business doesn't mean that you get one collective ARO against all of the active models. It means that you don't get one ARO against each of them, and get at most one ARO against one of them. Trooper B has to satisfy both requirements because Sixth Sense says so: An enemy must be inside the user's Zone of Control. That enemy must declare an Attack against the user. The ARO delay part of Sixth Sense is poorly written, but also understood to be independent of the rest. You get to delay your ARO without being attacked, after all.
I'm assuming there is LoS to Trooper "B" in the described situation. That would mean they normally get to ARO against trooper B, but not be able to delay against them due to ZoC. In all the situations where this would be happening "A" has to Declare the BS Attack (Fireteam, G:Synch, Coordinated Order) even if unable to actually do it (thus turning it into an Idle). In that situation the requirements are met. "In the Reactive Turn, Sixth Sense L1 allows its user to delay his ARO declaration until after the declaration of the second Short Skill of the enemy inside his Zone of Control." As we do not have any sort of ruling how SS works with multiple ARO units you would, at worst, be able to declare a ZoC (Rest, Change Face) ARO against "A". At best you would be able to shoot "B" as all the requirements of SSL1 are met (The enemy inside your ZoC has declared an Attack against the user, they all generate one ARO, which you can now delay against due to the Reactive clause of SSL1).
I don't think that's actually a foregone conclusion, for example, a pan O Auxilia could declare combi rifle shots at the SSL1 trooper while his Auxbot declares flamer with an entirely different target. In that case, even though a BS Attack is declared inside ZOC, it does not constitute "an attack against the user".
Good point. I was going off the example given which didn't bring other units into play than the 3 described. There are a lot more possibilities that could play out as you broaden the scope.
