andre_rifaut wrote:

If there would be a “pause all” just like the “stop all” this would be easy.
Without that you have to pause yourself each active sprite, clones, the “timers” if you use them, …

It would be difficult to provide to the user the possibility to pause at any time.

One way to provide a pause functionality , is to design your game with specific phases that allow a possible pause.
This is highly dependent on the game.

Different ways to do this are the following:
1) You can design your game so that the red flag (or the use of “stop all”) would put the game in a state that can be restared with the green flag (or a global message “restart” for instance). Note that in this case, the clones will be irremediably “killed”, so do not do that when clones are necessary.
2) Allow your game to store its full state in a string variable or a list. In that case the state of the game could be restored later. If you store it in a cloud var, you can use that to pause the game for a number of days.
3) Insert in all scripts a “wait until” with the pause condition. If your game is well designed you should be able to minimize the number of scripts containing the “wait until”.

In all case, you will not be able to have a perfect real-time synchronization between all scripts pauses.

This is a difficult problem.

if <If you have a script like this,
[scratchblocks]
when green flag clicked
forever
    if <> then
    
end
end
[/scratchblocks]> then
    
end[scratchblocks]

if <> then
if <> then
if <> then
if <> then
else
wait until <>
repeat until <>
repeat until (mouse y)(mouse y)<key [ v] pressed?>
ask <color [#f0f] is touching [#0f0]?> and wait
    
end
    
end
    
end
    
end
    
end
    
end
    
end
[/scratchblocks]