All of you who are complaining need to actually try programming a game of this magnitude.
Look mistakes happen and I understand why so many are upset, but I am impressed that we lost so little progress after an event like this happened. Obviously Bungie needs to be more careful with how updating the game is handled as I have no idea how this happened, but at the same time, if you were on this dev team I doubt you would handle it any differently.
For all of you saying that they didn't apologize enough, they fixed it in a decently quick manner so a huge apology is honestly not necessary.
Everyone needs to remember that Destiny 2 is not a small game, and it has a lot of moving parts! Server/Client architectures with this much data being transferred make it hard to debug these kinds of things in controlled sessions. Anyone who says they don't test the game in house -- thats such a small population of players that server bugs can often go entirely unnoticed until it's too late.
Keep it up Bungie, I'm glad you fixed it with such a low amount of lost progress, but I wish it never happened in the first place for everyone's sake.
English
-
-
-
-
Joke of a comment
-
I've written software (including games in assembler by hand back in the 65C02 days) and designed hardware for the past 35 years. A debacle like we saw yesterday would result in management (Q&A managers especially) and entire Dev teams being let go for incompetence.
-
While I don’t have the same experience as you have, game development is something I enjoy doing so I am very curious how something like this happened. If bungie made a full explanation I would gladly read it.
-
Bungie will never give us an explanation - they never do. My guess would be insufficient testing, poor version management and lack of self control (i.e. don't tinker with code unless it's broken or you are doing full test regression on what you changed) are the primary reasons.
-
nice try cozmo
-
-
[quote]🤗[/quote]