It’s not about the API itself, but I guess it’s a relevant problem year-over-year for some community devs.
Is there a special/priority way to receive a guaranteed invitation to betas/test realms for community devs?
My Story
…and why it’s important (at least for me):
As for now, I am making a discord bot, which allows users to evaluate game-items in World of Warcraft based on API data. I made it a couple of months ago, but I need to prepare all the formulas for shadowlands.
If you are interested in or might wanna take a look at https://i.imgur.com/FyMLNN3.png
The problem is, that (in this certain case) I needed to receive a full list of Shadowlands items obtained from vendors or all items that belong to the trade_class: Herbs.
You might wanna say: Wowhead it! Right? - Wrong.
This is how Wowhead returns all herb items from shadowlands.
https://shadowlands.wowhead.com/herbs?filter-any=82:166;2:9;90001:0
The problem with the vendor obtained items is much complex than that.
https://shadowlands.wowhead.com/items?filter=166:92;9:1;0:0
(even vendor-page itself doesn’t have a list of all selling items)
At least we have Marlamin’s wow.tools
? But there is not an easy way to obtain vendor items.
So, the easiest way is to log in on Shadowlands beta, come to Orebos and check the vendor manually, with listing every item id one-by-one on paper.
Which I really could do, if I have access to it. But thank god, I play in some Hall of Fame TOP 100 guild, so almost every guild member has an access to it. Except me, which is such an irony.
This story has a happy end. Because I asked a friend, and as soon, as he logs on, I receive all the necessary data. But it’s only a «for now» solution.
BUT!
Conclusion
As for my point, there are two options to fix it. The first is:
-
Form a list / make an online application form for community devs, with reviewing / pre-moderating (so people won’t span with ‘GIMME BETA’ for fun) current dev’s projects, which is a bit bureaucratic.
-
Or to enable
Battlenet-Namespace
header/param in all endpoints, allowing to request game-data not from the past, but the future or upcoming versions of the game. Like this one:https://us.api.blizzard.com/data/wow/item/178787?namespace=static-us&Battlenet-Namespace=static-9.0.1_35598-us&locale=en_US
as sometime Araspair mentioned in his message via API community discord:
Now that I’ve explained the versioning: when I say that static data has a TTL of 42 days, this is from the last publish for a server version. As in, if the server version does not change for a month, this TTL is refreshed every weekly maintenance until the server version is next bumped. When the server version is bumped, the new data will be published to a new namespace (
static-{new_version}-{region}
), and the TTL for the old static namespace will be 42 days from the last publish .static-{region}
will point to the new namespace.
I understand that probably I should post it not here, but Press and Media Contacts in my region. And I know for a fact, that there are other more priority requests for the API team, which are mentioned in relative «Our vision is to help you achieve yours » thread, like bonus_list for items, API schemas and so on.