API talk:2/itemstats

I'm not sure if this is worthwhile but here goes. There is a crzy amount of empty itemstats in the API, so to sort through all of them I made myself this list. I'm not sure how long this will be 'correct', but for now it seems to hold.

ID	name
153	shaman
154	rabid
155	cleric
156	magi
157	valkyrie
158	knight
159	rampager
160	carrion
161	berserker
162	soldier
559	celestial
605	Apothecary
616	cavalier
632	giver
686	sentinel
700	settler
753	assassin
754	dire
799	zealots
1011	forsaken
1012	apostate
1026	nomads
1067	sinister
1085	trailblazer
1109	crusader
1111	marauder
1118	vigilant
1123	minstrel
1131	commander
1140	wanderer
1153	viper

-Darqam (talk) 16:08, 29 June 2016 (UTC)

Without looking, I'd guess the blank ones are for ascended trinkets etc. Thanks for the information though. -Chieftain Alex 17:44, 29 June 2016 (UTC)

Upon further investigation, this list is already incomplete, and will possible be even more so depending on where an issue is with the new stat_choices in items. -Darqam (talk) 17:48, 29 June 2016 (UTC)

The 0-199 series stats are "original" item/gear stats; itemstats with a non-null name are pve sets. The empty sets in the 200 series, if a developer can confirm, should be test items. The 300 series (and others) that have null names are, I believe, pvp amulets stat sets (you should see sets of stats/values repeated among those with and without names.) Ascended items actually reference a skill id to acquire their stats/prefix and don't generally require a reference to itemstats; but they would also be referencing an itemstat that has a non-null name field. Despite my understanding of the data, I have seen a lot of repeated data, and without confirmation, even some of the data presented to us could also be items not in-game for player use. 108.65.96.234 19:41, 29 June 2016 (UTC) Did not realize I wasn't logged in Bandlero (talk) 19:42, 29 June 2016 (UTC)

Also, some of the itemstats I believe are for gear used by mobs. I guess I wanted to emphasis that all of the itemstats we see are not sets that are usable by characters. Bandlero (talk) 19:46, 29 June 2016 (UTC)

every itemstat (not sure on the engine definition as i've seen no named reference to it) has a uuid-like name hint so it might just lack localization data or be disabled in textdecode. ascended items do reference the same itemstat ptr just like every other item and will return a valid LUT result, the exception being ascended trinkets - the LUT value for these will be for the base item (eg. 268.884 is the LUT value for an ascended zerk ring giving 94/67/67 as the derived stats) followed by an inline adder that checks extended data on the itemstat ptr for baked-in values to add to the derived total to give you the stats you see on your hero panel. these baked-in values are also the reason why, on this endpoint and in-game, you will see several stat sets with the same name or no-name sets that are used strictly for this purpose.99.231.213.98 23:09, 25 October 2016 (UTC)

i should also add that everything that can be considered an upgrade has an itemstat, which may or may not have a name or even stats, such as superior sigil of force uses itemstat 261. there is no development item group as far as i can tell but they are grouped based on "similarity" like sigils or runes or jewels or 2/3/4pc stat sets or ascendedtrinket.99.231.213.98 06:02, 26 October 2016 (UTC)