@Ambush @sophia71205 @William04GamerA @Ducks_Happy @memorablechickenyay @Iamtrash
As others have said, the number is milliseconds & the sound plays for however long it is regardless of the “and Wait” #
However, what the Wait # represents is how long the Player waits before continuing on to the next code block from the start of the sound.
So, for example, Start Sound and Wait 0 (just like the regular Wait 0 would continue the code on the next “frame”. At 60 fps, that would be 16.7 milliseconds (1/60) later. If the next block was a second Play Sound this would play 2 sounds at almost the same time.
If you want 2 sounds to play one after the other, the 1st Wait # would need to correspond to the length of the 1st sound which you could find through trial and error (just keep adjusting the Wait # until it sounds right).
Using other values (shorter than the length of the 1st sound) can either created layered sounds with a lag as specified by the Wait # or (longer than the length of the 1st sound) delays between the sounds.