Not sure if this is a bug or not but I’d like to know if this is intended to work this way. I was growing tired of the secret hunter/mage meta I’ve been running into and added eater of secrets to my deck. My mage opponent had objection up and instead of it destroying it, it got countered by it first. Its battlecry is destroy ALL secrets so shouldn’t it destroy objection before it gets activated? I had assumed that and didn’t play a minion to test it first and it basically lost me the game
Intended. The Counter keyword triggers on play, which comes before Battlecry resolution, and negates all following events, and destroys the card.
1 Like
Same thing goes with flare and counterspell like secrets
1 Like
Well that’s very misleading then. Obviously if I’m playing that card the secrets are already going to be in play. So if all they have to do is have objection in play, seems like it’s not doing what it was intended to do
well at one point when a card counters a card that counters a card, one of them has to go first, and one will not do its job because it has been countered, no matter which one they chose to go first
I had the same issue and I don’t like it either. A card should have a counter. But only a hunter’s flare can remove the secret Objection, and not a neutral card.
I guess that’s why Objection is such a hated card.
objection is the counter to battlecry minions
Every secret has a counter: trigger it with a different card to save the card you intend to use.
Or, you know, play a low-value minion into the Objection, then play your real minion after.
It counters every minion, not only the battlecry ones.
You know why it’s bullshi*t? Because secrets pop in order that they are put… however, that retard card objection outpass the other secrets that the Eater of Secrets can remove. So no, the objection card is not fair.
I’m struggling to understand what you mean by that it ‘outpass’ the other secrets. Are you saying it proc’s out of order…? If so, let’s hear some examples so we can discuss it I guess. Most of the time, countering secrets proc out of order for specific reasons [take the spellbinder one and counterspell for example].
Other than that, declaring that objection is an ‘unfair’ card isn’t about bug reporting anymore. This is the bugs forum.
Objection indeed does not care of play order
In fact, objection is the only (to my knowledge) minion-oriented secret of the game that doesn’t trigger after the minion is played but before, so it can really counter the minion and all the effect that comes with it. Unlike potion of polymorphy that only triggers after the minion has been played, for example
I think the wiki is outdated on the rulebook but here’s the link of that :
https://hearthstone.fandom.com/wiki/Advanced_rulebook#Playing/summoning_a_minion
In resume :
Playing/summoning a minion
- The card is removed from your hand and its Mana cost is paid. The card enters Play as a minion, creating a Summon Event and becoming interactible. […]
- [Play Phase]
- [Whenever a minion is summoned phase]
- Battlecry Phase […]
- After Play & After Summon Phase [Secrets…]
[…]
Normal secrets trigger on phase 5, but objection triggers between phase 1 and 2. The secret does its check first regardless of the play order of the secrets since other secrets wait for their checks on phase 5
you are forgetting something objection is a WHEN card
when cards trigger when the condition is met but before it fully resolves
is the same as whenever
secrets that trigger in a similar way are counterpsell
spell bender
the same way we have secrets triggering
when a monster attacks(bait and switch ) resolving before it hits the target
and
after a monster attack ( reckoning ) resolving after it deals damage
Other secrets pop in order that they are put IF they all should pop upon some event.
But if the minion is countered, then other secrets have nothing to react to.
It’s not about Objection. You’re missing the point. It’s about Eater of Secrets not actually doing what it’s supposed to do… eat the secrets.
No, it’s about interaction of eater and objection. So it’s definetely also about objection. And if it’s not, why do you talk about it?
Anyways, you suggest to favor one counter over another. And then the same topic may be raised: “why my objection doesn’t work? It clearly says “counter a minion”, but enemie’s eater of secrets wasn’t countered”. What would be the point of that? It was somehow obvious to me that eater of secrets is the one who should be countered, because objection cancels battlecries. Why would eater’s battlecry be an exception to that rule? Regardless of what this battlecry says.
There are plenty of situations where a card won’t do what it is “supposed” to do, because some other card or effect stops it.
For example if I play Fireball on a minion with divine shield, the Fireball doesn’t deal six damage, because divine shield prevents the damage. That’s it’s job.
Or if I play Fireball when my opponent has a Counterspell, it’s the exact same situation as Eater. The Fireball is countered, so it never deals damage.
Eater of Secrets is no different. It doesn’t eat the secrets because it got countered. Objection has earlier timing, so it wins. Objection did its job before Eater could do its job. Simple as that.
3 Likes
that would be a bug because objection is supposed to prevent it from happening
Listen, I understand that your initial reaction to eater of secrets was ‘aha, a counter to secrets!’ and for the most part it is. But then you learned it’s imperfect. So now we’re here. You understand how the cards work and now you have a fuller picture of how to try to interact with secrets and play around them in future games.
So, the discussion is over. If you still think it’s unfair, then, that’s still a different issue.