Fuzzle_hc

Hot take?

I am glad Bungie focused on a robust API that allowed our talented community to program so many amazing tools and websites we use every day instead of trying to implement systems the community of millions will do three times better in half the time.

Hell, even I made my own little project with the API, it's very easy to get into and has a very high ceiling of possibilities.

This is a focus of our team (Bnet). We have a pretty small team, so we have to choose where to focus our resources. If we build lots of our own tools, we can't spend as much time focusing on including game features in the API, and building the stuff only we can make (Cross Save, etc). It would be really cool to build LOTS of features for everyone, but with a limited team size, it's very difficult to hit every use case. When we can, we provide features that enable the community to build super cool stuff on top of them. Finding that line is always a WIP, but it's really great to see that the community has made tools that provide stuff for everyone, even niche use cases.

Asterias19

Bug is still outstanding...fix any time soon?

It should read Mythic. If you are referring to the quest not progressing correcting for some players that should be fixed in the next update.

OrcaLyf

Is there anyway the funds raised for Australia could be better distributed? Both organisations are great and worthy, however, they only represent one state, New South Wales (NSW). As I understand WIRES legally cannot act outside of NSW. While many koalas have been harmed there, the safety net population on kangaroo island in South Australia (SA) was also hit hard. So far the bulk of the funding has gone to WIRES and not organisations based in SA or Victoria (Vic). Each state also has their own fire service. The RFS represents NSW, CFA represent la Vic and the CFS represents SA.

I believed that this agreement has already been finalized but I will give this feedback to our team. Thanks.

Keyastis

Any fix planned for the green with envy quest? @u/cozmo

Currently planned to be fixed in the next update.

Bhu124

Telesto now downgrades your Windows to Vista.

Windows Millenium Edition

slowsmo

Damn no mention of the unholy lag when switching mods

Nothing to report at this moment. Team is aware. Once we have some info on an investigation, we'll let you know!

Thanks for supporting a great cause! I look forward to seeing these shirts at future events to identify my fellow Guardians.

I have encountered this as well, in a few activities. I'll be sure to send this report over to the team, but I believe they're in the process of investigating this perf issue, among others.

Will give updates when we can!

Hey all,

After a quick investigation, looks like this was impacting all three of the solar ornaments (Hunter, Warlock, and Titan). The team has disabled the ability to purchase the 800 Silver versions, and we will be issuing refunds to those who were overcharged. The 500 silver versions will continue to be available on the seasons page.

Thanks for the post & screenshot, OP! This is indeed a bug.

This is wonderful.

Thank you for the feedback. We'll continue to pass it along.

More specifically:

1. Reputation granted from Telemetry Data does not feel appropriate

2. Some highly desirable ghost shells have undesirable perks

Thanks for the feedback - this ties in to a lot of threads at the beginning of Shadowkeep, where players were asking for the world loot pool to be refreshed. While we've added some reprised weapons, many players feel they're out of reach due to the pool size.

Will pass this along!

As a question to all, how do you feel about the current catalysts on alternate exotics?

Some give basic stat boosts, where others give alternate functionality.

This ties in to some of the exotic quest feedback we're getting right now, where some people appreciate the lore but wanted more in terms of depth. If a catalyst is appreciated due to kill count/gold box, but doesn't bring much change to the exotic itself, would it incur the same poor feedback?

Would love y'alls thoughts.

Animeye

As more and more end-game content REQUIRES fireteams due to lack of matchmaking (legendary sundial, high end ordeal, high end nightmare hunts), the fact that this STILL isn't fixed is a major issue.

Fixing this bug either needs to be a top priority, or these activities need to include matchmaking.

And please, don't say "add clan mates to your friends list" or "use external LFG". The existence of external tools doesn't absolve the game's broken functionality.

We're working on a fix.

Looks great! Love the color.

I've always played invis builds since the beginning of Destiny. Remember when all you had to do was crouch for a few seconds as a Blade Dancer?

I'll definitely pass along everyone's feedback. Seems like there are players voicing opinions on both sides of the argument and bringing up that giving up a super with a lot of slaying potential is a big tradeoff.

ralamus

Hey Cozmo, any chance that a Quickplay 4v4 will happen? 3v3 has been perfect for comp games but 6v6 has really felt like a clusterfuck on almost every map.

Edit: I'm not saying 6v6 should go away, just add a 4v4 option for it. The maps are too small for 6v6.

Seems like the overall community feedback was 6v6 was better than 4v4 when we made the switch in Y1. Happy to hear everyone's thoughts though.

We made some minor changes to the spawning of Dead Cliffs. You can read the full patch notes on what changes where made to the maps the returned here. Doesn't appear it was enough to prevent spawn trapping though. I'll put in a request to remove it from the Control playlist based on feedback here. I know it's still a popular map in some other modes.

I'll also give feedback on removing Gambler's Run. Let me know if anyone disagrees with anything I've taken away from this thread or if you have any other related feedback. Thanks!

Roses are red, a Titan protects ...you’ve been killed by the architects

dmg04

Some bugs can share the same priority levels, but one bug with a larger amount of conversation takes longer to fix due to the complexity of the issue. Other times, bugs with a loud conversation can go on without a fix for lengthy amounts of time, as the cost to address it could override the actual benefit.

In terms of player beneficial bugs, I'd like to give an example of an issue that was just discovered that may be fixed in a shorter amount of time than expected. Players can currently hide their weapons/arms, which is leading to some pretty cool content creation. While this bug is benefiting players, it's actually causing issues with memory in the game. The team is investigating the full impact, but things like this could lead to nasty issues the more that players use the bug in public areas. Think error codes, crashes, or other. I admit from a personal side, I'm sad to see the bug needs to be fixed, but a cursory look at the issue indicated a fairly low wake fix (low time to implement, test, and ship) on something that a designer was already looking at.

Another would be the Wormgod Caress. We quickly disabled the Exotic, and are investigating the issue for a future patch. While players were having some fun annihilating bosses, Gambit/Gambit Prime was slowly becoming an issue where players could kill the Primeval in a very short amount of time without many slayer stacks. It was exciting to see players breaking the game in fun and new ways, but there was wider impact than just raids or nightfall bosses. As such, we had to disable access to the exotic, even though the conversation around it was fairly positive out the gate.

I've told the story about the Mercury Sparrow issue a few times, but that's another good example of a highly visible community request where the cost of a fix would have negatively impacted other areas of the game.

As for the Sunbreaker issue, I'll check with the team. I don't mean for the explanations above to be excuses of why we aren't addressing this one specifically. Rather, it could be that we've developed a fix in the past that ended up breaking in another hotfix. It could be caused by connection issues, which would require a rework of the perk. Performing the quick google search is showing me quite a few posts from 2015 and 2016, but it seems the report volume has dropped, so the issue wasn't on our radar. If the repro rate is low enough internally, the priority of the investigation may drop as other issues arise in development on other items that haven't shipped yet.

In any case, we'll get a conversation started with the team and provide updates when possible.

Following up!

Looks like the team has been investigating for a bit, and they're planning to address this in future hotfix. Don't have specific details on the changes they're developing or when exactly to expect it, but will be sure to cover it in a patch note preview.