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

  • Any update on the privacy changes? Looks like recent activity and other info is still available to 3rd parties.

    Posting in language:

     

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

  • Noticed the Destiny/[membershipType]/Account/[membershipId]/Character/[characterId]/Advisors/ endpoint is up and working, but calling for one of my own characters gives me the privileges error. Is the privacy settings UI for users not deployed yet? Can't find the settings you mention for allowing Advisor data to be consumed.

    Posting in language:

     

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

    1 Reply
    • Edited by VThornheart: 1/27/2016 10:23:50 PM
      Heads up, we have discovered an issue in that you are unable to call the Item Detail API call on other users or anonymously, even if the item is equipped (/Platform/Destiny/{membershipType}/Account/{destinyMembershipId}/Character/{characterId}/Inventory/{itemInstanceId}/). We're working on testing the bug now and we will look for a release window for the fix as soon as possible. EDIT: We're going to try and release the hotfix tomorrow before noon PST as long as everything checks out. If anyone is negatively impacted, please hang tight. I'll update here if this release window changes.

      Posting in language:

       

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

      1 Reply
      • "[... they're sticky. They taste like pie and\/or victory.]" Placeholder or actual description? XD

        Posting in language:

         

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

        1 Reply
        • One more update, some last minute minor changes: * 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.

          Posting in language:

           

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

        • Am I the only one that can't access the following endpoint atm? Or have I misunderstood something? :-) Platform/Destiny/{membershipType}/Account/{destinyMembershipId}/Character/{characterId}/Advisors/

          Posting in language:

           

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

          6 Replies
          • Edited by BlazeBoss: 1/27/2016 9:35:46 PM
            [deleted]

            Posting in language:

             

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

          • [quote]* 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.[/quote] Does this mean that guns like Ace of Spades and Immobious will now have the right classType designation based on who it works for?

            Posting in language:

             

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

            1 Reply
            • Deployment is starting momentarily! Remember, privacy and the new "get other users' advisors" API will not be active right away, but the other features should be available when it is complete.

              Posting in language:

               

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

              8 Replies
              • all awesome fixes or adds to the current system. Curious as to why we early adopters of TTK weren't given the calcified fragment tracking upon release date. Seems to be a key piece of end game content to track that was erroneously left out of the build. Shame on you and thanks for finally showing up at least for the Christmas noobs.

                Posting in language:

                 

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

                6 Replies
                • Will i be able to finally DELETE my account? It is ridiculous that you can`t do that on Bungie.net. Every other friggin website i know let`s you DELETE your account. I asume you do it on purpose, but that is really, really bad practice, Bungie.

                  Posting in language:

                   

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

                • Edited by Mulchman: 1/23/2016 6:08:52 AM
                  This is great to see [relating to Calcified Fragments]. Would have loved this at TTK launch. Managing spreadsheets was not fun. :-) Glad future players will have this; this is much needed since a lot of LFG groups require Touch of Malice.

                  Posting in language:

                   

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

                  10 Replies
                  • Important update: we're delaying some of the changes above to fix some issues expressed by those of you using our stats data - it's coming in a little too hot to release right now, so we'd rather delay the privacy settings and the ability to access other users' Advisors until we get it right (as the new Advisor feature is all tied into the new privacy system, which we want to thoroughly validate after making these changes). It should be coming soon, and hopefully this will make everyone's lives a bit better. Here's the info: * HideDestinyHistoricalStats will be removed. Instead, a "HideDestinyActivityHistoryFeed" setting will exist in its place. PGCRs will still have user information, but you will not be able to directly request the Activity History of a user who enables this setting through the /Stats/ActivityHistory/ endpoint. I'll keep you all posted here when we get the green light!

                    Posting in language:

                     

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

                    11 Replies
                    • awesome info. :D good work fellas!

                      Posting in language:

                       

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

                    • Edited by loudenkl: 1/25/2016 10:10:08 PM
                      While I'm not a API developer, but as end user - I am glad to see these changes are coming soon. I'm surprised that the ability to track calcified fragments per character hasn't garnered a wider announcement. Regarding the Privacy settings, will they be more of an all (public) or none (private), or will users have the ability to tailor them, such as allowing only those that are set as a follower or those that are in some one's friends list?

                      Posting in language:

                       

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

                      3 Replies
                      • Edited by lowlines: 1/23/2016 3:22:06 AM
                        BWU for devs. This is fantastic! Both these changes and the fact that I didn't have to data mine it next week (but I obviously still will) :D

                        Posting in language:

                         

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

                      • Sounds great ! cant wait to see it.

                        Posting in language:

                         

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

                      • Love to see the start of privacy toggles. I foresee a quite powerful system (for those that opt into it) in 3rd party tools.

                        Posting in language:

                         

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

                      • "Dear Bungie, Please stop doing important feature additions to the Bungie.Net API on the same week that Iron Banner and Oryx CM happen" - signed Dweezil's wife Seriously though, this is great! [Tries to hold marriage and job intact]

                        Posting in language:

                         

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

                        1 Reply
                        • Bump

                          Posting in language:

                           

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

                        • Edited by sgtfrankieboy: 1/23/2016 4:59:01 PM
                          How will the Historical Privacy Stats Setting effect requests for PGCR Reports? Will that be purged? Meaning the entry of that person is no longer visible or will you just hide the characterId, membership info, etc. (Which is the preferred solution)? How does it affect any other statistics endpoint for that matter.

                          Posting in language:

                           

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

                          3 Replies
                          • Without being specific, as I know is near impossible with dev, is this release slated to happen in the coming hours? days? weeks? months? Just curious as to a vague/rough timetable. Overall looking forward to the much anticipated changes!

                            Posting in language:

                             

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

                            3 Replies
                            • this is great thanks!

                              Posting in language:

                               

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

                            • Wheres cozmos videos ? Jokes aside thats great news. Gj

                              Posting in language:

                               

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

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