Diablo® III

One question for ur dev team

People can be ignorant at times.. Programming Isn't that easy. With a game like D3 there are hundreds of thousands if not millions of lines of code. There are thousands of separate files these codes are written on. The time it takes to locate a bug in coding is fairly large. One code in one file can have an effect on another code in another file that is unforeseeable.
The patching process includes
Review - when the lead programmers discuss all of the bugs in the game, and proposed improvements, They will choose which ones will make that patch and which ones will be in future patches. 1 - 2 weeks
Coding - The programmers have to locate bugs and correct them, and also have to code new lines for improvements. 2 - 3 weeks
Internal testing - Internal game testers are used to test bug fixes and new content, They also look out for new bugs. 2 - 3 weeks
The the patch release. These time frames are based on pretty simple bugs and improvements. For larger patches such as 1.07 these times can go up to a month to 2 months in the coding and internal testing. I am positive the programmers at Blizzard are working as fast as they can on the bugs.
Also remember, bug fixes have been going on for 1.07 since before the PTR release, so I can see a PTR update in a week or 2.
Reply Quote
OP - just another deucebag from EU. I just lol'ed :P
Reply Quote
Blizzard is a big company. Anyone who works for a big company knows that it takes a long time to make changes to anything.
Reply Quote
man most of you guys are acting like spoiled children.

i see update list
me like, me want now!

where is it me want now! >:(

devs would do better not posting preveiws of updates n giving these children stuff to complain about.

im sure u guys post the preveiw for feedback from teh community, but i dont think ive seen too many posts with worthwhile feed back. its all these children !@#$%ing about this or that.
Reply Quote
01/20/2013 07:04 AMPosted by ZaSpecialist
So what you guys say is that its perfectly legit to wait...lets say 2 more weeks for the next PTR phase to start (after fixes are implemented in a patch) and maybe after that wait 2 more weeks for the new update and maybe by summer we can have the live update. When it finally comes then 3 months of silence will come, new ninja details will come and then we will know in like 2 months a new PTR phase will start. So when you all say its hard work coding you ment it's normal to wait like 6 months for an update to be built. Don't really understand you're logic but I can 100% say dev team is not really working as they should. After 1.0.7 they will be like: dude..we did it, now time for a time out, all that coding bored me to hell, they can play 3 more months our update that will keep interest max 2 weeks". Take you're time Bli$$ard and NEVER ever say you make perfect games, that ship sailed long time ago.


The game launched in May. Since then we've had several major patches a PTR all in about 8 months. Stop acting like a drama queen.
Reply Quote
01/20/2013 08:41 AMPosted by mingles
Blizzard is a big company. Anyone who works for a big company knows that it takes a long time to make changes to anything.


I'll have to agree with you on that, and the saddest part is that sometimes there are people who are really high up who make things slow (whom perhaps haven't even touched diablo) so it's likely that the people you all are blaming aren't really the ones at fault.

Jay leaving is, IMHO, quite a clear sign that the expectations of this game have become too overwhelming.

Keep it up and you can expect the dev team to leave next, if it comes down to that...

You should really reconsider what you post, when you post, and the main point of your post.

If you really want this game to heal. Be positive and patient. Like this dude said, it's a helluva big company, who knows how many approvals it takes on how many cupcake eatin desks before a fix is allowed for whatever reasons.
Reply Quote
ughh..
Reply Quote
01/20/2013 04:38 AMPosted by Timmytentoes
diablo 3: 12yearspath of exile: 1year,ho wait its 12times less


PoE hsa been in Development ALOT longer than one year. That comment is so ignorant and trollish it hurts lol


PoE = 6 Years and still in Beta, but a good (not great) game...i just play them both...yea thats possible! Potatoes gonna Potat.
Reply Quote


Keep it up and you can expect the dev team to leave next, if it comes down to that...



wouldn't be the first time.
Edited by Jables#1843 on 1/20/2013 9:35 AM PST
Reply Quote
sup guys.
Edited by Lhotse#2699 on 1/20/2013 9:38 AM PST
Reply Quote


Keep it up and you can expect the dev team to leave next, if it comes down to that...



wouldn't be the first time.


you have

no mercy.

(lol)
Reply Quote
Keep making excuses, meanwhile a small indie game company made up of 13 people on a small island in the middle of the Pacific continues to make you look silly.

http://cdn.memegenerator.net/instances/400x/33679192.jpg
Edited by GodlyMe#1768 on 1/20/2013 10:22 AM PST
Reply Quote
01/18/2013 06:13 PMPosted by Xort
The reality is, game development is a hugely iterative and time-consuming process, with many people involved along the way. Design takes time, Coding takes time, art takes time, QA takes time: you name it.


So the many years of development before release wasn't enough...?


is there really anything that is "perfect"
Reply Quote
One statement I’ve seen over and over on these forums and elsewhere are proposals for “easy” fixes and overarching assumptions about how long implementation for a variety of changes “should” take.

The reality is, game development is a hugely iterative and time-consuming process, with many people involved along the way. Design takes time, Coding takes time, art takes time, QA takes time: you name it. There are also multiple steps in the pipeline for each and every proposed change and bug fix, no matter how minor, and what issues are being worked on in what order and by who can and do change as new matters arise. Sometimes extra testing is also needed for bugs that come back broken and need to be retested, because we didn't want them to go live with a bad fix.

While there may indeed be a list of known issues and bugs that run alongside some patches, for every one you are aware of, there can be dozens or hundreds being worked on behind-the-scenes that you likely never be aware of. We do things just as quickly as we can, but even then, it’s a process that takes time.


The reason we think things are easy is because of those other troublesome Blizzard games which seem get patches faster, despite having less user dissatisfaction.

http://us.battle.net/sc2/en/forum/topic/7591982824#1

12 patches in 4 months. I know it's beta, but come on. It really doesn't take that much time to get certain things out into a patch and test it. If for some reason the management structure really is delaying Diablo 3 patches that much more than it is for Starcraft 2, then removing some of those roadblocks should be an extremely high priority for the Diablo 3 staff.

I mean EXTREMELY high priority. It's just not excusable that one part of Blizzard has so much trouble getting out any patches whatsoever while another part is getting very productive use from player testing and has an obvious connection between development staff and the players (they post on the forums!).

The difference in community interaction is also notable. D3 players have a reputation for hating Blizzard's guts while SC2 players have a reputation for worshiping the ground that Blizzard touches. I wonder if that has anything at all to do with how the games are supported so differently? Developers and patches for one game, the other gets a few months between patches and no developer interaction. Hmmmm......
Edited by Polaris#1903 on 1/20/2013 11:48 AM PST
Reply Quote
When you develop a game for many years you end up with something you have to envision as a steaming pile of crap that many average programmers helped to build up that just happens to meet desired outputs for the reference inputs (these don't include the ones the players discovered to result in bugs)

They throw on a nice aesthetic shell at the end to make it look all purty and make everyone think some great code wizards were working at the company.

But now that you have this picture imagine what you ask when you want a bug fix or a new feature. Its like trying to play Jenga with a 20 ton pile of blocks. You want them to thrust their hands in there .... rip something out ... and shove something bigger right back in there.

Yeah, needless to say that doesn't work that way ... even if the D3 programmers were good ... it takes time.
Edited by Delkerramak#1500 on 1/20/2013 11:59 AM PST
Reply Quote
I think the game is a lot better now than at launch, it still was fun at launch.
The patches keep comming in regulary and they are changing quite important things.
I wouldn't expect more, some things arent perfect, some things are great and gettin' better.

Keep in mind that this isnt WoW, you aint paying monthly to play this game, you aint paying for an expansion every year, instead you payed once for it. Also you had the chance to try the beta / or play a friends character, and see what you were getting into before buying the game.

I hope Blizzard keeps in mind that there are players enjoying this game without having to bash the forum for quick changes.
Reply Quote
Geez so many morons in blizzard forums these days -_- grop up kids go outside clear your heads,do look stupid with all you talks here not smart
Reply Quote
90 Human Death Knight
12460
There are games with 10x the complexity of Diablo 3 that take 1/1,000th the time to fix and patch.

All we have here are a bunch of lazy devs holding a game hostage and milking their salaries from their ignorant employers that have placed waaaaaaaaay too much trust in their crew, unwarranted trust which has been broken and abused.

I wish there was some way for us people on the bottom to tell the people on the top that the devs in the middle are abusing both of us.

edit: Case'n'Point: If there is an exploit that becomes popular it can and will be hotfixed almost immediately, no endless months of devs milking the clock needed.
Edited by Probability#1170 on 1/20/2013 1:57 PM PST
Reply Quote
One statement I’ve seen over and over on these forums and elsewhere are proposals for “easy” fixes and overarching assumptions about how long implementation for a variety of changes “should” take.

The reality is, game development is a hugely iterative and time-consuming process, with many people involved along the way. Design takes time, Coding takes time, art takes time, QA takes time: you name it. There are also multiple steps in the pipeline for each and every proposed change and bug fix, no matter how minor, and what issues are being worked on in what order and by who can and do change as new matters arise. Sometimes extra testing is also needed for bugs that come back broken and need to be retested, because we didn't want them to go live with a bad fix.

While there may indeed be a list of known issues and bugs that run alongside some patches, for every one you are aware of, there can be dozens or hundreds being worked on behind-the-scenes that you likely never be aware of. We do things just as quickly as we can, but even then, it’s a process that takes time.


I'm having trouble trying to express just how dumb this post is.
1) Your an $8.1 billion company. If you wanted something done, you have the money to get it done if not now, really *soon*.
2) You should have attracted at least some of the top talent from around the world given your previous games popularity.
3) Let's look at your previous posts: http://us.battle.net/d3/en/forum/topic/6794319883?page=32#629
Remember this one?
This was in October. You said you'd be fixing monks. Instead, you guys just literally DOUBLED some of the spirit spenders. In short, you guys hardly follow up on anything. Even after 4 months, you haven't done anything significant.

The truth is you made this game the lowest priority at of all your franchises. Why don't you just stop telling us things we want to hear or excuses and march an actual developer out here so we can get some answers? This middle man thing is pointless and is obviously just as effective as any game of telephone.
Edited by Snowjob#1504 on 1/20/2013 2:03 PM PST
Reply Quote
Remember how long it took to fix the grey-ed out button on the auction house? WEEKS. Sorry, doesn't take weeks to fix 1 button.
Reply Quote

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)
Submit Cancel

Reported!

[Close]