(edited by StevenL.3761)
Undocumented Changes
The “description” property seems to no longer be present on some items (I’m sure for consumable), so it seems that now is optional.
Edit: Also miniature 21047 and 39090 have no “description” parameter.
(edited by Alcarin.9024)
Possibly removed constant: armor.weight_class = “Clothing”
Can anyone confirm?
All clothing items were removed from the game, so yes, that value is now defunct.
The only trace left of clothing is on characters who haven’t been to the BL Armorsmith yet – they have a data record of what clothing they were wearing before April 15, so the game can determine which tonics or consumables to give in return.
Possibly removed constant: armor.weight_class = “Clothing”
Can anyone confirm?
There are still 65 armor with weight_class “Clothing”. This are their id: 20219, 20221, 20222, 20223, 20225, 20227, 20229, 20231, 20234, 20235, 20236, 20238, 20239, 20240, 20247, 20263, 20264, 20268, 20311, 20762, 20854, 36168, 36362, 36363, 36364, 36365, 36368, 36369, 36370, 36371, 36375, 36376, 36377, 36378, 36515, 36709, 37209, 37210, 38052, 38053, 38054, 38055, 38056, 38057, 38060, 39530, 39531, 39532, 39533, 39536, 39539, 39540, 39542, 39543, 41996, 41997, 41998, 41999, 42001, 43087, 43089, 43093, 43094, 43095, 43096.
Their descriptions are all about the same: “Town clothes can no longer be equipped separately.\n\nSpeak to a Black Lion Armor Trader at the trading post in any major city to exchange this item for an outfit wearable in combat.”
So they are still present but are no longer equippable.
Possibly added constant: weapon.damage_type = “Choking”
Example:
https://api.guildwars2.com/v1/item_details.json?item_id=6
Icon:
https://render.guildwars2.com/file/CC2E01E0F566A6EEF4F2EC2B19AA7A3E1FEFB1B4/60984.png
Not sure if this is real or not
New container type: OpenUI
Example:
https://api.guildwars2.com/v1/item_details.json?item_id=20313
New gizmo type: ContainerKey
Example:
https://api.guildwars2.com/v1/item_details.json?item_id=19980
(edited by StevenL.3761)
Possibly added constant: weapon.damage_type = “Choking”
Example:
https://api.guildwars2.com/v1/item_details.json?item_id=6
Icon:
https://render.guildwars2.com/file/CC2E01E0F566A6EEF4F2EC2B19AA7A3E1FEFB1B4/60984.pngNot sure if this is real or not
Looking at the stats… bundle usable anywhere? Probably not in the game.
I’ve added damage_type choking as known value on wiki documentation, altough it seems a test item, also the name of the only item of this type (id:6) is “((Assassin Coin Bundle))”…
Container type OpenUI and Gizmo type ContainerKey are used only for the new Black Lion Chest and Key, they are been added in the wiki documentation on 12 June.
New item type: Trait
Example:
https://api.guildwars2.com/v1/item_details.json?item_id=66115
@devs why isn’t this a consumable // unlock // trait type??
(edited by StevenL.3761)
Because “Trait Guide [Dogged March]”. It’s the trait unlock item which probably won’t fit into other categories because it’s actually a skill unlock. In fact, it would also fit into Consumable/Unlock – but who knows how it’s handled internally… For example, the Commander’s Compendium is Gizmo/Default.
Consumable/Unlock are so far only:
- bank tabs
- bag slots
- recipes
- dyes
- finishers (unknown)
(edited by smiley.1438)
New item flag: MonsterOnly
Example:
https://api.guildwars2.com/v1/item_details.json?item_id=8469
New item flag: MonsterOnly
Example:
https://api.guildwars2.com/v1/item_details.json?item_id=8469
Weird. Particularly since there’s a player version on the gem store right now.
The only critter I think might use this is The Beak of Darkness
This should be a bug. There is no reason for this flag, item_id 8469 IS the item in the gem store, it was added 5 August:
http://www.gw2services.com/items/show_news/05-08-2014
and there are no other items with the same name:
http://www.gw2services.com/items/search/primer
I added MonsterOnly to the API documentation just in case because it messed with my program. Also added WeaponTypes Toy and SmallBundle.
(edited by AysonCurrax.3254)
Thanks. Are you converting the flags to bit flags in your code? That’s usually what makes my program crash whenever they add a new value. I wish they would announce these changes, so I don’t have to.
Thanks. Are you converting the flags to bit flags in your code? That’s usually what makes my program crash whenever they add a new value. I wish they would announce these changes, so I don’t have to.
I have a table in my database where i map an id to each flag. since i added those manually, if the flag isnt in there because i couldnt find it in the documentation before, my code tosses errors at me when parsing all items into my database. another thing that caused problems for me in the past was the missing “bonuses” property on upgrade components which i also added to the documentation back then.
Added two more WeaponTypes to the API documentation TwoHandedToy and LargeBundle.
EDIT: Never mind, someone else beat me to it. not taking credit in that case. :P
EDIT2: Added Unlock_Type Unknown to the documentation.
(edited by AysonCurrax.3254)
Added restriction Mesmer to the documentation along with possible future values of the other classes, since the items using them are the Trait guides and hence will likely be used as they are discovered in the api.