***** IMPORTANT NOTE: this project is broken due to some changes with "touching sprite" behaviour in Scratch 3. To 'fix' it, please disconnect the touching test scripts in each of the two sprites. Also, the start-up order of scripts in Scratch 3 no longer depends on the script layer-order as it did in Scratch 2. Instead it depends on the creation order of the scripts' hat blocks. That means you have to swap the hat blocks between the two scripts instead of just moving a script. Once you've done that you should find the project fails to do anything every other time you click GF (i.e. you have to click GF *twice* to make it do what it was meant to do). READ BELOW, and READ COMMENTS IN PROJECT, to understand why it happens like this... ************************************************************* We've all done it at some point... expected Scratch to run our scripts in a particular order... and got burned for it later on... I've seen this kind of thing cause problems so often that I decided it was time to make a simple demonstration project about it. When it comes up again in the forums, I'll be able to point towards this project and hopefully it will help to explain how to rewrite the scripts so it doesn't happen again! :) If you want to understand more about how Scratch decides the order to start up scripts for a particular event, both within a sprite and across sprites, then take a look at this demo project: https://scratch.mit.edu/projects/18490761/
