Meleos

Hi, it's a weird bug that happens because after clicking on the first items your bot is "distracted" by your golem and/or spectres and tries to attack them. Then he goes back to selling items, and so on... Already reported this bug in discord, I hope it will be fixed soon.

The weapon switch bug happens to my bots too (with 69F). This happens rarely and I have no idea why (maybe lag+missclick ?).

In areas (Dried Lake...), "Max explore percent" is not working, the bot detects that the area is explored but keeps exploring instead of using TP. In maps "map clear percent" is working fine. Log: 2016-10-18 08:06:26 [info] -> Mission finished, considering current area as cleared. 2016-10-18 08:06:26 [info] -> Current complex map explored !! 2016-10-18 08:06:26 [info] -> Exploring to position(9501.218750, 16422.496094, -98.658447). State Priority: 2 2016-10-18 08:06:26 [info] -> Mission finished, considering current area as cleared. 2016-10-18 08:06:26 [info] -> Current complex map explored !! 2016-10-18 08:06:26 [info] -> Exploring to position(9564.886719, 16419.552734, -98.658447). State Priority: 2 2016-10-18 08:06:27 [info] -> Mission finished, considering current area as cleared. 2016-10-18 08:06:27 [info] -> Current complex map explored !! 2016-10-18 08:06:27 [info] -> Exploring to position(9654.636719, 16414.193359, -98.658447). State Priority: 2 2016-10-18 08:06:27 [info] -> Mission finished, considering current area as cleared. 2016-10-18 08:06:27 [info] -> Current complex map explored !! 2016-10-18 08:06:27 [info] -> Exploring to position(9718.980469, 16417.880859, -98.658447). State Priority: 2 2016-10-18 08:06:27 [info] -> Mission finished, considering current area as cleared. 2016-10-18 08:06:27 [info] -> Current complex map explored !! 2016-10-18 08:06:27 [info] -> Exploring to position(9781.958008, 16420.138672, -98.658447). State Priority: 2 2016-10-18 08:06:27 [info] -> Mission finished, considering current area as cleared. 2016-10-18 08:06:27 [info] -> Current complex map explored !! 2016-10-18 08:06:27 [info] -> Exploring to position(9850.888672, 16423.048828, -98.658447). State Priority: 2 Edit: It seems that this bug actually started with v64. I was using v63 until today, and it was working fine.

Sometimes the bot doesn't detect TP scrolls in inventory at the end of a map and exit to login instead of TPing. Same problem goes with ID scrolls, when trying to ID a map, the bot doesn't always detect the ID scrolls in stash/inventory and just stops. This problem seems to occur when experiencing a bit of lag, nevr happened before 0.60.

It's just part of the log to show the problem... It's looping like that for a few minutes (until I stopped the bot). Edit: Happened to another one of my bot who was stuck. Different loop : 2015-12-26 23:01:29 [info] -> Attacking monster using mouse_right key at distance : 5.886350 2015-12-26 23:01:29 [info] -> Current complex map explored !! 2015-12-26 23:01:29 [info] -> Restart state because no monster were killed for 120 s 2015-12-26 23:01:29 [info] -> Map finished!! 2015-12-26 23:01:29 [info] -> Attacking monster using mouse_right key at distance : 5.886350 2015-12-26 23:01:29 [info] -> Current complex map explored !! 2015-12-26 23:01:29 [info] -> Restart state because no monster were killed for 120 s 2015-12-26 23:01:29 [info] -> Map finished!! 2015-12-26 23:01:29 [info] -> Attacking monster using mouse_right key at distance : 5.886350 2015-12-26 23:01:29 [info] -> Current complex map explored !! 2015-12-26 23:01:29 [info] -> Restart state because no monster were killed for 120 s 2015-12-26 23:01:29 [info] -> Map finished!! 2015-12-26 23:01:29 [info] -> Attacking monster using mouse_right key at distance : 5.886350 2015-12-26 23:01:29 [info] -> Current complex map explored !! 2015-12-26 23:01:29 [info] -> Restart state because no monster were killed for 120 s 2015-12-26 23:01:29 [info] -> Map finished!!

I caught my bot today failing to pick an item (too many items on the floor) and the bot failed to leave the map after 120seconds (max idle time). There was some kind of loop. Here is a part of the log : 2015-12-26 15:42:22 [info] -> Going to pick item 2015-12-26 15:42:22 [info] -> Current complex map explored !! 2015-12-26 15:42:22 [info] -> Restart state because no monster were killed for 120 s 2015-12-26 15:42:22 [info] -> Map finished!! 2015-12-26 15:42:22 [info] -> Going to pick item 2015-12-26 15:42:22 [info] -> Current complex map explored !! 2015-12-26 15:42:22 [info] -> Restart state because no monster were killed for 120 s 2015-12-26 15:42:22 [info] -> Map finished!! 2015-12-26 15:42:23 [info] -> Going to pick item 2015-12-26 15:42:23 [info] -> Current complex map explored !! 2015-12-26 15:42:23 [info] -> Restart state because no monster were killed for 120 s 2015-12-26 15:42:23 [info] -> Map finished!! 2015-12-26 15:42:23 [info] -> Going to pick item 2015-12-26 15:42:23 [info] -> Current complex map explored !! 2015-12-26 15:42:23 [info] -> Restart state because no monster were killed for 120 s 2015-12-26 15:42:23 [info] -> Map finished!! 2015-12-26 15:42:24 [info] -> Going to pick item

Same problem here. Edit: Bot actually tries to level gems while there is no gem to level. Unchecking automatic gems leveling fixes the problem. Maybe the bot detects CWDT gems you don't want to level.

I can only recommend trading with Aeiz. He remained very cool while I was getting suspicious after a trade. Here is what happened: traded 70EX, didn't get the payment and there was no log of the transaction in his account, Phoned paypal who told me there was no trace of a pending transaction to my account. Only to find out on the community forum that some technical glitch is delaying some transactions for multiples hours. Got the money 5 hours later. Stupid paypal...

Could be but even if he isn't, it's stupid to discuss botting habits on the forum.

Thanks for the temporary fix.

I noticed too. Bot won't reroll nasty mods.

This bug was fixed in v50g ("bot focus Bearers of the Guardian first when facing an Animated Guardian.") but is back in v50i.

This bug started with v50e, so Alk probably already knows how to fix it. Happens with Divine Shrine too (bot try to kills immune monsters instead of taking the shrine).

Same problem here

Now in Standard league some monsters have Boodline mods. One of this mod is "Heralds of the Obelisk" ("Each corpse leaves an unkillable Obelisk that casts a random lightning spell. The obelisks disappear once the entire pack is killed"). The problem is that the bot tries to kill the unkillable Obelisks. Can you fix it or is there a way to configure the bot to go around it ? Same problem with Bearers of the Guardian mod (someone already posted about it) PS : If you want to reproduce the bugs with bloodline mods, the easiest way is to roll maps with "Magic monster packs each have a Bloodlines mod".

The bot stops every couple minutes for no reason, (when there is some lag maybe ?), and drinks all flasks in a few seconds, (even at full life), then keep going... It seems that "Dispel debuff" is bugged. It's configured as "no" and when I checked the log after the bot used all flasks in 2seconds I noticed a long list of "Dispel debuff".

No problem here since 16e, but it was very annoying when it was happenning to me. Maybe it's still happening whit some VPN's ?

same problem with stashing. It works fine for 5 of my bots, but the last one (who is the only one coming from domination) can't stash.

Still happening with 0.16b

With pickit activated and this : [Type] == "Empower" and [Type] == "Enhance" (and Min Gem quality > 1%), bot doesn't loot Empower or Enhance. It was working until POE 1.1 and it still works with Multistrike, CWDG, etc...

I switched back to 0.15m,and it still happens. So it's a problem with the server ?

Same here, no connection problems, but my bots loose elite every few hours since 0.16. Very annoying.

Don't spend too much on graphic card. I run 8 bots with a shitty R7 250 with 50% GPU load. You buy a R7 260x, you loose money not only when u buy it but with power consumption too.

The bot ony dance for 60sec (max idle time) when he is blocked in corners or stairs but not trying to pick an item. If he is trying to pick an item, "max idle time" doesn't kick in and the bot will continue until "max run time" kicks in.

The correct answer for me would be : between one item and exploring. A item drops, and the bot noticed it too late. Then he tries to go back pick up the item, but he tries to explore the map too -> running back and forth between the item and exploring.