Openkore.com

There are several new bugs now:

1. Sometimes it moves back and forth endlessly on two cells next to each other spamming "no line of sights from xyz". It should backlist those cells and try to move somewhere else, not between two cells which both do not work.

2. Similiar problem, it sees a monster, tries to move to it, moves out of sight, loses its target, tries to route normally again, sees the monster again, tries to reach it and so on...

3. It doesnt like corners. =D Bot often stands at the corner, acting like it can hit a target around the corner.

o= free tile
x= wall
P = player
T = target

oxooo
oxooo
Pxxxx
oooTo

How does it calculate how to hit a target and wether it has LoS?

That's about new code? New, compared with what?

r8099
r8092

If I am not mistaken, before those LoS fixes the bot's biggest problem was it mostly just stood at one point being unable to reach its target sometimes, now it is moving very supsiciously and I had to deactivate LoS check due to this and the other problems mentioned in the other thread. It works with little problems now compared to activated LoS check - works twice as good when judging from exp/h. :/

Better ask the committer.

It would be nice to have some unit tests for that.

unit tests?

Daedalus wrote:There are several new bugs now:

1. Sometimes it moves back and forth endlessly on two cells next to each other spamming "no line of sights from xyz". It should backlist those cells and try to move somewhere else, not between two cells which both do not work.

2. Similiar problem, it sees a monster, tries to move to it, moves out of sight, loses its target, tries to route normally again, sees the monster again, tries to reach it and so on...

3. It doesnt like corners. =D Bot often stands at the corner, acting like it can hit a target around the corner.

i have the same problems while botting at juperos 2, is there any fix to this?

Somebody should revert these changes as the contributor didn't react with anything in this topic.