JavaScript is required to use Bungie.net

Forums

originally posted in:BungieNetPlatform
Edited by VThornheart: 1/28/2016 6:39:21 PM
24

Platform changes in the next release

Barring any unforseen difficulties, next week we should be releasing another build of Bungie.net. This one has a few important and long-delayed service changes that you all will hopefully enjoy! [u][b]* "Checklist" Advisors[/b][/u] This is a new type of advisor created specifically for Calcified Fragments, but will hopefully be used for more in the future. These per-character advisors most notably have a "cards" property: this is a dictionary with the key being the Grimoire Card related to the checklist and the value being a boolean indicating whether or not the card's requirements have been met *ON THE SPECIFICALLY QUERIED-FOR CHARACTER*. For instance, with Calcified Fragments, the advisor data will effectively tell you which fragments you have acquired on a per-character basis, allowing you to finally hunt down the remaining ones you are missing. (In spoiler tag: changes that were set to be released but have been delayed. Stay posted on this group for updates) Current plan, subject to high potential variability, is to release it with our next major bnet release ~2 weeks from now. [spoiler][u][b]* Advisor endpoint for accessing other users' Advisors[/b][/u] <-- [b]Delayed [/b]pending changes to the new Privacy system Also known as the "GetAdvisorsForCharacter" endpoint, its signature will be: Platform/Destiny/{membershipType}/Account/{destinyMembershipId}/Character/{characterId}/Advisors/ By default, any Destiny character will be accessible through this endpoint. However, check the next section - privacy and privilege - for important caveats. [u][b]* Privacy and Privilege[/b][/u] <-- [b]Delayed [/b]pending changes to the new Privacy system In order to expose Advisors publicly, we wanted to also allow people to hide themselves from that exposure if they so desire. In doing so, we've built Destiny privacy settings into your account. Once we deploy this build, users will be able to go to their Settings -> Privacy page and toggle whether they want their non-equipped Inventory (private by default), Stats Activity History (public by default), and advisor data (public by default) to be visible by other users or anonymously. We anticipate that more settings will be added in the future, but these three will serve our most immediate needs. Note that these settings may cause you to receive data a bit differently than usual: * [b]You will get the "InsufficientPrivileges" error response if you query for something that is directly forbidden.[/b] For instance, if you query for a user's Advisors and they have their Advisors set to private, you will get InsufficientPrivileges. * [b]If what you're querying for is not *directly* forbidden, but has content that you shouldn't see, that content will be silently purged[/b]. For instance, if you query for a user's advisors and they are set to public, but they have their Inventory set to private (which will be the default!), you'll get back advisors but the data will be purged of any information about what is in the user's inventory. You'll still get Activity-based advisors, but most item-based advisors will be stripped. [b]Your application needs to handle the fact that any property returned about another user could potentially be stripped (excluded entirely) from the results due to their privacy settings[/b]. This should hopefully give you a lot more flexibility, while still providing people with the privacy that they desire. These privacy settings extend to other calls as well - so if you can convince your users to make their non-equipped Inventory public, you will be able to make non-authenticated queries for their inventory and get the entire set of data.[/spoiler] [u][b]--- Minor changes ---[/b][/u] * For those of you who noticed that the Trials of Osiris advisor has been missing for a while, it will finally be returning in Advisor results for the next time Trials comes around. Important changes: The "buffs" and "unredeemedRewards" properties are now deprecated: buffs are represented as talent nodes on the ticket item, and rewards are redeemed at PGCR time instead of having to hoof it over to the Trials vendor to get your reward. The "ticket" property now has a "ticketItem" property on it, which is of type DestinyInventoryItem: it should give you enough information to show the ticket's talent nodes and other item information. * Armor and Weapons in the "Explorer" endpoint as well as in static definitions that were meant to be "classless" but were instead categorized as "Titan" should now be categorized correctly. Similarly, weapons that had no class but were meant to be class specific should now have their appropriate classes.
English

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

View Entire Topic
You are not allowed to view this content.
;
preload icon
preload icon
preload icon