Honestly, I think I think your code is too long for someone to debug using pictures.
So right now when your program starts it reserves memory for all of those global variables and stores their initial value.
Then it gets to line 1 and says to itself "Okay, I need to update that text with varScore twice every tick"
Then it gets to line 2 it says "This event is true, so lets do the action."
Then it goes down to line 338 and executes that function call. Turning all of those things to invisible. (By the way we can't see any of the object in your actions because the names are hidden in your pictures.)
So after the program does everything in that function it goes back to line 3.
The conditions of the event on line 3 - 11 are all false at this point so it skips them and continues to the next line.
So I assume at some point the conditions of the event on line 5 become true. So it's going to go to line 365 for the function call. But since the function on line 365 is empty it will immediately go back to line 6. So that was basically unneeded code as it is now.
I think I'd start debugging by looking at where you are changing Active_level. It's easy enough to do in C2 by clicking on the Events tab and entering in Active_level in the search field. So you can see exactly where it's used. In your images... not so easy...