(EOS help) Notification Button Skips Timer

[Roblsforbobls]

Hi everyone, Happy Halloween!

I'm running into a strange issue with EOS and I was wondering if I'm doing something wrong.
I have a notification button set up that simply plays a sound and changes a variable. I also have two timers, one after the other, set to synchronous mode. The player is supposed to be able to click the notification button without affecting the timers, and the timers are intended to happen one after the other.

During the first timer if this button is clicked, the second timer starts before the first one ends (the first timer continues as well, so there is an overlap). I want to be able to use this notification button without having to worry about the player skipping timers by using it. Does anyone have an idea as to why this is happening and/or a possible solution?

Thanks,
Robls

[fapnip]

Unfortunately, that's how notifications in Eos work. When a notification button is pressed, it will essentially skip over any other action currently in a paused/wait state, be it a timer, say, choice, etc., and then continue execution of the actions that follow it, after any of the notification's actions have been executed -- assuming the page didn't change in those actions.

(It's a behavior I have yet to replicate in OpenEOS -- but eventually need to since some teases depend on it to operate properly.)

Asynchronous timers shouldn't be affected though. So, if you want you the second async timer to start after the first, the second async timer should be one of the async actions of the first.

[Roblsforbobls]

Hi Fapnip, thanks for the reply.

Asynchronous timers shouldn't be affected though. So, if you want you the second async timer to start after the first, the second async timer should be one of the async actions of the first.

I thought about doing that too, unfortunately the actions after the timers need to happen after they both finish. If I change them to asynchronous and put the second one as one of the async actions, it won't have the intended delay. Sounds like there's not much I can do aside from rethinking things Thanks again

[RemiHiyama]

Wouldn't that mean you would just need to put the stuff that is supposed to happen after both in the actions of the second timer?

[Roblsforbobls]

Wouldn't that mean you would just need to put the stuff that is supposed to happen after both in the actions of the second timer?

Hi RemiHiyama, thanks for the reply. I hadn't thought of this, but it seems promising. I'll have to try this solution along with Fapnip's suggestion and make sure they preserve the page's functionality, but from a quick glance I think this will work.

I appreciate both of you!