BlueTracker

Hi Wain,

We did recently make some changes to the way PvP gladiator mounts are included in the collections document, however I would not expect those changes to impact the collections document in the way you are describing. We are having some conversation internally to determine if there is a bug here.

Thanks for the report!

Greetings all,

First, we apologize for the delay in circling back to this issue.

While we are continuing to look into this and other related issues that have arisen, we want to provide some additional information that we hope will help.

With the API rework it was intended for the entire account’s collection to be returned for any player, but this is no longer the case.

While this is correct, with changes made in support of the World of Warcraft 8.3.7 update, the Character Collections Mount Summary API was modified with the intention of better representing the mounts that are available as well as actually usable at the character level while continuing to maintain the Account Mounts Collection Summary API as a holistic view of the mounts collected at the account level. One of these changes was the addition of an “is_useable” boolean, as well as the addition of an “is_character_specific” boolean, on each mount in the Character Collections Mount Summary document where they apply.

We’ve since discovered that some unintended changes may have also been introduced, and we continue to evaluate the scope and impact of these changes. Additionally, we realize that we failed to communicate the intended changes, and failed to recognize the unintended changes, and for that, we apologize.

As we know now, an unintended change introduced with the World of Warcraft 8.3.7 update is that when a player logs out of World of Warcraft for the first time on a character which hasn’t played since the update was released, the Character Collection Mount Summary documents for other characters on that player’s account will become unavailable until those specific characters also experience a logout. At this time, we are advising that API consumers encourage users who may be experiencing this issue to log their characters out of World of Warcraft, which will cause these documents to once again become available.

We will continue to investigate the additional issues that have been communicated in this thread and provide an update when we have one.

Thank you for the feedback and reports.

Greetings all,

To get right to it, we’ve determined that the Character Collections Mount Summary API is currently working as is intended. To be more specific, the API reflects the same data presented in-game should a player inspect their own mounts collection with all filters turned off, or more precisely, with the “Collected” and “Unusable” boxes both checked.

Additionally, the is_useable flag intends to allow consumers further to filter the document data to only useable mounts, as if the “Unusable” box was unchecked in-game. We understand this is not immediately apparent, and again we apologize for the lack of communication, documentation, and added confusion surrounding the addition of the is_useable flag property.

When possible, our intent with Character specific documents is to represent the data directly as a player would consume it in-game, and any deviation from this strategy is likely unintended or undesired. It is not our intention for Character specific documents to expose data that would be considered ‘account-wide’ when that same data would not be presented to the player in-game. An example of a deviation here is Achievement data, where the player can choose to display their account-wide achievements at the character level.

To best allow the player agency over their account-wide data and who consumes it, we recommend consumers interested in account-wide data integrate with the Account Mounts Collection Summary API available via the Battlenet OAuth Code Authorization flow, which provides a full picture of the mounts collected for an authorized account.

We understand and sympathize with the complexities and challenges this introduces for some projects. We wholeheartedly apologize for the lack of preparation you were given, and our failure to communicate the changes ahead of time. We failed to keep you informed that the previously observed behavior was being changed.

We much appreciate everyone’s patience and involvement in this discussion. Please continue to report any challenges you experience with the WoW APIs so that we can continue to grow and improve upon them together.

– Maguthul

Y hablando de Inverlandia, ¿listos para el evento? ¡No queda nada!

Últimas partidas del evento, mucha suerte y ¡feliz día de Reyes!