Dragon Fogel
Level: Smitemaster
Rank Points: 2763
Registered: 06-21-2014
IP: Logged

File: Slayer bug.hold (850 bytes)
Downloaded 1 times.
License: Public Domain

In the attached hold, the slayer starts near a soldier behind a door. He wants to open the door to reach his target, so he sends his wisp there.

However, get Beethro close to him and lead him to somewhere else in the room using close-range manipulation. Now get Beethro far enough away that the slayer no longer uses close-range tactics. The slayer goes for the orb, even when Beethro is close enough to be his target. I didn't test this with a pressure plate, but that probably works in the same way.

Now, there's behavior where Halph and slayers don't recalculate paths unless something gets in the way, and this has been used in published rooms. It's weird but we basically decided to accept it. But in this case, the slayer's path can be interrupted and he'll still go for the orb even if he has a target, and that feels like maybe it shouldn't happen.

Proposed fix to this behavior: in this situation, the slayer will target the orb until he has reason to evaluate another path. At that point, he will not keep going for the orb if he has a path to his current target.

This is a pretty specific edge case that I only found because I was messing with a room idea where a slayer and soldier have a path to each other after a door opens, so even though I know we're wary of changing slayer behavior, I don't think this would break any rooms.