ExilebuddyBeta Developers Testing/Feedback Thread

[alter5]

annoying problem the bot is surrounded by 3 enemys > keeps running around them not attacking even if i disabled (trytoavoidsurround) and i keep getting this error messages





[Blacklist] Blacklisting object with id 6602 for 00:00:01 (Expires at: 08/01/2014 22:41:38). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:41:39). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 20797 for 00:00:01 (Expires at: 08/01/2014 22:41:40). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:41:40). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 6602 for 00:00:01 (Expires at: 08/01/2014 22:41:40). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:41:41). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 20797 for 00:00:01 (Expires at: 08/01/2014 22:41:41). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:41:42). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 6602 for 00:00:01 (Expires at: 08/01/2014 22:41:42). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 20797 for 00:00:01 (Expires at: 08/01/2014 22:41:42). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:41:43). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 6602 for 00:00:01 (Expires at: 08/01/2014 22:41:43). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:41:44). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 20797 for 00:00:01 (Expires at: 08/01/2014 22:41:44). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 6602 for 00:00:01 (Expires at: 08/01/2014 22:41:45). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:41:45). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 20797 for 00:00:01 (Expires at: 08/01/2014 22:41:45). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:41:46). Reason: Unable to attack target.
[PoiManagerOnOnMetricsComplete] Name: aura | ExecutionStopwatch: 00:00:00.0182121 | TotalExecutionCount: 424 | SuccessfulExecutions: 0 | FailedExecutions: 424
[PoiManagerOnOnMetricsComplete] Name: combat | ExecutionStopwatch: 00:00:11.9906957 | TotalExecutionCount: 282 | SuccessfulExecutions: 214 | FailedExecutions: 68
[PoiManagerOnOnMetricsComplete] Name: explore | ExecutionStopwatch: 00:00:06.5419899 | TotalExecutionCount: 210 | SuccessfulExecutions: 210 | FailedExecutions: 0
[PoiManagerOnOnMetricsComplete] Name: buff | ExecutionStopwatch: 00:00:00.0001871 | TotalExecutionCount: 6 | SuccessfulExecutions: 0 | FailedExecutions: 6
[PoiManagerOnOnMetricsComplete] bounds: {40, 51}
TimeInInstance: 00:01:54.6510922
TimeInArea: 00:01:54.6514791
[Blacklist] Blacklisting object with id 20797 for 00:00:01 (Expires at: 08/01/2014 22:41:47). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:41:47). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 6602 for 00:00:01 (Expires at: 08/01/2014 22:41:48). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:41:48). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 20797 for 00:00:01 (Expires at: 08/01/2014 22:41:49). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:41:49). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 20797 for 00:00:01 (Expires at: 08/01/2014 22:41:50). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:41:50). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 6602 for 00:00:01 (Expires at: 08/01/2014 22:41:51). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:41:52). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 6602 for 00:00:01 (Expires at: 08/01/2014 22:41:52). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:41:53). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 20797 for 00:00:01 (Expires at: 08/01/2014 22:41:53). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:41:54). Reason: Unable to attack target.
[ExplorePoi] ClickToMove failed for position {877, 1078} with error Failed.
[Blacklist] Blacklisting object with id 20797 for 00:00:01 (Expires at: 08/01/2014 22:41:54). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:41:55). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:41:56). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:41:57). Reason: Unable to attack target.
[ExplorePoi] ClickToMove failed for position {872, 1082} with error Failed.
[ExplorePoi] ClickToMove failed for position {874, 1082} with error Failed.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:41:58). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:41:59). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 6602 for 00:00:01 (Expires at: 08/01/2014 22:41:59). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:42:01). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 20797 for 00:00:01 (Expires at: 08/01/2014 22:42:01). Reason: Unable to attack target.
[Blacklist] Blacklisting object with id 27747 for 00:00:01 (Expires at: 08/01/2014 22:42:02). Reason: Unable to attack target.

 

[pushedx]

Uncheck "TryToAvoidSurround" in ExilebuddyRoutine. The logic is pretty basic in trying to help you pull back from an incoming wave of mobs, but once you are surrounded, it relies on you actually being able to move, which sometimes it's not possible.

 

[cyberbot]

The beta sometimes fails to open the Sarcophagus in the Catacombs.

Please see the attached logs.

 

[pushedx]

Did the bot get stuck and not recover, or did it work itself out?

There's unfortunately not much that can be done to make the bot able to interact successfully all the time, so all we can do is try to have enough logic so it doesn't get stuck trying to do the same thing over and over. The core problem is that there is no reliable way to do anything in this game with how the client works. We can't send interact packets for a number of reasons, can't call interact functions directly on objects, so all that leaves us with is mouse/key emulation.

There's a lot of cases where the client doesn't perform the action you are trying to do, due to client "bugs" or in most cases, desync. Normal players rarely come across these issues because of the unpredictable nature of how they move the mouse cursor and subtly re-position the character to try and get something to work, something that is really hard for a bot to do. There's an accuracy issue when trying to position the mouse based on world coordinates, and between how the client handles target highlighting, it's a really tricky issue to deal with.

For example, one of the first thing I tried with the new Beta when it was created was trying to find ways to avoid issues like these by moving the cursor around like a player would in order to highlight a target successfully. The problem ends up being, if the target moves, the logic will never be able to highlight the target, so you end up with noticeable targeting delays. For stationary targets, such as chests, due to the way hit detection works, you are not guaranteed to even be able to highlight a target (which is why the bot always has had issues with breakable chests).

The key issue here is sometimes. For this game, the cases that shouldn't happen often, actually happen quite a lot, even though they are the small occurrence cases. This brings about frustrations when you can watch the bot do perfectly fine in an area for a few runs, you go away and come back to find it stuck on something that you'd think it should be working. Other times, you can sit and watch the bot and it seems to have all sorts of problems, when for someone else, it's not.

 

[cyberbot]

Did the bot get stuck and not recover, or did it work itself out?

There's unfortunately not much that can be done to make the bot able to interact successfully all the time, so all we can do is try to have enough logic so it doesn't get stuck trying to do the same thing over and over. The core problem is that there is no reliable way to do anything in this game with how the client works. We can't send interact packets for a number of reasons, can't call interact functions directly on objects, so all that leaves us with is mouse/key emulation.

There's a lot of cases where the client doesn't perform the action you are trying to do, due to client "bugs" or in most cases, desync. Normal players rarely come across these issues because of the unpredictable nature of how they move the mouse cursor and subtly re-position the character to try and get something to work, something that is really hard for a bot to do. There's an accuracy issue when trying to position the mouse based on world coordinates, and between how the client handles target highlighting, it's a really tricky issue to deal with.

For example, one of the first thing I tried with the new Beta when it was created was trying to find ways to avoid issues like these by moving the cursor around like a player would in order to highlight a target successfully. The problem ends up being, if the target moves, the logic will never be able to highlight the target, so you end up with noticeable targeting delays. For stationary targets, such as chests, due to the way hit detection works, you are not guaranteed to even be able to highlight a target (which is why the bot always has had issues with breakable chests).

The key issue here is sometimes. For this game, the cases that shouldn't happen often, actually happen quite a lot, even though they are the small occurrence cases. This brings about frustrations when you can watch the bot do perfectly fine in an area for a few runs, you go away and come back to find it stuck on something that you'd think it should be working. Other times, you can sit and watch the bot and it seems to have all sorts of problems, when for someone else, it's not.

Pushedx, I forgot to say. That isn't just any Sarcophagus, but the one to the corrupted area in the Catacombs. The bot is not stuck, but just standing next to it and waiting.

 

[pushedx]

Pushedx, I forgot to say. That isn't just any Sarcophagus, but the one to the corrupted area in the Catacombs. The bot is not stuck, but just standing next to it and waiting.

Yeap, I saw that from the logs. There is handling code to interact with that object, but the problem is pretty much what I wrote about. If the means of input were perfect, and the client didn't have the issues it does, it should open it 100% of the time.

I will look into trying to make it handle it better if it doesn't open (just ignore it), but that's why there is a problem in the first place.

 

[maths]

im trying the release, it work good, a little more complex but work great, but it attack slower than when i use the release, it kinda do :attack stop attack stop, i think it check if mobs are dead or if there is another better target close, is there a way to make it check for those thing less often like at every 3-4hit instead that at every hit. or i can be totally wrong and its something else the problem.

i also got back and forth problem that i didnt have with the release.
and for some reason when the time for the stuck detection log me out it doesnt log me in after, it just stop the bot completely.
i was wondering if the release we got now will still be usable, when beta wont be in beta anymore. (cuz it work very good for me)

 

[thunder]

the bot will stuck when the explore poi try to go through "undying blockage" in warehouse sewer, it never happens before.

 

[pushedx]

im trying the release, it work good, a little more complex but work great, but it attack slower than when i use the release, it kinda do :attack stop attack stop, i think it check if mobs are dead or if there is another better target close, is there a way to make it check for those thing less often like at every 3-4hit instead that at every hit. or i can be totally wrong and its something else the problem.

i also got back and forth problem that i didnt have with the release.
and for some reason when the time for the stuck detection log me out it doesnt log me in after, it just stop the bot completely.
i was wondering if the release we got now will still be usable, when beta wont be in beta anymore. (cuz it work very good for me)

Beta will not rely on the client to spam atacks like Release does. You can make the bot attack slightly faster by lowering the Settings->Main->MsBetweenTicks. I have another explanation in this thread why this is the case now, but basically, in order to fix issues Release had with stucks, more desync being added from the bot running so fast, and overall the speed at which the bot runs, the change is necessary.

I'll need a log for the stuck detection issue and your settings file for that plugin. The bot should never just stop and not recover. It has auto-restart logic called after it does a logout.

Back and forth issue is same as in Release. It's from the Explorer and Pois working against each other. One Poi says move "here", so the bot does. As the bot gets closer, another Poi says "move there", so the bot does that instead. As the bot gets closer, the other Poi tells the bot to go back, and it goes on and on. I do think I have a solution for it, but it requires changing the explorer and the pois, which I'd like to do before the big patch.

As for your last question, no. Release is going away in favor of Beta for a number of reasons. Beta is setup in a way where people can do a lot of things that are just not possible with Release. While a lot of people are used to Release, there was a time when the current Release was Beta, and the Release before that people said the same thing. Change is never easy, but moving forward, Beta offers the best stuff for everyone all around.

the bot will stuck when the explore poi try to go through "undying blockage" in warehouse sewer, it never happens before.

Release used to get stuck all the time until a small work around was finally added. It's most likely some changes are needed to get around that issue in Beta as well. I'll try to test it out soon. Basically, Beta doesn't have any quest logic handling, so things like that will give it issues. If there's a problem moving past that obstacle, the exploration node should be ignored, but there might be several cases why it doesn't actually happen. If you can get me a log as well, that might help.

 

[maths]

can we see run time and number of run we did in the beta? i cant find it anywhere. and also the exp counter i liked that feature (not as necessary as the run timer and numer of run we did) and does the plugin that gather the amount of currency and unique we got in our session work on the beta?

 

[pushedx]

can we see run time and number of run we did in the beta? i cant find it anywhere. and also the exp counter i liked that feature (not as necessary as the run timer and numer of run we did) and does the plugin that gather the amount of currency and unique we got in our session work on the beta?

The whole new design of Beta allows for an easier way to implement a BotStats plugin that tracks all that. For now though, I've not started one and probably won't make something that has a ton of stuff because it's just cosmetic, and there's a lot of other stuff that needs to be done before the big patch. I'll add a simple plugin for total ruins and some place holder logic for the loot and exp since that is useful for tracking progress, but for more, you'll most likely want to play with adding it into the code.

 

[54sgdg4d6s]

How about new item filter ability to sell items by name, not class item name? Some of uniqs, for examle Occultist's Vestment, can be Infernal Mantle and Shavronne's Wrappings too.

 

[pushedx]

How about new item filter ability to sell items by name, not class item name? Some of uniqs, for examle Occultist's Vestment, can be Infernal Mantle and Shavronne's Wrappings too.

For now, your best bet is to refine your sell filter by using the other options available.

If you want to sell all "Occultist's Vestment", then Infernal Mantle and Shavronne's Wrappings should be included, because they are indeed "Occultist's Vestment".

If you don't want to sell uniques, add a Rarity filter to exclude Uniques, so you don't have that overlap. I would never recommend making such a broad sell filter and not limiting things like rarity.

Adding a "Full Name" section (we do distinguish between the two) to the editor does make sense though, for people who want to keep specific rares based on their name for that one recipes, but in terms of adding that in as a feature, it's lower on the todo list. The new Item API still needs to be added which exposes things people have been wanting for a while now, such as DPS and other base item information.

Seeing as how a lot of people would like to go about item filters differently than what we provide, Beta has an IItemEvaluator interface that users can utilize to implement their own custom item filter logic and setup how they want. You won't be able to use our GUI for it, but you can certainly make your own.

The current Item Filter Editor is something that is just good enough for now. It's not great, but I fixed most of the bugs with it a while back. Ideally, I'd like to use a totally different system, but I doubt there will ever be time to do that. That's why at least giving people the means to do their own stuff and having an API that provides everything people need is the top most priority right now.

 

[pushedx]

Beta #863 was just built. This version expands our API by providing access to game data we used to externally provide. If you had any logic that used WorldAreaDat information, it will need to be updated to use the new stuff. If you need any help, feel free to ask, as usual.

New scripts users can run though the Dev tab have also been added. Using them is pretty straight forward, but I'll update the Dev tab guide later on to include running these as they are pretty useful. All you have to do is set the class to "MyClass", and add the 3 following assemblies: "ExilebuddyBETA.exe", "log4net.dll", and "GreyMagic.dll" and then press "Run File", after selecting the file via the "..." button.

The MapBot implementation has been delayed in favor of updating the API and addressing some more core issues before the big update. With the launch of the Taiwan beta test from the 1st for about a week, some 1.2 preview stuff can be looked at beforehand, which might help some before we see it in our version. As a result, trying to code and test the map stuff has been delayed in favor of working with that instead, so that is why you will most likely not see any updates in regards to that for the next week.

 

[babosasa]

"Taiwan beta test " do u mean the bot gonna support Garena version? that's nice

 

[pushedx]

"Taiwan beta test " do u mean the bot gonna support Garena version? that's nice

No, there are no plans to support Garena versions right now. However, since Taiwan has new 1.2 features no one else does, it's worth checking out.

 

[darkbluefirefly]

why do people keep wanting garen or TW version?? The popultion on there is 1:1000 of PoE, no one wants to buy orbs on there, so there really isn't any profit... Trust me, I talk to most of the suppliers.

 

[Farsight9]

The MapBot implementation has been delayed in favor of updating the API and addressing some more core issues before the big update. With the launch of the Taiwan beta test from the 1st for about a week, some 1.2 preview stuff can be looked at beforehand, which might help some before we see it in our version. As a result, trying to code and test the map stuff has been delayed in favor of working with that instead, so that is why you will most likely not see any updates in regards to that for the next week.

Does it delay the MapBot drastically? Because this is what I'm really looking forward to.

-Farsight9

 

[cyberbot]

Now the beta can handle summoning shrines pretty well (the bot ignores them after fighting for a while), but it seems the bot still is not able to deal with the divine shrines which make the mobs invincible. Is dealing with this special case something that you can add to the bot logic easily?

 

[2lazytotype]

Okay a few things I have noticed in this most recent build that could be helped in the future (unless I'm dumb, and cannot figure out how to do it).

• a1 Surround distance works beautifully and is really effective unless you in a tight area like the cavern of wrath, unless I'm dead close to the target, I spend more time moving and taking more damage not doing damage than just clearing the monster.
  
• a2 Use of flasks ( ele resist flasks )
  When I looked on the auto flask tab they only have option for bleeding, frozen ect. but not any percents for fire resist, lighting resist. As a ranger the red exploding things like blood suckers (can't remember there name) will explode but they do fire damage. The bot as far as i'm concerned cannot understand that so my ranger takes crap tons of damage. (If your going to tell me to use avoid on the bot re-read my first bullet point)
  
• a3 I come up with this error on boss farm when I chicken out due to reasons above
  
  

  [Tick] Exception during execution:Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000000, Size: 2120
  at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
  at GreyMagic.MemoryBase.ReadBytes(IntPtr addr, Int32 count)
  at Loki.Game.LokiPoe.LocalData.()
  at Loki.Game.Utilities.PerCachedValue`1.get_Value()
  at Loki.Game.LokiPoe.LocalData.
  ()
  at Loki.Game.Utilities.PerAreaCachedValue`1.ShouldUpdateCache(Boolean force)
  at Loki.Game.Utilities.PerCachedValue`1.get_Value()
  at Loki.Game.LokiPoe.ObjectManager.
  ()
  at Loki.Game.LokiPoe.ObjectManager.
  ()
  at Loki.Game.Utilities.PerCachedValue`1.get_Value()
  at Loki.Game.LokiPoe.ObjectManager.get_Objects()
  at Loki.Game.LokiPoe.ObjectManager.
  ()
  at Loki.Game.Utilities.PerCachedValue`1.get_Value()
  at Loki.Game.LokiPoe.ObjectManager.get_Me()
  at Loki.Bot.v2.Coroutines..
  ()
  --- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
  at Loki.Bot.v2.Coroutines.™.
  ()
  --- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
  at Loki.Bot.v2.Coroutines.œ.
  ()
  --- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
  at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
  at ExilebuddyRoutineNamespace.ExilebuddyRoutine.<Logic>d__1a.MoveNext() in c:\Users\Joseph\Desktop\EB BETA #863\Routines\ExilebuddyRoutine\ExilebuddyRoutine.cs:line 881
  --- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
  at Loki.Bot.Logic.Bots.ExilebuddyBot.Logic.Pois.OutOfTown.CombatPoi.
  .
  ()
  --- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
  at Loki.Bot.Logic.Bots.ExilebuddyBot.Poi.PoiManager..
  ()
  --- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
  at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
  at BossFarmBot.BossFarmBot.<MainCoroutine>d__4a.MoveNext()
  --- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
  at Buddy.Coroutines.Coroutine..
  .
  ()
  --- End of inner exception stack trace ---
  at Buddy.Coroutines.Coroutine.(Boolean )
  at Buddy.Coroutines.Coroutine.(Boolean )
  at Buddy.Coroutines.Coroutine.Resume()
  at BossFarmBot.BossFarmBot.OnTick()
  at Loki.Bot.v2.BotManager.(IBot )

These were the only issues I had with this beta build, other than these issues, it was solid and by far the best bot I have used. Keep up the good work.