2.6.0.a information

[KillerJohn]

- I'm still investigating the changes introduced in 2.6.0a.
- There is no final decision to release x86 or x64 yet.
- Updating both would require lot of work, but
- x64 build is not done yet and still have issues, also
- my internal x64 patch updater tools are not completed yet, so updating the not-even-released x64 branch will be hard

Do not ask for ETA.

[OnehitB]

Damn that is what I call bad timing, well, take your time KJ.

[Fazzler]

Doesn't seems like much has changed, only visualization and orbs spawn closer

General
Fixed a number of string corrections in German and Chinese localization clients
Fixed an issue where the special items from the Diablo Anniversary dungeon had lost their unique appearance, icons, and associated transmogs
Players who previously had these transmogs should have them once again after the patch deploys

Adventure Mode
When defeating enemies in Rifts, progress orbs that spawn will now be closer to the defeated enemy

Items
Moribund Gauntlets
The audio for Moribund Gauntlets has been adjusted to be quieter

Necromancer
Necromancer portraits have been updated
The existing portraits in game were intended to be placeholders, but weren't properly updated with the final patch. This is now resolved.

[SeaDragon]

A patch before the season is expected, and perhaps there will be another patch to fix 2.6.0a's BUG

[Eusta]

I wouldn't rush with the fix because seems a new patch coming soon (hope they roll it before season start).

I especially like that part of reply from Blizz:

Pretty much every kind of software that patches will fix some things, but break others. I can't really comfort you on this point; sometimes the issues that arise are more noticeable than others, but that's kind of just... how that works.

[AGenius]

Blizzard's comment is pretty true , I often introduce bugs into my apps when making changes for my clients , not on purpose I might add. sometimes there is just a knock on effect you didn't anticipate

[newbpwnz00r]

Take ur time with the 64bit, KJ! It's the future of hud

[cherouvim13]

You are comparing yourself with a company like Blizzard? Cmon...

With the size of a company like Blizzard, such mistakes (bugs etc.) shouldn't happen at all...

[dabnoj]

You are comparing yourself with a company like Blizzard? Cmon...

With the size of a company like Blizzard, such mistakes (bugs etc.) shouldn't happen at all...

also the size of their projects are not the same as any HUD ^^

[Kealsera]

You are comparing yourself with a company like Blizzard? Cmon...

With the size of a company like Blizzard, such mistakes (bugs etc.) shouldn't happen at all...

You obviously never developed a software which is capable of doing more than a calculator

[Eusta]

Blizzard's comment is pretty true , I often introduce bugs into my apps when making changes for my clients , not on purpose I might add. sometimes there is just a knock on effect you didn't anticipate

I didn't say that's not true, but after big slip with the exploit they still don't make proper tests, we still have no PTR and they still way too slow with fixing. Even THUD with much less resources has better QA than Blizz, so that "shit happens" sounds like lame excuse to me.

[Jalatiphra]

you have no clue of software development
not the slightest.

[MrOne]

In my opinion best way is to update current 32bit TH and then work with x64, why?
Because when season 11 start there will be very small change to that Blizz send next patch.
Most of seasons work on same patch + few serverside hotfix.
KJ if U update 32bit than U can work with x64 without disturbing from our side

[mv1986]

Thanks for all your work KJ... just donated to show support.

[KillerJohn]

In my opinion best way is to update current 32bit TH and then work with x64, why?
Because when season 11 start there will be very small change to that Blizz send next patch.
Most of seasons work on same patch + few serverside hotfix.
KJ if U update 32bit than U can work with x64 without disturbing from our side

I ignore most of the forum posts