Bluetracker

Tracks Blizzard employees across various accounts.

Defeating this tutorial, barrel to victory, is impossible. One turn, and 6 +1 mana, but costs of 8. Thx riot.

ACarelessWhisperer

Posted 5 years, 1 month ago (Source)

Welllllll that's a beatdown. Looking into a fix now and I'll try and update the thread when we have an ETA.

Sorry about this y'all!

Okay, update time!
ETA on the fix for this is next patch (1.14). If we end up doing a redeploy for anything else the fix for this will get included. We are going to add a warning message in the client (the little ! you sometimes see next to the quest menu) so hopefully other players don't get caught by this.

I also wanted to take a moment and say sorry to y'all that got stuck on this, I understand how frustrating it can be to burn a lot of time trying to solve something only to find out it was busted.

Lastly, thank you for posting this! It sucks to see bugs escape to live, but threads like this help a ton in letting us understand how bad a bug is, and the impact of it on players. Supes appreciate it.
ACarelessWhisperer

Posted 5 years, 1 month ago (Source)

Welllllll that's a beatdown. Looking into a fix now and I'll try and update the thread when we have an ETA.

Sorry about this y'all!

<blockquote class="quoted">
    <div class="md"><p>Welllllll that's a beatdown. Looking into a fix now and I'll try and update the thread when we have an ETA.</p>

<p>Sorry about this y'all!</p>
</div>
</blockquote>
<div class="md"><p>Okay, update time!<br/>
ETA on the fix for this is next patch (1.14). If we end up doing a redeploy for anything else the fix for this will get included. We are going to add a warning message in the client (the little ! you sometimes see next to the quest menu) so hopefully other players don't get caught by this. </p>

<p>I also wanted to take a moment and say sorry to y'all that got stuck on this, I understand how frustrating it can be to burn a lot of time trying to solve something only to find out it was busted. </p>

<p>Lastly, thank you for posting this! It sucks to see bugs escape to live, but threads like this help a ton in letting us understand how bad a bug is, and the impact of it on players. Supes appreciate it.</p>
</div> (<a href="https://i.redd.it/nzi236v1vvv51.jpggafzxdq">ACarelessWhisperer</a>)
<hr/>

<blockquote class="quoted">
    
</blockquote>
<div class="md"><p>Welllllll that's a beatdown. Looking into a fix now and I'll try and update the thread when we have an ETA.</p>

<p>Sorry about this y'all!</p>
</div> (<a href="https://i.redd.it/nzi236v1vvv51.jpggafc3nq">ACarelessWhisperer</a>)
<hr/>

Tweet

<p><div class="md"><p>Okay, update time!<br/>
ETA on the fix for this is next patch (1.14). If we end up doing a redeploy for anything else the fix for this will get included. We are going to add a warning message in the client (the little ! you sometimes see next to the quest menu) so hopefully other players don't get caught by this. </p>

<p>I also wanted to take a moment and say sorry to y'all that got stuck on this, I understand how frustrating it can be to burn a lot of time trying to solve something only to find out it was busted. </p>

<p>Lastly, thank you for posting this! It sucks to see bugs escape to live, but threads like this help a ton in letting us understand how bad a bug is, and the impact of it on players. Supes appreciate it.</p>
</div> (<a href="https://i.redd.it/nzi236v1vvv51.jpggafzxdq">Source</a>)</p>

<p><div class="md"><p>Welllllll that's a beatdown. Looking into a fix now and I'll try and update the thread when we have an ETA.</p>

<p>Sorry about this y'all!</p>
</div> (<a href="https://i.redd.it/nzi236v1vvv51.jpggafc3nq">Source</a>)</p>
    
    <hr/>