# What does sleep do in the pause menu?

**URL:** <https://forum.makecode.com/t/what-does-sleep-do-in-the-pause-menu/3346>\
**Category:** Arcade\
**Created:** [September 3, 2020, 9:10pm UTC](https://forum.makecode.com/t/what-does-sleep-do-in-the-pause-menu/3346 "2020-09-03T21:10:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![UnsignedArduino](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/unsignedarduino/32/592_2.png) [@UnsignedArduino](https://forum.makecode.com/u/UnsignedArduino)\
**Post date:** [September 3, 2020, 9:10pm UTC](https://forum.makecode.com/t/what-does-sleep-do-in-the-pause-menu/3346/1 "2020-09-03T21:10:30Z")

</div>

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

What does it do? Doesn’t do anything noticeable on hardware either.

---

<div class="post-metadata">

**Author:** ![richard](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/richard/32/5417_2.png) [@richard](https://forum.makecode.com/u/richard)\
**Post date:** [September 3, 2020, 10:09pm UTC](https://forum.makecode.com/t/what-does-sleep-do-in-the-pause-menu/3346/2 "2020-09-03T22:09:14Z")

</div>

Huh, it should put the hardware to sleep (screen turns off) but you’re right, I don’t see it working on my hardware either. Looks like you found a bug!

---

<div class="post-metadata">

**Author:** ![richard](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/richard/32/5417_2.png) [@richard](https://forum.makecode.com/u/richard)\
**Post date:** [September 3, 2020, 10:11pm UTC](https://forum.makecode.com/t/what-does-sleep-do-in-the-pause-menu/3346/3 "2020-09-03T22:11:21Z")

</div>

I’ve filed an issue for it here: [https://github.com/microsoft/pxt-arcade/issues/2413](https://github.com/microsoft/pxt-arcade/issues/2413)

---

<div class="post-metadata">

**Author:** ![Dreadmask197](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/dreadmask197/32/10494_2.png) [@Dreadmask197](https://forum.makecode.com/u/Dreadmask197)\
**Post date:** [September 3, 2020, 10:24pm UTC](https://forum.makecode.com/t/what-does-sleep-do-in-the-pause-menu/3346/4 "2020-09-03T22:24:26Z")

</div>

How did you guys code this coding engine or something like that?

---

<div class="post-metadata">

**Author:** ![jwunderl](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/jwunderl/32/5308_2.png) [@jwunderl](https://forum.makecode.com/u/jwunderl)\
**Post date:** [September 3, 2020, 10:54pm UTC](https://forum.makecode.com/t/what-does-sleep-do-in-the-pause-menu/3346/5 "2020-09-03T22:54:41Z")

</div>

Good question – the repo richard linked ([https://github.com/microsoft/pxt-arcade](https://github.com/microsoft/pxt-arcade)) is the portion that pulls things together for [arcade.makecode.com](http://arcade.makecode.com); it has stuff that is specific to that site, like the tutorials, theming, links to the simulator, etc.

pxt-arcade has dependencies on other packages (basically the same as extensions - code that lives somewhere else that you use), including things like

- [https://github.com/microsoft/pxt](https://github.com/microsoft/pxt), which contains most of the webapp - things like the home page, the way tutorials / editors work, etc
- [https://github.com/microsoft/pxt-common-packages](https://github.com/microsoft/pxt-common-packages), which contains things like the code for the blocks in the game and sprites categories
- [https://github.com/microsoft/pxt-blockly](https://github.com/microsoft/pxt-blockly), which has code related to the blocks themselves - how they’re created, what they look like, etc
- and a bunch more!

Which end up working together to create the editor! Most of the stuff is written in TypeScript (similar to the javascript you’d find / write within the editor itself), though there is a variety of things within the repo - documentation, html (a language that helps describe the structure of a website), css / less (languages that describe how a website looks), etc. And it’s important to note that not everything came at once; just like if you’re building a game in arcade, you build larger things piece by piece over time.
