EdgarVerona

Thanks! I'm glad to be of help when the opportunity arises!

Oh yeah, I definitely didn't see the OP as an API complaint for sure (nor any of your comments!). Sadly I don't have any control over the in-game choices and focus, but I do think it's good to know that people have this desire!

Yes, this is true - some of the API actions are limited to certain areas of the game (or while offline). Unfortunately, this'll be the situation for the forseeable future: the potential for abuse vectors if the API could perform actions in combat-capable activities is too high. Funny story, you can actually see some of the cheese that came from it when the flashback activity during Moments of Triumph accidentally allowed API equipping back in the day. There's some humorous videos out there, but it's the kind of category of problems that could cause potential grief if those actions were allowed in potential combat situations.

No prob, glad to provide help when I can! I wish we had more resources and info to share.

If it helps, the biggest initial conceptual hurdle to jump over is the fact that the API is actually split into two big components that need each other but that are accessed in very different ways:

1. The static data, which you can download and provides information about any entity in the game that doesn't change dynamically as you play. For instance, the names of items, or what plugs could possibly be inserted into which sockets for an item, or other information critical to use when showing or interpreting "live" data, but has no information about a specific character or "instance" of an item and its state. This data is contained in lists of "entity definitions" (for instance, the "definition" of a particular weapon, or the "definition" of a specific Triumph rather than an actual instance of one) and each of these entities is referred to by it's identifying "hash" (a numeric identifier that is unique for that given type of entity)
2. The "Live" data, which you c...

No problem, glad to be able to talk when I can!

And thank you all of you who gave info!

Ah, thank you for the report! I appreciate that - I'll forward that info along. Other folks experiencing this, are you finding similarly? That it's new characters having the issue rather than your pre-Shadowkeep characters?

Indeed! Last time around, it was because Triumphs are meant to be account-wide, but some of them were accidentally set up to be character specific: and there's certain times at which Triumphs (and other) data is updated, accessing the API is one of those times. In the game you don't notice because these events don't fire when you log into a new character, but if you're actively playing the game we load information about your inactive characters - and that might toggle a state that, under certain conditions, makes the game think you just earned the Triumph. I'm not certain if that's the situation now, or if it's something new. There was definitely a rework of how Triumphs are put together with the introduction of those new "interval" Triumphs: so it may have regressed this issue in the process of those changes, or something else entirely may have happened. If allowed to do so, I'll try to talk on the subject once it's resolved!

If it does have to do with account vs. c...

Folks are still investigating the current situation so I can't say authoritatively what's happening this time around, but I'll try to give an update (if allowed) when we find the source of what's happening this time!

Indeed! We are investigating!

I'm pretty sure I completed this quest last week when I undercooked my dinner.

... we should hopefully have these fixed next time we put out a new companion app build!

We're working on that one - currently, the "active" perks you've chosen are being returned. We have that on tentatively while we watch our server load.

Information on inactive-but-available perks needs more work, as with recent changes to the game the amount of data we return has become unsustainable. We're working to have some changes by the end of the month to return this data once more, potentially in a new form: but it will take some time on top of that for your favorite apps to adapt to the new data.

Greetings! Unfortunately the problems we've been having maintaining the ability to return sockets and plugs have been persistent! I apologize for the inconvenience this has caused many of you.

For now, we are back to returning your currently selected plugs: but we're keeping a close eye on it, and I consider the status to be "tentative and still experimental, but hopeful."

Information on plugs that aren't currently selected, however, is where we're running into more systemic problems that are going to take longer to resolve. The format in which we return non-selected plug data was not built to sustain the amount of plug information that has been adding up over the years: Armor 2.0 and other recent additions to plug data has tipped the scales into it being an unsustainable way for us to return this data.

We're exploring options currently, both testing backwards compatible and incompatible options to try and make it sustainable for whatever...

Thanks, I appreciate it! I'll say that DIM's quality and breadth of features is really fantastic and always amazes me when I see it. I've never written an API for public use before coming to Bungie, and seeing someone take raw data and just absolutely run with it to make something incredible has been a fun experience! Folks are taking this API in directions that I never would have imagined, and I'm really impressed by it!

I'm really glad you all enjoy it!

Phew, yeah we never did get the chance to loop back around to putting it in our app again! But hopefully you all have found the data useful.

Yes! Yeah, it's a really interesting and unfortunate story!

At some point I'll have to see if I can dig up the dissertation that I wrote when we first discovered the Magazine Size issue back in Destiny 1, but the TL;DR is that this is one stat in particular where the stat is so heavily modified by non-stat systems (the sandbox, the activity you're in, scripts that are run on the server etc... when you have certain perks applied, etc) that Bungie.Net doesn't have an authoritative way to calculate the stat, because we can't get at those. We think that potentially even the rounding algorithm being applied is different than it is for other stats, but I haven't had the time to investigate that. But what we can say is that in some situations you can even watch your magazine size change significantly even when doing something like going into an activity vs. being in orbit.

Back in D1 I almost pulled it out of the API, because I didn't want to return a stat if it was nev...

Oh no worries, I can totally understand where you're coming from - I get anxiety about a lot of things personally, so I can empathize with that being a source of anxiety. I sent it over to the game side triage so someone can take a peek.

Best of the Best of the Best

Ah, I see! Yeah, I dug in the data and it doesn't have anything that obscures it once it's over. Indeed the ability to fix it is out of my hands, *but* I'll bring this up to folks who can to see if they can do so, thanks for letting me know!

It's like if I had three Destiny characters, but they're all Titans!