# Updates YOU want to see in Makecode

**URL:** <https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713>\
**Category:** Forum Feedback\
**Tags:** game, make, extension, demo, music\
**Created:** [May 16, 2025, 7:39pm UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713 "2025-05-16T19:39:14Z")\
**Posts on this page:** 20\
**Page:** 11

<div class="post-metadata">

**Author:** ![TheGooberEarth](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/thegooberearth/32/36693_2.png) [@TheGooberEarth](https://forum.makecode.com/u/TheGooberEarth)\
**Post date:** [December 30, 2025, 1:49am UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/202 "2025-12-30T01:49:34Z")

</div>

![image](https://us1.discourse-cdn.com/flex020/uploads/makecode/original/3X/7/1/71048544c824592f18bc1de9c2cf0a3ddd592edd.png)

1. should be added and support
2. what is so unreliable because for pixel per frame it would be better for people with better computer to run the game better and pixels per second is super reliable

---

<div class="post-metadata">

**Author:** ![TheGooberEarth](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/thegooberearth/32/36693_2.png) [@TheGooberEarth](https://forum.makecode.com/u/TheGooberEarth)\
**Post date:** [December 30, 2025, 4:01am UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/203 "2025-12-30T04:01:03Z")

</div>

elaborate on no sound and visual updates please, so would it be in the editor where the visuals don’t change or, in the simulator they don’t change, same with the no sound

---

<div class="post-metadata">

**Author:** ![Luke](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/luke/32/32519_2.png) [@Luke](https://forum.makecode.com/u/Luke)\
**Post date:** [December 30, 2025, 4:14pm UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/204 "2025-12-30T16:14:19Z")

</div>

I was just thinking of the editor since you can just hide the sim

---

<div class="post-metadata">

**Author:** ![AgentBoom](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/agentboom/32/16635_2.png) [@AgentBoom](https://forum.makecode.com/u/AgentBoom)\
**Post date:** [December 31, 2025, 2:19am UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/205 "2025-12-31T02:19:48Z")

</div>

> [@babol](#):
>
> editor optimization. it lags like hell when editing a project significantly less advanced than the original super mario bros.

Maybe try turning off your wi-fi? works like a charm for me!

---

<div class="post-metadata">

**Author:** ![babol](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/babol/32/27355_2.png) [@babol](https://forum.makecode.com/u/babol)\
**Post date:** [January 5, 2026, 6:04pm UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/206 "2026-01-05T18:04:19Z")

</div>

the average 2D game engine (and the average retro game that makecode arcade is trying to replicate), uses a pixels per frame velocity system, for good reason.  
pixels per second sucks for EVERYTHING. it causes insane inconsistencies with games because of the lack of optimization, and any bit of lag would instantly break the game loop. cone’z broken bonez and coneguy’s christmas bash, for example run terribly on mobile devices with the player object being sent at unnecessarily high speeds because of the low FPS.  
these 2 issues were the only reason cone’z broken bonez, alongside AUAPTMR switched engines.  
“super reliable” is not REMOTELY ACCURATE. i’ve quit makecode entirely, and every time i think of coming back, i am reminded of the completely unreliable mess that is pixels per second. i had a sonic engine recreation in works, cancelled. i was making an AUAPTMR remaster, cancelled. i was making cone’z broken bonez, moved engines.  
what i’m getting at is : pixels per frame is more reliable than pixels per second in every way.  
no, man. people aren’t gonna make hyper advanced games with whatever insane deltatime stuff newer games have. we’re making the game maker games, the 2D classic ones. you know, the super mario bros and the sonic master systems. this one change could make makecode arcade a much more reliable engine, instead of making itself motivation to make a retro engine in scratch just to work in the same limited conditions, except with significantly better features. yes, i thought of that.

---

<div class="post-metadata">

**Author:** ![Rune](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/rune/32/18951_2.png) [@Rune](https://forum.makecode.com/u/Rune)\
**Post date:** [January 5, 2026, 10:14pm UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/207 "2026-01-05T22:14:15Z")

</div>

Dude, you got em mixed up. P/second does not rely on frame rate. Also, there’s an extension to get the raw delta, decide that by 1000 I think and it gives you seconds since last frame.

---

<div class="post-metadata">

**Author:** ![babol](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/babol/32/27355_2.png) [@babol](https://forum.makecode.com/u/babol)\
**Post date:** [January 8, 2026, 5:37pm UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/208 "2026-01-08T17:37:13Z")

</div>

if you played either CBB or CCB, you’d see the results.  
pixels per second does get affected by framerate. at slower framerates, the game sends the object at a higher speed to make up for the lost time. and yes, i’ve tried the deltatime solution. does not work.  
the lone addition of pixels per frame would also allow making the implementation of PPS completely optional, although not necessary.  
just add it and make it a toggle. best of both worlds, really. the 2 games i’ve mentioned show just how badly this velocity system affects makecode games.

---

<div class="post-metadata">

**Author:** ![Rune](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/rune/32/18951_2.png) [@Rune](https://forum.makecode.com/u/Rune)\
**Post date:** [January 8, 2026, 6:25pm UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/209 "2026-01-08T18:25:58Z")

</div>

Ok, you’re clearly better informed than me.

---

<div class="post-metadata">

**Author:** ![CopySprite](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/copysprite/32/36725_2.png) [@CopySprite](https://forum.makecode.com/u/CopySprite)\
**Post date:** [February 18, 2026, 6:20pm UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/210 "2026-02-18T18:20:07Z")

</div>

A feature that I’ve recently been thinking about is the fullscreen simulator.  
I think it would be nice to have an option to hide the controls and make the actual game take up the screen.  
Unless that already exists…

---

<div class="post-metadata">

**Author:** ![Astronomicality22](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/astronomicality22/32/18365_2.png) [@Astronomicality22](https://forum.makecode.com/u/Astronomicality22)\
**Post date:** [February 18, 2026, 10:51pm UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/211 "2026-02-18T22:51:37Z")

</div>

I think that there’s a setting under the little window on the far left of the site in the editor for a full fullscreen.

---

<div class="post-metadata">

**Author:** ![TheGooberEarth](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/thegooberearth/32/36693_2.png) [@TheGooberEarth](https://forum.makecode.com/u/TheGooberEarth)\
**Post date:** [February 18, 2026, 10:54pm UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/212 "2026-02-18T22:54:43Z")

</div>

Try this

> [@Makecode Full Screen Options?](https://forum.makecode.com/t/makecode-full-screen-options/41521/5):
>
> Use this URL template and replace the id with the id of your game and done
> 
> [https://arcade.makecode.com/---run?id=S05763-84768-62261-42850&hideSimButtons=1&fullscreen=1&autofocus=1&nofooter=1](https://arcade.makecode.com/---run?id=S05763-84768-62261-42850&hideSimButtons=1&fullscreen=1&autofocus=1&nofooter=1)

this should work

---

<div class="post-metadata">

**Author:** ![Awesomefreez](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/awesomefreez/32/24832_2.png) [@Awesomefreez](https://forum.makecode.com/u/Awesomefreez)\
**Post date:** [February 19, 2026, 7:48pm UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/213 "2026-02-19T19:48:16Z")

</div>

True Multiplayer not splitscreen. (This one probably will be hard to implement right now)

---

<div class="post-metadata">

**Author:** ![Iro](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/iro/32/34749_2.png) [@Iro](https://forum.makecode.com/u/Iro)\
**Post date:** [February 19, 2026, 11:34pm UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/214 "2026-02-19T23:34:21Z")

</div>

Uh, maybe like soft bodies or something, specifically for moving platforms and such.

---

<div class="post-metadata">

**Author:** ![Jakethesnake23](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/jakethesnake23/32/17617_2.png) [@Jakethesnake23](https://forum.makecode.com/u/Jakethesnake23)\
**Post date:** [February 23, 2026, 7:34pm UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/215 "2026-02-23T19:34:38Z")

</div>

And especially with separate player cameras

---

<div class="post-metadata">

**Author:** ![Air](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/air/32/26413_2.png) [@Air](https://forum.makecode.com/u/Air)\
**Post date:** [February 26, 2026, 11:05pm UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/216 "2026-02-26T23:05:08Z")

</div>

a repeat until block would be so useful

---

<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:** [February 26, 2026, 11:05pm UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/217 "2026-02-26T23:05:30Z")

</div>

is that not a while loop?

---

<div class="post-metadata">

**Author:** ![Peau12](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/peau12/32/29299_2.png) [@Peau12](https://forum.makecode.com/u/Peau12)\
**Post date:** [February 26, 2026, 11:08pm UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/218 "2026-02-26T23:08:14Z")

</div>

A (number) to (number) block too! (Not pick random!)

---

<div class="post-metadata">

**Author:** ![Air](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/air/32/26413_2.png) [@Air](https://forum.makecode.com/u/Air)\
**Post date:** [February 27, 2026, 11:34am UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/219 "2026-02-27T11:34:17Z")

</div>

yes, but up until quite recently (sometime last year) I didn’t know how to use that properly, so I thought about it for quite a while, and I feel like some people new to makecode wouldn’t know that.

---

<div class="post-metadata">

**Author:** ![goofycat911](https://avatars.discourse-cdn.com/v4/letter/g/54ee81/32.png) [@goofycat911](https://forum.makecode.com/u/goofycat911)\
**Post date:** [February 27, 2026, 11:34am UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/220 "2026-02-27T11:34:21Z")

</div>

cloud variables so i can make a global leaderboard for my school project

---

<div class="post-metadata">

**Author:** ![DimonSw0rd11](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/dimonsw0rd11/32/32564_2.png) [@DimonSw0rd11](https://forum.makecode.com/u/DimonSw0rd11)\
**Post date:** [February 27, 2026, 9:41pm UTC](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713/221 "2026-02-27T21:41:17Z")

</div>

I dont expect this to be seen considering how late i am but an “on song finish” block, i dont want to be forced to put an entire song into 1 code block as its harder for me to edit

[Previous page](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713.md?page=10)

[Next page](https://forum.makecode.com/t/updates-you-want-to-see-in-makecode/36713.md?page=12)
