Exilebuddy crashing

[Trras]

Hi there, I've been using Exilebuddy for 3 days now and I noticed an issue where my bot will just crash and my character will be left standing there doing nothing in the middle of a map.

I have 2 logs to show this. It both ends with the same similar logic null error.

2014-10-21 01:25:51,245 [14] DEBUG TravelToGrindZoneTask (null) - [TravelToGrindZoneTask] GrindZoneId = 1_3_1.
2014-10-21 01:25:51,321 [14] DEBUG TravelToGrindZoneTask (null) - [TravelToGrindZoneTask] PathToGrindZone = 1_3_1.
2014-10-21 01:25:51,323 [14] DEBUG TravelThroughBossAreasTask (null) - [TravelThroughBossAreasTask] GrindZoneId = 1_3_1.
2014-10-21 01:25:51,325 [14] DEBUG TravelThroughBossAreasTask (null) - [TravelThroughBossAreasTask] We are not currently in a boss area, or a supported boss area.
2014-10-21 01:25:51,361 [14] DEBUG TravelThroughBossAreasTask (null) - [TravelThroughBossAreasTask] We are not currently in a boss area, or a supported boss area.
2014-10-21 01:25:51,362 [14] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {759, 529} (128) [12.31102 %].
2014-10-21 01:25:51,784 [14] DEBUG AreaStateCache (null) - Adding location ["Waypoint"][10198] = {638, 539} for area [0xA71EC092]
2014-10-21 01:25:51,786 [14] DEBUG AreaStateCache (null) - [ResetAnchorPoint] Setting AnchorPoint to {646, 534} for 2803810450.
2014-10-21 01:25:51,787 [14] DEBUG AreaStateCache (null) - [ResetAnchorPoint] Setting CurrentAnchorPoint to {646, 534} for 2803810450.
2014-10-21 01:25:52,502 [14] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {644, 690} (125) [14.57883 %].
2014-10-21 01:25:53,860 [14] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {644, 736} (123) [16.73866 %].
2014-10-21 01:25:58,393 [14] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {644, 805} (135) [19.9784 %].
2014-10-21 01:25:59,631 [14] DEBUG ExploreTask (null) - [ExploreTask] Now exploring to the location {644, 828} (126) [21.05832 %].
2014-10-21 01:26:00,405 [14] DEBUG OpenChestTask (null) - [OpenChestTask] The current chest to open is [12389] Boulder at {678, 889}. We have been on this task for 00:00:00 and have been attempting to interact for 00:00:00.
2014-10-21 01:26:00,425 [14] DEBUG OpenChestTask (null) - [OpenChestTask] Now moving towards the chest 12389 because it is 158.393 away (can see).
2014-10-21 01:26:01,753 [14] DEBUG OpenChestTask (null) - [OpenChestTask] The current chest to open is [12389] Boulder at {678, 889}. We have been on this task for 00:00:00.6976836 and have been attempting to interact for 00:00:00.
2014-10-21 01:26:01,755 [14] DEBUG OpenChestTask (null) - [OpenChestTask] Now moving towards the chest 12389 because it is 97.4509 away (can see).
2014-10-21 01:26:05,448 [14] INFO ExampleRoutine (null) - [Logic] Now moving towards the monster Restless Archer because [canSee: False][pathDistance: 44.7172][blockedByDoor: False]
2014-10-21 01:26:05,550 [14] INFO ExampleRoutine (null) - [Logic] Now moving towards the monster Restless Archer because [canSee: False][pathDistance: 44.7172][blockedByDoor: False]
2014-10-21 01:26:05,647 [14] DEBUG OpenChestTask (null) - [OpenChestTask] The current chest to open is [12389] Boulder at {678, 889}. We have been on this task for 00:00:00 and have been attempting to interact for 00:00:00.
2014-10-21 01:26:05,691 [14] DEBUG OpenChestTask (null) - [OpenChestTask] Now attempting to interact with the chest. This is the #1 attempt.
2014-10-21 01:26:05,692 [14] DEBUG Coroutines (null) - [InteractWith] Now attempting to highlight 12389.
2014-10-21 01:26:05,814 [14] DEBUG Coroutines (null) - [InteractWith] Now attempting to interact with 12389.
2014-10-21 01:26:05,853 [14] DEBUG Coroutines (null) - [FinishCurrentAction] Waiting for the action to finish Interaction.
2014-10-21 01:26:06,096 [14] INFO ExampleRoutine (null) - [Logic] Now moving towards the monster Restless Archer because [canSee: False][pathDistance: 48.12613][blockedByDoor: False]

And


2014-10-21 03:46:58,153 [15] DEBUG LootItemsTask (null) - [LootItemTask] Now attempting to interact with the item. This is the #1 attempt.
2014-10-21 03:46:58,154 [15] DEBUG Coroutines (null) - [InteractWith] Now attempting to highlight 5886. holdCtrl = False.
2014-10-21 03:46:58,298 [15] DEBUG Coroutines (null) - [InteractWith] Now attempting to interact with 5886.
2014-10-21 03:46:58,353 [15] DEBUG StuckDetection (null) - [StuckDetection] {545, 1376} => 2
2014-10-21 03:46:58,356 [15] DEBUG StuckDetection (null) - [StuckDetection] bounds: {211, 258}
2014-10-21 03:46:58,357 [15] DEBUG StuckDetection (null) - [StuckDetection] TimeInInstance: 00:01:58.0593930
2014-10-21 03:46:58,358 [15] DEBUG StuckDetection (null) - [StuckDetection] TimeInArea: 00:01:58.0599159
2014-10-21 03:46:58,772 [15] DEBUG LootItemsTask (null) - [LootItemTask] The current item to loot is [5886] Wild Leather at {520, 1366}. We have been on this task for 00:00:01.3543028 and have been attempting to interact for 00:00:00.5912083.
2014-10-21 03:46:58,835 [15] DEBUG LootItemsTask (null) - [LootItemTask] The current item to loot is [5886] Wild Leather at {520, 1366}. We have been on this task for 00:00:00.1923386 and have been attempting to interact for 00:00:00.
2014-10-21 03:46:58,894 [15] DEBUG OpenChestTask (null) - [OpenChestTask] The current chest to open is [30031] Chest at {453, 1337}. We have been on this task for 00:00:00.2769558 and have been attempting to interact for 00:00:00.
2014-10-21 03:46:58,897 [15] DEBUG OpenChestTask (null) - [OpenChestTask] Now moving towards the chest 30031 because it is 73.40918 away (can see).
2014-10-21 03:46:59,601 [15] DEBUG OpenChestTask (null) - [OpenChestTask] The current chest to open is [30031] Chest at {453, 1337}. We have been on this task for 00:00:00 and have been attempting to interact for 00:00:00.
2014-10-21 03:46:59,623 [15] DEBUG OpenChestTask (null) - [OpenChestTask] Now moving towards the chest 30031 because it is 42.26399 away (can see).
2014-10-21 03:47:00,225 [15] DEBUG OpenChestTask (null) - [OpenChestTask] Now attempting to interact with the chest. This is the #1 attempt.
2014-10-21 03:47:00,226 [15] DEBUG Coroutines (null) - [InteractWith] Now attempting to highlight 30031.
2014-10-21 03:47:00,298 [15] DEBUG Coroutines (null) - [InteractWith] Now attempting to interact with 30031.
2014-10-21 03:47:00,340 [15] DEBUG Coroutines (null) - [FinishCurrentAction] Waiting for the action to finish Interaction.
2014-10-21 03:47:00,394 [15] DEBUG Coroutines (null) - [FinishCurrentAction] Waiting for the action to finish Interaction.
2014-10-21 03:47:00,425 [15] DEBUG Coroutines (null) - [FinishCurrentAction] Waiting for the action to finish Interaction.
2014-10-21 03:47:00,738 [15] DEBUG OpenChestTask (null) - [OpenChestTask] The current chest to open is [30200] Chest at {397, 1583}. We have been on this task for 00:00:00 and have been attempting to interact for 00:00:00.
2014-10-21 03:47:00,768 [15] DEBUG OpenChestTask (null) - [OpenChestTask] Now moving towards the chest 30200 because it is 255.2406 away (can't see).
2014-10-21 03:47:03,742 [15] INFO ExampleRoutine (null) - [Logic] Now moving towards the monster Undying Outcast because [canSee: False][pathDistance: 66.30483][blockedByDoor: False]


Anyone has the same issue as me?

 

[Nepthys]

Saw something similar awhile back, left the bot unattended & when I return was on the 'you have died' screen, bot was no longer running
happened in act2 crossroads I believe

made an autohotkey script as insurance will close path of exile if the bot is no longer running
remember to close the script when starting path of exile otherwise it'll close immediately before you have a chance to start the bot


SetTitleMatchMode, 2
Loop
{
ifWinNotExist, Exilebuddy
{
WinClose, Path of Exile
}
Else
{
sleep, 1000
}
}

 

[Trras]

Thanks buddy this helps alot. I usually have an autoflask/chicken script in the background but sometimes it just stops working. Lost 2 characters on Beyond already!
Still hoping that they fix this issue though

 

[darkbluefirefly]

Thanks buddy this helps alot. I usually have an autoflask/chicken script in the background but sometimes it just stops working. Lost 2 characters on Beyond already!
Still hoping that they fix this issue though

Buddy is not meant to be ran with other hacks/things that modify memory.

 

[pushedx]

Please attach full logs.

There's no crashing issues that I know of. There's a difference between the bot crashing, and the bot closing though.

If there's an auth issue, the bot will close, but there are options to exit the process or logout. If there's a protection issue, the bot will close. If the bot is crashing, you'll see the Window's crash dialog.

 

[Trras]

View attachment Exilebuddy 108 2014-10-21 10.31.txtView attachment Exilebuddy 144 2014-10-21 07.51.txt

 

[Trras]

View attachment Exilebuddy 2160 2014-10-24 19.04.txtView attachment Exilebuddy 3876 2014-10-24 19.17.txtView attachment Exilebuddy 536 2014-10-24 17.47.txt

More chest opening bugs that leads exilebuddy to close

I don't know what I'm doing wrong here. I only use a modified chicken script to chicken to beyond bosses but everytime I run my bot, after 30 minutes or so it'll crash. I cant even leave it on for long. Its getting pretty frustrating now

 

[darkbluefirefly]

View attachment 147750View attachment 147751View attachment 147752

More chest opening bugs that leads exilebuddy to close

I don't know what I'm doing wrong here. I only use a modified chicken script to chicken to beyond bosses but everytime I run my bot, after 30 minutes or so it'll crash. I cant even leave it on for long. Its getting pretty frustrating now

Hum... where are you grinding? Looks like a strongbox and it's trying to open it, It cannot because the monsters are not killed. I'll help with a strong box plugin latter. I have this issues as well so I'll get a fix.
But if it is not a strongbox and something else, are you running any FPS limiting software? That is another case where this happens often.
Thanks.

 

[pushedx]

All I can suggest is making a softcore character and try running the bot with no other 3rd party tools or scripts and see if the problem persists. If it does, then there is something on your machine causing the issue.

The reason is:
* Crashes on long loading screens is possible because of how the bot has to hook D3D to work. However, the majority of these should have been solved with recent PoE client updates and game changes.
* The bot running for a very long time and possibly crashing once in a while due to how software works on Windows.
* The bot reading bad memory and throwing a bunch of exceptions is possible, but will be logged. Crashing from that is unlikely because of the design of .Net.

The only 2 reasons for frequent bot closing would be:
1. Auth issues where your session goes invalid, but that should be logged.
2. The Buddy anti-***** protection is triggering due to matching something.

I can't help you with either of those, but I can try to ask Support to figure out what is causing it. Other than that, there's nothing in Exilebuddy itself that would trigger a bot close, especially trying to open a chest.

 

[Trras]

Hum... where are you grinding? Looks like a strongbox and it's trying to open it, It cannot because the monsters are not killed. I'll help with a strong box plugin latter. I have this issues as well so I'll get a fix.
But if it is not a strongbox and something else, are you running any FPS limiting software? That is another case where this happens often.
Thanks.

Doing it in catacombs, I realised that it isn't anything thats causing it to crash, bot specific. When I run the bot on my VMWare, it closes after some time randomly but if I run it on my main windows, it never crashes at all. Not running any FPS limiting software. I disabled all sorts of strongbox/chest/urns already but somehow its still crashing and logs arent showing anything. I haven't been able to look at my bot crash so I cant figure out what is it yet but I'll get to it.