Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a copy/pasted PR from kolton repo : kolton/d2bot-with-kolbot#1421
Added new property keyword
Skin
for pickit to filter rings, amulets, jewels and charms skin.Refactored getting the skin value of item with property
skinCode
in Unit prototype.Possible skin values are based on these :
Rings :
coral
orchain
smallblue
orsloop
bigblue
orbband
orangestone
ororangering
crown
oreturn
Amulets :
dot
orcross
sun
penta
orstar
Jewels :
pink
blue
orange
orpeach
green
red
white
Small charms :
brown
orfootball
bear
orbearfoot
orbearclaw
m
orcoin
Large charms :
paw
orpaper
horn
tower
orobelisk
Grand charms :
eye
dna
orlace
orspaghetti
dragon
ormonster
Usage :
You can specify the skin without item to be identified. This means that the skin property goes the same way as type, name or quality.
In your pickit :
If by mistake you specify a skin that does not exist for the item type, this item will NOT be kept.
For example
[type] == ring && [quality] == unique && [skin] == orange # [ItemAllSkills] > 0
It will NOT take any soj or bk because
orange
skin does not exist for rings.