# Multiple Path Following Bug

**URL:** <https://forum.makecode.com/t/multiple-path-following-bug/45120>\
**Category:** Help\
**Tags:** game, graphics-and-math\
**Created:** [July 29, 2026, 2:06pm UTC](https://forum.makecode.com/t/multiple-path-following-bug/45120 "2026-07-29T14:06:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![CodaKnight](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/codaknight/32/33491_2.png) [@CodaKnight](https://forum.makecode.com/u/CodaKnight)\
**Post date:** [July 29, 2026, 2:06pm UTC](https://forum.makecode.com/t/multiple-path-following-bug/45120/1 "2026-07-29T14:06:08Z")

</div>

Hey guys! I have a question about @jwunderl 's A\* path following extension. It seems that when I try to make multiple enemies follow the same sprite in an game update loop with time or a forever loop with a pause block, they seem to move back and forth every time the loop updates. If someone knows how to fix this bug, the help would be appreciated!

> **[Multiple Sprites Following Player (BUG)](https://arcade.makecode.com/S94140-19295-83634-73516)**
>
> Made with ❤️ in Microsoft MakeCode Arcade.

---

<div class="post-metadata">

**Author:** ![VoxelMaster64](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/voxelmaster64/32/32075_2.png) [@VoxelMaster64](https://forum.makecode.com/u/VoxelMaster64)\
**Post date:** [July 29, 2026, 5:11pm UTC](https://forum.makecode.com/t/multiple-path-following-bug/45120/2 "2026-07-29T17:11:45Z")

</div>

I’m not sure. when I remove the pause(500), they stay completely still. Maybe the first path the enemy is given to go to is the tile its already on?

---

<div class="post-metadata">

**Author:** ![YamJam](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/yamjam/32/29681_2.png) [@YamJam](https://forum.makecode.com/u/YamJam)\
**Post date:** [July 29, 2026, 5:15pm UTC](https://forum.makecode.com/t/multiple-path-following-bug/45120/3 "2026-07-29T17:15:40Z")

</div>

I’m no professional, but I’m pretty sure it’s because the sprites path following resets from the start every time it’s called.
