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.
Blocking terrain is blocking terrain. Circular, I know , but what I am trying to say is that there is no difference between brown lined blocking terrain printed on the map and blocking terrain created by Barrier. The Barrier will go away eventually, but they otherwise follow all the same rules.
Ok, so if that square was brown, it wouldn't block LoF of elevated to ground on that diagonal.
Elevated terrain and line of fire. An otherwise clear line
of fire between an elevated character and a grounded character is blocked
by grounded blocking terrain, giant characters and colossal characters.
So if blocking was in J13 there would be no LOF from K14 to I12
That's right, I mixed up grounded hindering and blocking in my thought process. If the fig that is grounded is a giant there would be line, but otherwise there isn't.
I think I know where the confusion is coming from
First, we have the example being asked about. Attachment 4456
Then, we have the following, which we are told, that intersections between hindering types, takes on the properties of the lowest terrain type
The below image would be considered passing through hindering. Attachment 4457
With the first example, the line is going through two elevated terrain corners.
Just letting everyone know that us rules-types decided to take a closer look at this issue and after discussing it for a bit and asking for GD's input, we've come to the conclusion that the new intersection rules need a wee bit of tweaking. Not much, and not enough that it will really impact game play most of the time (so keep using it as-is for now).
But this particular issue with the odd shaped corner created by the elevating terrain just wasn't sitting quite right and we realized that the intersection rules don't really support the 'on the exact diagonal, so it is clear' interpretation. In other words, the LOF under question in this thread would indeed be blocked, despite some of our original Orange-answers to the contrary. THAT is the wording that will be tweaked: to make it very clear that LOF is blocked in a situation like this.
Like I said, it shouldn't change the overall play of the game too much, so for now continue on as best you can. However, the issue has been noted and the revised intersection rules will be in the next Player's Guide.
The intent of the rules regarding intersections is that the LOF across an intersection is EITHER one square OR the other - whichever is in the LOF's favor (i.e., as clear as possible, blocked only if both squares cause blocking).
With that in mind, the "inside corner" of elevated terrain has 2 squares across the intersection. If the LOF would cross either one of those individually, the LOF would be blocked. Therefore, the LOF through that intersection is blocked. I think someone else on this thread got to this before we did and that guy gets a cookie.
So just to double clarify...in this case the line of fire is blocked from I12 to K14 because if the LOF went through either adjacent square of the intersection, the LOF would be blocked.
So just to double clarify...in this case the line of fire is blocked from I12 to K14 because if the LOF went through either adjacent square of the intersection, the LOF would be blocked.
Just remember that many people will see this change as bad. When they do, it will be you that they will blame.
Really???? Is that like finding a new star? Do I get to name the catchphrase?
Like it is now known as the "That stupid hillbilly from Iowa JB (who has a really cute 3 mo old baby) rule?"
And it's ok to admit that my baby intimidated you into changing your mind. I mean, the same day I put his photo up as my avatar, this ruling comes down. Coincedence? I think not.
Just letting everyone know that us rules-types decided to take a closer look at this issue and after discussing it for a bit and asking for GD's input, we've come to the conclusion that the new intersection rules need a wee bit of tweaking. Not much, and not enough that it will really impact game play most of the time (so keep using it as-is for now).
But this particular issue with the odd shaped corner created by the elevating terrain just wasn't sitting quite right and we realized that the intersection rules don't really support the 'on the exact diagonal, so it is clear' interpretation. In other words, the LOF under question in this thread would indeed be blocked, despite some of our original Orange-answers to the contrary. THAT is the wording that will be tweaked: to make it very clear that LOF is blocked in a situation like this.
Like I said, it shouldn't change the overall play of the game too much, so for now continue on as best you can. However, the issue has been noted and the revised intersection rules will be in the next Player's Guide.
Thanks!
Yay GD!
I support this ruling.
Quote : Originally Posted by jbship628
Like it is now known as the "That stupid hillbilly from Iowa JB (who has a really cute 3 mo old baby) rule?"
Well, if you get to name it I would probably leave out a couple of the adjectives, or at least use different ones.
Besides, how many maps out there have that indented corner?
If you really want to know, off the top of my head, I'm pretty sure on all of these (unretired maps only):
Asgardian Fountain
Dawn of Man and at least one of its Time Zones (the castle)
Great Arena
Space
Junkyard
Convention Exclusive Castle Ruins
Latveria
Legion of Super Heroes Plaza Square
LoSH Small Town
Danger Room Training Complex
Danger Room Institute Grounds
Icons Zoo
Yep, the game's ruined. Of course, I also have to wonder why I have that information just sitting in my brain.