Just lost a match due to decktracker saying that Misdirect wasn’t an option so I 48 attack to my own face.
1 Like
use your brain instead of relying on addons maybe?
6 Likes
Opponent is hacking 100%, there are never errors in deck trackers ever.
What deck tracker told you misdirect “wasn’t an option” and why would you believe it? Hunter has multiple ways to generate spells, so even if they used 2 of them already they could get more.
1 Like
I believe the deck tracker shows all secrets possible when a secret is played and then removes them as they get tested for. Example: you run a minion face when mage secret is up and nothing happens -> ice block and vaporize get removed from the list.
1 Like
Can you post a replay of the game? If it can be determined which action incorrectly eliminated Misdirection from the Secret tracker, it can be reported to the tracker’s developers and fixed.
I also ran into decktracker not recognising the secret properly. It was a secret he had ruled out. Maybe the algo is not optimal. It was also a hunter secret in my case but i did forget which one.
Misdirect was removed as an option meaning it recognized it wasn’t possible based on play. I had options to check for it, I even removed a minion that could’ve be targeted instead of my face, but because decktracker eliminated it as an option along with freezing trap there was no way for him to prevent lethal. I even dumped an extra spell that was a part of lethal.
Had I known it was still an option I would’ve checked for it, I probably wouldn’t of triggered his other secret to summon a 6/6 rat, I would’ve just played more taunt minions or zilliax to restore health and burned his secret and waited a turn, instead I took 48 to the face based on an error. Not sure what action it mistook as a trigger for it but it definitely did as the only 2 options was 6/6 rat and something else that didn’t prevent lethal.
I’m thinking based on the replay, it removed it as an option because I went face, but it triggered freezing trap, removed misdirect as an option without it actually triggering in game.
https :// hsreplay . net / replay / 9itxWBwK993yAmtVY5Qx9X
I havent watched it, but your best bet is to email this replay explaining the bug to:
It seems decktracker fell victim to forgetting the play order. Secrets trigger in order of play, so because Freezing Trap triggered first, the Misdirection had no reason to trigger since the Hunter wasn’t attacked anymore.
Seems it can happen any time the attack fails before Misdirection would trigger. Someone reported Explosive Trap killing the attacker caused this as well. I added yours to the list.
https://github.com/HearthSim/Hearthstone-Deck-Tracker/issues/3850
Cool thanks, wasn’t sure where to bring the issue up. I should’ve known better, in fact as I was playing the turn I was questioning it because he’d recently played a secret and I wasn’t sure that option was cleared but I seen the deck tracker predictions said I was safe so I just relied on that since its usually pretty reliable.