Diablo 3 - Hexendoktor tritt Zusammenkunft der Helden beiBereits vor fast zwei Wochen gab Blizzard bekannt, dass kurz nach Release Charakterprofile auf der offiziellen Webseite von Diablo 3 verfügbar sein sollen. Gleichzeitig will Blizzard auch eine Programmierschnittstelle (API) für Diablo 3 zur Verfügung stellen, die nun in einer Vorschau vorgestellt wurde.

Die API soll es Fanseiten und Entwicklern ermöglichen, auf bestimmte Daten der Charakterprofile zuzugreifen. Über die „Career“-Profil-API werden u.a. Informationen zum Spielfortschritt ausgelesen werden können, während die Helden-Profil-API Basis-Informationen zum jeweiligen Helden wie dessen Name, Geschlecht, Level sowie komplexere Informationen wie Begleiter-Infos, aktive Skills und Items liefert.

Eine Auktionshaus-API wie bei WoW ist derzeit laut Blizzard nicht geplant. Informationen zu den Erfolgen sollen ähnlich wie bei der WoW-API zur Verfügung gestellt werden. Die komplette Vorschau kannst du direkt im Anschluss lesen. Blueposter Straton wies jedoch explizit darauf hin, dass es sich um eine sehr frühe Vorschau handele, bis zum Release der D3 API werde es voraussichtlich noch einige Änderungen geben.

 With the release of Diablo 3, we are working hard to make career and hero profiles available to the community. With career and hero profiles, we are excited to also release a set of API resources specific to Diablo 3 for community fansites and developers to consume. I’d like to take this opportunity to give a preview of the progress we’ve made to the community and open up discussions around what data will be available.

Please keep in mind that this is an early preview and there will likely be many changes to the D3 API by the time it is released. Also note that we haven’t finalized several key pieces of information including artisan recipes, hero and follower spells and powers and achievements.

Career Profile

The career profile API provides top level (account) career information. This API resource is meant to provide a way to discover the heroes associated with an account as well as the artisan and game progression information for the account. To use the career profile API resource, a URL containing a battletag is crafted and a request is made. An example request for the Battletag “Straton#1” would be:

/api/d3/account/Straton/1

The following data structure is then returned:

{
"account": "Straton#1",
"heroes": [182, 183, 184, 185, 186],
"artisan": [{
"slug": "Blacksmith",
"level": 3,
"step": { "current": 4, "max": 5 }
},{
"slug": "Jeweler",
"level": 1,
"step": { "current": 0, "max": 1 }
}],
"progression": [{
"act": 1,
"difficulty": 0
},{
"act": 2,
"difficulty": -1
},{
"act": 3,
"difficulty": -1
},{
"act": 4,
"difficulty": -1
}],
"kills": {
"monsters": 4280,
"elites": 241,
"hardcore_monsters": 0
},
"time-played": {
"barbarian": 1.0,
"demon-hunter": 0.6,
"monk": 0.3,
"witch-doctor": 0.1,
"wizard": 0.0
},
"last_modified ": 1666805944000,
}

As you can see, there are several account specific data points to reference. The heroes attribute contains a list of all of the active heroes for the account. This list does not include fallen heroes. The artisans dataset includes a list of the artisans and the id, label, level and progression of each. Next are several progression attributes that can be used to determine the highest difficulty boss for each act. Last are several stats on the number of monsters and elites killed.

Hero Profile API

Hero profile API resources provide hero specific information including basic information like the name, class, gender and level as well as more complex information like follower information, hero statistics, active skills/powers and items. Unlike the career profile API resource, a hero id is used to craft a URL instead of a battletag. An example for hero 182 would be:

/api/d3/hero/182

The following data structure is then returned:

{
"id": 182,
"name": "Yharr",
"hardcore": false,
"hero_class": 1,
"level": 21,
"gender": 0,
"create_time": 1351949944,
"update_time": 1666805944,
"hireling": [{
"hireling_class": 1,
"level": 18
}, {
"hireling_class": 2,
"level": 20,
"active": true
}],
"skills": {
"active": [{
"slug": "barbarian-overpower",
"name": "Overpower",
"icon": "http://us.media.blizzard.com/d3/icons/skills/64/barbarian_overpower.png",
"rune": { "type": 5, "name": "Revel" }
}],
"passive": [{
"slug": "barbarian-brawler",
"name": "Brawler",
"icon": " http://us.media.blizzard.com/d3/icons/skills/64/barbarian_passive_brawler.png"
}]
},
"elites_killed": 241,
"attributes": {
"life": 1510,
"dps": 58.8255,
"armor": 345,
"strength": 129,
"dexterity": 43,
"intelligence": 50,
"vitality": 139,
"resist_arcane": 0,
"resist_fire": 0,
"resist_lightning": 0,
"resist_poison": 0,
"resist_cold": 0,
"crit_chance": 0.08,
"damage_reduction": 0.333756,
"magic-find": 15,
"gold-find": 14
}
}

The first set of information provided includes the name, level and class information. Following that is a list of the hirelings the hero has unlocked. Lastly, a block of statistics is returned that includes stats, resistances and kills. (Quelle)

FAQ

Q: Will the AH have API access in a similar manner to WoW?

A: There are no plans to create an AH API (even read-only) for gold, hardcore gold or real money.

Q: What about achievements?

A: We do plan on providing all achievement information much like we do with the WoW API. The difference being that achievements are account bound.

Q: How will the request limits work? Is the „~3000“ requests per day going to be shared between the D3 API and the WoW API?

A: The same as with the WoW API. The requests per-day limits will be shared between the APIs as most fansites and applications are game specific (with a few exceptions). (Quelle)


PS: Folge uns auf Twitter oder abonniere unseren RSS Feed, um nichts zu verpassen!


Verwandte Preisvergleiche

Kommentare zu "Diablo 3: Blizzard stellt D3 API vor"

Ufff ja was für Bastler, ich kann damit ja so gar nichts anfangen :\

Uh ja, mal gucken was wir da alles für http://www.DailyDiablo.de zaubern können. 🙂