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

[InteractWith] The target could not be highlighted.

sp3sh

sp3sh

Member
Joined
Jan 15, 2010
Messages
403
Reaction score
3
Unable to provide the log file due to its size but the bot recently is stopping due to the below.
I had to shorten the code below as i could not post more
i removed a whole chunk just repeating the below also in the middle

Error:
Code: 
2017-03-18 15:31:32,833 [9] DEBUG Logger - [Interact] "Scroll of Wisdom" has been successfully interacted.
2017-03-18 15:31:33,156 [9] INFO  Logger - [FinishMapTask] Final pulse 1/4
2017-03-18 15:31:33,872 [9] INFO  Logger - [FinishMapTask] Final pulse 2/4
2017-03-18 15:31:34,585 [9] INFO  Logger - [FinishMapTask] Final pulse 3/4
2017-03-18 15:31:35,370 [9] INFO  Logger - [FinishMapTask] Final pulse 4/4
2017-03-18 15:31:36,103 [9] INFO  Logger - [PostCombatHookTask] "GemLeveler" returned true.
2017-03-18 15:31:36,312 [9] WARN  Logger - [FinishMapTask] Now leaving current map.
2017-03-18 15:31:36,313 [9] DEBUG Logger - [TpToTown] Now going to open and take portal to town.
2017-03-18 15:31:36,314 [9] DEBUG Logger - [TpToTown] There is no ready to use portal nearby. Now going to create a new portal.
2017-03-18 15:31:36,331 [9] INFO  Logger - [ReactionWait] Now sleeping 299 ms.
2017-03-18 15:31:36,850 [9] INFO  Logger - [ReactionWait] Now sleeping 291 ms.
2017-03-18 15:31:37,184 [9] DEBUG Logger - [CloseBlockingWindows] IsLeftPanelShown || IsRightPanelShown. Closing them.
2017-03-18 15:31:55,150 [9] DEBUG Logger - [InteractWith] Now attempting to highlight 214.
2017-03-18 15:31:55,405 [9] ERROR Logger - [InteractWith] The target could not be highlighted.
2017-03-18 15:31:55,405 [9] ERROR Logger - [Interact] Fail to interact with "Immaculate Hideout". Attempt: 1/3.
2017-03-18 15:31:55,452 [9] DEBUG Logger - [StuckDetection] Small range stuck count: 10
2017-03-18 15:31:55,650 [9] DEBUG Logger - [InteractWith] Now attempting to highlight 214.
2017-03-18 15:31:55,901 [9] ERROR Logger - [InteractWith] The target could not be highlighted.
2017-03-18 15:31:55,901 [9] ERROR Logger - [Interact] Fail to interact with "Immaculate Hideout". Attempt: 2/3.
2017-03-18 15:31:56,168 [9] DEBUG Logger - [InteractWith] Now attempting to highlight 214.
2017-03-18 15:31:56,417 [9] ERROR Logger - [InteractWith] The target could not be highlighted.
2017-03-18 15:31:56,418 [9] ERROR Logger - [Interact] Fail to interact with "Immaculate Hideout". Attempt: 3/3.
2017-03-18 15:31:56,553 [9] ERROR Logger - [ErrorManager] Error count: 10/10.
2017-03-18 15:31:56,553 [9] ERROR Logger - [ErrorManager] Errors threshold has been reached. Now requesting bot to stop.
2017-03-18 15:31:56,554 [9] INFO  BotManager - [Stop] Now requesting the BotThread to stop.
2017-03-18 15:31:56,554 [9] ERROR BotManager - [Tick] Exception #3 during execution:
Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.Exception: MAX_ERRORS
   at EXtensions.ErrorManager.ReportError() in D:\Libraries\Documents\POE\3rdParty\_CONFIGS_\Mara\EXtensions\Content-718300859\ErrorManager.cs:line 36
   at MapBot.FinishMapTask.<Logic>d__2.MoveNext() in D:\Libraries\Documents\POE\3rdParty\_CONFIGS_\Mara\MapBot\Content-718303031\FinishMapTask.cs:line 35
--- 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.TaskManager.U%"e\[GcT9T'-kC\,%;ZE>$@<y!.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 System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at MapBot.MapBot.<MainCoroutine>d__14.MoveNext() in D:\Libraries\Documents\POE\3rdParty\_CONFIGS_\Mara\MapBot\Content-718303031\MapBot.cs:line 219
--- 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.'p$wUi<$ZjRoK4/4\&s-eNuS"#.2EE FaH%D${a\.w>IIx}LBR9~%.MoveNext()
   --- End of inner exception stack trace ---
   at Buddy.Coroutines.Coroutine.????????????????????????????????????????(Boolean )
   at Buddy.Coroutines.Coroutine.?????????????????????????????????????????(Boolean )
   at Buddy.Coroutines.Coroutine.Resume()
   at MapBot.MapBot.Tick() in D:\Libraries\Documents\POE\3rdParty\_CONFIGS_\Mara\MapBot\Content-718303031\MapBot.cs:line 144
   at Loki.Bot.BotManager.?????????????????????????????????????????(IBot )
2017-03-18 15:31:56,568 [9] DEBUG Logger - [MapBot] Stop
 
So do we get support with Exilebuddy? Im used to honorbuddy support - where you actually get support
 
sp3sh said:
So do we get support with Exilebuddy? Im used to honorbuddy support - where you actually get support
Click to expand...

Then you'll have to review your "community" meaning. :D

Well, you seems to have issue interacting with the portal, do you interact with the window or something at this moment? You shouldnt. Exilebuddy relies on cursor for a lot of things.

If that's not the issue, i'll let exvault/pushedx answer this, they don't have much time but once they can review some forums posts, they do. ;)
 
Yes, that much is obvious - its constantly stopping due to not being able to interact with the portal.
No one interacts with the machine, the bot runs when we are asleep.

this is what i wake up to:
v79x8o.jpg
 
a cut down log for the above - only the middle where it was working is missing. Start and end are there.
 

Attachments

Why do i need an ingame filter? The bot collects what i want, are you saying there is too much stuff on the screen for the bot?
 
Sorry to hear of your issues. While there's a few sections of this thread that need updating, please read: https://www.thebuddyforum.com/threads/exilebuddy-project-guide.178309/

Specifically, EB isn't an injected bot:
Exilebuddy is an out-of-process memory bot. It does not use pixels to operate, so it is not a pixel bot. It does not use packets to directly perform actions, so it is not a packet bot. However, it does full mouse and keyboard input emulation in order to work. Exilebuddy is written in C# and uses several low level libraries written in ASM, C++, and C++/CLI.

Path of Exile has a unique client design that prevents the typical bot design most other Buddy bots use from working correctly. While we cannot get into the details about this matter, Exilebuddy is quite unlike all the other bots Buddy provides. A lot of things work in ways that most botters might not expect, especially ones that use other Buddy products. In most games, bots are able to call client functions to perform actions with 100% accuracy and reliability.

This is not the case for Path of Exile, and as a result, the bot is bound to the limitations a normal user is as well as the client implementation itself. To be more specific, Path of Exile as a game is known for its desync issue. That issue greatly affects the bot, because the bot is reliant on the client for it's information. There are many other client issues that affect the bot, and as a result, there will be noticeable things that happen that might not make sense, but are done in order to have a working bot for this game.
Click to expand...

The issue you're seeing is because of how the game works. The item labels overlap the portal label so the bot can't interact with the portal's label. Using an in-game loot filter to hide trash that will never meet your loot filters will certainly help avoid the issue.

One thing we can look into is trying to add more logic to try and click the portal object itself rather than the label, but that's a change that will have to be looked into for 3.0. In either case, there's no way to "force interact" with the portal object itself, so work-arounds are needed.

We ask for full logs to see if there's a better solution possible if its our provided logic that is having the issue, and in this case, it would probably be better for MapBot to logout rather than stop in the event of this failure. I'll forward this to ExVault and we'll see what can be done, so thanks for attaching the full log.
 
pushedx said:
Sorry to hear of your issues. While there's a few sections of this thread that need updating, please read: https://www.thebuddyforum.com/threads/exilebuddy-project-guide.178309/

Specifically, EB isn't an injected bot:


The issue you're seeing is because of how the game works. The item labels overlap the portal label so the bot can't interact with the portal's label. Using an in-game loot filter to hide trash that will never meet your loot filters will certainly help avoid the issue.

One thing we can look into is trying to add more logic to try and click the portal object itself rather than the label, but that's a change that will have to be looked into for 3.0. In either case, there's no way to "force interact" with the portal object itself, so work-arounds are needed.

We ask for full logs to see if there's a better solution possible if its our provided logic that is having the issue, and in this case, it would probably be better for MapBot to logout rather than stop in the event of this failure. I'll forward this to ExVault and we'll see what can be done, so thanks for attaching the full log.
Click to expand...

Thanks for the response, i am now running with filters and it still has an issue - the stupid thing is, if i click start again it clicks the portal perfectly.

New log due to size uploaded to fileshare:

https://ufile.io/a52541
 
Thanks, we'll check that out.

From what you just described, that sounds like your routine or playermover has performed an action that is still trying to take effect when the portal taking logic runs, making interaction fail.

Stopping the bot resets all key states and the cursor, so if it suddenly works in that case, then we can add some more code to try and avoid that issue.

Edit: Actually never mind, FinishCurrentAction is already called in Interact code to clear key states - might just be a client issue or a hidden label issue still, so trying to click the portal itself might help
 
You must log in or register to reply here.
Back
Top