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

ExilebuddyBeta #890 Feedback and Discussion

please please please please in the next update full support for strongboxes. all in all what he has to do is just to click them. no matter if they white or yellow. just click :(
 
pushedx said:
Is your Always Highlight setting enabled?

If it is, and you still can't interact, I'll go check that object to figure out why it's not targeting it correctly.
Click to expand...
Yes, always enabled, unless bot untick it when meet strongbox.

PS, the town to upper god problem still exist, here is the log.
 

Attachments

another issue. please make it prioritize necromancer and all stuff that summon dead stuff... it gets messy when there are 2 necros :(
 
thunder said:
Yes, always enabled, unless bot untick it when meet strongbox.

PS, the town to upper god problem still exist, here is the log.
Click to expand...

Thanks for the log. It looks like some logic issues, but I'll have to think this though. Your log shows that it tried going to town twice, which should not be happening.
 
Not sure if these problems were already mentioned but here they are (again) :


Playing as a Ranged Character it's basically impossible, it behaves as melee character therefore dying a lot.

Another problem related to dying is the Ressurect. It is not properly clicking on it if the game window isn't focused.

There are many zones where the bot tries to walk through a wall, because it wants to explore a zone that is not reachable, staying stuck forever. Most common zone is City of Sarn.
 
tozededao said:
Not sure if these problems were already mentioned but here they are (again) :


Playing as a Ranged Character it's basically impossible, it behaves as melee character therefore dying a lot.

Another problem related to dying is the Ressurect. It is not properly clicking on it if the game window isn't focused.

There are many zones where the bot tries to walk through a wall, because it wants to explore a zone that is not reachable, staying stuck forever. Most common zone is City of Sarn.
Click to expand...
city of sarn is a known issue, the others I haven't experienced, and the pc is running 18 clients atm non vm, so are you running it in vm?
 
tozededao said:
Playing as a Ranged Character it's basically impossible, it behaves as melee character therefore dying a lot.
Click to expand...

If you mean it doesn't kite, move around, and play the build to its strengths, that's expected. If you mean, it's not using your ranged skills (not talking about melees mobs that run up to you and it stands there still), then what's your current CR configuration. I've been testing a Ranger in Normal and it's fine in terms of it actually using skills how it's designed. The change to make the CR walk towards a melee target was done because melee skills weren't even being used; there's certainly better ways to use ranged skills, but that's outside the scope of this particular CR.

Our CR doesn't kite or do anything advanced like that, so that might be part of the issue at higher levels if you don't have high suitability. There's not going to be any changes regarding that, though. I can't focus on a better default CR that does things like that, and most likely will not be able to in the immediate future. It's not that I don't want to, but I can't for reasons explained in previous posts. It'll be up to the community to pull together something better if it's needed. I will get an example of the priority system in place soon for people to work with, and making it visit other mob locations so it doesn't skip as many as it currently does.

For kiting logic, you should have everything you need. You just have to identify the case where you should kite (taking into consideration sometimes you shouldn't kite, as you could never attack), and then walk backwards to a starting position. AreaStateCache.Current.CurrentAnchorPoint will give you a position you can move towards to kite to the start of the instance. You can also look into trying to kite 'around' mobs, but that's a little more complicated based on the current tileset you are in.

I'll need a log for when the resurrect wasn't being clicked. The game window cannot be minimized, but it does not have to be a foreground window. Resurrect logic has been the same for a while now ever since GGG changed it like half a year ago or so, so there shouldn't be anything new with that.
 
Pushedx,

I've been getting a lot of desync (been playing a melee build double strike) after using the code you previous posted to fix the range melee
 
pushedx said:
If you mean it doesn't kite, move around, and play the build to its strengths, that's expected. If you mean, it's not using your ranged skills (not talking about melees mobs that run up to you and it stands there still), then what's your current CR configuration. I've been testing a Ranger in Normal and it's fine in terms of it actually using skills how it's designed. The change to make the CR walk towards a melee target was done because melee skills weren't even being used; there's certainly better ways to use ranged skills, but that's outside the scope of this particular CR.

Our CR doesn't kite or do anything advanced like that, so that might be part of the issue at higher levels if you don't have high suitability. There's not going to be any changes regarding that, though. I can't focus on a better default CR that does things like that, and most likely will not be able to in the immediate future. It's not that I don't want to, but I can't for reasons explained in previous posts. It'll be up to the community to pull together something better if it's needed. I will get an example of the priority system in place soon for people to work with, and making it visit other mob locations so it doesn't skip as many as it currently does.

For kiting logic, you should have everything you need. You just have to identify the case where you should kite (taking into consideration sometimes you shouldn't kite, as you could never attack), and then walk backwards to a starting position. AreaStateCache.Current.CurrentAnchorPoint will give you a position you can move towards to kite to the start of the instance. You can also look into trying to kite 'around' mobs, but that's a little more complicated based on the current tileset you are in.

I'll need a log for when the resurrect wasn't being clicked. The game window cannot be minimized, but it does not have to be a foreground window. Resurrect logic has been the same for a while now ever since GGG changed it like half a year ago or so, so there shouldn't be anything new with that.
Click to expand...

I wasn't talking about kiting, its like even the first spell it uses, it goes straight it moves to target's position before it casts even if we have have LOS.

About resurect I'll get you a log soon.
 
Will be continuing to try this out once selling is implemented, no bugs so far for me but have only done a couple of runs. When do you think selling will be implemented Pushed ? sometime this week ? CR is giving me some troubles but nothing some time and effort won't fix!
 
The last 2 deaths it actually clicked on the release button, I'm gonna try to replicate it because it happened when I had that game window on my second monitor and was manually playing on the first.
 
Okay it finally happened, apparently if you die while you are waiting for an action to finish it doesn't resurect.

Code: 
[ExploreTask] Now exploring to the location {322, 1311} (319) [94.22382 %].
[ExploreTask] Now exploring to the location {322, 1311} (316) [94.22382 %].
[ExploreTask] Now exploring to the location {322, 1311} (312) [94.22382 %].
[ExploreTask] Now exploring to the location {322, 1311} (309) [94.22382 %].
[ExploreTask] Now exploring to the location {322, 1311} (306) [94.22382 %].
[ExploreTask] Now exploring to the location {322, 1311} (303) [94.22382 %].
[ExploreTask] Now exploring to the location {322, 1311} (300) [94.22382 %].
[ExploreTask] Now exploring to the location {322, 1311} (297) [94.22382 %].
[ExploreTask] Now exploring to the location {322, 1311} (295) [94.22382 %].
[ExploreTask] Now exploring to the location {322, 1311} (292) [94.22382 %].
[ExploreTask] Now exploring to the location {322, 1311} (288) [94.22382 %].
[ExploreTask] Now exploring to the location {322, 1311} (282) [94.22382 %].
[ExploreTask] Now exploring to the location {322, 1311} (276) [94.22382 %].
[ExploreTask] Now exploring to the location {322, 1311} (271) [94.22382 %].
[ExploreTask] Now exploring to the location {322, 1311} (264) [94.22382 %].
[ExploreTask] Now exploring to the location {322, 1311} (264) [94.22382 %].
[ExploreTask] Now exploring to the location {322, 1311} (264) [94.22382 %].
[ExploreTask] Now exploring to the location {322, 1311} (264) [94.22382 %].
[ExploreTask] Now exploring to the location {322, 1311} (263) [94.22382 %].
[ExploreTask] Now exploring to the location {322, 1311} (260) [94.22382 %].
[ExploreTask] Now exploring to the location {322, 1311} (243) [94.22382 %].
[FinishCurrentAction] Waiting for the action to finish Shockwave Totem.
[ResurrectTask] This is the #2 time we have died in this instance.
 
tozededao said:
Okay it finally happened, apparently if you die while you are waiting for an action to finish it doesn't resurect.
Click to expand...

Is FinishCurrentAction spammed continuously after that? Having a full log from start to stop really does help. :p
 
No, it just stands still there, thats why I saw no point in posting anything predeath, after death there is nothing on the log.

Code: 
2014-09-03 20:49:35,286 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (337) [94.22382 %].2014-09-03 20:49:35,381 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (333) [94.22382 %].
2014-09-03 20:49:35,477 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (329) [94.22382 %].
2014-09-03 20:49:35,567 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (325) [94.22382 %].
2014-09-03 20:49:35,652 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (322) [94.22382 %].
2014-09-03 20:49:35,726 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (319) [94.22382 %].
2014-09-03 20:49:35,805 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (316) [94.22382 %].
2014-09-03 20:49:35,886 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (312) [94.22382 %].
2014-09-03 20:49:35,970 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (309) [94.22382 %].
2014-09-03 20:49:36,039 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (306) [94.22382 %].
2014-09-03 20:49:36,118 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (303) [94.22382 %].
2014-09-03 20:49:36,185 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (300) [94.22382 %].
2014-09-03 20:49:36,253 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (297) [94.22382 %].
2014-09-03 20:49:36,322 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (295) [94.22382 %].
2014-09-03 20:49:36,396 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (292) [94.22382 %].
2014-09-03 20:49:36,481 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (288) [94.22382 %].
2014-09-03 20:49:36,630 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (282) [94.22382 %].
2014-09-03 20:49:36,774 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (276) [94.22382 %].
2014-09-03 20:49:36,902 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (271) [94.22382 %].
2014-09-03 20:49:38,615 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (264) [94.22382 %].
2014-09-03 20:49:38,693 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (264) [94.22382 %].
2014-09-03 20:49:38,783 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (264) [94.22382 %].
2014-09-03 20:49:38,853 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (264) [94.22382 %].
2014-09-03 20:49:38,929 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (263) [94.22382 %].
2014-09-03 20:49:39,004 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (260) [94.22382 %].
2014-09-03 20:49:40,801 [35] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {322, 1311} (243) [94.22382 %].
2014-09-03 20:49:40,953 [35] DEBUG Coroutines (null) - [FinishCurrentAction] Waiting for the action to finish Shockwave Totem.
2014-09-03 20:49:45,743 [35] DEBUG ResurrectTask (null) - [ResurrectTask] This is the #2 time we have died in this instance.
2014-09-03 20:52:09,990 [1] INFO  BotManager (null) - [Stop] Now requesting the BotThread to stop.
2014-09-03 20:52:10,052 [35] DEBUG BasicGrindBot (null) - [BasicGrindBot] OnStop
2014-09-03 20:52:10,052 [35] DEBUG LeaveCurrentAreaTask (null) - [LeaveCurrentAreaTask] Now resetting task state.
2014-09-03 20:52:10,053 [35] DEBUG GemLeveler (null) - [GemLeveler] Stop
2014-09-03 20:52:10,053 [35] DEBUG DualTotemRoutine (null) - [DualTotemRoutine] Stop
2014-09-03 20:52:10,052 [35] DEBUG AutoFlask (null) - [AutoFlask] Stop
 
tozededao said:
No, it just stands still there, thats why I saw no point in posting anything predeath, after death there is nothing on the log.
Click to expand...

And that's why I'd need a full log. :p

The fact it's not spamming FinishCurrentAction means that it's not stuck in there, since I have that code setup to log every 100ms while it's waiting. It's something else I'll start looking into, but I need the entire log, since there will be other task debugging calls that are useful to me.

Based on what you just posted, it looks like the bot gets stuck in some logic loop elsewhere, and the ResurrectTask never executes again. I'll start looking for places where that can happen.
 
Last edited:
Happened again,

Code: 
2014-09-03 21:04:24,702 [41] DEBUG OpenChestTask (null) - [OpenChestTask] Now moving towards the chest 2017 because it is 94.44463 away (can't see).2014-09-03 21:04:24,870 [41] DEBUG OpenChestTask (null) - [OpenChestTask] The current chest to open is [2017] Chest at {926, 1091}. We have been on this task for 00:00:02.1590834 and have been attempting to interact for 00:00:00.
2014-09-03 21:04:24,887 [41] DEBUG OpenChestTask (null) - [OpenChestTask] Now moving towards the chest 2017 because it is 88.06126 away (can't see).
2014-09-03 21:04:25,051 [41] DEBUG OpenChestTask (null) - [OpenChestTask] The current chest to open is [2017] Chest at {926, 1091}. We have been on this task for 00:00:02.2227567 and have been attempting to interact for 00:00:00.
2014-09-03 21:04:25,084 [41] DEBUG OpenChestTask (null) - [OpenChestTask] Now moving towards the chest 2017 because it is 80.07212 away (can't see).
2014-09-03 21:04:25,271 [41] DEBUG OpenChestTask (null) - [OpenChestTask] The current chest to open is [2017] Chest at {926, 1091}. We have been on this task for 00:00:02.3071597 and have been attempting to interact for 00:00:00.
2014-09-03 21:04:25,303 [41] DEBUG OpenChestTask (null) - [OpenChestTask] Now moving towards the chest 2017 because it is 71.02657 away (can't see).
2014-09-03 21:04:28,429 [41] DEBUG OpenChestTask (null) - [OpenChestTask] The current chest to open is [2017] Chest at {926, 1091}. We have been on this task for 00:00:02.3874255 and have been attempting to interact for 00:00:00.
2014-09-03 21:04:28,460 [41] DEBUG OpenChestTask (null) - [OpenChestTask] Now moving towards the chest 2017 because it is 64.17342 away (can't see).
2014-09-03 21:04:28,661 [41] DEBUG OpenChestTask (null) - [OpenChestTask] The current chest to open is [2017] Chest at {926, 1091}. We have been on this task for 00:00:02.4673312 and have been attempting to interact for 00:00:00.
2014-09-03 21:04:28,692 [41] DEBUG OpenChestTask (null) - [OpenChestTask] Now moving towards the chest 2017 because it is 53.96117 away (can't see).
2014-09-03 21:07:43,630 [41] DEBUG ResurrectTask (null) - [ResurrectTask] This is the #1 time we have died in this instance.
2014-09-03 21:12:10,261 [1] INFO  BotManager (null) - [Stop] Now requesting the BotThread to stop.
2014-09-03 21:12:10,290 [41] DEBUG BasicGrindBot (null) - [BasicGrindBot] OnStop
2014-09-03 21:12:10,291 [41] DEBUG AutoFlask (null) - [AutoFlask] Stop
2014-09-03 21:12:10,290 [41] DEBUG LeaveCurrentAreaTask (null) - [LeaveCurrentAreaTask] Now resetting task state.
2014-09-03 21:12:10,291 [41] DEBUG DualTotemRoutine (null) - [DualTotemRoutine] Stop
2014-09-03 21:12:10,291 [41] DEBUG GemLeveler (null) - [GemLeveler] Stop

Deaths @

20:49:45
21:07:43
 

Attachments

Last edited:
Happened third time, I'm gonna swap the window from my second monitor to my main and run a bit to see if it fixes it.
 
Any chance update bot by instance timer? Something like anti stuck logic - logout after 5-10mins. Sometimes bot stuck at wall, the biggest problem - desync or barrels on his way.
Another problem the summoners. Bot attacking skeletons and the summoner keeps summoning the skeletons away from attack range.
 
I did a totaly new install of EB and used https://gist.github.com/anonymous/0587de7b32d4054895a1

It works, but somehow it creates huge lagspikes or something. The char is next to mobs but does not hit, then I stop the bot, and uses /oos and i get teleported 5-15 yards away..

And when it cast auras it driks Hybrid flasks for the mana it losses
 
kuskner said:
I did a totaly new install of EB and used https://gist.github.com/anonymous/0587de7b32d4054895a1

It works, but somehow it creates huge lagspikes or something. The char is next to mobs but does not hit, then I stop the bot, and uses /oos and i get teleported 5-15 yards away..

And when it cast auras it driks Hybrid flasks for the mana it losses
Click to expand...

I noticed this too. Causes lots of desync (don't know about the aura problem)- previous versions did not cause so much desync
 
You must log in or register to reply here.
Back
Top