|
We don't have any information on that right now. Peratryn will be able to keep the community updates with changes to the APIs coming with MoP.
|
Oh don't feel bad for us. We have awesome jobs. And, all things considered and relative, Mr ujournal is polite, respectful and seems to have (mostly) good intentions here. |
No, there are no plans on implementing that feature at this time. |
It's not a proxy service, the code is 100% client-side and uses the WoW web APIs. It's one HTML page with the functional javascript embedded within it. View the source before shooting it down. Any time someone says "hey, go get that data here" where "here" isn't our own APIs, we have to make it clear that the data may be different than the source (our APIs). Don't take it personally. |
To be clear, we don't support or endorse the use of proxy services such as this to retrieve data that is otherwise available through the official WoW web APIs. |
|
To openraid, we did receive your email and we have taken appropriate action. As I'm sure you are all well aware of by now, it has been a really busy week and we have been keeping deploys and production changes to a minimum.
To everyone else, although I'm really glad to see everyone excited about sites like openraid, this isn't the place to discus them or their application limits. They have contacted us through the official channels and it is between openraid and Blizzard to figure out why they are hitting their application limit (which is already really high). If you want to discuss openraid or talk about how it impacts you as a player, do it on their forum. |
|
Locking this thread and creating a new one for it on the D3 game site.
http://us.battle.net/d3/en/forum/3355037/ |
|
Hi everyone! Today we released D3 Game site profiles and will be releasing the D3 web APIs very shortly. As a result, I'll be locking this thread and creating a new D3 specific developer community forum on the D3 game site.
I'm so grateful to have answered your questions and gotten feedback on the D3 API. I'm very excited to have it launch soon and see what awesome things the community can create with it. More at: http://us.battle.net/d3/en/blog/6821782/Character_Profiles_Now_Available-8_6_2012 |
|
I'll post the status of profiles and the D3 web APIs on Monday. I've been out on vacation.
|
I'm assuming the D3 API falls under the same Terms & Conditions as the WoW API Yes, that is correct. |
Are account profiles bound to regional hosts? Requests made to a given region only return information specific to that region. |
|
Simmer down. Lets keep this thread on point so I don't have to lock it.
|
I'll have to double check that.
NOPE. When we make achievement data available, you'll be able to use that.
The same way the WoW API supports multiple languages.
Before I ask you to rephrase the question using big-boy words, I suggest you go back and read this thread in its entirety as it has been covered already. |
If so I guess i'm surprised that this information won't be shown. We won't be able to even hand calculate DPS without IAS, min/max, crit dmg. Yes I know it's shown for us in Damage field but alot of the ideas people had in mind revolve around seeing how items would affect a player, and that will be impossible without pulling all other items and totalling them up manually. That isn't the sort of information we want the community to have. J/K It was an oversight, those stats will be added and the documentation updated. |
Pulling items one by one involves many requests. Well, the items of a hero are provided when requesting a single hero through the API. It is the "item details" that are specific to the item generator that requires additional calls. That same data is also available to use with the tooltip JS provided on the D3 game site, if you don't want to store all of that information. We could entertain the idea of providing that additional item data with the hero API resource, but I'm leaning heavily against it because the amount of data returned is already very large as is. |
Is it intended that the precise salvage chances are exposed by this API? I noticed that we get much more precision on the chances of Firey Brimstone salvaging. The decision to expose the disenchant info was deliberate. The Diablo game team could swoop in and request that we change it, but with what we've shown them recently I don't think that will happen. There aren't any plans to support a 'lite' version at this time. It is something that I can talk to the team about, but it won't likely be done any time soon. |
That information is already calculated and totaled with the stats on the hero. |
The example of "Straton#1" was just an example. The format of a battletag is as follows: The code will almost always be greater than 100, but it should be treated as an integer. |
Sadly no. If banners are squeezed in, it'll be through a front-end image layering feature (if that is possible). I didn't have the time to build the banner renderer as we had hoped.
I do believe that we plan on providing the base banner detail information (ie the flags to indicate what is displayed and in what colors), but it may be useless until we get the chance to properly explain how to reverse engineer the data. |
|
Gah, looks like someone stole my thunder.
So we've made a lot of progress with the data APIs and I've updated the documentation to include the item data resource. I plan on creating a few additional example json files for different item types, so stay tuned for that update as well. |
