{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
2/12/2020 1:09:40 AM
24
Are They Sure That They Fixed the Issue This Time?
Just expressing my concern here. A couple of weeks ago, quite a few things were reported to be fixed, but it seems like they actually weren't like the Wormgod's Caress and Winter's Guile glitches, Bright Dust returns for some players after the last rollback and some other technical things.
I hope the next update isn't going to break anything again. Maybe the 3rd time will be the charm, perhaps?
-
1 回覆Let's be real. They ain't sure about a damn thing except how much they want to throw in eververse.
-
[quote]Just expressing my concern here. A couple of weeks ago, quite a few things were reported to be fixed, but it seems like they actually weren't like the Wormgod's Caress and Winter's Guile glitches, Bright Dust returns for some players after the last rollback and some other technical things. I hope the next update isn't going to break anything again. Maybe the 3rd time will be the charm, perhaps?[/quote] Just stop playing 1 hour before the hot fix... 🤞🏻😬
-
1 回覆
-
Yea no this is over the top. Yea certain things reoccurring make sense like Telesto. Just because there's so much going on with it and how its probably got some obvious overlap in its coding so that it works the way it does. But the resource bug and the Wormgod/Guile issue? Along with some other stuff that kept popping back up in the past? Come on Bungie.
-
They’ve had emergency maintenance like 4 times in a row now, the last 2 for the same reason. They obviously don’t test anything before releasing it and they are just embarrassing themselves every week with their incompetence. They probably tried to push out the exact same update as last week without changing anything first, considering how lazy they’ve gotten.
-
1 回覆They never “fix” the issue they just move it to something else 😆 that’s all they’ve ever done. They just chase the error around the games code but never ever remove it 🤦♂️
-
They're probably stealthily removing dust from as many accounts as they think they can get away with. This is the same group of people that had an invisible bar on your XP meter, holding you back. When we found out they slapped us on the peepee and doubled the requirement of XP. Just to spite us. Bungie has literal contempt for its players, quit playing this game!
-
quote]Thanks for continuing to prove me right. You’ll patch the sever to override faulty game code...and leave in the faulty code? Not expecting it to eventually bite? Smart...real -blam!-ing smart. No wonder the game performs shitty. [i][u][b]Intentionally[/b][/u][/i] leaving faulty code in the game itself. Too busy to properly fix your game because you’re...doing what again? It’s clearly obvious you have as few people working on this game as possible. So if you don’t care, we shouldn’t either. You have one game to service and you can’t do that right. It’s -blam!-ing sad. Especially when other, newer, studios juggle multiple games. Just a clown show at this point. Sad to see it happen, Bungie was a great studio for so long, but at the same time you guys made this mess. So it’s all on you. Not me.[/quote]
-
3 回覆Their blog post about the issue was pretty interesting, like after the last update they did a band-aid while working on a permanent fix. But manual reboots on some crashed servers at reset caused the band-aid fix not to be applied to them. In the grander scheme of things a permanent fix will be applied soon and one issue causing a rollback in 6 years isn't bad really.
-
Maybe its all part of a new community challenge involving time travel. Every roll-back the lost mats and shards go towards production of a brand new weapon. A shotgun/sword hybrid that outranges erentil and fires grenades. Special quest for trials
-
The issue is that: Bungie already had this content planned out when last update happened (the one that caused the roll back) They weren’t working in crimson days for a week or something like that they just deployed a update that they had done for weeks (so just the last updates bugs and stuff with crimson days added)
