Nice to see a voice of reason

You blame the seasonal content crap. They don't have a lot of time to develop and test. Remember they have 3 months to develop and test. Apex and Fornite can do this because they have one map and the rest of the development will be ornaments or cosmetics but Destiny 2 is a huge game and top of that they are adding and removing codes every 3 months. Since Shadowkeep launch this game has seen a lot of game-breaking bugs that's because they don't have time to test every possible scenario or do regression testing on their previous codes. I don't think Bungie has the capacity to maintain two franchises at the same time so you will see more game-breaking bug has their main focus will be on developing the new game. And people have to stop saying "Bungie is a single studio now". They knew what they are jumping into and that shouldn't be the reason for crappy code build.

You ever heard the saying “fool me once shame on you. Fool me twice shame on me”. The first time this happened it was okay (sorta). But the same thing happened again. Which means bungie didn’t learn. When a mistake is made, you fix it and make sure it doesn’t happen again. Bungie didn’t do that. Frankly it’s unacceptable.

Here is my gripe with all this... the explanation. They didn't do their due diligence like they're supposed to and admitted as such. Their testing was short sighted and was not completely vetted. This is someone who was supposed to do something the right way, didnt (for whatever the reason they chose to) but checked the box anyways. The person in charge of the the group didn't insist on further testing and validation and let it go into production. This is akin to the inmates running the asylum. The testing they used, in theory was sound. They wanted to ensure that things would work accordingly when the servers crashed due to high traffic. The only problem was that they didnt replace all of the code on each server and then used a simple throw it at the wall and see if it sticks test, rather than spending the time and resources to check each server one at a time. This is where they said they got "unlucky" which doesnt happen with programs. Programs do exactly what the programmer tells it to do. When a program doesn't, then it's no longer a program, its AI. Unlucky is tearing the cover off a ball right at someone. The hitter couldn't hit the ball any better, but still made an out. This was someone choosing to use a batch of test tubes for testing without first ensuring they were all clean. The final thing I have issues with is the decision to roll back vs looking at individual accounts and fixing them one at a time. They chose the roll back because they didnt want to risk the chance of missing someone. Rolling back isnt the right choice. They should have fixed individual accounts. Even if they didn't want to look at each account individually, a simple solution would have been to just load every account with an large some of mats that went missing like 9999. Prisms and ascendant shards to the max quantity that they're set at. Glimmer at the max quantity of 250k. Legendary shards at 7500. Who is it hurting if someone got more materials than they deserve. At least people dont lose any loot drops, like any raid exclusive RNG drops. Silver should be looked at individually. It's one item, and not everyone has silver. Then set up a separate help contact where people can message if anything is still missing. Also warn players that false request can result in account suspension. This is to discourage anyone trying to abuse the help section. In the end, this was a failure in leadership to lead this game. Like back in y1 when the whole xp throttling thing came out. Once they found it, they said they fixed it, but they really didnt. Fast forward 2 years and we are back at it again.

Death threats from ppl hiding behind anonymity on the internet. Classic Internet Warrior Nerds. 99% would probably sh!t themselves if confronted IRL. Welcome to the Internet! Don’t take these ppl seriously. I don’t. Especially in Texas. Where Firearms are legally carried almost everywhere. It’s not going to be in their best interest to go “hunt someone down.” Castle Laws are there for a reason. Good luck with that... Imagine raging so hard over a video game. I get little kids throwing temper tantrums but they’re kids. That’s what they do. But full grown adults? It’s sad and quite frankly pathetic. I love this game but if it’s down it’s down. The world isn’t going to end because of it. Sometimes things happens. Happens to all of us. They’re going to have to get over it.

There’s a long list of checks and balances to avoid this issue. Yes, sometimes it might get missed but its supposed to be rare. To have it happen two weeks in a row is just pure incompetence by Bungie. There’s literally no excuse for it.

If per chance they didn't fix the problem and they have to rollback again this Tuesday... You ain't seen nothin' yet.

I personally haven't seen any 'death threats', but if there are any, obviously that is not just against the CoC, but also illegal in other ways. Of course, DDoSing is also illegal, and yet it's 2020 and we still don't have dedicated servers, so. *shrug*

Death Threats? Hell no. The people giving out death threats are -blam!-ing children that shouldn't be listened to. Harsh Language? Very much deserved for the crap that is happening.

lol @ "death threats." [spoiler]😂😂😂[/spoiler]

[quote]Yes, Bungie screwed up with the reset. Yes, it’s irritating. But I don’t believe it warrants death threats and all the harsh language from people that don’t know anything about coding or game development. I don’t know anything, so I’m not gonna say anything. It’d be nice if others do the same. It’s unfortunate, but at the end of the day, it’s a game, now let’s try to have some fun, shall we?[/quote] This

Indeed. Just mutter “classic Bungie” and move on. All jokes aside, you don’t have to understand software development to read the statement Bungie put out. The events that led up to this are... not good. It paints a pretty unflattering picture of how Bungie’s QA works. They caught issues, didn’t fully understand them, but shrugged them off anyway, mitigated issues in a lazy way, didn’t verify that their servers were running on the latest patch, rolled back 100% of accounts even though less than 1% were affected... etc. At every single step they took the easy way out, and that’s why it happened twice. Beyond all of that, servers running on an old patch is a big deal. This specific instance doesn’t sound like there were security vulnerabilities, but it’s now public knowledge that Bungie didn’t verify, which is scary. I’d be surprised if this doesn’t cause them some problems in the EU with the GDPR. The insults and death threats are obviously stupid, but Bungie deserves some heat for this debacle.

"I don’t know anything, so I’m not gonna say anything" well you already failed there by making this post bud.

You pay for something to work, when it doesnt its justified.

nice try cozmo

If youve been around as long as some of us have...the Bungie Petience-o-meter is extremely limited at this point

I don’t need a Doctor of Dental surgery degree to know to brush your teeth twice a day.... Easily compare what’s being produced by similar developers and see how much bungie is slacking