Click the green flag again after the last King Nickel starts jumping to avoid timing issues. This project is testing the precision of the wait block. There are 22 clones of King Nickel, and each one has his own clone number shown above him. Using that number, each clone follows the code in the forever loop that's in the top-left corner. The first thing I noticed while watching this was that the clones were jumping in groups, meaning that some clones were perfectly synced together with other clones. These groups were clones 0-3, 4-6, 7-9, 11-13, 14-16, 17-19, and 20-21 (clone 10 was alone). But as I let the project run, these groups slowly became out of sync. Since Scratch runs at 30 FPS, I had always assumed that the wait block just rounds to the nearest one-30th of a second, which would explain why there were groups. But now, I'm not sure if that's entirely accurate.
