Item Upgrade API Changes

We're not going to have anything on day 1, we're working on it now and I will update once I know what it will look like. Sorry for the delay.

We definitely will provide an upgrade id on the item in the tooltipParams referencing a /data api that will expose the cost and ilvl upgrade. I'm not positive how we'll show stat changes yet. Once we get it implemented on the site I'll post with final information of course.

EDIT: We're putting the ilvl upgrade right in the tooltip params. I just posted an example at the end of this thread. We're not exposing the cost information in the api [yet], if there is a large need for this let me know.

Item upgrade information will be available tomorrow (afternoon, pst) if all of the deploys go as planned. Sorry it took so long to get this out. We're working on ways to speed this up for future patch changes.

We also realize that this first pass doesn't give all the data people wanted in the way that they wanted it. Hopefully we'll be able to fill some gaps in future updates.

The fields=items option on characters is getting a bunch of data added to it. First there is a new tooltip param section for updates that has the current and total upgrade options and the current item level upgrade.

On top of this the item (when viewed on a character profile) also is getting the item level, stats, armor and weapon info added to it since these are all of the values that can be edited. This means that character profile items now have all of their stats in edited forms (with reforges, enchants, upgrades etc). The values you see on the profile page tooltips are listed here.

One of the current issues we have is for viewing items NOT in the context of character profiles (/api/wow/item for instance). We have no data about how much an item can be upgraded in this view so all we can add is one boolean flag "upgradable". The logic for how an item can be upgraded is extremely flexible so while in game it's pretty clear what it is (currently), we weren't able to add it into the api for this update.

An example of a character profile item (weapon in this case to show all fields):mainHand: {
id: 81279,
name: "Tempestuous Longbow",
icon: "inv_bow_1h_pandung_c_01",
quality: 3,
itemLevel: 471,
tooltipParams: {
upgrade: {
current: 1,
total: 1,
itemLevelIncrement: 8
}
},
stats: [
{
stat: 32,
amount: 646,
reforged: false
},
{
stat: 3,
amount: 969,
reforged: false
},
{
stat: 31,
amount: 646,
reforged: false
},
{
stat: 7,
amount: 1454,
reforged: false
}
],
armor: 0,
weaponInfo: {
damage: {
min: 7433,
max: 13805
},
weaponSpeed: 3,
dps: 3539.6667
}
}

I will try to get the docs updated with this and the other things that are missing this week.

For an epic the "current" field would be 0, 1 or 2, and total will be 2 (if the item upgrades like most epics do). The "itemLevelIncrement" field will be 0, 4 or 8 depending on what upgrade level you're at.

The stats will be whatever the stats of the item currently are, just like on that blue example.

For the CN/TW upgrades it will be the same. The stats should be the current stats of that character's item while the "total" will be the max number of upgrade states, and "current" being which one you're at. The "itemLevelIncrement" will again say how many item level points are being added onto the item.

12/17/2012 07:58 PMPosted by Edgy

However, before you deploy tomorrow, could you update the weapon Min/Max damage calculation to use the exact value? In the API, you are incorrectly rounding to integers, and then the provided DPS number is being derived from those integers.

I will look at this tomorrow morning, but let me make sure I understand correctly. You just want unrounded min/max numbers exposed, and then for us to use those values when calculating dps correct? (I'm not going to remove DPS from the api, but making it more correct is fine).

Much appreciated.

I'm sure that (since there are thousands of items) getting all the details straight must take a lot of babysitting for the system to be viable and error-free for all possible items.

Just to be sure, I hope that the old TooltipParams for gems and reforging will stay the same? For example, Haste reforged to Hit had a code of 151. And there were gemslot and equipped gem codes as well. Are those changed?

Those should not be affected in any way.

Thanks for finding these problems!

Indeed we aren't showing the reforged stat in the list of stats which I will fix. This stat will have "reforged: true" (this field was originally just for whether or not to color the stat green). I'm going to remove the reforged field from the output if it's false (just for clarity).

On the stat that has it's value decreased, I'm going to add the amount of the decrease in a "reforgedAmount" stat.

For example: on the chestplate that Landsoul is talking about, the reforged field will not be there on stat 36, but there WILL be a "reforgedAmount: -313" field. The other stat will also show up with an "amount: 313" and a "reforged: true" field. Here is an example:

"stats":[{"stat":32,"amount":978},{"stat":4,"amount":1315},{"stat":36,"amount":471,"reforgedAmount":-313},{"stat":7,"amount":2232},{"stat":49,"amount":313,"reforged":true}]
Hopefully this fixes these issues. I'm hoping to deploy this tomorrow but other things may get in the way of that.

12/18/2012 01:40 PMPosted by Edgy

The exactMax however appears to be rounded. Possibly this could be fixed?

This value is floored in the wow code when computing max weapon dps, so this should be the actual value used when doing all calculations. If you find discrepancies in numbers that you see in game due to this let me know.