Order expenditure sequence question

If you check the credits on the first page of the Rulebook:

There's our man IJW! He doesn't like to blow his own trumpet but I believe he spends most of his time working for CB in a freelance capacity nowadays.

 

Thank you, good to know!

 

Hi, just trying to put some light on this. CARE.
Rule written in spanish is different than rule written in english for ARO.

In english (p21) says:
"The ARO declarations of the Reactive Player’s Troopers are considered valid in the
following situations:
◼ An enemy Trooper activates within its Line of Fire (LoF).
◼ An enemy Trooper activates within its Zone of Control (ZoC).
◼ It has a Special Skill, weapon, or piece of Equipment allowing it to react to enemy
actions without LoF.
◼ It is affected by a Template Weapon, or is the target of a Hacking Program or other
Comms Attack."

While in spanish the sentence is:
"Una Tropa del Jugador Reactivo tendrá derecho a declarar una ORA si cumple alguno de
los siguientes casos:
◼ Si disponen de Línea de Tiro (LDT) con la Tropa que está siendo activada por el
Jugador Activo.
◼ Si se activa una Miniatura enemiga en el interior de su Zona de Control (ZC).
◼ Si dispone de alguna Habilidad Especial, arma o Equipo que le permita reaccionar
sin LDT.
21
REGLAS BÁSICAS
◼ Si se ve afectado por un Arma de Plantilla, o es objetivo de un Programa de Hacker
o de cualquier otro Ataque de Comunicaciones."

This is NOT THE SAME MEANING. The rule in spanish is pointing that only troopers meeting at least one of that 4 situations can ARO. so no anybody can declare ARO. just the ones that are triggered by the active model in one of these 4 situations during step 2 or 4. at step 5 you will check the meeting if needed (for example ZC distance measurement) and at step 6 you will see if the ARO choosen meets the hability requirements.

 

This doesn't work, though, which is why the ENG rule (which is newer) says something different. I don't know why the change didn't get translated back into ESP. :-(

You have to be able to declare Zone of Control AROs without knowing if you're declaring a valid ARO, because you're not allowed to premeasure Zone of Control. That's the whole purpose of step 5 ARO Check.

 

then, what about mines, i have to declare the action before measure the range, and if the mines is out of range what happens?

 

Mines don't declare AROs, but this is specifically covered in the Mines rule. Bullet 8:

• Once on the game table, Mines must trigger when an enemy Model or Marker declares or executes a Skill or ARO inside their Trigger Area, checking it at that moment by placing the Small Teardrop Template. If it is determined that the Model or Marker is not within the Trigger Area, the Mine will neither detonate nor be revealed.

My emphasis.

 

So.
ORDER SEQUENCE:
step 1: Active model behind a wall moves in zc to a model without getting LoF with the enemy.
step 2: enemy declares ARO BS attack shoot back.
step 3: active moves into lof of enemy
step 4: nothing
step 5: measures zc for that aro and lof. it is ok.
step 6: check ARO requirements of bs attack. they are all OK.

the active gets a shoot.

RULES:
1. Activation: The Active Player declares which Trooper will activate.
1.1. Order expenditure: The Active Player removes from the table, or otherwise
marks as spent, the Order he uses to activate the Trooper.
1.2. Declaration of the First Skill: The Active Player declares the first Short Skill
of the Order, or the Entire Order he wants to use.
If movements are declared, the player measures where the Trooper can move,
chooses the route, and places the Trooper at the final point of its movement.
2. Declaration of AROs: The Reactive Player checks Lines of Fire to the Active
Trooper, and declares AROs. Troopers are not forced to declare the AROs, but if a
Trooper can declare an ARO and fails to do so, the chance to declare an ARO is lost.
3. Declaration of the Second Skill: The Active Player declares the second Short Skill
of the Order, if applicable.
If movements are declared, the player measures where the Trooper can move,
chooses the route, and places the Trooper at the final point of its movement.
4. Declaration of AROs: The Reactive Player checks Lines of Fire to the Active
Trooper from those Troopers who didn’t declare an ARO before, and can declare any
new AROs that are available.
5. ARO Check: Check that each Trooper that declared an ARO has been in one
of the situations that makes their ARO declaration valid. If they have not, they are
considered to have declared an Idle.
6. Resolution: Check that the declared Skills, Special Skills, and pieces of
Equipment meet their respective Requirements, measure all distances and Zones
of Control, determine MODs, and make Rolls. If any Skill, Special Skill, or piece of
Equipment does not meet its Requirements, the Trooper is considered to have
declared an Idle.
6.1. Effects: Players apply all effects of successful Skills, Special


BS ATTACK
SHORT SKILL / ARO
Attack.
REQUIREMENTS
► Be using a BS Weapon, or a Skill or piece of Equipment capable of making a
BS Attack.
► Be able to draw Line of Fire (LoF) to the target of the BS Attack, unless the BS
Weapon, Skill or piece of Equipment used doesn’t require LoF.
► Not be in Engaged State during the Activation phase of that Order.

 

Note that LoF is not checked at step 5. It’s checked at the start of step 2, before declaring any AROs.

There will be clarification from CB on this, but I don’t know when, as it’s a long holiday weekend in Galicia, and there is a ton of other stuff being worked on at the moment, like ITS12.

 

appreciate the replys. thanks. we will wait for CB to make a decision or clarify wording on this. cause now this does not make any sense. check lof at step 2 but the rest at 6? ...

 

Because LoF requires no measurements i think

 

I can see that step #6 could use better wording about skills....but not checking LoF at step #2 would be rather silly. What u will do then? wait for your opponent to declare an ARO for EVERY SINGLE model on the table? just to say at step#6 that 99% of those ARO are now invalid?

the best solution would be to check LOF + ZOC at step#2 and gg

 

As much as people clamor for this to reduce some odd rules interactions, it's pretty clear to me that this is not something they are willing to change about Infinity. It's effectively codified in the rules now with Step 5: They simply don't want you pre-measuring ZoC before declaring skills. Your next shot at having them moving ZoC measurement earlier is probably N5.