Bluetracker

Tracks Blizzard employees across various accounts.

Patch 2.4.2 Hotfixes - Updated 8/4 - Forums

Nevalistis

Posted 8 years, 1 month ago (Source)

Thanks very much! :)

You're welcome! Have fun in S7.
Nevalistis

Posted 8 years, 1 month ago (Source)

I do not understand the priorities of the Developers... can someone explain it to me please? Twister Wizard was ignored for 2 whole Seasons. Even the Firebird Bug was then acknowledged and left untouched for another season. Other important changes to the balance for different classes and sets are being LEFT UNTOUCHED for quite a while now... being consistently ignored (for example Crusader and their set problems, Barbarian Waste Set etc...). What is going on here... ? Why is something like this immediately prioritized... ?

The basic answer is that some fixes are easier to deploy than others. Firebird's presented us a lot of different challenges (though I can't speak to the specifics, as I'm not a developer). In this case, we determined we could fix quickly, it was just a matter of determining whether it could be a hotfix or required patching.

All changes take a variable amount of research, implementation, and testing. Some are more cumbersome than others.
Nevalistis

Posted 8 years, 1 month ago (Source)

Slightly OT, but does anyone know how you hide the UI? Thanks in advance.

The hotkey for it is Alt + Z. :)
Nevalistis

Posted 8 years, 1 month ago (Source)

I'd decided on something other than WD but why wait until the night before to do this? A lot of people's plans are going to get shit on because of this.

You'll find more information behind the change here.

TLDR: The build was discovered fairly late in the PTR, and we couldn't get a fix into the patch. Investigating whether or not something is a hotfix is not an instantaneous process.

<blockquote class="quoted">
    <div class="md"><p>Thanks very much! :)</p>
</div>
</blockquote>
<div class="md"><p>You're welcome! Have fun in S7. </p>
</div> (<a href="http://us.battle.net/d3/en/forum/topic/20748074646#1d65qxy7">Nevalistis</a>)
<hr/>

<blockquote class="quoted">
    <div class="md"><p>I do not understand the priorities of the Developers... can someone explain it to me please? Twister Wizard was ignored for 2 whole Seasons. Even the Firebird Bug was then acknowledged and left untouched for another season. Other important changes to the balance for different classes and sets are being LEFT UNTOUCHED for quite a while now... being consistently ignored (for example Crusader and their set problems, Barbarian Waste Set etc...). What is going on here... ? Why is something like this immediately prioritized... ?</p>
</div>
</blockquote>
<div class="md"><p>The basic answer is that some fixes are easier to deploy than others. Firebird's presented us a lot of different challenges (though I can't speak to the specifics, as I'm not a developer). In this case, we determined we could fix quickly, it was just a matter of determining whether it could be a hotfix or required patching.</p>

<p>All changes take a variable amount of research, implementation, and testing. Some are more cumbersome than others.</p>
</div> (<a href="http://us.battle.net/d3/en/forum/topic/20748074646#1d65pol5">Nevalistis</a>)
<hr/>

<blockquote class="quoted">
    <div class="md"><p>Slightly OT, but does anyone know how you hide the UI? Thanks in advance.</p>
</div>
</blockquote>
<div class="md"><p>The hotkey for it is Alt + Z. :) </p>
</div> (<a href="http://us.battle.net/d3/en/forum/topic/20748074646#1d65pkxo">Nevalistis</a>)
<hr/>

<blockquote class="quoted">
    <div class="md"><p>I'd decided on something other than WD but why wait until the night before to do this? A lot of people's plans are going to get shit on because of this.</p>
</div>
</blockquote>
<div class="md"><p>You'll find more information behind the change <a href="http://us.battle.net/d3/en/forum/topic/20747675200?page=6#110">here</a>.</p>

<p>TLDR: The build was discovered fairly late in the PTR, and we couldn't get a fix into the patch. Investigating whether or not something is a hotfix is not an instantaneous process.</p>
</div> (<a href="http://us.battle.net/d3/en/forum/topic/20748074646#1d65phq5">Nevalistis</a>)
<hr/>

Tweet

<p><div class="md"><p>You're welcome! Have fun in S7. </p>
</div> (<a href="http://us.battle.net/d3/en/forum/topic/20748074646#1d65qxy7">Source</a>)</p>

<p><div class="md"><p>The basic answer is that some fixes are easier to deploy than others. Firebird's presented us a lot of different challenges (though I can't speak to the specifics, as I'm not a developer). In this case, we determined we could fix quickly, it was just a matter of determining whether it could be a hotfix or required patching.</p>

<p>All changes take a variable amount of research, implementation, and testing. Some are more cumbersome than others.</p>
</div> (<a href="http://us.battle.net/d3/en/forum/topic/20748074646#1d65pol5">Source</a>)</p>

<p><div class="md"><p>The hotkey for it is Alt + Z. :) </p>
</div> (<a href="http://us.battle.net/d3/en/forum/topic/20748074646#1d65pkxo">Source</a>)</p>

<p><div class="md"><p>You'll find more information behind the change <a href="http://us.battle.net/d3/en/forum/topic/20747675200?page=6#110">here</a>.</p>

<p>TLDR: The build was discovered fairly late in the PTR, and we couldn't get a fix into the patch. Investigating whether or not something is a hotfix is not an instantaneous process.</p>
</div> (<a href="http://us.battle.net/d3/en/forum/topic/20748074646#1d65phq5">Source</a>)</p>
    
    <hr/>