I have a projectile. It is invisible and just detects collisions.

I have an /obj that serves as the appearance for the projectile. The projectile has a limited range, so the /obj is shifted with animate() to the projectile's end position (it assumes no collision, it disappears when the projectile hits something) so it smoothly flies, client-side. (The camera is fixed so the appearance is always visible)

I fire only one projectile at a time. When I fire the projectile, the /obj is set to the initial position of the projectile, its pixel offset is reset to zero, and its animation plays.

If I fire the projectile while it is already flying, I reuse it by re-initializing it. This is where the bug is.

The Bug:
The animation of the appearance /obj does not always reset in Dream Seeker. If the already-flying projectile is fired again, the appearance glides from its current, mid-flight position to the end position, slower than usual because its distance is shorter. It should instead snap back to the projectile's initial position and play the animation from there.

The webclient does not have this bug.

I'll have a test project eventually...