It's really hard to understand what's going on in your code. The biggest mistake is that events 10, 16, 24 and some others may be executed multiple times. When the condition is true, all actions inside these events are repeated 60 times per second. What's even worse is that you have "Wait" actions inside these events. This creates hundreds of wait-threads which cause a complete chaos.
An easy and dirty fix is to add "Trigger once" to such events, but you should be really careful with this, because when used incorrectly "Trigger once" can cause more problems than you already have.
The correct solution is to stop using so many "Wait" actions and use Timer behavior instead. "On Timer" events are triggered only once, not on every tick. And with Timer you will have complete control over the sequence of events. You can pause or stop timers, which will allow players to skip intro text etc. (Because unskippable intros are bad!)