Search the Community

Hey guys, i noticed some weird bug (i guess) regarding a combination of the pickit operators "&&" and "||". If u want an item to have the mods A and B or C you have to write it like this: # (B || C) && A that works fine. but if you use: # A && (B || C) it wont work as intended and the bot will stash any item with one of the mods A or B or B Example: I had the line: [Category] == "Gloves" && [Rarity] == "Rare" # [base_maximum_life] >= "50" && ([attack_speed_+%] >= "10" || [attack_minimum_added_physical_damage] >= "5") and the bot stashed gloves with 11% IAS but without any life I tryed [Category] == "Gloves" && [Rarity] == "Rare" # ([attack_speed_+%] >= "10" || [attack_minimum_added_physical_damage] >= "5") && [base_maximum_life] >= "50" and it worked fine. Any ideas or is is really just a bug?

Hi. What I am about to say was already suggested few times before (1, 2, 3, 4), but it probably was not said clear enough. Current state of pickit programming: "know what you want to keep, sell or not even pick up the rest". This is a great priority, indeed pickit programmer more often wants something specific. But it have it's negative sides too. Look at how unique handling ended up, ugly huge pickit files with rarity=unique#sell=true, followed by hundreds of lines type=name&rarity=unique//keep this item X100500. And a note "you may miss some of new uniques, lol". While current pickit system works well for most cases, it does not in case of uniques. Everyone wants to be safe they will not miss something extremely good. And it should require no programming. What I want implemented is !important flag or something like this. So code rarity=unique //keep all uniques type=name&rarity=unique#sell=true !important //this would override the Keep rule, and still sell this item. This would allow to build lists of unwanted uniques. This would be much safer solution than what current state of things is.

I see a lot of pickit files with wrong syntax Ex: [Category] == "Chest" && [Rarity] == "Rare" && [base_maximum_life] >= "60" && [base_cold_damage_resistance_%] >= "25" && [base_fire_damage_resistance_%] >= "25" # [StashItem] == "true" Should be: [Category] == "Chest" && [Rarity] == "Rare" # [base_maximum_life] >= "60" && [base_cold_damage_resistance_%] >= "25" && [base_fire_damage_resistance_%] >= "25" Smart Pickit Syntax. Ok explanation: We have this on default.ipd file // You'll find the mods list in the ModsList.txt file, in the main bot folder, remember to only use expressions from the right (ie. local_minimum_added_physical_damage, base_maximum_energy_shield, ...). // Expressions to the left are only here to help you choosing the right ones ... // Syntax is: [Key] operator "Value" ... // # is used to separate mods checked after item identification. If an item matchs mods before the # and doesn't match the ones after, it will be sold to vendor. # If you put that symbol, your item will be identified. Everything in left of # is to tell the bot which item will pick up Everything in the right of # is to tell the bot which modifiers it will check in that item, if they match that item will be stashed Ex 1. You want to take belts and stash it unids [Category] == "Belt" && [Rarity] == "Rare" Bot will take any rare belt. No # so item it is left unidentified. Ex 2. You want any belt with life > 40 and cold and fire res > 20 [Category] == "Belt" && [Rarity] == "Rare" # [base_maximum_life] >= "40" && [base_cold_damage_resistance_%] >= "20" && [base_fire_damage_resistance_%] >= "20" [Category] == "Belt" && [Rarity] == "Rare" --> Bot will pick up any rare belt. Left side of # # --> Item will be identified. [base_maximum_life] >= "40" && [base_cold_damage_resistance_%] >= "20" && [base_fire_damage_resistance_%] >= "20" --> Bot will check all mods if they match will be stashed. Right side of # Ok that was the basic info. ****************************************************************************************************** A little more info: Expressions to the left, I am going to call those KEYS Expressions to the right, I am going to call those MODS KEYS: Everything in left of # is to tell the bot which item will pick up Syntax: [Key] operator "Value" Possible values (all of them): [Type] operator "xxx" --> operator values: ( == ), "xxx" values: Any name from file ItemNameList.txt [itemLevel] operator "xx" --> operator values: ( ==, <=, >=, <, > ), "xx" values: Numeric [Armor] operator "xx" --> operator values: ( ==, <=, >=, <, > ), "xx" values: Numeric ** [Evasion] operator "xx" --> operator values: ( ==, <=, >=, <, > ), "xx" values: Numeric ** [Energy Shield] operator "xx" --> operator values: ( ==, <=, >=, <, > ), "xx" values: Numeric ** [Rarity] operator "xx" --> operator values: ( ==, != ), "xx" values: "Normal", "Magic", "Rare", "Unique" [Quality] operator "xx" --> operator values: ( ==, <=, >=, <, > ), "xx" Numeric, Item Quality, (1-20) [sockets] operator "xx" --> operator values: ( ==, <=, >=, <, > ), "xx" Numeric, Item Sockets, (1-6) [Linked] operator "xx" --> operator values: ( ==, <=, >=, <, > ), "xx" Numeric, Number of linked sockets (1-6) ???? [Category] operator "xx" --> operator values: ( ==, != ), "xx" possible values: "Chest", "Shield", "Helm", "Ring", "Amulet", "Flask", "Weapon", "Gloves", "Boots", "Belt", "Map" All those keys will be before # ** Only apply for Helmets, Body Armour, Gloves, Boots and Shields, since poe has fixed base values, those keys are not very useful (imo) Ex. Saintly Chainmail --> Armor:286, Energy Shield:98: Evasion:0 All Saintly Chainmail have those values Astral Plate --> Armor:507, Energy Shield:0: Evasion:0 All Astral Plate have those values MODS: Everything in the right of # is to tell the bot which modifiers it will check in that item, if they match that item will be stashed Syntax: [Mod] operator "Value" Possible values: [xxx] operator "nnn" xxx: any value from file ModsList.txt (use the expresion on the left, before -> ). ** operator values: ( ==, <=, >=, <, > ) "nnn": Numeric ** You can use a mod by his index (if it is not in the ModsList.txt file) this way [modindex] == "value", ie. [587] == "30". MORE: * Press F7 to dump inventory and find mod indexes. First press pause (F12). * Operators && and || are available, parenthesis are working. This can be used only outside condition not inside. Ex 1. No Ok [Category] == "Chest" && [Rarity] == ("Magic" || "Rare") # [stashItem] == "true" && [base_maximum_life] >= "60" && [base_cold_damage_resistance_%] >= "25" && [base_fire_damage_resistance_%] >= "25" Ex 2. Ok [Category] == "Chest" && ([Rarity] == "Magic" || [Rarity] == "Rare") # [stashItem] == "true" && [base_maximum_life] >= "60" && [base_cold_damage_resistance_%] >= "25" && [base_fire_damage_resistance_%] >= "25" * Flags that can be used are : [stashItem] == "true", [sellItem] == "true", [sellUnid] == "true" and can not be false * The bot evaluate all pickit lines and Stash have priority over Sell. Remember Exiledbot still beta, there will be bugs. Gracias.