myreal

before the auras rework i could have curse auras, now an aura lie flammability is not listed and is not working anymore we need curses that are converted in auras via support gem to be supported and work

i believe this will be relay useful, i would relay like a death log, i went away from computer with 0 deaths, came back 30 min later and had 7 deaths, what how, when , any log and info on deaths from simple map name to more detailed info will be relay helpful (i'm runing normal maps no mods, and i skip arenas, and i have him chicken on all boss names) instead of me guessing what maps are bad for my build, better have a log and see on map x died 6 times ...

anything about this?

poe 3.0.1e bot 0.72 problem reapeared

same issue dx9 enabled normal game client and bot just walks north east, stays 2 sec , walks again north east again stays 2 sec...

anyone can confirm the problem happens for them also ?

before entering an arena/boss i always drop a portal just in case i die i don't have to run back the whole map will be a good idea if bot will do same just in case.

i agree with configurable map level, rarity will be very nice

so i have set him on doing normal maps no mods, and found he died couple of times but i have no idea on what map. it should not be hard to do every time it dies to save in a file the map and the mods/difficulty. by luck i found that bot+hero combo just cannot deal with a certain boss mechanic and i had to ignore that map. (would have been nice to see dead mapx, dead mapx, dead mapx in a log) i'm using the bot to farm XP so it's important not to die. or if i die to know in what circumstances. extra bonus it says on summary window i died 400+ times i doubt that is the case. but hey i'll be curious to know on what map/mods/difficulty i was when that happened.

whenever the character dies, log in a file the map name and the map mods (or difficulty) will be interesting to look on what maps or mods i usually die.

anyone any idea how to do [OneSocketEachColourUnique] or [local_one_socket_each_colour_only] or any way to pick only the chromatics that take max 4 spaces in inventory ?

ok fixed the lines and again once i uncomented all chance lines, it started experiencing same problem if you have time can you give it a try so at least we know if happens only for me or for multiple people uncomment all chance lines from the chance section, and let it do 1 map it should experience the problem quite often

i have a 4k monitor (not sure if that is the problem) and i use in windows 10 scaling of 200-250 the interface of poe bot all looks good except the save and start bot buttons, they overlay on top of the bot settings the bot window size needs to be a bit taller, so the buttons fit ok and not be on top of other settings

i looked more i seen things like [Type] == "Assassin's Garb" && [Rarity] == "Rare" # [Computed Evasion] >= "1800" && [base_maximum_life] >= "100" [StashItem] == "true" looks like && is missing in front of [statshItem] there are 20+ lines like this could this cause problems ?

i get syntax error , how do you sell chromatics using pickit, or the checkbox will pick and sell ? [Type] == "Nailed Fist" && [Linked] >= "3" && [local_one_socket_each_colour_only] # [SellItem] == "true"

i have plenty of chance orbs , why not use them to get a chance at an unique. i also tried to limit the number of uncommented rows trying to isolate the row with the issue but no matter what i uncomment same result, mayeb something broken with the ChanceItem functionality. anyway let me know if at least you can reporduce it. so uncomment all that, and let the bot do his ting and watch it, that sometimes will get into this state.

any idea which line from this section looks bad ? just uncoment all lines and give it a try you will see the issue

ok i located it, if i uncoment this section it starts acting strange, i comment it and it works fine ///////////////////////////////////////////////////////////////////////////////////// // // // C H A N C I N G // // // ///////////////////////////////////////////////////////////////////////////////////// // [Type] == "Onyx Amulet" # [ChanceItem] == "true" && [Rarity] == "Normal" // Astramentis preferably // [Type] == "Slaughter Knife" # [ChanceItem] == "true" && [Rarity] == "Normal" // Bino's // [Type] == "Sharkskin Booots" # [ChanceItem] == "true" && [Rarity] == "Normal" // Blood Dance (Vaal Roll +1 Frenzy) // [Type] == "Varnished Coat" # [ChanceItem] == "true" && [Rarity] == "Normal" // Carcass Jack // [Type] == "Penetrating Arrow Quiver" # [ChanceItem] == "true" && [Rarity] == "Normal" // Drillneck // [Type] == "Deicide Mask" # [ChanceItem] == "true" && [Rarity] == "Normal" // Heretic's Veil // [Type] == "Glorious Plate" # [ChanceItem] == "true" && [Rarity] == "Normal" // Kaom's Heart // [Type] == "Desert Brigandine" # [ChanceItem] == "true" && [Rarity] == "Normal" // Lightning Coil // [Type] == "Deerskin Gloves" # [ChanceItem] == "true" && [Rarity] == "Normal" // Maligaro's Virtuosity // [Type] == "Gavel" # [ChanceItem] == "true" && [Rarity] == "Normal" // Mjolnir // [Type] == "Judgement Staff" # [ChanceItem] == "true" && [Rarity] == "Normal" // Pledge of Hands // [Type] == "Titanium Spirit Shield" # [ChanceItem] == "true" && [Rarity] == "Normal" // Rathpith // [Type] == "Ursine Pelt" # [ChanceItem] == "true" && [Rarity] == "Normal" // Rat's Nest // [Type] == "Granite Flask" # [ChanceItem] == "true" && [Rarity] == "Normal" // Rumi's Concoction // [Type] == "Occultist's Vestment" # [ChanceItem] == "true" && [Rarity] == "Normal" // Shavronne's Wrappings // [Type] == "Sorcerer Boots" # [ChanceItem] == "true" && [Rarity] == "Normal" // Skyforth // [Type] == "Siege Axe" # [ChanceItem] == "true" && [Rarity] == "Normal" // Soul Taker // [Type] == "Gold Ring" # [ChanceItem] == "true" && [Rarity] == "Normal" // Ventor's Gamble or Andvarius // [Type] == "Prophecy Wand" # [ChanceItem] == "true" && [Rarity] == "Normal" // Void Battery // [Type] == "Conjurer Gloves" # [ChanceItem] == "true" && [Rarity] == "Normal" // Voidbringer (Vaal Roll +1 Gems) // [Type] == "Spine Bow" # [ChanceItem] == "true" && [Rarity] == "Normal" // Voltaxic Rift // [Type] == "Prophecy Wand" # [ChanceItem] == "true" && [Rarity] == "Normal" // Void Battery

hmm all i did was to uncomment some lines and the only place i did something by myself was here [Type] == "Harbinger Bow" && [Rarity] == "Normal" && [ItemLevel] >= "83" && [local_critical_strike_chance_+%] >= "49" # [StashItem] == "true" [Type] == "Diamond Ring" && [Rarity] == "Normal" && [ItemLevel] >= "83" # [StashItem] == "true" [Type] == "Rustic Sash" && [Rarity] == "Normal" && [ItemLevel] >= "83" # [StashItem] == "true" is there any way to know on what line it fails or what is the error maybe something in the log regarding parsing fail or conflicting rules ...

hi, version 70c i have an issue where bot just sits there, and mouse moves few pixels up and up and up (even exits from the poe window area and wonders on desktop) for couple of good seconds, and then it starts moving properley then again gets in one of this pahases were just sits there and mouse start jumping few pixels up and up (and i believ he preses also ALT key because teh items from gound are showing each tiem mouse jumps few pixels up) i have pickit enabled and i have use ALT to loot enabled also 2017-04-15 20:08:33 [info] -> Picking item 2017-04-15 20:08:33 [info] -> Running state priority: 24 2017-04-15 20:08:34 [info] -> Running state priority: 24 2017-04-15 20:08:34 [info] -> Running state priority: 24 2017-04-15 20:08:35 [info] -> Running state priority: 24 2017-04-15 20:08:35 [info] -> Running state priority: 24 2017-04-15 20:08:36 [info] -> Running state priority: 24 2017-04-15 20:08:37 [info] -> Running state priority: 24 2017-04-15 20:08:37 [info] -> Running state priority: 24 2017-04-15 20:08:38 [info] -> Running state priority: 24 2017-04-15 20:08:39 [info] -> Running state priority: 24 2017-04-15 20:09:02 [info] -> PickItem timeout, item X: 509, item Y: 542, item is going to be skipped 2017-04-15 20:09:02 [info] -> Running state priority: 24 2017-04-15 20:09:03 [info] -> Running state priority: 24 2017-04-15 20:09:03 [info] -> Running state priority: 24 2017-04-15 20:09:04 [info] -> Running state priority: 24 2017-04-15 20:09:05 [info] -> Running state priority: 24 2017-04-15 20:09:05 [info] -> Running state priority: 24 2017-04-15 20:09:06 [info] -> Running state priority: 24 2017-04-15 20:09:06 [info] -> Running state priority: 24 2017-04-15 20:09:07 [info] -> Running state priority: 24 2017-04-15 20:09:08 [info] -> Running state priority: 24 2017-04-15 20:09:08 [info] -> Running state priority: 24 2017-04-15 20:09:09 [info] -> Running state priority: 24 2017-04-15 20:09:10 [info] -> Running state priority: 24 2017-04-15 20:09:10 [info] -> Running state priority: 24 2017-04-15 20:09:11 [info] -> Running state priority: 24 2017-04-15 20:09:11 [info] -> Running state priority: 24 2017-04-15 20:09:12 [info] -> Running state priority: 24 2017-04-15 20:09:13 [info] -> Running state priority: 24 2017-04-15 20:09:13 [info] -> Running state priority: 24 2017-04-15 20:09:14 [info] -> Running state priority: 24 2017-04-15 20:09:15 [info] -> Running state priority: 24 2017-04-15 20:09:15 [info] -> Running state priority: 24 2017-04-15 20:09:16 [info] -> Running state priority: 24 2017-04-15 20:09:16 [info] -> Running state priority: 24 2017-04-15 20:09:17 [info] -> Running state priority: 24 2017-04-15 20:09:18 [info] -> Running state priority: 24 2017-04-15 20:09:18 [info] -> Running state priority: 24 2017-04-15 20:09:19 [info] -> Running state priority: 24 2017-04-15 20:09:20 [info] -> Running state priority: 24 2017-04-15 20:09:20 [info] -> Picking item 2017-04-15 20:09:20 [info] -> Running state priority: 24 2017-04-15 20:09:21 [info] -> Running state priority: 24 2017-04-15 20:09:21 [info] -> Moving to position(11374.927734, 5929.418457). State Priority: 24, Path index: 0 2017-04-15 20:09:21 [info] -> Running state priority: 24 2017-04-15 20:09:21 [info] -> Moving to position(11374.927734, 5929.418457). State Priority: 24, Path index: 0 2017-04-15 20:09:21 [info] -> Running state priority: 24 2017-04-15 20:09:21 [info] -> Going to pick item 2017-04-15 20:09:21 [info] -> Running state priority: 24 2017-04-15 20:09:21 [info] -> Going to pick item 2017-04-15 20:09:21 [info] -> Running state priority: 24 2017-04-15 20:09:22 [info] -> Running state priority: 24 2017-04-15 20:09:22 [info] -> Running state priority: 24 2017-04-15 20:09:23 [info] -> Running state priority: 24 2017-04-15 20:09:24 [info] -> Running state priority: 24 2017-04-15 20:09:24 [info] -> Running state priority: 24 2017-04-15 20:09:25 [info] -> Running state priority: 24 2017-04-15 20:09:26 [info] -> Running state priority: 24 2017-04-15 20:09:26 [info] -> Running state priority: 24 2017-04-15 20:09:27 [info] -> Running state priority: 24 2017-04-15 20:09:27 [info] -> Running state priority: 24 2017-04-15 20:09:28 [info] -> Running state priority: 24 2017-04-15 20:09:29 [info] -> Running state priority: 24 2017-04-15 20:09:29 [info] -> Running state priority: 24 2017-04-15 20:09:30 [info] -> Running state priority: 24 2017-04-15 20:09:31 [info] -> Running state priority: 24 2017-04-15 20:09:31 [info] -> Running state priority: 24 2017-04-15 20:09:32 [info] -> Running state priority: 24 2017-04-15 20:09:33 [info] -> Running state priority: 24 2017-04-15 20:09:33 [info] -> Running state priority: 24 2017-04-15 20:09:34 [info] -> Running state priority: 24 2017-04-15 20:09:34 [info] -> Running state priority: 24 2017-04-15 20:09:35 [info] -> Running state priority: 24 2017-04-15 20:09:36 [info] -> Running state priority: 24 2017-04-15 20:09:36 [info] -> Running state priority: 24 2017-04-15 20:09:37 [info] -> Running state priority: 24 2017-04-15 20:09:38 [info] -> Running state priority: 24 2017-04-15 20:09:38 [info] -> Running state priority: 24 2017-04-15 20:09:39 [info] -> Running state priority: 24 2017-04-15 20:09:39 [info] -> Running state priority: 24 2017-04-15 20:09:40 [info] -> Running state priority: 24 2017-04-15 20:09:41 [info] -> Running state priority: 24 2017-04-15 20:09:41 [info] -> Running state priority: 24 2017-04-15 20:09:42 [info] -> Running state priority: 24 2017-04-15 20:09:43 [info] -> Running state priority: 24 2017-04-15 20:09:43 [info] -> Running state priority: 24 2017-04-15 20:09:44 [info] -> Running state priority: 24 2017-04-15 20:09:44 [info] -> Running state priority: 24 2017-04-15 20:09:45 [info] -> Running state priority: 24 2017-04-15 20:09:46 [info] -> Running state priority: 24 2017-04-15 20:09:46 [info] -> PickItem timeout, item X: 512, item Y: 562, item is going to be skipped 2017-04-15 20:09:46 [info] -> Running state priority: 1

same here version 69f any solution to it ?

bot sometimes picks by mistake items they are usually grey/blue items instead of stashing could he vendor them or have a sellit tab similar with pickit, where we could configure vendoring options

did you found a solution to this ? or an workaround ?

2017-03-13 16:47:40 [info] -> Area switched from none to The Sarn Encampment 2017-03-13 16:47:40 [info] -> Areanav stage 1 2017-03-13 16:47:40 [info] -> Areanav stage 2 2017-03-13 16:47:40 [info] -> Areanav stage 3 2017-03-13 16:47:40 [info] -> Areanav stage 5 2017-03-13 16:47:40 [info] -> Areanav stage 6 2017-03-13 16:47:40 [info] -> Areanav stage 7 2017-03-13 16:47:40 [info] -> Areanav stage 8 2017-03-13 16:47:40 [info] -> Areanav stage 10 2017-03-13 16:47:40 [info] -> Trying to go to stash recorded position : 100 310 !! 2017-03-13 16:47:40 [info] -> Running state priority: 8

are there any settings saved in registry or somewhere that they get saved between versions.? anyway created a new setup fresh os poe and bot version 69c started it and it worked like a charm for 3-4 hours then i believe it crashed anyway i restarted it now it sets the resolution by itself to the game to some custom value and of course is not able to click on stuff properly. unziped version 69d started again everything and same stuff it resizes poe to a custom (non standard) resolution is any way 69c and 69d are shearing settings? (they are unziped in different folder.)