Author Topic: A radio that would kill you when switching to a certain song?  (Read 412 times)

Using the 'Simple Radio' technic, i made a radio, but what i want it to do is this, when i switch to 'You shouldn't have done that', i want it to say "You've met a terrible fate, haven't you?", then have the player be burnt (burnPlayer event) and then die shortly after, my way doesn't work though, i got too mixed up in all of the events that needed to be toggled, when going to 'You shouldn't have done that', nothing will happen until you click the radio controller again, then you'll have the message appear, be burnt and then die, but occasionally, the song will switch back to 'Song of Healing' by itself, or it'll stay on 'You shouldn't have done that' when you've pressed the controller a second time rather than switching to the next song, and if it does switch to the next song, the message, burnt player and kill events are still active, so they activate once you get to the next song, which isn't supposed to happen



I think that the problem is that you didn't but a delay on event 14, so it turns 13 and 14 off at the same time it turns them on.

Try that, and tell me if it made a difference.

I have all but the first two events disabled just like the picture above, event 14 has a 3500 delay, i click the controller until it gets to 'You shouldn't have done that', the event works and it resets back to 'Song of Healing' after i've died

But then once the music brick is set to NONE, out of nowhere, Song of Healing comes back on, when i check the event menu after this happened, the first and last two are enabled

I have all but the first two events disabled just like the picture above, event 14 has a 3500 delay, i click the controller until it gets to 'You shouldn't have done that', the event works and it resets back to 'Song of Healing' after i've died

But then once the music brick is set to NONE, out of nowhere, Song of Healing comes back on, when i check the event menu after this happened, the first and last two are enabled
it's because it turns off onactivate, as you didn't delay it turning off, but rather instead have a toggle there to make you click it off