Search results

Fix is already scheduled for the next version.

Most likely you are trying to use some old plugins from pre 3.0 era (August 2017)

Will be fixed in next version.

This is a first version of incursion plugin, meant to provide basic league mechanic functionality. Ability to enter a bossroom in the temple will be added in future versions.

Sextant and Zana mod support has been added in alpha version of the bot. You can check it out now or wait till Incursion league. p.s. currently bot cannot get your "max sextants" value from the game, do not set maps for sextanting more than your available sextanting slots.

@Invested This is intended. @uupiits It will be added.

Lavianga's Spirit is treated as an ordinary mana flask. It will be used according to your MP% setting.

Ordinary PoE game crash. Not bot related.

It usually means that you are running some "overlay" software alongside the bot. See the full list here.

Your ranges are way too huge. Set both to 70.

- Setting openPortals to false might be the best solution for you, if you do not want to go much into coding. But, generally, I'd suggest you to make a better build, if your character dies from mobs while opening portals (1-2 sec) thats not ok. - You cannot ignore bossroom in Burial Chambers...

Bot opens portals for a reason. If you die/disconnect/chicken bot will be lost in a multilevel map. It will re-explore it from the start, possibly in a wrong direction. If you wanna risk and change it in code, thats your choice.

Your exploration percent is zero.

It usually means that you manually gave the bandit amulets to Eramir, but did not take the apex. Or you interrupted the bot while it was taking the apex. Anyway, now you must finish the bandit quest manually.

Ensure that: - Movement skill (footsteps icon) is bound to non-mouse button. - Networking mode is Predictive.

This looks like a normal stuck detection case when bot cannot get to the target monster. You should see the reason by yourself, in game.

You choose combat routine for your character build, not for mapping or questing. Before trying to change anything you must first ensure that problem comes from the routine. Download a fresh bot copy, don't use any 3rd party code, check if you still have problems with stuck detection.

Stuck detection logs you out if you stand in one place for a long time. You should never have problems with that, unless you are using some very slow build with negative movement speed. In your case, this is most likely caused by the beast capturing plugin you are using.

This is a random error that can happen any time. It usually means that target's name label overlaps with some other object (like chest or item on the ground). Not much we can do to fix that, its just how this game works.

It usually means that you are running some "overlay" software alongside the bot. See the full list here.