What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

ExilebuddyBeta #889 Feedback and Discussion

oook thats weird to me but the bot skips mobs to go for chests. like completely runs riught by mobs to get to chests.. dont know if this was said already but thought id comment
 
sfrattini said:
yeah stuck here too and often...running tidal island, the only place with no obstacles lol
Click to expand...

Mine gets stuck on nothing sometimes not really stuck just stops lol.

Anyone know if we can make it run corrupted areas yet? Cant seem to find the config file like the old versions.
 
bcain1787 said:
Well the main problem is just the random stops. It just randomly stops stands still and does absolutely nothing then when i click the game window it will start moving again. Nothing posts to the log about the problem.

I'm sure pushed is aware of this just thought I would bring it up in case it was only me.
Click to expand...

No, I'm not aware of that issue. One of the big changes in the input system as part of the 1.2 update was some things to try and avoid the client dropping input actions from the bot, which was a problem before with the old system. So far, I've not seen any cases of it while testing the new system. I've run tidal island and ledge for hours now when testing new functionality.

Additional changes were made to movement as well, MoveTowards, which makes sure the bot is always trying to move towards it's target, rather than sometimes trying to move to a point that might be in the client's movement dead zone. Before, when moving towards a location and following a path, the next hop could be close to the character's feet, so movement would just stop because of the dead zone eating the messages.

That definitely should not be happening now. If the bot just stops and does nothing, like WIMM's log shows, only two explanations are possible:
1. It's stuck in an infinite processing loop somewhere, which is possible, but there's not even that much logic yet for that to be a real concern. Most likely, it'd be from the CR itself.
2. There's some system in place in the client, that is trying to prevent what we are doing. I've not noticed it myself, and most feedback up to this point has been pretty positive in terms of how the bot is actually moving around, so that leads me to thinking it's #1.

However, if you're able to click in the client, and it all of a sudden fixes itself, then that has to be #2, but I'm not sure why.

What combat ranges do you guys have set in the CR? If it's too far, your cursor will be offscreen, and not do anything, but there's no mobs in Tidal that don't move towards you that should trigger that. Ledge has totems that would, but it should be pretty obvious what is going on in that case.
 
bcain1787 said:
Mine gets stuck on nothing sometimes not really stuck just stops lol.

Anyone know if we can make it run corrupted areas yet? Cant seem to find the config file like the old versions.
Click to expand...
run it without exilehud hack and see.
 
pushedx said:
No, I'm not aware of that issue. One of the big changes in the input system as part of the 1.2 update was some things to try and avoid the client dropping input actions from the bot, which was a problem before with the old system. So far, I've not seen any cases of it while testing the new system. I've run tidal island and ledge for hours now when testing new functionality.

Additional changes were made to movement as well, MoveTowards, which makes sure the bot is always trying to move towards it's target, rather than sometimes trying to move to a point that might be in the client's movement dead zone. Before, when moving towards a location and following a path, the next hop could be close to the character's feet, so movement would just stop because of the dead zone eating the messages.

That definitely should not be happening now. If the bot just stops and does nothing, like WIMM's log shows, only two explanations are possible:
1. It's stuck in an infinite processing loop somewhere, which is possible, but there's not even that much logic yet for that to be a real concern. Most likely, it'd be from the CR itself.
2. There's some system in place in the client, that is trying to prevent what we are doing. I've not noticed it myself, and most feedback up to this point has been pretty positive in terms of how the bot is actually moving around, so that leads me to thinking it's #1.

However, if you're able to click in the client, and it all of a sudden fixes itself, then that has to be #2, but I'm not sure why.

What combat ranges do you guys have set in the CR? If it's too far, your cursor will be offscreen, and not do anything, but there's no mobs in Tidal that don't move towards you that should trigger that. Ledge has totems that would, but it should be pretty obvious what is going on in that case.
Click to expand...

My Combat range is 80 and I am not running exile hud or any other hack. What seems to be happening now is the cursor gets stuck hovering over a flask in the bottom left the info for the flask comes up and he just stands there. Next time this happens I will get a log but to me it doesn't appear as if anything is showing in the log it just stops sending logs until I manually click on the client window for poe then exilebuddy immediately resumes where it left off if I haven't died or chickened yet usually I can catch it tho. Also I am running in the library not the tidal island.

Other then this little problem that breaks it from being afk able for myself I have to agree with everyone else and everything you said overall movement and activities are much much smoother then before can't wait for more functionality to be added.
 
Last edited:
bot constantly stop moving and attacking... I tried multiple settings and it happen random. most of the time after or while interacting with a chest, causing the bot to die
 
also something I have noticed, my bot never use the abilities set to the AoE slots non of melee or range... is there something I need to look at ?
 
thenotorious said:
bot constantly stop moving and attacking... I tried multiple settings and it happen random. most of the time after or while interacting with a chest, causing the bot to die
Click to expand...

Please make a support thread and include as much info as you can about your system and setup. There seems to be more reports of this now, but most of the people I've talked to, are not seeing it.

Likewise for your bot not using AoE slots and stuff, please post your ExampleRoutineSettings.json file, and tell me what skills are in which slots. You can find the settings file in Settings\<Configuration>.
 
Nexic said:
I am using double strike. After killing a few mobs in a ranged pack, it gets stuck without moving towards the other ranged mobs and then continues to just attack in place. Anyone else have this problem?
Click to expand...
thunder said:
I can start testing some api now, dominus farm works fine. But the bot doesn't unlock waypoints now, it seems the LokiPoe.InGameState.WorldPanel.AvailableWaypoints will just return all waypoints in game, and AreaStateCache.Current.HasWaypointEntry always return true even I don't have the waypoint in that map.
Click to expand...
Hi, push. Any idea about these problems?
 
Bot starts talking whit masters and gets stuck *Doesnt click Goodbye* So annoying cant do runs longer than one hour (For all the people whit bot issues download the new version dont update it)
 
pushedx said:
Please make a support thread and include as much info as you can about your system and setup. There seems to be more reports of this now, but most of the people I've talked to, are not seeing it.

Likewise for your bot not using AoE slots and stuff, please post your ExampleRoutineSettings.json file, and tell me what skills are in which slots. You can find the settings file in Settings\<Configuration>.
Click to expand...

here the file

{
"SummonRagingSpiritCountPerDelay": 3,
"SummonRagingSpiritDelayMs": 5000,
"SummonSkeletonCountPerDelay": 2,
"SummonSkeletonDelayMs": 5000,
"MineDelayMs": 5000,
"AlwaysAttackInPlace": true,
"SingleTargetMeleeSlot": 2,
"SingleTargetRangedSlot": 8,
"AoeMeleeSlot": 1,
"AoeRangedSlot": 3,
"FallbackSlot": 5,
"CombatRange": 30,
"MaxMeleeRange": 10,
"MaxFlameBlastCharges": 5,
"MoltenShellDelayMs": 5000,
"ArcticArmourCastMode": 1,
"TotemDelayMs": 5000,
"TrapDelayMs": 2500
}

slot1:infernalBlow
slot2:moltenstrike
slot3:spectraltrow
slot4:moveonly
slot5:defaultattack
slot6:empty
slot7:anger
slot8:cyclone
 
hakansukru said:
Bot starts talking whit masters and gets stuck *Doesnt click Goodbye* So annoying cant do runs longer than one hour (For all the people whit bot issues download the new version dont update it)
Click to expand...

how do you make it talk ? my bot just pass by and do shit... never interact with masters
 
hakansukru said:
Bot starts talking whit masters and gets stuck *Doesnt click Goodbye* So annoying cant do runs longer than one hour (For all the people whit bot issues download the new version dont update it)
Click to expand...

Your "Move only" skill cannot be on your Left Mouse Button. When it is, the client will talk to the NPC rather than move around it.
 
thunder said:
Hi, push. Any idea about these problems?
Click to expand...

There's an API issue with Waypoints and them not being correctly detected. It's currently being worked out.

I replied to that Dual Strike issue I believe already, it's a CR configuration issue.
 
thenotorious said:
here the file
Click to expand...

Just tested using your setup, and it's working as designed (but maybe not as expected for users).

Code: 
                var cachedNumberOfMobsNear = Utility.NumberOfMobsNear(bestTarget, 15);

                ...

                // Logic for figuring out if we should use an AoE skill or single target.
                if (cachedNumberOfMobsNear > 3 && cachedRarity < Rarity.Rare)
                {
                    aoe = true;
                }

                // Logic for figuring out if we should use an AoE skill instead.
                if (myPos.Distance(cachedPosition) < ExampleRoutineSettings.Instance.MaxMeleeRange)
                {
                    melee = true;
                }

Melee AoE requires a pack of 5 mobs to trigger, and those mobs need to be somewhat close to each other (15 units from best target) to cast.

Perhaps a better setup would be if the best target is melee, determine AoE around the player instead.
 
Bumping my previous post- don't think you saw it pushedx

Nexic said:
new auras (herald of ash/ice) do not work.
-----

getting stuck on city of sarn cruel farm (started it as I am in town of Sarn Encampment) edit: all act 3 wps do not work for cruel when in city of sarn (tried docks,sarn, slums and others)

[HandleBlockingChestsTask] Now resetting task state.
[ReturnToGrindZoneTask] Now resetting task state.
[TravelToGrindZoneTask] Now resetting task state.
[LeaveCurrentAreaTask] Now resetting task state.
[TravelToGrindZoneTask] The waypoint's location has been found from AreaStateCache.
[TravelToGrindZoneTask] The waypoint to move to is 16050 at {219, 211}.
[InteractWith] Now attempting to highlight 7633.
[InteractWith] Now attempting to interact with 7633.
[TakeWaypointTo] WorldPanel.TakeWaypoint returned WaypointNotUsable.
[TravelToGrindZoneTask] TakeWaypointTo returned TakeWaypointFailed. This is the #1 try.
Adding location ["The City of Sarn"][30989] = {307, 89} for area [0xB30A8F10]
[CloseBlockingWindows] LokiPoe.Gui.IsLeftPanelShown || LokiPoe.Gui.IsRightPanelShown. Closing them.
[TravelToGrindZoneTask] The waypoint to move to is 16050 at {219, 211}.
[InteractWith] Now attempting to highlight 7633.
[InteractWith] Now attempting to interact with 7633.
[TakeWaypointTo] WorldPanel.TakeWaypoint returned WaypointNotUsable.
[TravelToGrindZoneTask] TakeWaypointTo returned TakeWaypointFailed. This is the #2 try.
[CloseBlockingWindows] LokiPoe.Gui.IsLeftPanelShown || LokiPoe.Gui.IsRightPanelShown. Closing them.
[TravelToGrindZoneTask] The waypoint to move to is 16050 at {219, 211}.
[InteractWith] Now attempting to highlight 7633.
[InteractWith] Now attempting to interact with 7633.
[TakeWaypointTo] WorldPanel.TakeWaypoint returned WaypointNotUsable.
[TravelToGrindZoneTask] TakeWaypointTo returned TakeWaypointFailed. This is the #3 try.
[CloseBlockingWindows] LokiPoe.Gui.IsLeftPanelShown || LokiPoe.Gui.IsRightPanelShown. Closing them.
[TravelToGrindZoneTask] The bot has failed 3 times to take a waypoint to another area. Now stopping the bot because it cannot continue.
[Stop] Now requesting the BotThread to stop.

--------

Gets stuck in city of sarn against the walls

1002.022 away.
[LeaveCurrentAreaTask] The area transition to move to is 26386 at {291, 1655}.
[LeaveCurrentAreaTask] Now moving towards the area transition The Sarn Encampment because it is 1002.022 away.
[LeaveCurrentAreaTask] The area transition to move to is 26386 at {291, 1655}.
[LeaveCurrentAreaTask] Now moving towards the area transition The Sarn Encampment because it is 1001.024 away.
[LeaveCurrentAreaTask] The area transition to move to is 26386 at {291, 1655}.
[LeaveCurrentAreaTask] Now moving towards the area transition The Sarn Encampment because it is 999.0303 away.
[LeaveCurrentAreaTask] The area transition to move to is 26386 at {291, 1655}.
[LeaveCurrentAreaTask] Now moving towards the area transition The Sarn Encampment because it is 999.0303 away.
[LeaveCurrentAreaTask] The area transition to move to is 26386 at {291, 1655}.
[LeaveCurrentAreaTask] Now moving towards the area transition The Sarn Encampment because it is 1000.027 away.
[LeaveCurrentAreaTask] The area transition to move to is 26386 at {291, 1655}.
[LeaveCurrentAreaTask] Now moving towards the area transition The Sarn Encampment because it is 1001.024 away.
[LeaveCurrentAreaTask] The area transition to move to is 26386 at {291, 1655}.
[LeaveCurrentAreaTask] Now moving towards the area transition The Sarn Encampment because it is 1001.024 away.
[LeaveCurrentAreaTask] The area transition to move to is 26386 at {291, 1655}.
[LeaveCurrentAreaTask] Now moving towards the area transition The Sarn Encampment because it is 1001.024 away.
[LeaveCurrentAreaTask] The area transition to move to is 26386 at {291, 1655}.
[LeaveCurrentAreaTask] Now moving towards the area transition The Sarn Encampment because it is 1002.022 away.
[LeaveCurrentAreaTask] The area transition to move to is 26386 at {291, 1655}.
[LeaveCurrentAreaTask] Now moving towards the area transition The Sarn Encampment because it is 1002.022 away.
[LeaveCurrentAreaTask] The area transition to move to is 26386 at {291, 1655}.
[LeaveCurrentAreaTask] Now moving towards the area transition The Sarn Encampment because it is 1000.027 away.
[LeaveCurrentAreaTask] The area transition to move to is 26386 at {291, 1655}.
[LeaveCurrentAreaTask] Now moving towards the area transition The Sarn Encampment because it is 999.0303 away.
[LeaveCurrentAreaTask] The area transition to move to is 26386 at {291, 1655}.
[LeaveCurrentAreaTask] Now moving towards the area transition The Sarn Encampment because it is 999.0303 away.
[LeaveCurrentAreaTask] The area transition to move to is 26386 at {291, 1655}.
[LeaveCurrentAreaTask] Now moving towards the area transition The Sarn Encampment because it is 998.0339 away.
[LeaveCurrentAreaTask] The area transition to move to is 26386 at {291, 1655}.
[LeaveCurrentAreaTask] Now moving towards the area transition The Sarn Encampment because it is 999.0303 away.
[LeaveCurrentAreaTask] The area transition to move to is 26386 at {291, 1655}.
[LeaveCurrentAreaTask] Now moving towards the area transition The Sarn Encampment because it is 1000.027 away.
[LeaveCurrentAreaTask] The area transition to move to is 26386 at {291, 1655}.
[LeaveCurrentAreaTask] Now moving towards the area transition The Sarn Encampment because it is 1001.024 away.

---

Is instance logout based on a timer in the works (I got stuck behind a barrel for like 15+ minutes) ? Or will this be a plugin function?
Click to expand...
 
Nexic said:
Bumping my previous post- don't think you saw it pushedx
Click to expand...

The waypoint issue will be fixed for the next version.

The general stuck issues with City of Sarn are a longer term problem to solve, and there's nothing I can do about those just yet.

StuckDetection is best implemented via a plugin, so people can customize it how they need. i do plan to get an example added soon, but right now, all my time is going into fixing some of the core issues reported.
 
You must log in or register to reply here.
Back
Top