• Content count

  • Joined

  • Last visited

  • Time Online

    654d 15h 3m 29s

Community Reputation

3593 Excellent

1 Follower

About solkan

  • Rank
  1. The only horizontal movement allowed when using Climb is what is necessary to get to a legal end position. Like it shows in the book, where the model moves a base width or so forward because it needs to stop in a supported position. There are situations where you effectively get an inch or so of "free" movement, that ends up being free because Climb doesn't let the model "pay for it" out of movement allowance. A model with Climbing Plus usually declares Move and then proceeds to use the movement to travel up the wall. So a model with Climbing Plus can move to the side or whatever it wants while moving across the vertical surface if it declared Move. If it declares Climb, then it follows the Climb rules. Note that Climb is more restrictive (you have to get to base contact with the scenery using a different skill), that's what balances out the small amount of free movement.
  2. From two years ago: Three out of four references say "before", evidence that the one that says "after" is wrong.
  3. It depends on what you're trying to do to it, and do to it. The TAG doesn't stop being a valid target because the pilot got out, but what it can do changes.
  4. I'm going to just defer to this previous thread: But at the moment Warning doesn't cancel Suppressive Fire either, so there's a compelling argument to be made that you're always allowed to turn to face your Attacker. :-/
  5. Getting shot (by a non-template, non-comma attack) weapon isn't a criteria to get an ARO. You still need to satisfy the ARO criteria somehow: Line of sight Zone of control Attacked by an ARO generating attack (template, comms attack, etc.) Alert won't help the Immobilized trooper because Alert only grant Change Facing AROs, and Warning won't help because Warning doesn't grant ARO (Warning is at the conclusion of the order for things that didn't get an ARO or get activated, and the pivot isn't a Change Facing.)
  6. The FAQ has an illustration of "base contact" that includes one figure's base touching the side of the volume of the other. So dismounting in base contact at the TAG's chest level or whatever isn't a problem.
  7. Naturally, I'm just delighted to have a FAQ that overrules the current understanding (that coordinated orders had to be the same named skills) without giving any other guidance on what constitutes "the same order".
  8. Stealth means that there's no ARO against the Taskmaster. The hacker gets to/has to declare an ARO, but it must be a valid ARO when it is declared. The only valid ARO is against the model without Stealth.
  9. Previously asked and answered variations of this question:
  10. For what it's worth, I liked the model a lot better after I saw some different angle shots. I definitely think it's the same OST (or original anime) vs. NG (or live action) that the Morat models have gone through, though--oth well executed, but also radically different styles.
  11. Things that are in HSN3 that weren't in HSN2: Tohaa Some new Combined Army stuff (including a new title page) I'm pretty sure the material in HSN3 includes some of the material that has happened since HSN2 came out, the same way that N3 includes some of the material that has happened since N2 came out. But I don't have my HSN2 copy handy to compare.
  12. As specified by the Dodge rules, the first step you have to do is separate the engaged models by 1mm. If the Move specified by the Dodge is no longer valid after separating the models, then you're done. That's all that you need to worry about for the Dodge. If those are friendly models if equal or lower S values and gets past them, sure. If the movement would enter base contact with an enemy model, it stops short. For reference: The order declaration sequence determines that. The active turn models have declared and resolved their movements, those positions are final. This is not 2nd edition, there is no uncertainty or "everything happens at once" nature for movement. The quantum Dodge and engage is dead. Look at the part of the order declaration sequence where movements are declared and then executed. That's WHY. The fact that skills are resolved along the movement path doesn't change anything. There's no difference in resolution. If the Disengage succeeds, you separate the model from everyone, whether that bace contact was established this order or in a previous order.
  13. "If you fail that roll, not only do you automatically lose, but I get bonus points. And you can't re-roll because it's not a friendly trooper. If you agree to that, you can use Doctor on the HVT." Do you think the other player would have accepted the consequence of failing the roll?
  14. More importantly, note that nowhere in "neutral" does it make the model 'friendly': Compare that to friendly: One of the parts that prevents you shooting your own HVT is the civilian status: Anyone tempted to use Doctor on a civilian (either an HVT or regular civilian) should remember the penalty for causing a civilian to die: Civil liability lawsuits in Infinity are serious business. The scenarios are only giving an exception to the rule for attacking the other player's HVT. Note that you can't use a MediKit on the HVT because it specifies: But Doctor just requires being in base contact with the target, with Engaged being what prevents Doctoring the enemy. (Only about half of Doctor mentions trooper.)
  15. I think you've overlooked this statement in "The target can only benefit from the effects of one GADGET Program at a time. Players must declare which one they will apply." Fairy Dust is a Gadget program. Reboot is a Gadget program. [Considering that that statement is in a GADGET-EVO program, I think it's safe to conclude that GADGET-EVO programs are considered GADGET programs.] That seems to rule out applying the effects of both Fairy Dust and Reboot without having to figure out what the yellow text bullet point means.