kurtz
Member
- Joined
- Jan 15, 2010
- Messages
- 44
- Reaction score
- 0
List of bugs I found by watching the bot work (last version build 84) I think most of them were already reported, anyway:
I'm using a barbarian, tried the generic and the other routine. no difference.
- Does not prioritize mobs, in the middle of the fight goes to open chests and pick loot left behind.
- Does not prioritize goblins, ex: finds a goblin, runs after it, finds more mobs/chests and goes to them. By the time it opens the chests and kills other mobs the goblin is already gone. I still didn't kill one goblin in all my runs. Another thing it also does is picking all the gold the goblin leaves behind when running it should only do this after killing it.
- Tries to use shrines that were already used, fortunately it goes away after trying one time...
- (maybe class related?) Leaves behind mobs almost dieing (rares, champions or even normal ones...), just runs away toward the ending point (using core of arreat profile). If it gets to the ending point, it starts using the town portal, even with mobs attacking him. After a while since he can't teleport the bot starts the countdown to leave the game (10 sec to leave game) while the mobs are beating the crap out of him...
- Sometimes the bot stops and doesn't go anywhere unless I manually move the char to the next pack of mobs...
- HUGE FPS drops when in core of arreat a pack of spiders is close by (more than 10), it shutters like hell. I've tried limiting fps in the game, changing resolution, put everything to low, vsync on and off. nothing works.
- New: Usually it happens with mobs that kite/run away, goes after one mob and stops to go to another... in a pack of champions where we have 3 mobs running away in all directions the bot doesn't focus on one mob at a time.
I'm using a barbarian, tried the generic and the other routine. no difference.
Last edited: