on my bound when i do switch 2 and stop switch 1, switch 1 wont stop and it keeps going which screws up the bound entirely plz help

on my bound when i do switch 2 and stop switch 1, switch 1 wont stop and it keeps going which screws up the bound entirely plz help

clear the level switch after the level is done...

clear the level switch after the level is done...

I assume you are using waits for the bound, it won't stop until all the waits have run through. Use [URL=http://Falkoner.CoW.GooglePages.com/Death_Counts.html]Death Counts[/URL] if you want to get rid of it.

I assume you are using waits for the bound, it won't stop until all the waits have run through. Use Death Counts if you want to get rid of it.

Pls be exact when speaking about triggers and switches. You can clear/set switches, but you can only stop a trigger (from RErunning by making its condition false, e.g. clear a switch). You cannot interrupt a trigger when it has already fired. You'll have to wait until all actions have been executed. Falk suggested to divide your bound triggers into small fragments and fire them depending on a death counter. That way you can stop any obstacle literally instantly by modifying the death counter.

Pls be exact when speaking about triggers and switches.
You can clear/set switches, but you can only stop a trigger (from RErunning by making its condition false, e.g. clear a switch).
You cannot interrupt a trigger when it has already fired. You'll have to wait until all actions have been executed.
Falk suggested to divide your bound triggers into small fragments and fire them depending on a death counter.
That way you can stop any obstacle literally instantly by modifying the death counter.

Or you can alternate players who own the obstacle triggers :P Example: Player 7 owns "level 1" triggers, Player 8 owns "level 2" triggers, Player 7 owns "level 3" triggers, Player 8 owns "level 4" triggers, and so on. It's easier if you don't want to divide your levels and use death counts (Although death counters > waits). No way! It's Penguin! Come on, I thought you knew how to make switches work! You were a higher rank than me back in wLTb...

Or you can alternate players who own the obstacle triggers

Example: Player 7 owns "level 1" triggers, Player 8 owns "level 2" triggers, Player 7 owns "level 3" triggers, Player 8 owns "level 4" triggers, and so on.

It's easier if you don't want to divide your levels and use death counts (Although death counters > waits).

No way! It's Penguin! Come on, I thought you knew how to make switches work! You were a higher rank than me back in wLTb...

Death counts are annoying to use in bounds imo. however you could have a death counter cycling from 1-10 with just 1 wait required, and depending on the level, it will do a certain obstacle.

Death counts are annoying to use in bounds imo.
however you could have a death counter cycling from 1-10 with just 1 wait required, and depending on the level, it will do a certain obstacle.

i did the same switch thing i did on all my bounds so ima try what u guys said

i did the same switch thing i did on all my bounds so ima try what u guys said

Okay what force///player do you have the bound triggers on? You need to be specific with triggers as someone already said.

Okay what force///player do you have the bound triggers on? You need to be specific with triggers as someone already said.

Well, a method that I think works best, is a mix of death counts and waits, you split it into sections, but rather than using the death count for the timing, you use it for what step is running, so you run that step, Wait X, Add 1 to Death Count, then if that death count is X, run step X, it allows you to stop the bound immediately.

Well, a method that I think works best, is a mix of death counts and waits, you split it into sections, but rather than using the death count for the timing, you use it for what step is running, so you run that step, Wait X, Add 1 to Death Count, then if that death count is X, run step X, it allows you to stop the bound immediately.

that's exactly what I suggested earlier

that's exactly what I suggested earlier

woops, delete

woops, delete