enlitenkrokodil

I'm probably very dense, but is there an easy way to exclude a certain type of item from being picked up? For instance, let's say I do not want to pick up rare Vaal Regalias, but still have all my [Category] == "Chest" && [Rarity] == "Rare"...-checks apply to all other chests being picked up. Help would be appreciated.

Bot is trying to chance mirrored items.

Type-O. +1.

To me it looks more like the bot is not going back for chests, but to make sure it has explored 100% and meanwhile opening chests it was not in range of before. And yes, it kind of sucks.

I don't know what you are replying to. Obviously everyone has seething flasks set to 0 ms. I'm talking about leveling cases where the bot is having a slightly hard time but is still getting kills, for example level 50 and a bit undergeared in broken bridge vs the big beasts. I've watched the bot use flasks inefficiently and as a result chickening instead of recovering because of flasks being mistimed. However, when actually farming this is not an issue at all of course.

+1. Seeing the bot standing trying to kill mobs at a divination shrine makes me sad.

Everything is available for the right price. Everything.

Yes, there was a PoE patch, which usually means you need a new bot version (because of offset changes). https://exiled-bot.net/community/index.php/topic/2830-release-beta-version-v018/

Are you sure you are running 1) v0.18 of the bot 2) an OS newer than windows xp and 3) PoE in 800x600 resolution?

I've thought of that as well, was mostly thinking about it from another angle though: If a wisdom scroll, portal scroll, armourer's scrap, blacksmith's whetstone or any of the useless orbs can't be picked up at the very first try, then I would want them ignored.

1) I notice that if the bot doesn't find an item, it just loops trying to do the very same thing again. I would suggest adding a pickup_try_offset_x variable as well, since if an item is not found the first two times the chance that it is going to find it the third time is very slim. Also having the bot ignore the item after a certain amount of times. 2) If the bot is looking for a specific item to loot and hoover over another item that is going to be looted later, it should pick that item up. Very often when there are many drops, the bot will take a lot of time finding all the drops.

I tried this on one of my new bots. I don't see the point of Koam's Primacy (the culling strike is not that useful for a bot, I do see the use when running 6 man stuff though) so I just bought a higher dps rare axe for cheap. All in all, a sturdy and decent build, very rarely chickens in library/catacombs.

This, as well as the not so efficient use of time that this problem leads to, is the reason I stopped doing maps with my bots and just went back to lib/cat/docks.

All of these ended with the bot waiting for the idle time to run out before exiting. Let me know if this is at all helpful or if it's documented enough and I should just not bother to gather more of them. http://imgur.com/a/Aop1Q

It's not the same thing as corrupted memory, it is intended and if you increase the absurd hp setting in one of the config files it will work just fine.