heisenburger

Not a big bug, but the bot sometimes keeps attacking thin air after the map is finished. This goes on until the "max run time" is reached. Log:

New crash logs: Lastrun: Timer:

No prob. I tried disconnecting several times but couldn't reproduce the bug either.

The bot sometimes crashes right after chicken. Tested under normal mode as administrator. OS: Win8.1 Log: 2015-10-05 17:58:55 [info] -> Attacking monster using mouse_wheel key at distance : 2.828427 2015-10-05 17:58:55 [info] -> Attacking monster using mouse_wheel key at distance : 4.242640 2015-10-05 17:58:55 [info] -> Attacking monster using mouse_wheel key at distance : 2.000000 2015-10-05 17:58:56 [info] -> Attacking monster using mouse_wheel key at distance : 1.000000 2015-10-05 17:58:56 [info] -> Restart state because no monster were killed for 160 s 2015-10-05 17:58:57 [info] -> Chickened via method ESC+CLICK! 2015-10-05 17:58:57 [info] -> Chicken state because no tp found in player's inventory 2015-10-05 17:58:57 [info] -> Restart state because area is cleared 2015-10-05 17:58:58 [info] -> Logging into the game 2015-10-05 17:58:59 [info] -> Chicken state because no tp found in player's inventory 2015-10-05 17:58:59 [info] -> Restart state because area is cleared 2015-10-05 17:59:05 [info] -> Logging into the game 2015-10-05 17:59:06 [info] -> Current complex map explored !! 2015-10-05 17:59:06 [info] -> Chicken state because no tp found in player's inventory 2015-10-05 17:59:06 [info] -> Restart state because area is cleared 2015-10-05 17:59:07 [info] -> Chickened via method ESC+CLICK! ...and crash...

In skills.ini, if the target is set to "normal only", the bot would ignore all normal mobs and keep moving. I tested using the most simple config: 1 skill only, no auras skills.ini Log: 2015-10-03 20:36:24 [info] -> Moving to position(10061.303711, 7411.553223). State Priority: 22 2015-10-03 20:36:24 [info] -> Moving to position(10061.303711, 7411.553223). State Priority: 22 2015-10-03 20:36:25 [info] -> Moving to position(10061.303711, 7411.553223). State Priority: 22 (you get the idea...)

Don't bother. It's a cool tool, but too many people are doing this. You'll realize there's almost nothing worth flipping once you start scanning the market.

It's definitely not a top priority. If it does get implemented, the [retry] property can be an optional feature, so you don't have to edit your map file at all.

When the bot gets stuck in a map, it would quit and re-enter the map. If the map isn't so good, it'd be better to start a new map instead.

A lot of cheap maps are not worth running twice, left alone 6 times. Can we have a property in the map file like this: "[Retry] == 3" //retry the map 3 times at most

Just thought it'd be handy to have an option like this: If the bot chickened because it got stuck picking up items, go back to map. If the bot chickened for any other reason, start new map

The bot just stopped again. Timer log: World update took: 16ms Game informations update took: 16ms World update took: 16ms Game informations update took: 16ms World update took: 16ms Game informations update took: 16ms . . . Same 2 lines on and on....

The bot's been running fine for 24 hours since I attached it to a different process. I didn't bother digging into the timer log because it was "too large to be opened by notepad", but if the problem happens again, I'll let you know.

Same here.

Once every few hours, my char just stops doing anything and gets killed, and nothing new shows in the log. Anyone else having this problem?

Another problem: after you die, the bot doesn't resurrect.

After the bot chickens out of a map for any reason, can the bot have the option to start a new map instead of going back to the old map 5 more times?

Tried the same thing before. Fairly sure map names are not supported in any way.

No aero. Just the basic Win7 theme (with bigger borders compared to classic). At this point I can confirm wrong window border size affects where the bot clicks.

The "ExiledBot" string still shows up in the process description. Please randomize that too.

Fixed the problem by changing my windows theme from classic to default and changing the windows display scale from 120% to 100%. Looting seems rock-solid now. I think the height of the window top-border has an effect on the bot's coordinates. It seems (0,0) is the top-left corner of the entire window (including the window border), so if your border is too big/small, it'll shift the bot's Y-coordinates down/up. But I could be wrong. It all depends on whether Alk used GetClientRect or GetWindowRect. Hopefully this is of some help.

It'd also be nice if the bot no longer clicks on strongboxes since these boxes automatically open when all box-mobs are killed.

Thanks for the update. I just tried again on a different pc and the bot had no problems with looting.... edit: nvm. the cursor still gets stuck when there are many items on the ground.

Looting failure rate is pretty high now because the bot no longer moves the cursor around to find what's on the ground. When the above happens, the bot gets stuck and the last line of the log shows: Rotten Entity not Ccleaned detected: address 554b1ef8, id 0ee9 Anyone else having the same problem?

+1. I'll pay $30 just to see this fixed. For now this little bug kind of cripples the whole chancing/map-upgrading feature. Would really appreciate a fix.

I agree with all the complaints. Hopefully someone on the EB team could explain why the bot sometimes has trouble accurately getting an item's coordinate on the screen. I know some coding and want to help out.