# Sprite/Wall Collision Event Repeated

**URL:** <https://forum.makecode.com/t/sprite-wall-collision-event-repeated/487>\
**Category:** Arcade\
**Created:** [August 26, 2019, 3:10pm UTC](https://forum.makecode.com/t/sprite-wall-collision-event-repeated/487 "2019-08-26T15:10:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mileswatson](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/mileswatson/32/333_2.png) [@mileswatson](https://forum.makecode.com/u/mileswatson)\
**Post date:** [August 26, 2019, 3:10pm UTC](https://forum.makecode.com/t/sprite-wall-collision-event-repeated/487/1 "2019-08-26T15:10:14Z")

</div>

Relevant Issue: [https://github.com/microsoft/pxt-arcade/issues/1242](https://github.com/microsoft/pxt-arcade/issues/1242)

**Describe the bug**  
When a sprite collides squarely with a wall tile, the “on sprite of kind \_\_\_ hits wall \_\_\_” block is called twice.

**To Reproduce**

1. Replicate this image in MakeCode Arcade  
 ![](https://i.imgur.com/kqoLJls.png)
2. Notice that the score is increased twice each time the sprite collides with the green block. This happens in all four directions, as long as the sprite is directly in line with the tile.

**Expected behavior**  
The score should only increase once per collision - the collision event should only be called once.

**Demo**  
 ![](https://i.imgur.com/baXkpYc.gif)

**Desktop (please complete the following information):**

- Windows 10
- Chrome, Firefox
- Arcade 0.14.3, MakeCode 5.21.6

It is very difficult to debug, and so could be off-putting to younger students with little understanding of collision detection.

Can you think of any ways around this?

---

<div class="post-metadata">

**Author:** ![kjw](https://avatars.discourse-cdn.com/v4/letter/k/e79b87/32.png) [@kjw](https://forum.makecode.com/u/kjw)\
**Post date:** [August 26, 2019, 4:53pm UTC](https://forum.makecode.com/t/sprite-wall-collision-event-repeated/487/2 "2019-08-26T16:53:57Z")

</div>

It looks like alignment is a critical factor in triggering this bug.

Having said that, I’m wondering if this is related to [Wall collisions and sprite vy](https://forum.makecode.com/t/wall-collisions-and-sprite-vy/481). That also has _two_ events where the velocity value is the impact velocity. Or is that something else?