# Game Update thing

**URL:** <https://forum.makecode.com/t/game-update-thing/37439>\
**Category:** Help\
**Created:** [June 20, 2025, 9:13pm UTC](https://forum.makecode.com/t/game-update-thing/37439 "2025-06-20T21:13:18Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![4SYLLABLES](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/4syllables/32/21357_2.png) [@4SYLLABLES](https://forum.makecode.com/u/4SYLLABLES)\
**Post date:** [June 20, 2025, 9:13pm UTC](https://forum.makecode.com/t/game-update-thing/37439/1 "2025-06-20T21:13:18Z")

</div>

Hi! I’m wondering whether I should change all my game update blocks to forever blocks. A lot of mechanics in my game are time based and I don’t want the game balance to be different across devices. Thank you for reading!

---

<div class="post-metadata">

**Author:** ![4SYLLABLES](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/4syllables/32/21357_2.png) [@4SYLLABLES](https://forum.makecode.com/u/4SYLLABLES)\
**Post date:** [June 20, 2025, 9:56pm UTC](https://forum.makecode.com/t/game-update-thing/37439/2 "2025-06-20T21:56:06Z")

</div>

I should’ve mentioned, I’m relying on the on game update blocks to resume timers after pausing. Does anyone know a way to have both?

---

<div class="post-metadata">

**Author:** ![WoofWoof](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/woofwoof/32/32523_2.png) [@WoofWoof](https://forum.makecode.com/u/WoofWoof)\
**Post date:** [June 22, 2025, 2:39am UTC](https://forum.makecode.com/t/game-update-thing/37439/3 "2025-06-22T02:39:04Z")

</div>

Both Forever and On Game Update blocks will be unreliable for time keeping, though On Game Update blocks would theoretically be much more effected by different devices, and forever blocks would technically be better. I would consider using delta time in your programs, which is what normal sprite movement uses to keep sprites looking the same speed on different devices.

---

<div class="post-metadata">

**Author:** ![WoofWoof](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/woofwoof/32/32523_2.png) [@WoofWoof](https://forum.makecode.com/u/WoofWoof)\
**Post date:** [June 22, 2025, 2:39am UTC](https://forum.makecode.com/t/game-update-thing/37439/4 "2025-06-22T02:39:21Z")

</div>

Can you elaborate on what you mean by this second comment? I can’t tell what exactly you’re asking.

---

<div class="post-metadata">

**Author:** ![4SYLLABLES](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/4syllables/32/21357_2.png) [@4SYLLABLES](https://forum.makecode.com/u/4SYLLABLES)\
**Post date:** [June 22, 2025, 4:25pm UTC](https://forum.makecode.com/t/game-update-thing/37439/5 "2025-06-22T16:25:49Z")

</div>

I mean that I’m using on game update blocks to resume timers after pausing. For example, I will create a variable for whether or not the timer is active, a variable for the time left, and a variable for the starting time. When the first variable I mentioned is true, the timer variable will go down every certain amount of game updates. When it hits 0, the first variable will be set false and the timer variable will be set to the starting time variable. I was wondering if there was a way to make timers consistent across devices and resume timers after pausing. Thanks for the feedback!

---

<div class="post-metadata">

**Author:** ![AlexK](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/alexk/32/33339_2.png) [@AlexK](https://forum.makecode.com/u/AlexK)\
**Post date:** [June 22, 2025, 4:29pm UTC](https://forum.makecode.com/t/game-update-thing/37439/6 "2025-06-22T16:29:05Z")

</div>

You may want to include a sample to show what you’ve tried and what isn’t working.

Also, if you’re implementing timers, then this may help.

> [@Stopwatch Part II: Advanced Stopwatch](https://forum.makecode.com/t/stopwatch-part-ii-advanced-stopwatch/3827):
>
> Let’s continue with the ideas from my first post on creating a stopwatch. If you have not yet created the basic stopwatch, then you’ll probably want to head back to the first post: [Making a Stopwatch](https://forum.makecode.com/t/making-a-stopwatch/3814) Now, let’s extend this basic stopwatch with some added functionality. Finished code Here is a link to the finished version of the project. Feel free to run the project in the simulator. As before, if you’re planning on walking through this journey with me, then please don’t look at the code yet. …

---

<div class="post-metadata">

**Author:** ![WoofWoof](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/woofwoof/32/32523_2.png) [@WoofWoof](https://forum.makecode.com/u/WoofWoof)\
**Post date:** [June 22, 2025, 4:38pm UTC](https://forum.makecode.com/t/game-update-thing/37439/7 "2025-06-22T16:38:45Z")

</div>

Yeah, delta time will also be useful for that too! Just a little bit of logic/math to get pausing working ofc. I don’t remember if delta time is normally in blocks, so you might have to find an extension for it.
