Repository navigation
Confirm on a real client that a stopped bot or a dying creature no longer snaps back #570
Description
Expected. A Character or creature that stops mid-walk halts exactly where the client has drawn it. It does not snap back toward the position the server last wrote on its 500 ms movement tick.
Actual (at 87109e3c). The code is fixed. stop_where_rendered places the mover at its interpolated position before emitting the zero-length stop leg (tick/mod.rs#L765-L783), and the death stop calls it (death.rs#L566). The playerbots Package's runner stop calls the same function (playerbots/src/runner.rs#L1003). Nobody has watched this on a real client yet.
How to check. On a Realm with the playerbots Package, watch a bot mid-leg on a bent path while a decision interrupts it, a cast starting, or the controller switching. It must halt where it is drawn and face its next waypoint, not snap back. Separately, kill a creature mid-walk and watch its corpse land where it was drawn, not at its last ticked point.
Done when. Both observations are recorded here, with the client build and the commit. The related snap-back on a path renewal was fixed in #612.
Activity
Mathih13 commentedon Oct 3, 2026
Both halves are merged:
5fd77c1) addedstop_where_renderedand fixed the death stop.dd2fac7) makes the runner stop where the Route Path renders the bot. Its test fails with the runner change reverted.This issue stays open for the real-client check: watch a bot on a bent path when a decision interrupts it mid-leg (a cast starts, or the controller switches). It should halt where it is drawn, not snap back, and face the next waypoint. Also watch a creature killed mid-walk.
The related snap-back on a path renewal is tracked in #608.
[-]fix(playerbots): a bot stopped between a Route leg end and the creature tick snaps back short[/-][+]Confirm on a real client that a stopped bot or a dying creature no longer snaps back[/+]