Diablo II 1.14c Patch and Ladder Reset Announcement

Hey all,

Diablo II ladder reset has been announced for May 17, 2016 at 10:00am PDT. This maintenance will also include a Diablo II patch from 1.14b to 1.14c that addresses a few bugs from the previous 1.14a and 1.14b patches.

The full announcement can be found on Blizzard's forums.

Happy gaming!

Update 2016-05-17 5:52pm: Blizzard has taken the servers down as of 12:00pm CDT and as of now they are still down while they perform maintenance. More information can be found in their new forum post. Thanks all!

Update 2016-05-17 9:48pm: All maintenance has been complete and the servers are all back online!

Blizzard will be updating Starcraft too!

On April 13, 2016, Blizzard announced that in addition to the updates they have made to Diablo II and Warcraft III, they will also be updating Starcraft!

It all is detailed in the forum post that quickly went off-topic from its Diablo II question and turned into a Starcraft conversation:

xboi209: Hey Clásico, it seems that there's absolutely no mention of any work on StarCraft at the moment. I do agree that D2 should support higher resolutions but in my opinion, bug fixes and compatibility for StarCraft should be worked on first before the eye candy for other games.

Clásico: Hey hey! I will say that, as of right now, Starcraft IS being worked on.

Bingbing: This thread no where even mentions Brood War.

Clásico: When I say Starcraft, I'm implying that it's Brood War. Sorry if that wasn't clear.

Bareleon: Are there going to be bug fixes? Any balance updates? A ladder like sc2's?

Clásico: Afternoon Bareleon, as of right now we're working on Compatibility and bug fixing for SC and SC:Brood War.

So there you have it folks! Starcraft is coming down the pipeline soon.

Diablo II 1.14b Maintenance Release

On Thursday, April 7, 2016, Blizzard announced a patch to Diablo II. The new version upgrades Diablo II from 1.14a to 1.14b. There are no known version byte or hash file updates so far, but we will revise this news post if there is.

The announcement from Blizzard is as follows:

Howdy All,

We are releasing 1.14b for Diablo II today. We will take the servers down at 1000 Pacific and expect the maintenance to last 4 hours. Patch notes:

Specific Changes & Improvements

  • Glide Wrapper will now load properly on PC by adding -3dfx to the end of the game shortcut
  • Mercenaries will no longer become “An Evil Force”
  • Fixed Mac client crash on “Save & Exit”
  • Capped the frame rate to 200 to save batteries, spare system load, and prevent hot lap syndrome
  • Created new German installers to fix localization issues in Act V (Will require a fresh install to fix the missing dialogue data)

Blizzard completed their maintenance an hour after the announcement and all servers should be back online operating at full capacity.

BNETDocs Phoenix is now live!

With all of the updates that have been happening to BNETDocs Phoenix lately, I felt it was ready to be promoted to the main site! Don't worry, Redux is still accessible.

Feel free to look around and get familiar with the new UI/UX. There are still places that are work in progress, such as the commenting system. There's also tons of data that needs to be converted to using Markdown instead of legacy HTML/BBCode. As updates continue, this main site will change, so please be aware.

Please also let me know if there's anything broken or something that could be enhanced over on GitHub.

Now that Phoenix is live, I will be archiving Redux and not even syncing data between Phoenix and Redux anymore. It will become stagnant. This should also encourage updates to Phoenix exclusively.


Warcraft III 1.27a MSVCR120.dll Error

When Blizzard released Warcraft III patch 1.27a earlier this month, it turns out that they had forgotten to include the Microsoft Visual C++ Redistributable package when patching from earlier versions. This is the cause of why some may be receiving the error about MSVCR120.dll when launching the game.

Fortunately, Blizzard posted to their forums detailing how to fix the issue.

If you get this error after patching to 1.27a then you have a few options:

  1. Reinstall using the new installer
  2. Install Visual C++ Redist Package
  3. Wait for the 1.27b patch. We do not have a definitive date to share at the moment.

Original Thread

Hopefully this helps anyone looking around for a solution to this problem!

< 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 >