• Content count

  • Joined

  • Last visited

  • Time Online

    660d 8h 26m 35s

Community Reputation

366 Excellent


About Robock

  • Rank
    Comlog Addict
  • Birthday 11/30/1984


  • Location Ottawa, ON. CA


  • ITS PIN F5049
  1. in Army Profile, a dot seperates distinct skills while a slash represent an option that you need to make. When printed, the skills are seperated by comma, but these pairs have a chechbox so that you can pick only one of two skill.
  2. Yes, because if they BS Attack in ZVZ then ZVZ allow to attack back at a penalty. And both SS1 and SS2 specifically allow you to shoot back without the -6 (inside ZoC in the case of SS1). I don't think it apply to non BS Attack made through ZVZ. Even speculative and intuitive are BS Attacks for which you could shoot back if he was not in total cover. In other word, the restriction of requiring LoF for BS Attack is only lifted because of the ZVZ rule. For other skills you want to declare and/or in response to other sources of attack, you need to meet the skill requirement (unless those skill requirements are also lifted by SS1/2). That sounds like you saying if he move+CC then he's revealed for his whole movement such that any other model that was watching can shoot him. It is not the case. There are rule about camo being revealed for the whole Order, I don't remember reading such for being "hidden by" ZVZ. Getting shot with MSV2 would count as "an enemy inside his Zone of Control, even without LoF to the attacker and regardless the facing of the user." (for ss1) or " an enemy outside his LoF and regardless the facing of the user " (for ss2) but a CC attack is in ZoC and inside LoF.
  3. Yes. In order to shoot back through ZVZ you need to be shot at with BS Attack (it is a ZVZ rule). SS1 allow to ignore the penalty for shooting back, and it allow you to hold your ARO, but it does nothing to allow you to shoot back without LoF provided you have the correct facing similar to what the ZVZ rule allows. SS2 allow to react to attack outside your LoF regardless of your facing, but CC inside a smoke is an attack in your LoF and doesn't count for this line. I think. At least SS allowed you to ignore the surprise attack penalty, and to wait to see what was his chosen method of attack before choosing your skill.
  4. one of them is the rule on how to use tokens. The other is a rephrasing of what can cause cancelation. If you follow exactly the usage rule then the cancelation clause will never be wrong, it will just happen only on the owning player active turn and never happen on the owner reactive turn. That it does not happen as often does not make the sentence is wrong. On the other hand, if you follow exactly the "how does this state is canceled" phrasing and try to cancel possess after the order count then the "how to use the token to acheive that effect" rule is broken : by spending token in your reactive turn, and also by canceling posses too late as you must do so before the order count. So to me, it is easy to know which one to follow.
  5. You don't reveal the model at the start of the movement. The game example shows that the 3 Lu Dian moves in and the AROing player have no clue which one is the real one. If they Delay ARO like in the example, then yes you reveal with your shooting and they know which one to attack back. But there is a catch in that if they delay they can only ARO if the Lu Dian reveals itself with the second short skill. So the Lu Dian could simply move-move. Yes in most case that would be the case.
  6. thank you for the ressource
  7. You can remove my fireteam example and use any other example of less common interaction if you wish, it doesn't change that the absolute statement "there is no reason to expect ..." is false. Here is another example. Special Terrain N3 Rules give example of Hostility Level, referring back to N2 Paradiso, and that rule interaction is something that, like MorphoScan, I have yet to encounter in any casual or tournament play since N3 came out. The N3 book will refer to rules found in older books that had not been updated (when N3 came out) when it see fit. And they did not include being merely scanned as a cancellation clause for holoechoes, you need to either make a ARM/BTS roll or get Crited. Speaking of being scanned, I did not check, but how does Data Scan interact with holoechoes? (I address the question at large, not at anyone in particular).
  8. Why ? Fireteam was in HSN2 and the N3 rules still made reference to it even if the fireteam had not been updated. For example, Suppressive Fire cancellation lists say that joining a fireteam (which is a N2 HS skill) will drop you out of Supp Fire. So they could very well write in Holoecho N3 cancellation that getting hit by a N2 Moprho Scan even if there is no roll will remove the holoecho.
  9. They lose their order as their order can only be used to bring them onboard, and you opted to bring them onboard using an order from the order pool instead. It is also in the FAQ on the AD page.
  10. Exactly. We cannot simply measure ZoC during the whole order, the rule give precise points where you measure for coherency. Anyway, it could get complicated when you have two model at different speed, to know at what distance they were from each other at precisely each point of time of their movement.
  11. That is my take for g:synch as well. For fireteam for a sec I thought you checked on skill declaration, but reading the rule section again, it seem when you declare ARO skills, you re-check for cancellation clause and re-calculate the applicable bonus if someone left, but only left due to declaring a different skill. All coherency checks are only initial and final (after guts movement) for fireteam the same way they are for g:sync.
  12. @ButlerYep, as IJW said, seeing means if you make a first player shooter (1st perspective ?) drawing, you should see 3mm x 3mm. I don't think the ruleset need to take a paragraph to explain to a player what seeing means. If you allow for a square on a plane not perpendicular, how can you call what was visible to the model in your drawing as anything but "a sliver of a vertical line, much less than a head size even thinner than a hand" ? Also technically a model cannot "see" a volume unless the material you are seeing is translucent. a square is better description of what you see. Anyway... the rule already give example of how you place a silhouette to check if the 3x3 black square is visible or not. And there is no example of placing the paper sideways in order to claim seeing the whole square.
  13. And the roll (a hit in your example) does not only apply to the primary target in FtF but is used for comparing with every other additional targets. So you could miss (I mean a hit canceled by a better one) against the primary target and still hit the others.
  14. Armand (Minelayer) 42 1.5 doesn't list minelayer when you print it. Armand (MSV1) 45 1.5 is working correctly.