Diablo II 1.13 Stash Size Issues Causes Temp Delay

Posted 1st Oct 2009 03:06 AM by Medievaldragon

Bashiok updated the latest news on patch 1.13 status.  Sadly, its release will take a bit longer. There was no ETA, but matters have slowed down development until they investigate and find a solution to a problem that the increased stash size has introduced.  A few days ago, there was a mysterious incident where some characters disappeared.  It’s uncertain if that has a connection with patch 1.13 or Battle.net 2.0 internal tests.

The Diablo II team though discovered a potential impact on the Battle.net service with the introduction of this stash feature.  Bashiok will offer a follow up soon. From bits in his statement, it looks like there were plans to put patch 1.13 on the PTR, but this issue caused them to abort and hold until they find a solution.  Take it this way, better to be done right, than to be released and have the servers crash. It’s good this was discovered before 1.13 went live. Be patient.  It’s taken a while, but it will be worth the wait.

Bashiok speaks after the break.

Blizzard Quote:
Update 9/30:

Bashiok: The Diablo II 1.13 patch is on temporary hold while we investigate potential impact on the Battle.net service. As we moved closer to launching the patch concerns grew that an increase in the player stash size (a feature in the patch) could compromise the Diablo II Battle.net service. The hardware and configuration could potentially not handle the increased stash size gracefully under heavy load. Currently we’re investigating potential impact as it is one of the larger content features in the patch and we’re hoping it can remain a part of the release. If it does have to be removed it will require additional time to remove it, generate new patches, and test, which will add time before we can go live on the PTR.

We’re hoping to have our diagnostics and a final decision on how we’ll be moving forward decided by early next week and we’ll have an update for you at that time.

Thanks, Lyquid.




Bookmark and Share

Comments

Page 1 of 4 pages  1 2 3 >  Last »
stillman
Posted 01, Oct 2009 06:29 AM
(0)
 

I agree; better safe than sorry. It’s at least good to hear they must have been close to having it complete, even though there will now be a ton of delays.

Reply
 
Medievaldragon
Posted 01, Oct 2009 07:00 AM
(0)
 

Yea that report from Bashiok really makes it look like it was ready to go live on PTR server within a 2 week window or so. Maybe less.

Reply
 
Inkarnus">Inkarnus
Posted 01, Oct 2009 08:44 AM
(0)
 

First: Thx for the 1.13 information smile

Increased stash -> heavy load on the servers…..

Have you compared the server load from this:

* 100 uber geared bots that runs a lot of baal-runs imba fast
VERSUS
* 100 legit players in normal gear who move and fight slower?

I bet the bot causes a lot of server load so attack the core problems.

Implement shared stash or in game mailing so we get SAFE transfers of items instead of a lot of mule-games.

And do something about the bots, they have killed the game. The size of the stash is nothing compared to problems from the bot and dupes.

Good luck hunting

Reply
 
Teitanblood
Posted 01, Oct 2009 09:57 AM
(0)
 

Don’t be naive people - this is just a cover story to explain away yet another delay caused by lack of motivation to support a game that doesn’t rake in cash.Seriously,are we supposed to believe a corporation the size of blizzard,with the quality of people blizzard employ (as they constantly tell us) can miss a simple issue like this in a 10 year old game that has been patched dozens of times already?The stash size has already been upped once,it’s not like they have no experience with this sort of implementation.

This is bullshit,we all know it.Last time it was some magical mystery war 3 issue (good timing,eh?),this time it’s some server load issue because of a feature they already have massive experience with?As above poster said,there are other GENUINE server load issues they simply refuse to deal with.I can’t remember the last time i played in a public game where 3/4 of my screen wasn’t covered in bot spam.

Reply
 
nasarius
Posted 01, Oct 2009 10:14 AM
(0)
 

a simple issue like this in a 10 year old game

...with ten year-old network and database technology. Make sense now?

Reply
 
Teitanblood
Posted 01, Oct 2009 10:59 AM
(0)
 

Nice strawman.

a)the age of the game and b.net service it uses is an argument for faster patches,not slower.

b)they have already implemented larger stashes before

c)this is at least the 2nd time that something is alleged to have just popped up out of the blue to delay the patch.

d)how can a larger stash space overload the servers?it’s going to REDUCE the load - in the form of less muling,less mule characters

e)how come this issue rears its head on the very eve of the patch either going live or going into pre-testing on a large scale.Surely something this serious would have become apparent quite a while ago,or are the programmers incompetent?One begins to wonder,what with the state of the realms in regards to bots.

Again i just can’t get past the fact that this issue has already been dealt with before.

Reply
 
ElSmisko
Posted 01, Oct 2009 11:20 AM
(0)
 

Teitanblood took up a few points that I was thinking.
I get the feeling that they are really not interessted in releasing it but to keep interest up for D3 they are kind of forced to do it. But since interest is lacking progress is going slow and it’s convenient to blame other problems for the slow work.
Man, I havn’t played since april waiting for the ladder reset…

Reply
 
Moonfrost
Posted 01, Oct 2009 12:03 PM
(0)
 

Working hard or hardly working?

Reply
 
dragonhelmuk
Posted 01, Oct 2009 02:59 PM
(0)
 

Lets be honest, if a problem was found with the Single Player version of the patch it would have been released on the realms and SP might have seen a version of it a year later. How about being fair; if the problem is with Battle.net then give the patch to SP first!

I suppose if they’re contemplating removing new features they’d probably best do that before we get them instead of taking them out after they’ve been implemented.

Reply
 
Kiroptus
Posted 01, Oct 2009 03:02 PM
(0)
 

They might as well be honest and say how they absolutely hate to touch the mess that is Diablo 2’s archaic code. Whenever there is a patch or something to be done with D2, its always this soup opera.

Whenever blizzard has to touch something in D2 it always feels as they are dragging themselves, moaning and whinning with their boss saying “Do we really have to do it? Cant we just let this old game rot?”.

Im no programmer but I always feel that Diablo 2 has a mess of an archaic code which no programmer, not even payed by Blizzard, would want to touch it even with a 10-ft pole.

Reply
 
Page 1 of 4 pages  1 2 3 >  Last »

Syndicate