Mistress of Pain + Auchenai Soulpriest Bug

On December 12 2014 16:23 Geo.Rion wrote:
^Yeah, it always amazes me, how some people take the time to reply some undermining shit, but cant read the 5-10 lines of the OP they re trying to discredit.

Probably the bug occurs because Soulpriest considers the self-damage taken to be an attack of the player, thus triggering MoP again, which triggers her again etc... Obviously a bug.

On December 12 2014 16:05 kingjames01 wrote:
Did you even read the post? Apparently he enters into an infinite loop whereby he loses ALL of his HP.

On December 12 2014 16:23 Geo.Rion wrote:
^Yeah, it always amazes me, how some people take the time to reply some undermining shit, but cant read the 5-10 lines of the OP they re trying to discredit.

Probably the bug occurs because Soulpriest considers the self-damage taken to be an attack of the player, thus triggering MoP again, which triggers her again etc... Obviously a bug.

On December 12 2014 16:59 Fleetfeet wrote:
Considering that there are exceptions for other potential infinite loop scenarios (Jeeves comes to mind) it does seem odd that this actually infinite loops, so I can see why people are calling it a bug.

On December 12 2014 17:07 Sutty wrote:
At the end of the day, something following the card text should not be reported as a bug in the first place.

You just have to google the "Mistress of Pain Auchenai Soulpriest" to see all the examples of past instances of this...

On December 13 2014 00:46 Zampano wrote:
Ok, let's try this again. Every time Mistress of Pain causes damage, she restores that much health to your hero. With ASP, she attacks, does 1 damage, then procs. The Proc causes the Mistress of Pain to deal 1 damage to your hero, which procs Mistress' ability and so on. No inconsistency,

On December 13 2014 00:52 Zampano wrote:
The reason HS is less likely to have viable infinite combos than MTG is that there are caps on Health and card draw, making those much less desirable, as well as cards having built in limits, such as Bouncing Blade. They shouldn't fix this interaction, as it's very unusual and can't be consistently abused.

On December 13 2014 00:31 S1eth wrote:

I will never understand the minds of people who have to decide between "do a 5 second google search, or spend 10 minutes making a forum post AND a bug report and then wait for responses" and choose the latter option.

They're causing trouble for both themselves and others. Maybe they're just extremely extroverted and looking for attention or something.

On December 12 2014 17:55 Origence wrote:
I doubt they fix it, is a ctually one of these incredible stories that can happen in Hearthstone.
The combo is quite hard to pull off.
To start with is a huge misplay from part of the Priest, so he deserves to lose anyways.

The annoying part is that it limits priests to put both Auchenai and Piloted Shredder in same deck to avoid this combo to happen.

On December 13 2014 03:00 RenSC2 wrote:

Just don't play auchenai at the same time as shredder unless you have a way of finishing off the soulpriest on your turn. Likewise, you can play a thoughtsteal mistress, just make sure you let it die before dropping the soulpriest.

On December 12 2014 17:34 Wuster wrote:


Jeeves is more a case of poor/ambiguous wording than an infinite loop imo. Probably it's because I'm a programmer by trade, but I understood that what it really meant by 'draw until' was 'draw as a single action (draw 0-3 cards based on hand size)', which is why it doesn't infinite loop.

On December 13 2014 06:00 Fleetfeet wrote:


Sure, but technically the wording implies infinite loop. As would Bouncing Blade + Commanding Shout, which also has exceptions that prevent it from being an infinite loop.

I mean, I'm not offended by the idea that priests can oneshot themselves, but it -IS- inconsistent for them to allow this infinite loop while specifically working around others.

On December 13 2014 06:26 Acritter wrote:

The reason behind it is that all the other potentially infinite combos being either totally endless, reasonable to create within a game, or both. You can create a deck around Bouncing Blade+Commanding Shout and just troll people on ladder with it. You can kill yourself (or the other player) with Jeeves with literally any class. This combo can only happen if you yourself let it happen (barring some really weird Sylvanas situations) and requires two specific classes in order for it to work. It's rare enough that it's a cool and funny occurrence, and so has been left in the game based on Blizzard's do-fun-stuff policy.

That's why.

On December 13 2014 07:20 Fleetfeet wrote:


I understand that, and once again state "I can see how people are upset, seeing as it is inconsistent for them to allow this infinite loop while specifically working around others."

On December 13 2014 07:30 S1eth wrote:


Jeeves draws you 3 "fatigue cards". There, done.

On December 13 2014 06:00 Fleetfeet wrote:


Sure, but technically the wording implies infinite loop. As would Bouncing Blade + Commanding Shout, which also has exceptions that prevent it from being an infinite loop.

I mean, I'm not offended by the idea that priests can oneshot themselves, but it -IS- inconsistent for them to allow this infinite loop while specifically working around others.

On December 13 2014 13:30 NewSunshine wrote:

There's nothing inconsistent at all. In the case of Bouncing Blade, it was up to Blizzard's discretion as to what happens with Commanding Shout, since it's a corner case that isn't clear based on card text. For the Mistress of Pain loop to not kill you, they would have to make the card behave differently from how it's written, or otherwise change the card or rules about damage. Since it's such a rare case that can't be used with any consistency, and something a Priest should know to avoid, they're choosing to leave it as is, and let the cards do exactly what they say.

On December 13 2014 13:46 Fleetfeet wrote:


Jeeves reads "At the end of each players' turn, that player draws until they have 3 cards". If you don't already know how card drawing works in hearthstone, it would be fair to assume that it would kill you if you if a Jeeves was on the board, and you entered fatigue state with less than 3 cards in your hand, because it would attempt to draw until you had 3 cards. Obviously, it would be STUPID if it worked that way, but it's completely understandable were someone to read the text that way.

Similarly, the paladin card Divine Favor implies the same effect, where it would keep drawing until you have X number of cards in your hand. Again, this is NOT actually what happens with the card, and you in truth attempt to draw a number of cards that -would- give you the same number of cards as your opponent, provided you have those cards to draw. It does NOT do exactly what the card says exactly to avoid an infinite loop scenario.

+ Show Spoiler +

So yes, I do think that the Mistress of Pain + Auchenai Soulpriest scenario is inconsistent, even though it's doing exactly what the card text says.

On December 13 2014 16:45 Fleetfeet wrote:
While you wouldn't know about fatigue damage from overdraw until you first experience it, that wasn't the esoteric tidbit I was referring to. What I was referring to was the fact that, in cases of overdraw, a fatigue draw is considered "a card" even in situations where the card text says to draw till you have X number of cards in hand, as in the case of Divine Favor and Jeeves. That's not something that would be common knowledge, and until you know that, you would almost definitely read Divine Favor as "If you play this on the verge of fatigue, you fucking kill yourself".

Also I and most of the people I know that play HS have no other card game background. I'm assuming a fair amount of the game's population doesn't have experience from other card games to draw from.