-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle item variant quality/rarity #117
Comments
Does this work for all items? Using only the class name (excluding
As they all share the class name |
It seems that the ID I mentioned above was not consistent. |
Issue
In the current API, the same item in different sets are not considered being variants of each other. For example, Morozov-SH Helmet only has
Aftershock
,Red Alert
,Snowdrift
,Terracotta
, andThule
as variants, which are all in set 01. Items in set 02 and 03 are not included in thevariants
output.Proposal
It seems that the first digit in the class name of the item determines the quality of the item. The syntax kinda looks like this:
itemname_XX_YY_ZZ
, whereXX
is the set/quality/rarity,YY_ZZ
is the color (YY could be rarity of the color).Takes the Morozov-SH Helmet as an example. You can see the temperature stats are progressively better when
XX
is higher:Morozov-SH Helmet (
rrs_specialist_heavy_helmet_01_01_01
)Morozov-SH Helmet Brushdrift (
rrs_specialist_heavy_helmet_02_01_01
)Morozov-SH Helmet Redshift (
rrs_specialist_heavy_helmet_03_01_01
)In that case, items in other sets should be included because they are also the variants of the same item, with a way to identify which set each items are from.
The text was updated successfully, but these errors were encountered: