[Issue Report]: goatmen minions of blighthorn do snapback charges while tethered

[FitzRoyX]

Operating System

Windows x64

DevilutionX version

1.5.4

Describe

I don't have the savefile for this anymore, but this video I took a while back shows some strange buggy interplay between tether and charge. Can't remember if I've ever seen a rhino do this.

goatmenchargebug2.mp4

To Reproduce

find blighthorn minions, lure them to the edge of their tether radius and stand at a certain angle?

Expected Behavior

No response

Additional context

No response

[StephenCWills]

... stand at a certain angle?

Perhaps it has something to do with the goat's surroundings, like if the charge is interrupted by collision on the very first frame. Do you still have the save file, and can you share it? That would make it significantly easier to reproduce the angle and surroundings.

[AJenbo]

Having a save or seed infor for this would have bene very helpful in figuring out what is going on.

[FitzRoyX]

oh I think I found it
single_9.zip

[StephenCWills]

Observe the solid table in the following image.

Both goatmen are trying to charge through the tile to their NE. In the case of the goatman in front, that would be the solid tile NW of the door. In the case of the goatman in back, that would be the tile occupied by the goatman in front. The reason this is so obvious is because the tethering is making them stand still in such an awkward position where there's no clear line to charge you, but this is ultimately kind of a mixture of #2232 and #6693.

Also note that I loaded this up in vanilla and saw exactly the same behavior.

[kphoenix137]

Close as duplicate?

[AJenbo]

Uplicate of what?

[StephenCWills]

If we tweak LineClearMissile() to be consistent with the path a missile actually travels, it would fix this as well as #6693. If we find a way to resolve #2232, then the goats wouldn't be stuck in a position that causes them to keep attempting to charge through each other and through walls. Therefore, this issue is somewhat ambiguous in that it could be a duplicate of either or both those other issues, and it doesn't really describe anything distinct that the other two issues didn't already cover.