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.
Mob mentality does protect from Sinestro, cause the people are not attacking when sinestro attempts to stun them, so they are guarded by Mob Mentalities effect.
that is, if you have some way of making those guys physical
It is an interesting question though, since sinestro says 'stun that ATTACKER' and since his effect resovles after the attacker is no longer an attacker, how does sinestro even work at all?
It definitely seems like an inconsistency in the timing of things to allow sinestro to stun as he does but not count mob mentality in a similar way. If sinestro said 'stun that character', for instance it would not be an issue at all, since it would trigger just as he is supposed to, but then stun after combat, as he is intended to. It just seems that the use of the word attacker is the source of the inconsistency to me.
I'm fully aware that this is how he works, mind you, but doesn't it look like an inconsistency to anyone else?
It seems that way with a casual glance, but the phrase, 'that attacker', is a reference to which character is getting stunned. The game no longer recognizes the character as having the attacker characteristic, but it knows that it did attack, and it's fairly intuitive for players to reference the former attackers. They could have added 'former' to the phrase, but it's unnecessary and a bit bulky. There's no real problem there. :)
(totally-out-of-left-field video game analogy ahead)
Sinestro's effect is like a douchebag teammate in (Warcraft 3 mod) DotA. You know, the kind of guy that runs in after your team blows its entire load trying to win the skirmish and is now lying dead, then proceeds to kill the almost-dead enemy team just for the score. (and the right to say his teammates suck :cheeky: ) In no way was he involved in combat, ever, it just happens really really right after.
Its like that issue with Cosmic giving invulnerability. A character can't have the invulnerability after it stuns because the counter is lost so it appears that the invulnerability has no effect. The fact of the matter is that at the time of combat stuns the game is in the spot where any sort of information and cause-and-effect relationships you have is totally screwed up. Its arguably the point when you have the least complete information, a mini Vs-Heisenberg Principle effect! So the game looks at the last known point where it had complete information i.e. the instance JUST before the stunning happened.
This is a similar (although I hesitate to say identical) occurence.