Bungie's replacement developers (of the original) cannot be any good; otherwise they wouldn't (either) foul things up so bad, or continue working for bosses that make them do stupid things. I say this, being a retired programmer, that majority of the programmers write "working code," but not "efficient code." No, I'm not trolling or being glib. I'm simply stating what I've concluded after updating countless other people's code over the years. In fact, statistically speaking, chances are their coding is nothing more than a bloated functioning code that has been created using illogically dysfunctional design rather than a quality designed system using efficient coding techniques. Don't believe me? Here is a list of good programming habits that most people would agree are Good Things in principle, yet precious few adhere to in practice: If a file has more than 300-400 lines of code, you must consider refactoring the code into helper classes. A method should do only "one job." Do not combine more than one job in a single method, even if those jobs are very small. Do not hardcode numbers. Use constants instead. Do not hardcode strings. Use resource files. Avoid using many member variables. Declare local variables and pass them to methods instead of sharing a member variable between methods. These are just a few, and I only posted these from what has been said from the updates. Like: [url]https://www.bungie.net/en/News/News?aid=12540#![/url] [quote]They still hunt bugs where they live, no matter how deep, or for how long, they’ve burrowed into the code. ... The basic flaw here is an ordering problem. Our inventory system creates your weapons when your characters spawn. When that happens, it tries to restore the same fraction of ammo that you had when you died. The bug occurred because the weapon is created before capacity modifiers from armor perks are applied, so the persisted fraction yields fewer rounds. ... Fixing bugs in a live game is always about managing risk. What are the chances that the fix is going to cause an issue that might be worse than the original bug?[/quote] Ok, that was only one example, of the many times I have read such things on the updates. No wonder you cannot provide us what we request. No wonder why you are allowing this crud to disgust your player base. There is a lot of good things in your program, and I attribute that to the original programmers. But I think that you now have lousy programmers working for you. Even though you can fool those that aren't familiar with real coding, by making statements like: [quote] I still remember the time, long ago during the age of another game, when one of them posted “I just fixed a ten-year-old bug,” on a social network. I was shocked to learn that there were bugs buried so deep in the code that they could take a decade to squash – and that there were developers tenacious enough to hunt them for that long. That developer was Jon Cable. These days, Jon works on Destiny as a Sandbox Engineer. The fancy title means he’s one smart guy on a team of smart people who create the code that makes your armor and guns work. They still hunt bugs where they live, no matter how deep, or for how long, they’ve burrowed into the code.[/quote] It makes me question how good he is, if it took him 10 years to find and fix a known bug. Your downloaded program (without TTK) is 17 gig. If I had my crew back, your code would be rebuilt and fully functioning in approximately a year. Then you would not have all these bugs that take you so long to fix. They would be quick to find and fix. Get yourself some good programmers. Make your customers happy!