# Makecode (blocks) bug

**URL:** <https://forum.makecode.com/t/makecode-blocks-bug/11028>\
**Category:** Help\
**Created:** [November 22, 2021, 6:58pm UTC](https://forum.makecode.com/t/makecode-blocks-bug/11028 "2021-11-22T18:58:52Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![shakao](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/shakao/32/113_2.png) [@shakao](https://forum.makecode.com/u/shakao)\
**Post date:** [November 22, 2021, 7:05pm UTC](https://forum.makecode.com/t/makecode-blocks-bug/11028/2 "2021-11-22T19:05:16Z")

</div>

Ah! Thanks so much for reporting this, we released an Arcade update last Friday and it looks like we broke some things in our blocks along the way. We’re aiming to have this fixed in the next day or so, in the meantime you can try the method described here:

> [@iPad problem(s)](https://forum.makecode.com/t/ipad-problem-s/11018/3):
>
> Haha, okay. Looking forward to see this fixed. BTW, a workaround is to override the slider value with an integer pulled in from the block area. Cheers!

or use the standalone `set mySprite x to` block:

![image](https://us1.discourse-cdn.com/flex020/uploads/makecode/original/2X/0/07a6e980931b40e1ec3345ed29da9b1ae5492e1c.png)

to set the x and y. Sorry for the inconvenience, and hopefully it won’t be an issue for very long!

---

_[View the full topic](https://forum.makecode.com/t/makecode-blocks-bug/11028)._
