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.
So if I call in a Colossal retaliator though an ID card, would they be able to retaliate based on their wording?
ID card - Friendly characters have "POWER: If no other friendly characters have been given this same action this turn and this character is equal or more points than the ID character, place the ID character adjacent, then remove this ID card from the game and your opponent scores it.
Colossal Retaliation: "If no friendly character has been placed this turn"
I m inclined to believing no, the character wouldn't be able to retaliate, but I wanted to get a ruling on it. Thanks!
They can use their Retaliation. Pg. 12 of the rulebook-
Quote
Placing a game piece onto the map from off the map (including at the beginning of the game) isn’t the same as the game term “place” discussed here. “Can’t be placed” effects stop Telekinesis, carrying, knock back, and any other effects that choose a character already on the map and place it elsewhere on the map, but do not affect “placement” from off the map onto the map.
We need a different word for putting pieces on the map from outside than "placing". "Summon" mayhaps? Or "recruit"?
We do, but this is nothing new, and WK doesn't seem inclined to change it.
Waller KOs: AA Robin, Kid Devil, Joker, Question; AW E Cap; FCBD Iron Man; Miracle/Oberon; John Stewart x2, Iron Patriot; Shatterstar; IH Herc; CW Photon & Nitro; FF Nite Owl; 10An R Thor, E Iron Man, Weapon X; FF Kilowog; Hugo Strange; Calender Man; Legion Cosmic Boy & Lightning Lad, LE Pete Wisdom
We need a different word for putting pieces on the map from outside than "placing". "Summon" mayhaps? Or "recruit"?
I wish they hadn't chosen "generate" for bystanders because you can't really borrow it for this. I mean you can, it doesn't feel right to have an ID card "generate" though IMO.
So the placing by id card is considering a "different placement" because is from "off the map" to "on the map".
I have different situations to be seen:
1-I use a colossal retaliation with surtur already on the map(this is a placement) , surtur calls id colossus prime: can colossus prime use colossal retaliation?I don't think so...
2-I use a telekinesis on a piece(this is a placement), that heroclix call colossus prime, can colossus prime use colossal retaliation? I don't think so...
3-I use free placement 3 squares kobik cosmic cube(this is a placement), kobik calls id colossus prime, can colosus prime use colossal retaliation? I don't think so...
Those are all No. Not sure where the confusion is from?
Agreed.
I'm guessing the confusion is coming from the misunderstanding of placing a character.
Because bystander generation and ID call-in placement won't bar Colossus Prime from using Colossal Retaliation, players convince themselves the wording is "confusing" and then question all uses.
It's like I tell my students, it's the difference between understanding vs vaguely getting it. If you vaguely get it, you don't understand. As long as the question is to seek understanding, people learn.
Visible Dials and Pushing Damage need to be optional. This is the way.
Thanks.
So colossal retaliation of iceman/storm/colossus/phoenix is very hard to do, because you have to keep the character within 5 squares from caller id, and the only way to move the caller id and call id (using retaliation) is side step.
So id colossal retaliation has the following "range"
Storm prime : +2 side step caller id +5 squares +1square(because it is a close) tot=8
Colossus prime: +2 side step caller id +5 squares +2 squares.for giant reach 2 :tot=9
Iceman and phoenix tot=10 for giant reach 3.
So storm colossal retaliation is very strong but in my opinion is very hard to be played
Thanks.
So colossal retaliation of iceman/storm/colossus/phoenix is very hard to do, because you have to keep the character within 5 squares from caller id, and the only way to move the caller id and call id (using retaliation) is side step.
So id colossal retaliation has the following "range"
Storm prime : +2 side step caller id +5 squares +1square(because it is a close) tot=8
Colossus prime: +2 side step caller id +5 squares +2 squares.for giant reach 2 :tot=9
Iceman and phoenix tot=10 for giant reach 3.
So storm colossal retaliation is very strong but in my opinion is very hard to be played
Correct.
And, to me, that is a good thing.
The combo you are proposing is an anathema to everything that I enjoy about Heroclix. Totally legal, mind you, but something I would personally never consider fielding
So the fact it has several limitations (not enough in my mind) is a stumble towards improved design.
Now if only map designers would move towards balance... Ah, - but that is a rant for another time.
Visible Dials and Pushing Damage need to be optional. This is the way.
Because bystander generation and ID call-in placement won't bar Colossus Prime from using Colossal Retaliation, players convince themselves the wording is "confusing" and then question all uses.
As an engineer who has done a fair amount of technical writing over a couple decades, I can confidently assert that using the same keyword for two similar but distinct meanings constitutes poor documentation.
When it is a game rule book, it generates argument about intent and whether it is confusing or not. When it is a requirements document, it results in the delivery of systems that don't do what the customer intended.
In the later case I can speak from experience it doesn't result in endless bickering over what the intent was - it results in expensive redesigns and the document writer losing their job. Just because the consequences for the former case are significantly less doesn't make the initial bad practice any more excusable. Clean up the documentation, don't blame the customer for the publishers' mistakes.
As an engineer who has done a far amount of technical writing over a couple decades, I can confidently assert that using the same keyword for two similar but distinct meanings constitutes poor documentation.
When it is a game rule book, it generates argument about intent and whether it is confusing or not. When it is a requirements document, it results in the delivery of systems that don't do what the customer intended.
In the later case I can speak from experience it doesn't result in endless bickering over what the intent was - it results in expensive redesigns and the document writer losing their job. Just because the consequences for the former case are significantly less doesn't make the initial bad practice any more excusable. Clean up the documentation, don't blame the customer for the publishers' mistakes.
While I don't disagree that WK should change the terms, it has been discussed and documented enough times that it should be filtering through the HeroClix population - but especially in this thread.
That being said, there are plenty of misapplications of clear terms because of bias from the reader, a stated exception misinterpreted as a 'new rule', and of course the ever-present "I read it somewhere".
Again, I agree WK really should use a new term for bringing a figure into the game other than "place", the fact the question follows an explanation of the difference between the terms (and included documentation) is why someone did not understand how there could be befuddlement. I was merely offering an explanation on why someone is asking a question which was already answered.
Visible Dials and Pushing Damage need to be optional. This is the way.
In this situation I call storm prime, she makes running shot pulse wace and she is with a part of the dial within 5 squares from caller id and with the other part is out of 5 squares: what happen? Does She remain or she go away?