Piggygirl3838 wrote:

Support.

My question would be:

Would it pause forever blocks? I think so, but the forever block is intended to go… well… forever!

This might be confusing, but I agree with all of the supporters

(mouse y)
(mouse x) //What about these blocks, would they continue to report the mouse x and y?

medians wrote:

Bringing this topic up.

-ElectronicArts- wrote:

----Windows---- wrote:

Support, it would help animators to debug animations faster.

-ElectronicArts- wrote:

what will happen to multiplayer games lol

It only affects you, and not the cloud variables.

you can disconnect in multuplayer games

ThisIsTemp1 wrote:

(#248)

-ElectronicArts- wrote:

----Windows---- wrote:

Support, it would help animators to debug animations faster.

-ElectronicArts- wrote:

what will happen to multiplayer games lol

It only affects you, and not the cloud variables.

you can disconnect in multuplayer games

Disable if it uses cloud variables.

julmik6478 wrote:

Support. There is pause button in scratch browser extension and scratch mods like turbowarp and codeskool So why not in Vanilla scratch?

DangerPuppy10 wrote:

(mouse y)
(mouse x) //What about these blocks, would they continue to report the mouse x and y?

Blue_Blaze56 wrote:

(#256)
This idea is awe-inspiring! When you catch an issue in your code and take the initiative to correct it immediately, it feels like reviving the entire project. It’s similar to hitting a reset button at the right moment, allowing you to maintain clarity and focus. By addressing problems as they arise, you enhance the overall quality of your work and cultivate a habit of being alert and proactive in your development process. This approach ensures that your project remains on track and continues to evolve positively.*

*Source = Grammarly

"Follow me! I'm new to scratch" - @Blue_Blaze56

mrsteve wrote:

scimonster,

I understand, my concern is that pausing timers could create unintended consequences and potentially change the behavior of existing projects (or new ones created in 1.4).

Ie: a “trick” to beat a game that uses a timer, where you pause and then move things around, then hit resume. Or a strategy game that times your moves and you pause to think about it to avoid the timer expiring or losing points.

Another case would be collecting data in a cloud list on times to solve a maze for an existing contest. One could use pause to “improve” your score.

In fact the above things could happen even if they didn't use a timer but used a counter that incremented/decremented in a forever loop.




So how to deal with the above cases…

• Well we could have two types of timers (just to confuse kids and raise the floor a bit ) where one is pausable and one isn't.

• We could have blocks to detect “Pause hit”

• We could have a timer option (pause on pause, or not)
  
  

Okay all that said, I don't even know if such projects exist or how many actually use timers and for what purpose. And if they did exist and kids found “tricks” (I HATE the word “cheats”) it could be argued that could create a learning opportunity.

hmmmmm….. In any case more thought needed.

jromagnoli wrote:

What about this work-around?

when [space v] key pressed
wait until <not <key [space v] pressed?>>
stop [other scripts in sprite v]
broadcast [stop v]
wait until <key [space v] pressed?>
when I receive [stop v] //This script goes in the other sprites.
stop [other scripts in sprite v]
stop [this script v]