I think the best solution might be to move the checking of requirments from declaration to when it's executed. So you can declare whatever you want but if it's not possible to use when the order happens it gets turned to idle.
Big problems with this... not least of which is giving every single model a potential ARO every time you move (including HD units).
I think you would still want to keep the rule where you need LoF or ZoC (or Hacking Area) to receive an ARO trigger in the first place.
Yeah the ARO trigger would stay as it is. The point is to that you no longer can get forced into declaring AROs that you don't want to declare
Chasseurs are definitely an interesting corner case when talking about changing this level of core rules. I don’t think anyone else has the combo of Sixth Sense and a camo state. Sometimes you can’t streamline one thing without breaking another - do you think that losing this interaction would unduly hurt them? Camo is still strong and Chasseurs still have good weapon options to force bad choices.
I don't honestly know. I think it hurts MRRF a lot more than Chasseurs in isolation. Chasseurs have such perfect skills and gear for a skirmisher.
That's actually part of the point and why I had the idea. In my opinion any forcing a wasted ARO in the form of "I know declaring X is best and that is want I want to do but I can't because of Y" is bad design, and most(all?) of those interaction seems to be uninteded and is not something that rules explicitly allow. However I don't think situations such as an hakcer being able to chose between hacking or bs and forcing a bad aro on the reactive unit. But that would mean that CC needs a buff, which is probably true anyway.
Not necessarily, if you don’t lift the restriction on what you can declare for a ZoC ARO. Even if you don’t check requirements until skill execution you still can’t declare BS Attack from a ZoC violation.
Right now, there's no restrictions on what you can declare for a ZOC ARO. Either you meet the requirements at declaration or it's not valid. You'd need to Introduce a 'if the ARO is generated due to X you can only respond with Y'.