an inconsistency when comparing proto calls to Invocations would be my best guess, the proto call must actually have Exodar dealing the damage otherwise shudderblock shouldn’t negate it
Shudderblock only prevents battlecry cards if trying to deal damage directly to the opponent’s hero. Since armor gain is not dealing damage, you would get 3x the already 2x armor for the health of the spaceship, or 6x times the spaceship health as armor.
wrong question, “why can’t the protocal”
we(people who read the cards) already know shudderblock prevents the damage that the Exodar does with a battlecry
I didn’t say it couldn’t, blizzard did
I never said it shouldn’t either, again they did
I would have been fine with it being that way from the start(If to meta dominating a nerf or rework to as is now) maybe then shaman starships could have been a real deck
this was my initial comment/interaction, just pointing out that hearthstone is very inconsistent
and then
I was simply being picky with his choice of words(and hearthstones) providing the information that the protocol(happy I spelled it right this time) doesn’t say what is dealing the damage and hearthstone considers the Exodar to be doing the damage so shudderblock negates it.
One interesting thing to think about is why it doesn’t allow to deal face damage
One obvious reason could be “so it doesn’t deal a quadrillion damage with a single battlecry”
Yeah
But it wouldn’t anyway, since you can’t tripple the effect of the Exodar
The battlecry both checks if you are building a starship AND launches it.
So at the time of the second battlecry, you are no longer building a starship and it simply fizzles.
Not a single protocol can be trippled with shudderblock because of that.
You just get scammed for free with the damage protocole where the first battlecry is not allowed to deal face damage