Hi,
Summoning (not just playing) “Korrak the Bloodrager” while having “Spiritsinger Umbra” onboard cause an infinite trigger-loop of korrak’s deathrattle .
It result in board full of hard-to-remove 3/5 as soon as turn 4… Which is obviously not sane nor fair.
I globally find Korrak’s deathrattle fair, despite being too easy to trigger. But that specific interaction goes overboard.
I feel that the true culprit is Umbra’s ability; Which globally triggers in too many scenarios.
I suggest to fix it by making Umbra only trigger deathrattle of played minions instead of summoned ones.
Regards,
This is the bug report forum. If you want to make card suggestions, you should post under community discussion. You’re more likely to get better feedback there. Take care!
-Valas
1 Like
This is a bug report ; The interaction between the two card does not work as expected :
Neither I or my opponent expected me to fill my board with copies of Korrak. I merely expected one copy.
Consequently, my opponent conceded/rage-quitted which is bad gaming experience for both the player.
Your expectations were incorrect.
Umbra: “After you summon a minion, trigger it’s Deathrattle”
Korrak: “If this wasn’t honorably killed, resummon Korrak”
Korrak is summoned, Umbra triggers it’s deathrattle, Korrak was not honorably killed so another Korrak is resummoned and the cycle repeats until the board is filled. This is EXACTLY how the cards should interact. This is NOT a bug…
You suggesting CHANGES to Umbra further demonstrates that you KNOW this isn’t a bug, and instead acknowledge that it is an UNDESIRABLE effect (something you don’t like), but working exactly as intended.
Please explain how this is a bug instead of something you don’t like / didn’t expect.
-Valas
3 Likes
There’s rules as written (RaW), there’s rules as intended (RaI) and there’s rules as fun (RaF).
You may indeed argue that the interaction works under RaW. It is.
But it’s certainly not fun. My opponent raged-quitted. If it were a tabletop game, I would make up some house rule to fix the situation. Using a litteral interpretation of the rule would be nonsensical. Because, there’s virtually no way for my opponent to make a comeback. (you would need to deal exactly 5 damages to all my board on turn 5. How many decklist could realistically pull it off ?)
And I daresay it does not work as intended :
Let’s compare it to the interaction with Baron Rivendare.
Both umbra and rivendare triggers deathrattle. Both are 4 costed, and have roughly the same body. They’re are both balanced around the same expectation : You’re meant to leverage the effects of your deathrattle twofold.
The difference being that rivendare do so at the death of the minion; whereas umbra do so on summoning. Which doesn’t make much difference.
My point is that Korrak currently break that balance :
If you play it with Rivendare, you will trigger its deathrattle twice. As intended.
If you play it with Umbra, you will trigger its deathrattle up to six time. Which is broken.
It may not be bugged from a coding perspective. But it is bugged in its design.
I understand where you’re coming from, but that’s more of a community discussion than a bug report. Umbra and Rivendare have two different functions, and both work as indicated based on the card text. Rivendare is limited to “twice” and Umbra is limited to “Summons”.
I do agree that a full board on turn 5 would be rather frustrating to deal with, though there certainly are ways to deal with it such as - killing Umbra turn 4, Mass dispell followed by dragonfire potion, 2x incanter’s flow into turn 5 flamestrike, etc… Sure, not a “fun” situation or one that players likely have an answer for, but you’re playing in wild, not standard, and absurd combos are going to be seen in this particular game mode. Furthermore, Splitting Festeroot + Umbra have interacted the exact same way Korrak does now, and that combo has been around for 3+ years.
Regardless, our discussion at this point furthers my original statement which was that this is more of a community discussion topic than a bug report. These card interactions aren’t, “bugged in design”, they’re simply undesirable based on what you refer to as, “Rules as Fun”.
I wish you the best, and simply feel that you’ll receive more feedback (and possibly results from developers) if you were to post in the appropriate forums. Take care!
-Valas
2 Likes
No…
There is no limit imposed on Umbra’s trigger, unlike Rivendere. If a minion is summoned and has a deathrattle, Umbra will trigger it.
What are you high on…it makes a world of difference. Cards like Pyros can’t stay on the field due to Umbra immediately triggering the deathrattle. Anomalous is an immediate 16 damage aoe on summon with Umbra on the field. Both these cards aren’t immediate triggers normally or with Rivendere and as such can be countered by silence or transform effects on them, or mitigated by killing Rivendere.
And the combo in question can be negated at turn 5 because at that stage it’s a two turn combo. If you want to prevent it, just kill Umbra before the opponents next turn…
The cards are behaving exactly as written and exactly as expected. This isn’t a bug. You not liking it doesn’t make it one. If you want to argue for a balance change, you can do so in the discussion forums. This doesn’t belong in bug report.
2 Likes