Auto Simulacrum Farming Bot (Updated)

[Sikaka]

Different github, different post as I can't edit the original one's title.

This is a re-write of my simulacrum farming plugin for ExileAPI
This significantly improves the reliability of the bot (less issues of getting stuck) but more importantly makes it much more configurable to use on other builds.

You can now select skill usage logic, targeting types, etc. This includes support for targeting mercenaries with link skills.
It also includes support to auto apply incubators to improve profit/hour.

GITHUB LINK: GitHub - Sikaka/AutoPOE
COMPILED FILES: AutoPOE/Compiled/AutoPOE at main . Sikaka/AutoPOE . GitHub



IMPORTANT SETUP STEPS

Take the compiled plugin (AutoPOE folder) and place it in your Plugins/Compiled folder - or use the source version, I'm not your real dad.

When you first load the plugin, it needs you to configure your skills. Please do this before you complain things don't work.
Select the key binding for each skill, the name of the skill assigned to that binding (so the bot can read if the skill is on cooldown or not), a targeting type and a minimum delay between usages.


Ensure 1 skill is the movement key with very minimal delay and 'is movement key' is checked.
Ensure you have a second movement skill such as frostblink/flamedash to help get unstuck. This also needs to be tagged as 'is movement key'.

MOVEMENT KEYS SHOULD BE SET AS 'DO NOT USE' unless they are also intended to attack enemies with!

For skills that have low/no cooldown but add buffs to your character, enter the buff name and it won't re-cast until that buff is removed. Prime example being righteous_fire


Make sure your hideout isn't too cluttered, I've seen it where a misclick would click on a npc causing things to get stuck - minor but a nice tip to know.


Bot is designed to work in full screen 1920x1080, there's some hardcoded coords that means it will not work in other resolutions.





Same as before, if there's issues or feature requests - let me know. Feel free to submit change requests directly to git as well if you prefer.

[kaminage12345]

Good job!! thank you

I would like the ability to switch stash pages when Stash is full on a sub-account that does not have a Quad Stash.

--------

The incubator works great, but sometimes the tool stops after removing the item it is equipped with.
Is it because of the fast clicking and cursor movement?

There is a situation once in 10Maps where the simulacrum is set on the map device and cannot be activated and stops.
The cursor was at Active, but I was not able to click on it.

I tested 60Map on two computers and these were the only two problems.
Stack Causes

[Sikaka]

Good job!! thank you

I would like the ability to switch stash pages when Stash is full on a sub-account that does not have a Quad Stash.

--------

The incubator works great, but sometimes the tool stops after removing the item it is equipped with.
Is it because of the fast clicking and cursor movement?

There is a situation once in 10Maps where the simulacrum is set on the map device and cannot be activated and stops.
The cursor was at Active, but I was not able to click on it.

I tested 60Map on two computers and these were the only two problems.
Stack Causes

Thanks, glad to hear some feedback on this version!

Incubators are a bit buggy (which is why they are marked in the bot as being in beta).
Basically I'm waiting for the cursor to change to make sure we're giving enough delay. It works in all my tests but then randomly will screw up and try to grab your equipped items.
I added the emergency stop to (hopefully) not have it start dropping people's gear on the ground.

I might take another stab at the incubator logic - or maybe someone will want to do some testing and propose a fix.





Multi stash tab support is a good idea. I'll have to think a bit about the best way to handle it.
I'll have to confirm how easy it is to detect a stash being full. Counting items doesn't work as there's size of gear. I'll have to confirm that I can detect the size of a stash tab, calculate out slots occupied, etc...

From a usability perspective, I'm guessing you'd want the bot to list off what stash tabs you have and you can select which ones to use as dump tabs?


For further improvements, I'll probably add another skill usage type for 'use on buff active'. I think something like that could be used to automate detonating mines cause I think that's the main skill usage type not currently supported.



Minor Update

The bot now has a option to automatically revive mercenaries. If merc shows as dead, it will click the revive button.
If the revive fails (no gold, misclick, etc) it will try again after 2 minutes.


Also testing a minor pathfinding change for starting next round. Should avoid some potential stuck issues. If this shows improvements, I'll take a look at the same for things like opening new map.

[miahjere18]

Great work!

I was working on trying to update your previous code not knowing you were also updating at the same time.

There seems to be an issue with picking up loot on the 15th wave. sometimes if the character is closer to the portal than the loot, it just ignores the loot and moves on.

2 very minor things:

1. Could there be a setting so the character moves less often (for chieftain node -20% fire res while standing still)
2. I tried using a smite character and it's spamming smite despite not having any enemies in sight. It slows down the bot quite a lot because it's even using smite on the way to loot or entering the next wave (not sure if this is a setting mistake on my part)

[Sikaka]

Great work!

I was working on trying to update your previous code not knowing you were also updating at the same time.

There seems to be an issue with picking up loot on the 15th wave. sometimes if the character is closer to the portal than the loot, it just ignores the loot and moves on.

2 very minor things:

1. Could there be a setting so the character moves less often (for chieftain node -20% fire res while standing still)
2. I tried using a smite character and it's spamming smite despite not having any enemies in sight. It slows down the bot quite a lot because it's even using smite on the way to loot or entering the next wave (not sure if this is a setting mistake on my

15th wave:
This shouldn't be happening in this updated version. There's a forced timer before leaving/starting wave to avoid losing loot. Have you tried adjusting the time between waves delay? If so is it just ignoring it entirely on 15th wave? if so this is something new from one of my recent changes and I'll look into it.

Smite Spamming
What is the targeting type you have set for smite? If it's set to any monster targeting type, it shouldn't be using the skill unless targetable monsters are within your combat range.
Check the targeting type and potentially lower the combat range. Should make a big difference.

Stand Still More Often
That was the concept of the original one but honestly I found that constantly moving towards the biggest group seemed the most reliable way to make it support all builds.
Definitely gives up some of the benefits many afk sim builds push into (vines, growing aoe, increasing armour, reducing res, etc).

Let me know once you use it some more how much of an issue it poses. If it's a common request I can probably implement a combat logic switch to move towards more standing still but I expect this version will just be significantly more reliable.





Also I'm going to test a fix later today (just running a sample of 20 on current version to make sure it's stable) to have it hide/show loot if it gets stuck. Happens very rarely but if the monolith window covers the loot it can cause things to freeze up. Should be a pretty simple fix but I wanna make sure I don't introduce bugginess to something that's largely working well.

[miahjere18]

I'll try again with the Smite and report back

The 15th wave: I did see the character wait by the portal (i increased the wait time to 8 seconds) but it proceeded to leave instead of going to the loot after the wait time

[miahjere18]

Smite is now working with the settings you have mentioned.

One last feature request
If there's a way to catch if there had been no keypresses/actions in the past 60 seconds, hit flamedash/frostblink (this unstucks most stuck situations

[Sikaka]

Pushed a small update. Bot should walk to the center of the map if it's not ready to start wave/leave map yet and the wave isn't active.
Hopefully that will fix the issue you were seeing with it ending round 15 near a portal and out of range of where the loot is dropping.

Second change: If it fails to loot items, it will hit the Z key twice to reposition loot labels and hopefully cause things to not get stuck.
This is optional and disabled by default - turn it on in the bot settings.


Test Run: Was able to complete 16 runs without any interaction or getting stuck. Pretty happy with this as a baseline.
I'm basically considering any feature that can consistently complete 10 full 15 wave runs as stable enough for release (but leaving any potentially run breaking settings as optional).
Wave Stats.jpg

Smite is now working with the settings you have mentioned.

One last feature request
If there's a way to catch if there had been no keypresses/actions in the past 60 seconds, hit flamedash/frostblink (this unstucks most stuck situations

It's already doing that during most actions. Do you have a specific action where it's still getting stuck and not using movement skills after a few seconds to try to calculate a new path?
My hope is I'll find a really reliable way to make it happen and then just apply it to all actions. Right now I believe it's in combat, explore, store, start wave and leave wave (although I'd have to look).




Anyone have any experience with cross plugin communication? I think the big feature I'd like to add to this would be a basic loot filter support using the ninja price plugin...
For example skill gems set a minimum chaos price to loot them. Some 23 quality gems are valuable where 99% are rare as example. Same with the clusters.

Being able to say "pick up non unique clusters only if they are over 40c in value" would be a really nice change to stop having to empty stashes so often.

[miahjere18]

From what I have seen, it seems to be that it's consistently been in Oriath's Delusion where it gets stuck. It seems to skip the loot action since when it gets stuck the loot is still there), but the current action is Start Wave. When I manually cast flamedash, it doesn't recognize the loot when going to start the new wave

[kaminage12345]

Thanks for the update.
I did 40Maps each on 2 PCs with the latest version.

I haven't seen any loot skips so far, my item filter doesn't allow for many drops to begin with...

Stacks in 80Map are
----Incubator
3x Grabbed equipment and got stuck.
(One of those times he tried to drop it on the ground. Stuck on the screen to choose Keep or Drop)
1x Grabbed the loot and stuck.
----Map Device
3x Attempt to click on the portal behind the map device UI without activating the map.

[camapxam]

any chance we got to change the resolution? or it's fixed, only operate on 1920 1080?

[miahjere18]

is there a way for the bot to recognize mtx map devices?

[nguoidoi222]

can you make the bot rush to the best spot we choose in map after wave start instead of running around?

[Sikaka]

is there a way for the bot to recognize mtx map devices?

Currently no. I did a quick test and the MTX ones I have are a different object type and different naming structure.
It's not that I couldn't do it but that it appears like I'd potentially have to support EACH MTX one. Honestly just change your map device. it's easier than trying to support every possible configuration.

any chance we got to change the resolution? or it's fixed, only operate on 1920 1080?

Current bottleneck of known hardcoded coords are related to incubators. You could try running it with that turned off. Not sure what else would break.
Unlikely to change at this time as even on my VM I just run it at 1920x1080. The source is open if ppl wanted to try to handle multi resolution support.

can you make the bot rush to the best spot we choose in map after wave start instead of running around?

Done. It now uses the idle action instead of explore action between waves. The idle action returns to the 'center of map' position.
Currently this is roughly the most dense monster spawn area. It should be close enough to see loot but you can always tweak the coords inside Navigation/Map/GetSimulacrumCenter method.


Update Pushed to Github

Incubators no longer experimental. They are working as intended across many tests.
During map downtime it will return to center position instead of exploring. Should be more reliable.


At this point unless major issues are reported I think this is probably 'good enough'.
Taking suggestions for very repetitive farming methods that I could write bots for. Looking for super repetitive/simple farm types that ideally require less gear than simulacrum that would be useful during a league start.

[Silitonga]

Currently no. I did a quick test and the MTX ones I have are a different object type and different naming structure.
It's not that I couldn't do it but that it appears like I'd potentially have to support EACH MTX one. Honestly just change your map device. it's easier than trying to support every possible configuration.



Current bottleneck of known hardcoded coords are related to incubators. You could try running it with that turned off. Not sure what else would break.
Unlikely to change at this time as even on my VM I just run it at 1920x1080. The source is open if ppl wanted to try to handle multi resolution support.



Done. It now uses the idle action instead of explore action between waves. The idle action returns to the 'center of map' position.
Currently this is roughly the most dense monster spawn area. It should be close enough to see loot but you can always tweak the coords inside Navigation/Map/GetSimulacrumCenter method.


Update Pushed to Github

Incubators no longer experimental. They are working as intended across many tests.
During map downtime it will return to center position instead of exploring. Should be more reliable.


At this point unless major issues are reported I think this is probably 'good enough'.
Taking suggestions for very repetitive farming methods that I could write bots for. Looking for super repetitive/simple farm types that ideally require less gear than simulacrum that would be useful during a league start.

if im check list the incubator, it stop when finish round, but if i unchecklist it works.