Boss battle misjudgement

[JueXiuHuang]

Sometimes bot will misjudge that it enter boss battle successfully(In normal combat), but the fleet was stuck somewhere.
Boss Battle did show on map, but bot entered battle with another enemy fleet.

[emelrad12]

Hmm after some investigation, it seems out that if it gets stuck, it attacks randomly, after getting unstuck it attacks also randomly but it thinks that it is attacking the boss, which is false. I will try running it with max fleets to clear, so it kills everything before the boss.

Edit: On further investigation seems like it remembers the old boss coords, even when the camera has moved.

[observeroftime02]

Same issue here. I have it set up to grind 3-4 for example, with a single fleet, and it now frequently decides the boss battle is done after like 4 or 5 engagements, even though the boss node is still on the map. I think the issue comes from enemies blocking the way to the boss, so after a few unsuccessful attempts to move towards the boss, it falls back on fighting a node that's available, and after that one is completed it thinks the boss was defeated, even though the boss node is still on screen.

Maybe add some checks that tell it:

1. When a boss node is found
2. If the path towards the boss node is blocked
3. Fight an available node
4. Recheck if the boss node is still on the map
5. Try to move towards the boss node again.

I'll get some screenshots for this in a bit when it happens again.

Here you can see it trying to engage the boss, not being able to reach it, then clicking on the wrong squares until it blacklists them, then fighting another enemy, and thinking the boss is defeated.

Here's the console log

[emelrad12]

Same issue here. I have it set up to grind 3-4 for example, with a single fleet, and it now frequently decides the boss battle is done after like 4 or 5 engagements, even though the boss node is still on the map. I think the issue comes from enemies blocking the way to the boss, so after a few unsuccessful attempts to move towards the boss, it falls back on fighting a node that's available, and after that one is completed it thinks the boss was defeated, even though the boss node is still on screen.

Maybe add some checks that tell it:

1. When a boss node is found
2. If the path towards the boss node is blocked
3. Fight an available node
4. Recheck if the boss node is still on the map
5. Try to move towards the boss node again.

I'll get some screenshots for this in a bit when it happens again.

Here you can see it trying to engage the boss, not being able to reach it, then clicking on the wrong squares until it blacklists them, then fighting another enemy, and thinking the boss is defeated.

Here's the console log

I have made a pull request that should fix the issue you can clone it at https://github.com/emelrad12/ALAuto

while waiting for it to be merged or fixed

[observeroftime02]

Thanks a bunch, I'll give it a go next time I need to use it 👍

[empathist-dot]

Reporting the same issue. I'll try using emelrad12's pull for now.

[empathist-dot]

Emelrad's fix resulted in a new possible issue where the bot can't see the boss when it's behind user fleet. It just keeps searching for the boss.

Here's a gif showing this problem

[emelrad12]

Emelrad's fix resulted in a new possible issue where the bot can't see the boss when it's behind user fleet. It just keeps searching for the boss.

Here's a gif showing this problem

I am sorry but that shouldn't be from my fix, the game searches for the boss icon, and it is well, obscured. I am afraid not much can be done there.

[sant0hat]

It's not only that though, at 3-4 the bot also gets stuck sometimes. It detects it cant get to the boss and searches for a blocking mob, it then attacks that mob. However sometimes the detected mob is one tile away, combat is started but the bot gets stuck in the pre-combat screen. It's not actually iniatating battle it still thinks it needs to search for a mob. The mob is one tile away, but not visually blocked by my fleet. I am using a bossfleet, without one this issue doesn't happen

stuckatcombatscreen.txt

[probabilitystatistic]

It's not only that though, at 3-4 the bot also gets stuck sometimes. It detects it cant get to the boss and searches for a blocking mob, it then attacks that mob. However sometimes the detected mob is one tile away, combat is started but the bot gets stuck in the pre-combat screen. It's not actually iniatating battle it still thinks it needs to search for a mob. The mob is one tile away, but not visually blocked by my fleet. I am using a bossfleet, without one this issue doesn't happen

stuckatcombatscreen.txt

This also happens in my case but I think it's not related to Emelrad's fix but just an unsafe execution in the original repository. You can have a look at #146 for the description and a simple solution. I'm also using Emelrad's fix(though for me boss misclassification still happens) and after the modification it hasn't stucked in the pre-battle screen anymore in my case.