Tracked bugs, why percentages, QoL updates to old content
- (Cozmo believes) They have figured out the cause for weapons and player models going randomly invisible during Crucible matches and are working on a fix. (Reddit)
- In regards to missions like Bad Juju: They try to create different challenges and moods with some activities rewarding teamwork, while others test your grit even when no one is backing you up. (Reddit)
- Crucible spawn errors in Competitive are being investigated. (Twitter) 2
- Free rewards glitch in Tribute Hall is being investigated. (Forums)
- Has let the team know that Sparrow Horns are something the community would like to see brought to Destiny 2 at some point in the future. (Forums)
- Feedback that players want to see more interactions with civilians (such as escort missions) has been passed along. (Forums)
- On Menagerie chest post-patch feedback: "We have got a lot of feedback about the Menagerie chest bug being fixed. I have seen a lot of suggestions on reaching a middle ground that still allows multiple rewards per run. Let me know your thoughts and I will pass them along to the dev team." (Forums)
- GuardianCon emblem will appear later this summer. (Twitter)
- Reason why some Triumphs/Pursuits have percentages:
A bit of reason to this madness:
When we do exact numbers, there’s extra work if we have to update them. Lets say you have to get 300 grenade kills, and we decide to lower it to 100. Every localized version of Destiny 2 has to make, test, and verify the change works. Sure, changing a 3 to a 1 doesn’t seem to hard, but when you’re doing dialogue tor the entire game, typos can slip through, and lead to confusion.
With percentages, the change can be made on the backend, communicated via TWAB/tweet, and done. No risk to game text that could have a minor bug introduced, then require a future hotfix to address.
We put exact numbers where we can as often as we can, but sometimes opt for percentages to give room for updates if needed, without having to test in every language. (Reddit)
- On lack of QoL updates to previous seasons and expansions:
Thanks for the continued feedback on QOL requests from previous seasons and expansions. It helps us to prioritize what players want most, and gives teams an idea of what to schedule for future patches/hotfixes.
To give some context on why QOL is sometimes delayed or not acted upon, I want to call out the Mercury Sparrow bullet in particular. This was something that players were asking about many, many moons ago. It's something that the team actually tried to implement, but it ended up causing some bugs that would crash the game, or impact various activities on Mercury. This jammed up our development timeline, as we essentially lost resources that could have been allocated to testing other content that was being cooked up.
Ultimately, it was decided that the Mercury Sparrow QOL request needed to be reverted and looked at again in the future, as we didn't have enough time to hammer away at the issues brought on by the change. To put another way, each QOL request has a trade off. Do we go back and add sparrows to mercury, or do we spend the same amount of test time on things like the Dreaming City curse cycle? What if a simple QOL request ends up bringing deep rooted bugs that require more time to hammer out? Keep working on that, or hit other items that are easier to implement? Prioritize the emblem, or prioritize the Rocket Launcher? We have eyes on the other weapons as well. A bit more tricky as the backend setup is different than a nightfall drop. (Reddit)
Another example that we worked on during Season of the Drifter - do we add bad luck protection to sleeper nodes, or do we focus on bad luck protection for Raids and Wayfarer objectives first? We'd been getting a lot of feedback on RNG requirements for Seal acquisition, so we needed to figure out which objectives would make players happiest, knowing that we couldn't hit all of them in one fell swoop. Sometimes we have to make these calls knowing that we won't have time to address the items we couldn't hit, so we have to prioritize what to tackle ASAP based not only on community feedback, but our release timelines and people we have available to work on the content.
All that said, we're going to continue collecting feedback from threads like this to ensure community priority is understood. Hope this gave a bit of insight as to how we approach these feedback items!