[quote=blacklight28]I can't put both of them in front of the hypers [...][/quote] why not? And if you want to make it absolutely failsafe, use a switch that you set at the beginning of every trigger with a wait and clear it at the end. Then you have all triggers with waits check if that switch is cleared.

Quote from blacklight28

I can't put both of them in front of the hypers [...]

why not?

And if you want to make it absolutely failsafe, use a switch that you set at the beginning of every trigger with a wait and clear it at the end. Then you have all triggers with waits check if that switch is cleared.

The problem is for some reason, no matter which order I put my triggers in, one of my obstacles has a wait problem.

The problem is for some reason, no matter which order I put my triggers in, one of my obstacles has a wait problem.

Are they trying to run at the same time?

Are they trying to run at the same time?

Yes, but that shouldn't make a difference.

Yes, but that shouldn't make a difference.

If they run at the same time, one will block the other. You need to use switches; or better yet, death counters. I have a few example bounds for you to poke at if you want... Well, if you can figure out how to end one obstacle and start the next on your own, you don't need to look at the examples. Just know that if they try to run at the same time, they will block each other.

If they run at the same time, one will block the other. You need to use switches; or better yet, death counters. I have a few example bounds for you to poke at if you want...

Well, if you can figure out how to end one obstacle and start the next on your own, you don't need to look at the examples. Just know that if they try to run at the same time, they will block each other.

It's ok, I fixed it with switches, I couldn't get it with death counters.

It's ok, I fixed it with switches, I couldn't get it with death counters.