After yesterday’s patch my client is crashing again, blurring again, sluggish, just like the start of the season. Makes me wonder, did someone forget to pull before they merged their changes in the codebase?
Separately, with this constant reintroduction of previous bugs can we please get mandatory CR’s on all PR’s?
Dude took Tech 101: Intro to Coding at some Community College (at like age 29) and came here to spam jargon in some bizarre attempt to feel intellgient.
and you came here to cry about his post, that makes you the bigger B.
Intelligent* at least spell it right
And i came here to see a post that happens during every PTR. Nothing to see here. Move along. These arent the droids youre looking for.
I think that would explain HOW they break stuff that was not even changed according to the change log 
Why did Horde stop counting? Noting was touched for it
They break stuff everyday. All they have are interns that copy/paste code and nobody that can say “I am going to deep dive the code and fix the stuff that needs to be fixed”. 2 weeks into a season is the same patch that fixes the broken copy. They copy the base game but are too lazy to go and fix it.
They used D3 code and new D4 code to make this game. Diablo 4 should have 100% new original code.
FYI, Horde got fixed (at least the last time i saw it) it was counting waves and drops.
Says the person who can’t spell “intelligent”. There’s an old saying: “those who live in glass houses shouldn’t throw stones”
But it’s got limited mileage. I agree the “intellgient” flub was hilarious. But ‘glass houses’ runs on shame & hypocrisy, and a typo is like a grain of sand rather than a stone.
Re: topic… Has anyone seen a detailed timeline of such “bugs” that keep being resurrected? It’s a meme by now. There must be dozens of these from the past 2 years. If someone had a thorough list, it could provide clues. Or at least valuable entertainment.
why are keybinds still broke?
Yes, season to season. Will see the same bugs at the start of S9 to be patched 2 weeks later to then come back in 10 to be patched again 2 weeks into that season.
patched 2 months into the season.
No, I know they keep coming up (I swear I can’t tell if you’re in character 
) that’s why I call them a meme… what I’m looking for is a ‘comprehensive’ list or spreadsheet someone may have created, to keep track of all of them over the entire 2 years.
It’s one of several ways but they all stem from a poor understanding of source control tools which you’d expect from a org that exclusively hires inexperienced developers. This is simply the most common way old bugs repeatedly get reintroduced.
In truth tho it can happen to experienced dev’s if they’re working in branch hell. They could have dozens of branches locally or on the remote to manage. They might not be closing out local branches, or it could be everyone pushing their local branches to remote (branch hell).
They do have a habit of not merging correctly or at all. Back when we’d have two teams deving seasons each season would wipe out progress patches from the previous, because noone bothered to patch those changes onto their seasonal branch. A lot of that has gone away now that one team is running seasons, but the same lack of experience with source control remains.
A requirement to have all PR’s code reviewed would cut down on these kinds of self inflicted wounds. And it’s embarrassing that we as customers would have to ask for this. But if that’s what it takes to get them to operate at professional standards then that’s what I’ll do.
I went through a “version control” nightmare 30 years ago, & I still, occasionally, end up re-visiting it in my mind. In our case, we had highly experienced people & still managed to lose roughly 1/3 of a database, all because some people wanted to “cowboy.”
Just look up the patch notes…should be a comprehensive list of fixes.
No. Because patch notes don’t address everything, especially recurring bugs, and because patch notes are a tedious morass of intern-created fluff that routinely gets moved to different pages, relabeled, is incomplete (as mentioned previously), and is 99.99% made up of other stuff (ie. not recurring bugs that’ve previously been patched over).
That’s why I’m looking for a list or spreadsheet some chad has been compiling since Early Days, if one exists. It should, given how meme-y this meme is.