gvd0x1

i've tried that before, i don't think there was a mod for that. Plus, with only 4 stash tabs u will run out of space in an hour.

version 75d, e etc standalone client Sometimes bot misclicks on alva dialogue option and invites her to hideout. Then bot gets confused by alva, because she does not have "sell items" option. Bot walks to her (because she is closest to the waypoint when she was invited) and then clicks away from her, since it can't sell items. Bot walks away from her a bit and then same process repeats ad infinitum. 2018-06-22 13:44:41 [info] -> Selling item... 2018-06-22 13:44:41 [info] -> Already reached destination from current path to follow. 2018-06-22 13:44:41 [info] -> Already reached destination from current path to follow. 2018-06-22 13:44:41 [info] -> Running state priority: 12 2018-06-22 13:44:41 [info] -> Moving to position(1711.956543, 1472.826050). State Priority: 12, Path index: 0 2018-06-22 13:44:42 [info] -> Already reached destination from current path to follow. 2018-06-22 13:44:42 [info] -> Running state priority: 12 2018-06-22 13:44:42 [info] -> Selling item... 2018-06-22 13:44:42 [info] -> Counldn't find sentence Sell Items in NPC Dialog ! 2018-06-22 13:44:43 [info] -> Already reached destination from current path to follow. 2018-06-22 13:44:43 [info] -> Running state priority: 12 2018-06-22 13:44:43 [info] -> Selling item... 2018-06-22 13:44:43 [info] -> Already reached destination from current path to follow. 2018-06-22 13:44:43 [info] -> Already reached destination from current path to follow. 2018-06-22 13:44:43 [info] -> Running state priority: 12 2018-06-22 13:44:43 [info] -> Moving to position(1711.956543, 1472.826050). State Priority: 12, Path index: 0 2018-06-22 13:44:43 [info] -> Already reached destination from current path to follow. 2018-06-22 13:44:43 [info] -> Running state priority: 12 2018-06-22 13:44:43 [info] -> Selling item... 2018-06-22 13:44:43 [info] -> Counldn't find sentence Sell Items in NPC Dialog !

you can't read notes? Added some anti-detection code that is currently slowing the bot. This will be tweaked on the next versions.

i run bot on 3 computers direct, no vm. All bots banned. I've got bots earlier going for lvl 97+, so I know what not to do behavior vise. After ban, started few new ones, even with few month old accounts all got banned as soon as they hit lvl 25(point where u can actually transfer currency etc)

not going to happen. If anything #1 priority for extra stuff would be to implement progression thru acts.

not sure how cookie is relevant. I bot on separate rigs and there's no sharing of any kind, each bot ran on its own pc which runs nothing else. So cookies mean nothing. It is behaviour of the bot that nails us down.

did you bot on your main??? Or on the same computer? If you don't mind sharing some details. I have dedicated separate rigs for botting, so my main is in no way connected to the bots.

It's not 'could', it is behaviour based. I have characters that are lvl 100 as well as others that got banned. The banned ones always ran some zone overleveled/played for too long. A simple test case is to run bot just few hours a day, none of these bots got banned. The ones that ran 12+ hours got all nailed. Especially on fresh accounts.

+1

Beta version v0.75c Poe Version: Vanilla (it affects all versions) Hideout on: Yes Zana in HO: Yes Map Enabled: Yes Selected Zone: any Smart Pickit: Yes Alva Valai, the path of exile 3.3 temple opener: bot sometimes clicks on her and sometimes manages to click on "view temple map" dialogue option which opens giant temple overlay and then bot gets stuck trying to click to move, but can't because it is clicking on that overlay.

it works. read and fiddle with settings

100% guaranteed not to work

Solved. Adding tier to upgrademap fixes the issue. Though ideally shaped arcade map != arcade map.

it sells shaped maps together with their unshaped/low tier. arcade arcade shaped arcade Only arcade should be selected for upgrading maps when selling in threes. Either tier is detected incorrectly or upgrade code path does not check tier.

This has been the problem for many bot versions, specific steps: 1) bot comes back from map with some maps, 1 of these maps would be a map that bot will run next 2)bot stashes stuff leaving 1 map in its inventory to be run next. Some of the stashed maps now end up being making a triplet of maps -> eligible to upgrade 3)bot detects there are maps to be upgraded in a stash, selects them and sells triplet + the single map it was about to run This constantly sells my red maps, since usually they are few. If needed I can even show a video of the behavior.

dont post this in bugs. This is not a bug and happens every week.

2017-10-27 01:10:11 [info] -> Total runtime: 435 minutes 2017-10-27 01:10:11 [info] -> Current complex map explored !! 2017-10-27 01:10:11 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:11 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:11 [info] -> Running state priority: 34 2017-10-27 01:10:11 [info] -> Creating tp... 2017-10-27 01:10:13 [info] -> Current complex map explored !! 2017-10-27 01:10:13 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:13 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:13 [info] -> Running state priority: 34 2017-10-27 01:10:13 [info] -> Creating tp... 2017-10-27 01:10:15 [info] -> Current complex map explored !! 2017-10-27 01:10:15 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:15 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:15 [info] -> Running state priority: 34 2017-10-27 01:10:15 [info] -> Creating tp... 2017-10-27 01:10:17 [info] -> Current complex map explored !! 2017-10-27 01:10:17 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:17 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:17 [info] -> Running state priority: 34 2017-10-27 01:10:17 [info] -> Creating tp... 2017-10-27 01:10:19 [info] -> Current complex map explored !! 2017-10-27 01:10:19 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:19 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:19 [info] -> Running state priority: 34 2017-10-27 01:10:19 [info] -> Creating tp... 2017-10-27 01:10:21 [info] -> Current complex map explored !! 2017-10-27 01:10:21 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:21 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:21 [info] -> Running state priority: 34 2017-10-27 01:10:21 [info] -> Creating tp... 2017-10-27 01:10:23 [info] -> Current complex map explored !! 2017-10-27 01:10:23 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:23 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:23 [info] -> Running state priority: 34 2017-10-27 01:10:23 [info] -> Creating tp... 2017-10-27 01:10:25 [info] -> Current complex map explored !! 2017-10-27 01:10:25 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:25 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:25 [info] -> Running state priority: 34 2017-10-27 01:10:25 [info] -> Creating tp... 2017-10-27 01:10:27 [info] -> Current complex map explored !! 2017-10-27 01:10:27 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:27 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:27 [info] -> Running state priority: 34 2017-10-27 01:10:27 [info] -> Creating tp... 2017-10-27 01:10:29 [info] -> Current complex map explored !! 2017-10-27 01:10:29 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:29 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:29 [info] -> Running state priority: 34 2017-10-27 01:10:29 [info] -> Creating tp... 2017-10-27 01:10:30 [info] -> Current complex map explored !! 2017-10-27 01:10:30 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:30 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:30 [info] -> Running state priority: 34 2017-10-27 01:10:30 [info] -> Creating tp... 2017-10-27 01:10:32 [info] -> Current complex map explored !! 2017-10-27 01:10:32 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:32 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:32 [info] -> Running state priority: 34 2017-10-27 01:10:32 [info] -> Creating tp... 2017-10-27 01:10:33 [info] -> Current complex map explored !! 2017-10-27 01:10:33 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:33 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:33 [info] -> Running state priority: 34 2017-10-27 01:10:33 [info] -> Creating tp... 2017-10-27 01:10:35 [info] -> Current complex map explored !! 2017-10-27 01:10:35 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:35 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:35 [info] -> Running state priority: 34 2017-10-27 01:10:35 [info] -> Creating tp... 2017-10-27 01:10:36 [info] -> Current complex map explored !! 2017-10-27 01:10:36 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:36 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:36 [info] -> Running state priority: 34 2017-10-27 01:10:36 [info] -> Creating tp... 2017-10-27 01:10:38 [info] -> Current complex map explored !! 2017-10-27 01:10:38 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:38 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:38 [info] -> Running state priority: 34 2017-10-27 01:10:38 [info] -> Creating tp... 2017-10-27 01:10:39 [info] -> Current complex map explored !! 2017-10-27 01:10:39 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:39 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:39 [info] -> Running state priority: 34 2017-10-27 01:10:39 [info] -> Creating tp... 2017-10-27 01:10:41 [info] -> Current complex map explored !! 2017-10-27 01:10:41 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:41 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:41 [info] -> Running state priority: 34 2017-10-27 01:10:41 [info] -> Creating tp... 2017-10-27 01:10:43 [info] -> Current complex map explored !! 2017-10-27 01:10:43 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:43 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:43 [info] -> Running state priority: 34 2017-10-27 01:10:43 [info] -> Creating tp... 2017-10-27 01:10:44 [info] -> Current complex map explored !! 2017-10-27 01:10:44 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:44 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:44 [info] -> Running state priority: 34 2017-10-27 01:10:44 [info] -> Creating tp... 2017-10-27 01:10:46 [info] -> Current complex map explored !! 2017-10-27 01:10:46 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:46 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:46 [info] -> Running state priority: 34 2017-10-27 01:10:46 [info] -> Creating tp... 2017-10-27 01:10:47 [info] -> Current complex map explored !! 2017-10-27 01:10:47 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:47 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:47 [info] -> Running state priority: 34 2017-10-27 01:10:47 [info] -> Creating tp... 2017-10-27 01:10:49 [info] -> Current complex map explored !! 2017-10-27 01:10:49 [info] -> Bot trying to take tp for 100000 milliseconds, something went wrong.. Exiting to login (you can edit this timeout value in system.ini: 'tp_creation_timeout'). 2017-10-27 01:10:49 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:49 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:49 [info] -> Running state priority: 34 2017-10-27 01:10:49 [info] -> Chickened via method TCP DISCONNECT! 2017-10-27 01:10:54 [info] -> Current complex map explored !! 2017-10-27 01:10:54 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:54 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:54 [info] -> Running state priority: 34 2017-10-27 01:10:54 [info] -> Creating tp... 2017-10-27 01:10:55 [info] -> Current complex map explored !! 2017-10-27 01:10:55 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:55 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:55 [info] -> Running state priority: 34 2017-10-27 01:10:55 [info] -> Creating tp... 2017-10-27 01:10:57 [info] -> Current complex map explored !! 2017-10-27 01:10:57 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:57 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:57 [info] -> Running state priority: 34 2017-10-27 01:10:57 [info] -> Creating tp... 2017-10-27 01:10:59 [info] -> Current complex map explored !! 2017-10-27 01:10:59 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:10:59 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:10:59 [info] -> Running state priority: 34 2017-10-27 01:10:59 [info] -> Creating tp... 2017-10-27 01:11:00 [info] -> Current complex map explored !! 2017-10-27 01:11:00 [info] -> Restart state because no monster were killed for 47 s 2017-10-27 01:11:00 [info] -> Restart because run timer exceeded 1000 seconds 2017-10-27 01:11:00 [info] -> Running state priority: 34 2017-10-27 01:11:00 [info] -> Creating tp... 2017-10-27 01:11:06 [info] -> Stopped to read entity list before the end because number of tries is too high (1500). 2017-10-27 01:11:06 [info] -> Stopped to read entity list before the end because number of tries is too high (1501). 2017-10-27 01:11:06 [info] -> Stopped to read entity list before the end because number of tries is too high (1502). 2017-10-27 01:11:06 [info] -> Stopped to read entity list before the end because number of tries is too high (1503). 2017-10-27 01:11:06 [info] -> Stopped to read entity list before the end because number of tries is too high (1504). 2017-10-27 01:11:07 [info] -> Stopped to read entity list before the end because number of tries is too high (1500). 2017-10-27 01:11:07 [info] -> Stopped to read entity list before the end because number of tries is too high (1501). 2017-10-27 01:11:07 [info] -> Stopped to read entity list before the end because number of tries is too high (1502).

Earlier version I used 71h, used to quit the game if bot stepped inside the map trial. Switched to version 72 and found my bot in map trial trying to portal out(which is disallowed in map trial), so the bot kept trying to open portal for hours.

seems to be working in 69c. Thanks!

can't do multilevel areas i.e flooded depths, chamber of sins level 2 etc Any time it enters a 2nd area of the 1st dungeon, it opens portal and bails and keeps looping like that. I modified in config the setting that says 'use portal for multi level area', but that had no effect. Anyone is aware of it? I don't want to be carrying my bots to grab quest items from those areas. It used to work in 0.67 just fine, 0.68 and 0.69 have the bug(other people mentioned same issue in discord chat as well). Thanks for the amazing bot!

duh, should have used <0. Thanks a lot for the tip.

it works fine for me, bot doesn't run any reflect map when i comment out appropriate sections.

poe has a bunch of new map affixes and there's this one map_players_block_chance_+% that is unacceptable to be on map while botting hardcore. This didn't work [map_players_block_chance_%] >= "1" && [Rarity] == "Magic" # [ignoreMap] == "true" reroll section also didn't do anything. Is there a bot change required to be aware of this new suffix? thanks

yeah, never do it on main ip. I've got a ton of bots banned even if i was watching them running(especially true while doing acts, mapping is safer). Certain patterns etc could trigger a ban.

don't do it on your main ip. Even if the bot doesn't enter into some infinite loop, you can still be flagged and banned.