{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
7/15/2019 1:45:56 PM
7
Do you really think they're ignoring it?
It's a bug. A particularly nasty one. It's going to take a while to figure out what causes it and deploy a fix that doesn't make things worse, across two consoles and PC. Bug fixing is not waving a magic wand as soon as the forums yell about it.
Is it annoying? Yes. Do I think bugs should be dealt with as promptly as possible? Yes.
But I also know that not all bugs are created equally, and some are right -blam!- to fix.
English
-
2 points for being rational.
-
Whatever pal. This is a massive game-breaking bug that was obviously implemented in the last patch. It's not something they don't know how they introduced.
-
How long has this season been out? A little over a month? Already we have had... -Truth quest glitch -Menagerie chest glitch -Bad JuJu quest glitch These are off the top of my head and I am sure there are more. In their rush to stop people getting loot from the chest they have basically broken the game. This does not bode well for September when entire game systems are being reworked. This is the content people have paid their money for?
-
What? That's just resetting a timer, right? How does that make sweaty blinking warlocks invisible in the crucible?
-
since d1 every patch bungle do fixes 2 things and breaks 4 others , its down to no play testing , poor programming , poor net code and lets face it a really sh1tty game engine thats about 5 years behind other engines and bungles use of amazon servers with the above mentioned problems.
-
Figure out what? Roll back. Thats all.
-
Well if they managed to put out an updated that didn't break the game maybe, but again we are at this point the where they fixed a glitch and broke other parts of the game.
