1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Hemos actualizado nuestra Política de Privacidad acorde con la nueva RGPD. +Info // We've updated our Privacy Policy to comply with the GDPR. +Info
    Dismiss Notice

Holoprojector L2/Perimeter Weapon Interaction

Discussion in 'Rules' started by Koval, Mar 26, 2020.

  1. Koval

    Koval Well-Known Member

    Joined:
    Mar 15, 2019
    Messages:
    118
    Likes Received:
    88
    Hello,

    I have a question concerning troopers with both the Holoprojecter L2 skill and perimeter weapons, such as the Kanren and... that might be it. When deploying and moving, what do the perimeter weapons have to be in zone of control of? The one represented by a model? The secretly-noted real one? Any of the holoechoes? All of the holoechoes?
     
  2. colbrook

    colbrook Black Fryer

    Joined:
    Nov 23, 2017
    Messages:
    6,293
    Likes Received:
    11,496
    They have to be in ZoC of the controller, which is the actual trooper. The echos don't copy skills and equipment so won't count as controllers.
     
  3. Koval

    Koval Well-Known Member

    Joined:
    Mar 15, 2019
    Messages:
    118
    Likes Received:
    88
    Thanks, that makes sense.
     
  4. inane.imp

    inane.imp Well-Known Member

    Joined:
    Jan 28, 2018
    Messages:
    4,858
    Likes Received:
    5,825
    Just to be absolutely clear:

    They need to be in Coherency of the controller. You're obliged to check Coherency at specific points (including during deployment) ; you're not obliged to measure ZOC for Deployable Equipment that is deployed within ZOC (ie. Mines).
     
  5. Mahtamori

    Mahtamori Well-Known Member

    Joined:
    Nov 23, 2017
    Messages:
    8,292
    Likes Received:
    10,369
    There is no difference between deployment rules for a Minelayer and a Perimeter weapon. Both must be deployed inside zone of control of user. Perimeter do not oblige a formal coherency check at deployment
     
    inane.imp likes this.
  6. inane.imp

    inane.imp Well-Known Member

    Joined:
    Jan 28, 2018
    Messages:
    4,858
    Likes Received:
    5,825
    You know I missed they the deployment Coherency check was permissive. I'd always understood all Coherency checks to be mandatory. The things you learn.
     
  7. Mahtamori

    Mahtamori Well-Known Member

    Joined:
    Nov 23, 2017
    Messages:
    8,292
    Likes Received:
    10,369
    No, I mean, a Perimeter item does not have Coherency Check as part of deployment at all, but you are still forced to make sure that they are within ZoC during deployment for both Minelayer and Perimeter.

    Still, now that I re-read the coherency rules, that's interesting that it's allowed, but not forced, during deployment. That's got some pretty interesting consequences for technically legal rules abuse when it comes to Repeaters on Synchronized units.
     
  8. inane.imp

    inane.imp Well-Known Member

    Joined:
    Jan 28, 2018
    Messages:
    4,858
    Likes Received:
    5,825
    Or Repeaters and say Koalas. Because they never appear on the same model.

    Honestly I was always under the impression that *can* read *must* and since Perimeter Items are subject to Coherency would get caught by it.
     
  9. solkan

    solkan Well-Known Member

    Joined:
    Dec 19, 2017
    Messages:
    877
    Likes Received:
    1,431
    I think part of this may be an argument over an artifact of history—they added the notion of “coherency” after the main rules, so deployables don’t explicitly use it. Perimeter rules were written/revised late enough to be able to reference coherency.

    But I think you’d cause unnecessary problems by not subjecting deployables that can (only) be deployed in ZoC to the deployment time coherency rules.
     
  10. Mahtamori

    Mahtamori Well-Known Member

    Joined:
    Nov 23, 2017
    Messages:
    8,292
    Likes Received:
    10,369
    Coherency rules are a fun way, btw, to circumvent pre-measuring ZoC as you're forced to measure the ZoC when doing the check, not just the distances between the individuals being checked.

    P.s. this one"Holoprojector L2, Holoecho and Fireteam Example:" is just a piece of work. A hypothetical Holo2 trooper inside a 5-man Fireteam activates without getting Team Leader first and declares Holoprojector 2 while in the Fireteam and gets individually kicked out of the team without triggering the Holo1 cancellation clause and goes directly into Holo2 as the fake loadout.
     
  11. inane.imp

    inane.imp Well-Known Member

    Joined:
    Jan 28, 2018
    Messages:
    4,858
    Likes Received:
    5,825
    It's kinda irrelevant anyway. It's permissive so you can measure during deployment if you want to.