gvd0x1 4 Report post Posted February 21, 2016 why is 2nd # usefull? [Type] == "Harbinger Bow" && [Rarity] == "Magic" # [local_physical_damage_+%] >= "135" # [stashItem] == "true" Used to be just ANDed with &&. Why this change? Quote Share this post Link to post Share on other sites
jps42 138 Report post Posted February 21, 2016 (edited) No clue, was carry-over from previous pickit, I think the second # should just be a &&. I think the syntax still works. Edited February 21, 2016 by jps42 Quote Share this post Link to post Share on other sites
alkpone 1000000 Report post Posted February 22, 2016 This is garbage, no one should ever use multiple #. The # should solely be used to separate conditions that are checked after itentifying the item. Already updated the pickit to : // [Type] == "Harbinger Bow" && [Rarity] == "Magic" # [local_maximum_added_physical_damage] >= "49" && [StashItem] == "true" // Tempered&Flaring // [Type] == "Harbinger Bow" && [Rarity] == "Magic" # [local_physical_damage_+%] >= "135" && [StashItem] == "true" // Cruel&Tyrannical&Merciless // [Type] == "Maraketh Bow" && [Rarity] == "Magic" # ([local_socketed_gem_level_+] == "1" || [local_socketed_bow_gem_level_+] == "2") && [StashItem] == "true" // +3 gem psn arrow craft Quote Share this post Link to post Share on other sites