Robock

Members
  • Content count

    1,682
  • Joined

  • Last visited

  • Time Online

    1141d 8h 18m 36s

Community Reputation

513 Excellent

4 Followers

About Robock

  • Rank
    Comlog Addict
  • Birthday 11/30/1984

Converted

  • Location Ottawa, ON. CA

ITS

  • ITS PIN F5049
  1. 7 orders at 300 ? I'd rather just go up to 400 and make a LI list. You still have a bit of AVA left in Grenzer and Securitate (ah the old days of all my bakunin hackers are also repeater for each other).
  2. The KHD and the Contender are specific to the Pilot. You cannot use them as long as the active profile used is the TAG. Once the pilot gets out, then as he is active profile you can use the KHD and Contender and you can even go prone; but you cannot do anything that is limited to the TAG profile (such as HRMC, HFT, and ECM).
  3. Faq v1.3 already answer that becoming irregular (for example because of isolation) you don't lose datapack or anything like that. Another answer in that faq 1.3 is that if you become REM (for example because you are a Remote Presence TAG and you dismount) then in this circumstance, the REM is allowed to be the datatracker (same as how a pilot who dismount keeps the datapack). So with those 2 restriction covered that only leaves what happen if you become marker state ? Well, for that, the rule is clear you cannot voluntarily become marker state, but what if the enemy posses my TAG and spend an order on him to reactivate TO ? His own datatracker is still a model. So far, probably nothing. My datatracker is Null, and there is no problem having your Datatracker not on the board because he's dead. Well then next turn, i recover my TAG, I guess he lose TO marker ? or not ? But that is wayyyy to specific of a case unlike Isolation (EM or Jammer).
  4. Obviously, you'd think that. the thread is 15 page cause you shut down any player input. And claiming that a TO who reads at several place how dogged refer to not lasting longer than 1 turn will think everything is fine that somehow a model starts a new turn already dogged. As someone else wrote early on, if you start a turn with a model already dogged (who's leftover from a past turn), then you must realize something is wrong. You claim a TO will says "nah, everything is fine". I only add that even if you are to stay dogged you cannot later claim to benefit from any effect that says "for the remaining of the turn" because this current turn IS NOT the remaining of the turn in which he became dogged. End of Turn is the 4th phase inside the active/reactive player turn sequence.
  5. and furthermore, the effect of ignoring the Unconscious is limited to making the Unc state non-Null treating it as Normal state and that is specifically limited to "the rest of the player turn." If you somehow forget to remove him during the end of turn (because you checked for any dogged prior to taking zone damage) you would on the following turn be unable to spend Order/ARO because the model will be Null state again.
  6. hmm, you have a good point. I thought Guided did say to be used against any target in the state, but that it then reffered to Targeted state for the exact effect. Yet, the Targeted state does not have the effect of giving a +6 BS MOD. That effect is specific to the Guided trait and is irrelevant of being a trooper or not. Yes, the Targeted state does say that troopers in that state " can be chosen as targets of Attacks using BS Weapons with the Guided Trait, " but that does not prevent other rules/equipment/traits to also allow BS Attack with Guided Trait and having their own requirements.
  7. as IJW said above, you can put in the targeted state, but then nothing happen because the effects only apply to trooper. I also see nothing inherently wrong about targeting non-troopers, but the FAQ answer about antenna (targetable non-trooper scenery) also apply to targetable non-trooper equipment/weapon. In other case, we always knew spotlight didn't help smoke grenades that target the ground and i see nothing inherently wrong about allowing to spotlight an antenna, a lamppost, etc. that spotlight to help you spec throw costed an Order in preparation of doing so.
  8. oh true, it really suck for satlock. and also for satlocking into an ambush camo. at least sensor is still as useful as before.
  9. you can still spec fire a grenade having it off-centered to the primary target (a revealed mine) and clip a camo nearby. But you cannot Spotlight the mine first to give yourself better odds.
  10. that is not exactly what the rule says. IMP is lost upon declaration. The rule for G:Synch is : The Controller and the G: Synchronized trooper must declare the same Order, declaring the same Short Skills of the Order. However, it is not compulsory that they have the same target. If either trooper is not able to perform the Order (whether the Entire Order or both Short Skills of the Order), then that trooper will perform an Idle, while the other trooper will perform his complete Order normally. If either trooper is not able to perform one of either Short Skills of the Order, then that trooper will perform only the Short Skill he is able to perform, and the other Short Skill will be an Idle. While the other trooper will perform his complete Order normally. As we can see, when you cannot do an attack, what happen is that you perform Idle, not that you declare Idle. The duo still declared a synchronized attack revealing both of them, and then only one is performing it while the other performs an Idle. The declaration was never changed from Attack to Idle. It could be dangerous to revert a skill declaration into a movement skill declaration during the declaration of the Order phase. For example: I declare Shoot with the bot, the controller doesn't meet the requirement to declare a shoot skill (for whatever reasons) and declares a Idle Skill. The controller then declare a CC skill which the Bot is not allowed to declare (for whatever reasons, including because he already declared a short) and therefore the bots declaration is reverted to declaring an Idle movement skill. I don't think there is a guardrail against that if we allow for skill declaration to be converted into movement declaration during the declaration steps. Instead the declarations made stands during the declaration step, and only during the execution step the model will perform Idle.
  11. Oh interesting i always thought it was active only (on the basis of CC working the same as BS, but using bonus found in cc bonus chart).
  12. touching is already covered by being physically engaged in a close combat. You don't need to actively go and touch the REM, the REM can decide to touch you and if you are doing nothing to oppose him touching you, you get shocked. That is similar to Berserk where you allow your opponent to touch you freely (with either electric pulse as in the e pulse example saying it is allowed; or a knife in normal cases) in order to also make a non-FTF attack on him. EPulse is a CC weapon, you use it the same way as any other CC weapon by trying to touch the opponent during the execution of the short skill. With the difference the roll is automatic and there is no ARM save. Unless they are forming a Linkteam, why the distinction ? i understand in active turn, only the leader rolls (with extra Burst); but in ARO they can each ARO with their own skill (declaring the same skill of course), it work with BS ARO why not with CC ARO ?
  13. if he wanted he could have Dodge which would have been FtF to all AROs, but he chose to only oppose 1 and therefore the other 2 are Normal Success.
  14. you mean holo:3, as holo:2 cannot be linked. fortunately, the old specop tables (still used in current ITS) only have access to holo 1 and 2 but not 3.
  15. Well the existing wording starts with "this program CANNOT interact with ED". From there everyone would assume you cannot Expel ED. But it ends in "When used against TAG with this piece of Equipment, Expel works normally, as described here, but replacing “the Pilot” with “the Operator”." From there, everyone would assume that this program (Expel) CAN interact with ED. So, it's a case of a rule paragraph that was contradicting itself (both sentence contradicting the each other) and a FAQ that override one sentence to give priority to the other.