movementStopped does not catch the destination tileSee original GitHub issue
After some testing, I’ve noticed that
movementStopped doesn’t register on the tile you stop moving on, but instead the tile behind you, in the direction you came. For example, if you’re on (1, 1) and you move right to (4, 1), then the position you get in
movementStopped is (3, 1).
I don’t imagine this behavior is intentional, and it really messes with using this observable for it’s intended purpose.
- Created 2 years ago
- Comments:10 (5 by maintainers)
Top GitHub Comments
Haha, working perfectly! Thanks a ton for your work, man. If you ever open a $5/mo sponsor spot, lemme know 😉