Upgrade slots and Materials

Upgrade slots and Materials

in API Development

Posted by: Elfo Bianco.3786

Elfo Bianco.3786

Hi, ok lot of items are actually missing in API:2/items, but Lawton said that soon or later that will be fixed.
Now I’m continuing to read the data from API:2/items and I have some issues.

First issue: the items says how many and which infusion slots they have, but that is not the same for the common upgrade slots. For example the item ID: 42426 (Sclerite Karka Shell), how can I know that this item doesn’t have any upgrade slots? In that case I can’t consider that all ascended item doesn’t have any upgrade slots, while all the other items yes.

Second issue: for recipes there is the API:2/recipes that gives all the info about the crafting disciplines required and the minimum rating required to craft the item. For materials there is the API:2/materials, but I don’t find any info about which crafting disciplines can use them and at which rating. I don’t understand if I missing something, I have already seen wiki pages, but nothing yet.

Upgrade slots and Materials

in API Development

Posted by: darthmaim.6017

darthmaim.6017

42426 has the flag “NotUpgradeable”.

Upgrade slots and Materials

in API Development

Posted by: Elfo Bianco.3786

Elfo Bianco.3786

42426 has the flag “NotUpgradeable”.

Ah that is the meaning of that flag :\ thank you!

I have seen that this flag is not there on 42426, maybe is related to the know issue with items’ flags..

(edited by Elfo Bianco.3786)

Upgrade slots and Materials

in API Development

Posted by: darthmaim.6017

darthmaim.6017

Yep, I guess it’s related to the broken flags atm, the cached version I use for gw2treasures still contains the flag: https://en.gw2treasures.com/item/42426/json.

Upgrade slots and Materials

in API Development

Posted by: Lawton Campbell

Lawton Campbell

Web Programmer

Yep, I guess it’s related to the broken flags atm, the cached version I use for gw2treasures still contains the flag: https://en.gw2treasures.com/item/42426/json.

FWIW, it should be fixed now