A minor patch and a round of hotfixes were released on the Diablo III servers Thursday. These brought fixes to client crashes and other bugs, along with updating the graphics to the in-game cursor. This took care of some glaring issues that showed up in Patch 2.4
, getting the game ready for the start of Season 5
on Friday evening.
Patch 2.4.0 Minor Patch Update
A small technical patch was released to fix a handful of client bugs, and to make the Diablo III cursor icon easier to see.
Users may notice a small patch going through today, launching in a similar maintenance-free manner as Patch 2.4.0. While there are no gameplay or balance changes going into this patch, there are a few updates we want players to be aware of:
- Fixed an issue where players running Diablo III on a 32-bit operating system could experience periodic client hard locks
- Fixed an issue where some players could experience a client crash after extremely long game sessions (5+ hours)
- A border has been added around the new mouse cursor to increase visibility.
Thank you for your patience while we worked to resolve these issues, and we'll see you in Season 5!
Login Server Issues
When the major Patch 2.4
landed on Tuesday, it was the first time a Diablo III patch was rolled out without any server downtime. The minor patch was intended to be deployed the same way, but it didn't go as smoothly. Players were disconnected from the server, and the login server was down
for a short time.
This shouldn't have happened at all; the intent was to deploy this patch similar to how 2.4.0 launched with no need for maintenance or downtime. Clearly, that was not the case.
We're investigating why players were removed from games and apologize for the inconvenience.
Patch 2.4.0 Hotfixes
The first set of hotfixes for patch 2.4 was pushed live along with the minor patch. Combined with the patch, these fix the biggest issues in the Patch 2.4.0 Known Issues
Below you will find a list of hotfixes recently applied or coming soon that address various bugs or mechanic tweaks.
These hotfixes should not require you to download a new patch. Some of the hotfixes below will go live the moment they are implemented while others may require restarting the game to go into effect. Please keep in mind that some issues cannot be addressed without a client-side patch. Also note that changes to certain abilities will not be reflected in its tooltip until a patch is issued.Last updated January 20. Hotfixes are denoted by the date they were applied to live servers.Previous Hotfixes: [2.2.0] [2.2.1] [2.3.0][LIVE HOTFIXES]Note: Items previously marked as "Upcoming Hotfixes" have now been applied and are consolidated in the notes below.General
- Fixed a crash that would occur when the Skeleton King attempts to continue to whirlwind while after he has been defeated (1/20)
- Fixed an issue that could prevent some players from logging in (1/20)
- Fixed an issue where Armor Scavengers (Primordial Scavengers) would not lose their armor when hit by pets. (1/27)
- Fixed an issue where the 6 piece Shadow's Mantle set bonus would cause Impale to inherit the damage type of an equipped weapon when being used with Convention of Elements. (1/27)
- Black Hole
- Fixed an issue where enemies affected by both Black Hole - Event Horizon and Taunt would remain at 1 hit point and be unable to be killed (1/20)
- Ray of Frost
- Black Ice
- Fixed an issue that caused the Black Ice rune to stop functioning. (1/27)
- Fetish Army
- Fixed an issue where fetishes could stop casting Poison Dart while using the Carnevil Legendary Voodoo Mask (1/20)
- Set Dungeons
- Fixed an issue where the game could crash when a Set Dungeon begins, but there is not a valid portal saved (1/20)
- Fixed an issue where taking fatal damage in a Set Dungeon could cause the Set Dungeon to be empty the next time it was entered (1/20)
- Dungeon of Firebird's Finery
- Fixed an issue where completing the objective to set 20 enemies on fire 6 times would prevent the objective to hit enemies with the Revive Meteor from tracking (1/14)
- Dungeon of Roland's Legacy
- Fixed an issue where players would not always be properly be prompted with the completion window if they kill all monsters before the time expires (1/14)
- Fixed an issue that could cause the Wortham Survivors bounty to become unable to be completed. (2/11)
- Fixed an issue where Carnevil would impact non-Witch Doctor pets summoned by items (1/14)
- Fixed an issue where the transmog item, Lachdanan's Stormshield, was dropping as Legendary quality instead of Common (1/14)
- Fixed an issue that caused the movement speed bonus provided by a rank 25 Wreath of Lightning to stop functioning. (1/27)
- Fixed an issue that could cause the Custom Engineering Hellfire Amulet to stop functioning after a period of time. (2/11)
Read on for more Blizzard Blues, including explanations from developer Wyatt Cheng about the removal of the Inspect
command in the game, and a bug with Furious Charge
that will exist through Season 5.
Furious Charge and Animation Cancelling
The Barbarian skill Furious Charge
is the focus of recently updated The Legacy of Raekor
class set, seen in the Top Barbarian Legendary and Set
charts. The full animation for that skill can be cancelled to eke out extra damage. Developer Wyatt Cheng stopped by the forums to note that this bug will be left in place for Season 5, but fixed in a future patch.
Hey Barbarian friends,
For those who don’t know, it is currently possible in the live game to cancel the Furious Charge animation by moving, allowing you to start another Furious Charge slightly earlier and resulting in a damage increase. Some players have wondered if this is a bug or a feature.
This is a bug, and not a new one. It was a result of some of the optimizations we made to Furious Charge in Patch 2.2, when we were working to make using this skill smoother, more responsive, and allow you to hit monsters more easily than before. While we would like to fix this, we have a long-standing philosophy to avoid making changes (even bug fixes) that could cause a class to perform worse than before during a season. Due to the nature of the change needed, we cannot fix it before the start of season while still ensuring Furious Charge retains its current level of power.
So, for Season 5, Barbarians who enjoy the trick and want to play around with using the animation cancelling should feel free to do so. For those who don’t enjoy that style of play, there are many other builds that are fun to use and highly effective. We will fix this bug in a future patch and, when we do, we will certainly re-examine the power level of Furious Charge and the Raekor set relative to other sets across all classes at that time.
Inspect Merged with View Profile
selection in the game, to check out the gear and skills used by another hero, has been removed. Mr. Cheng explained the change, and how that functionality has been merged with the View Profile
Quick update on this.
After looking at reports and testing it seems the underlying functionality is working correctly but the feedback in the user interface is inadequate.
View Profile was always available but the results were not guaranteed to be up to date (usually based on when the person last entered/left a game)
Inspect was NOT always available (had to be within 100 yards of other player) but the results were always current of what the player is wearing.
What is currently live:
Functionality of View Profile and Inspect have been merged. If the other person is not in range, you get the same information as View Profile before. If the other person is in range for Inspect, then you get the most current information of what the player is wearing.
However, there is no interface feedback at whether you are looking at a "Live" version of a "Cached" version of the data. This is understandably confusing and something we'll look at.
To summarize: View Profile works and if you're within 100 yards of your target you are given a live view of them.
AMD Graphics Card Black Screen in Desolate Sands
A long-standing issue with AMD graphics card can cause a black screen when going into the Desolate Sands area in Act II. This can be fixed by downloading the latest beta of the AMD Catalyst graphics driver, found here
Workaround for Black Screen in Desolate Sands/Act II
- Some players using AMD Radeon video cards may experience a black screen when entering the Desolate Sands zone in Act II
WORKAROUND: AMD has released a new 15.9 driver that is confirmed to resolve this issue.
More Zombie Dogs Coming to Console
The Ultimate Evil Edition
of Diablo III on the PlayStation 4 and Xbox One currently has fewer Zombie Dogs than the PC version, for historical reasons. That will change in an upcoming console hotfix or patch.
PC - Summons 3 dogs for 30% Damage as Physical each
Console - Summons 2 dogs for 47% Damage as Physical each
PC - Summons 3 dogs for 120% Damage as Physical each = 360% total
Console - Summons 2 dogs for 47% Damage as Physical each = 94% total
This is a bug. Our intention is for the Console numbers to match the PC numbers. Thanks for bringing this up!
Please note. I don't have an ETA for you. We'll look into hotfixing and if not then a future patch. (What does and doesn't get hotfixed usually comes down to the underlying technical implementation)
How can Zombie Dogs match PC when the Console version has one less dog?
Console would go up a dog.
Agreed, not too sure why we get 1 less dog. Is it just no feasible? I dont think thats the case cause you can get up to 5 with passives. Who knows, it is odd though.
Console having 1 less dog is historical
With the PS3 and 360 versions of the game it both put a little more performance cost on those systems and having many pets out in same-screen co-op caused a lot of clutter, so we went down to 2 dogs per witchdoctor and increased the damage.
Next Gen systems don't have the same performance issues, and we also don't see 6 zombie dogs per player in 4-player shared-screen co-op to be the most visually noisy thing that can happen based on the way Diablo has evolved. So we are putting the extra dog back.
Rest assured the dog was well cared for while on sabbatical.
Hm, this hotfix should be live on both consoles as of yesterday. Hang tight and let me investigate.
Thanks for the reports, folks!
Unfortunately, this hotfix did not make it out yesterday. :( Apologies for the miscommunication. Currently, we do not have an ETA for its arrival, but it is being worked on.
Performance Issues on PS4 and XB1
The Quality Assurance team is collecting feedback from console players who are seeing framerate drops and other performance issues in patch 2.4 - post any reports on the Battle.net thread
We've been unable to reproduce this internally so far, so let's see if we can find a pattern and identify what's going on.
Can players affected by console performance issues let us know the following information? Apologies if you've posted parts of this in the thread already, but the format will help greatly when we dive into the information. Please fill in as much information as you can. Thank you for helping us research these issues!Platform (Xbox One or PS4):Region (US, Europe, etc):Character Class:Skills used:Are you playing solo or party? If party, with how many other players?:Do you notice this at specific in-game locations?:For those experiencing menu issues, what menus?:Description of performance issues. Is framerate dropping constant? Do you notice it sometimes more than others? Do you notice it when performing certain tasks?: Is there any other information you think could be relevant?:How much free space is available on your system?
- Go to Settings > System Storage Management and look for "Free Space"
- Xbox One
- From the Home screen, press the right trigger and select My games and apps
- On the left side of the screen, a meter shows the percent of storage space used and your total free space