Boost states that "it is triggered when an enemy Model declares or performs an Order or ARO in its Zone of Control". Given that you don't measure ZOC until step 5/6 I expect the timing is as follows: 1. The Active Trooper is activated, the order is spent and the Trooper Moves into <8" of a Perimeter Weapon 2. AROs are declared 3. Trooper declares Second Short Skill 4. AROs are declared 5. AROs are checked for Validity 6. The Perimeter Weapon's ZOC is measured, and if the Trooper was inside the ZOC at either Step 1 or 3 the the Perimeter Weapon will trigger. IE. "when" is taken as "during the order" not as "immediately". This is distinct from Mines where players are told to "check it at that moment". Implications of this: 1. Players are not obliged to inform their opponents of likely inbound Explosive/Adhesive Hugs during the order (other than normal courtesies for ensuring that your opponent is aware of the game state) 2. The Player who owns the Perimeter Weapon is not required to declare which active Trooper the Perimeter Weapon Boosts towards until after measuring their ZOC (and determining which are valid targets of Boost) 3. Perimeter Weapons don't move and are not removed until Resolution so remain in place as valid targets (of, say, Impact Template Weapons) and for other purposes such as (potentially) blocking Movement until then.
Interesting. Mines have a rule that says you check 'at that moment' a model declares an Order or ARO that might be inside trigger area, but Boost doesn't have the same qualifier.
TBF in the case of Mines there's an argument to be made that you check whether they trigger "at the moment" an enemy declares or performs an Order or ARO near them but they wouldn't actually trigger (and be removed) until Resolution. There's a lot of like about that interpretation as it leaves changing the game state to Resolution where - for most things - it properly belongs.
I would assume that you would inform your opponent that you think the perimeter weapon is triggering as soon as they declare a matching skill. Consider it sportsmanship as much as anything else.
You only check declared pieces of equipment at step 6. If the Koala hasn't been declared by then, it won't be checked. How and when to declare Boost is simply missing in the rules as far as I can tell. Edit: also the only example of Perimeter weapons says a Moran wants to intimidate a Jujak, but it is a Daturazi on the image
They've very carefully changed Boost to no longer be an ARO, so it seems to me there's a clear intention that it's no longer declared, and instead happens automatically like a mine. But @RobertShepherd also makes a good point that Boost lacks the wording in Mine explicitly telling us to check upon triggering. The Boost wording seems clear that Boost triggers as soon as the victim declares a skill, same as a mine. The Boost wording also says "when triggered, the weapon must move until it reaches..." If "when triggered" means "as soon as triggered," then the koala has to be removed from the table right away. That's also consistent with mines which are removed right away. (The alternate reading would be that "when triggered" means "at the Resolution of the order in which triggered," but as @Mahtamori says, Resolution only resolves declared skills. Since Boost isn't a declared skill, it seems likely that it happens immediately like a mine, not at Resolution.) So, I think that Boost is triggered, and the koala leaves the table, immediately upon victim skill declaration. If I'm right, then that still leaves the question: does this mean we're allowed to measure ZoC immediately? Or do we wait until step 6 to measure, and then determine, retroactively, whether the koala left the table at the moment its victim declared its skill? I don't have an answer to that one.
So they rewrote mines to make the expected behavior explicit, but forgot to rewrite Perimeter the same way, when it has to work the same way. Because that’s what’s changed between N3 and N4: N4 Boost says basically the same that N3 mines detonate did, down to creating the same “So when do we check and what happens if we guess wrong?” questions. Pour one out for the first time a player deploys a CrazyKoala not realizing they removed “follow along” mode.
And what happens if there are several enemy models 1) activating at the same time* (coordinated or fireteam) 2) having an ARO after my first/second short skill at the same time* Against which trooper does the koala react? The team leader( because he seclares the skill)? The first who declares his ARO?( because of 'when it is triggered') Does the controlling player get to choose? *point in the order expenditure sequence
It's declared Skills, Special Skills and deployed pieces of equipment. Because you need to check the requirements of Automatic Skills at Resolution to see if they apply even if their use wasn't declared during Steps 1-4. I see no reason why a Perimeter Weapon where neither player realised that it had triggered until Step 6 (and ZOC is checked) wouldn't validly Trigger. Consequently, I'm also increasingly on the "you check if a Mine Triggers during Step 1-4 but you resolve it during Resolution" bandwagon as that means that "when" is consistently interpreted as "the order in which".
Controlling player gets to choose. I'm fairly certain that IJW has pointed this one out somewhere on the forums already.
As I wrote, the exact sequencing is missing. Step 6 is as invalid as step 1-4. I'm more of a mind that a Perimeter ought to be checked earlier, same sequence as a mine.
I can see another argument for why the mine shouldn't explode until resolution: I declare a coordinated order with troops A and B. A is a model, B is an Impersonation marker. I declare Move and move both troops. We check and determine that A is inside a mine's trigger area, but B isn't. The mine triggers and you place the teardrop template to hit A. Now I declare a second Move and move B into the mine's template. At Resolution, the mine doesn't explode because if it did, it would hit a friendly model. If we had already taken the mine off the table, we'd have to put it back. Now, obviously that exact reasoning wouldn't apply to a koala, since a koala isn't a template weapon and can't accidentally hit a friendly model. But if I'm right that a mine triggers immediately on order declaration but isn't removed from the table until Resolution, then it follows that a koala would also not leave the table until Resolution. That's the opposite result from what I proposed earlier in this thread. My previous post was based on the idea that Boost isn't declared. However, reading the Order Expenditure Sequence again, it says "Check that the declared Skills, Special Skills, and pieces of Equipment meet their respective Requirements." That could mean "the declared (Skills, Special Skills, and pieces of Equipment)" or "the (declared Skills), Special Skills, and pieces of Equipment." On the second interpretation, the koala is a piece of equipment so it would be checked at Resolution despite not having been declared.
Quoting for emphasis: Trying to spring a "gotcha" on your opponent by not telling them that something triggered Boost on their first skill would be not only very questionable within the rules, it would also be unsportsmanlike.
Definitely. Assuming that the koala's ZoC isn't checked until Resolution, at the ARO declaration stage the reactive player would say something like "this Koala might trigger." Technically that's not an ARO declaration, but it still seems like a necessary part of the process of jointly confirming what has happened as a result of the first Move.
@QueensGambit the OES has to say "(declared Skills), Special Skills and pieces of equipment" . Because you need to check whether the requirements of Automatic Skills are met at that point, and - by-and-large - Automatic Skills aren't declared. So the second is just "Special Skills" not "declared Special Skills". And while I agree that it's very courteous and the right thing to do to point out that a Koala may or may not Trigger the rules don't oblige it as they stand. So I'm with @Mahtamori that this could do with a clear example, albeit I do think the rules provide enough to support that Perimeter Weapon triggering happens in Step 6.
