IMPORTANT: There are times where [Wait () frames] custom block won't actually solve all your timing issues (mainly for music synced animations). In this case, timer block is better for sync. New project is here: https://scratch.mit.edu/projects/513124730/ EDIT: Use 'change volume by (0)' instead of 'move (0) steps', if you're worried about size/position hack breaking when you use the block. EDIT 2: Timing by 'seconds' is *probably* better if you need the music sync, but using Wait () seconds has a 1 frame delay for no reason... may do testing on 'wait for () beats'. A very easily memorisable set of 2-3 blocks that allows you to time everything by frames rather than seconds. You shouldn't run into that infamous 'desync by lag' problem again. (You'll still have lag, but timing shouldn't just break outright at the very least) The required code is tucked inside neatly. Please share with others if you can. Use left and right keys to navigate the slideshow... presentation... whatever you want to call it. Music is Bakemonogatari Medley. Post Analysis Everything that works with "Wait ( ) frames" > One exception to all blocks stated. ANY TIMED BLOCK will have a 1f delay within itself, however they will not trigger the requirement for the loop itself having a 1f delay. In most situations, this doesn't matter, however, there are some... strange circumstances that may trigger said requirement for loop having 1f delay, so it's not reliable. - Any motion block (Using rotation will not break position hack) - Any looks block, with the following exceptions: > timeless say/think block MUST have input and must also be shown to allow delay > hide blocks do not work > layer changes also do not work - Sound blocks that change volume or sound effect Anything else does not trigger the 1f delay.
