WesleyDeveloper9
That is not an ideal way to do structure your events.
What will happen is that once the txtPlayerPoints is "16", all the actions will be executed every single tick while that condition is true (60 times a second). So, it will continuously try to stop playing tag 2, restart "Forever Believe" (all you will hear is a buzz), try to destroy the objects, and enable the button... while it is waiting for the player to click it.
you should structure it so that the actions only execute once. One way to do that is to set a global variable "LevelOver" to 1.
and move the button click code to the top level. You don't really have to have to check LevelOver on the button click because the button is disabled and invisible before points gets to 16, but it doesn't hurt.