Nevermind, don't post here.

Add “go to front” in the script “when I start as a clone”.

The problem was that I used “broadcast exit and wait” instead of just a “broadcast exit”.

1234abcdcba4321 wrote:

The problem was that I used “broadcast exit and wait” instead of just a “broadcast exit”.

Huh, that's strange, because as soon as I added a “go to front” block it worked fine.

Yeah, it's one of those projects where you have to press green flag twice for some reason to work. I'm not sure why.

1234abcdcba4321 wrote:

Yeah, it's one of those projects where you have to press green flag twice for some reason to work. I'm not sure why.

In some project you can have a lot of “green hats”.
The user expects some execution order between some of the “green hats”: for instance he expects some variable initalisation in a “green hat” before the occurrence of some message in some other “green hat”.

But the interpreter excutes the “green hats” in some other execution order than expected. When pressing twice, the firsts initalisations were already made and the messages are resent.

If you want to have the right execution order in projects, you should have only one “green hat”, say in the backdrop that raise initalisation messages in the correct order.

This way of doing is also interesting to code different levels of “restarting” the game.

Well, I know. I only have one gf script per sprite (costume, hide, effects, etc.). I fixed it by putting some wait 0.1 secs around, though.