You are currently viewing HCRealms.com, The Premier HeroClix Community, as a Guest. If you would like to participate in the community, please Register to join the discussion!
If you are having problems registering to an account, feel free to Contact Us.
I if got a character adjacent /next to a character with poison, a solid wall divided them [the thick black line], do my character still take damage from the poison?
I if got a character adjacent /next to a character with poison, a solid wall divided them [the thick black line], do my character still take damage from the poison?
No. Poison requires adjacency. The wall breaks adjacency.
If the wall is between the characters, the characters aren't adjacent.
The wall makes sense, but two characters on diagonal squares also form a "wall" blocking line of fire. That said, is a character in a diagonally adjacent square considered adjacent for the purposes of poison if the line is blocked by the aforementioned diagonal characters, already adjacent? Does my question
make sense? Example below:
12
34
Character 1 has poison. 2&3 are poisoned on his turn. Is 4 safe or does 4 receive poison regardless of 2&3 forming a blocked line of fire?
The wall makes sense, but two characters on diagonal squares also form a "wall" blocking line of fire.
No, they don't.
This a very good example of why it is never a good idea to think of things in shorthand terms or to think of them as being something else.
They do not block line of fire because they form a wall. They block line of fire because the rules say that they block line of fire. Walls also block line of fire because the rules say that they block line of fire.
The fact that both things block line of fire does not automatically mean that the two are the same thing. It simply means that both things block line of fire.
Alright, that's fine. This is why I am initiating discussion because we want to play the right way when we play. Thus, (correct me if I'm wrong, please) by this rationale, the following actions, all employing the use of the word "adjacent" do not consider line of fire consisting of diagonally line-of-fire-blocking "non-terrain" characters when activated:
Forceblast D6 effect
Energy Explosion aftereffects
Poison
Pulse Wave ("these lines of fire ignore all game effects except for walls, blocking and elevated terrain")
Smoke Cloud (after first legal smoke cloud has been placed)
Super Strength (picking up and placing objects)
Defend
Mastermind
Empower
Enhancement
Leadership
Support
any Close Combat Attacks ("A close combat action can be given to a character to activate a close combat attack that targets an adjacent opposing character")
Yes or no?
Last edited by Johnny Blaze; 07/28/2013 at 02:45..
This a very good example of why it is never a good idea to think of things in shorthand terms or to think of them as being something else.
They do not block line of fire because they form a wall. They block line of fire because the rules say that they block line of fire. Walls also block line of fire because the rules say that they block line of fire.
The fact that both things block line of fire does not automatically mean that the two are the same thing. It simply means that both things block line of fire.
PS
Guilty of explaining a fallacy that has been a consistent paradigm in my gaming corner, I suppose. Merely exploring this forum for the correct interpretation from more experienced players than I.
The real problem is in the wording of adjacency in rulebook as follows:
"Adjacency: Squares on opposite sides of
blocking terrain are not adjacent. Two squares
of blocking terrain adjacent to each other
across the diagonal of an intersection would
prevent adjacency between the two squares
on the opposite side of that intersection."
If your character is in a square it blocks line of fire, but as someone already pointed out, "characters are not terrain". A glib, though astute observation. I think it is an easy mistake to make and, you're right, one which is a serious oversight as a result of a casual observance of the rules.
Last edited by Johnny Blaze; 07/28/2013 at 02:36..