Jump to content

Recommended Posts

Posted

In addition to:


- 1 ONCE
- 2 REPETITIVE ACTION
- 3 SWITCHED CONDITION
- 4 MISSIN START

What would be helpful in debugging and mission building, would be :

5 - BYPASS TRIGGER (or SKIP TRIGGER)


Rather than having to delete a trigger, being able to skip it for testing would make our lives a little easier.

Posted

Unless you're deep into the mess of nested OR conditions (where the grouping and order of evaluation is already very murky), it's usually easier to just set a condition that cannot possibly be true. This has the benefit that the testing happens when it should happen, it just doesn't trigger the action, whereas if you change the trigger type, you might end up with no testing at all. For the most part, this shouldn't matter, but once you start doing performance tweaking and mix in scripts, it can turn out to make a difference to a surprising degree.

But yes, if the purpose is to not have a test at all, then a separate dummy trigger type would indeed be handy.

❧ ❧ Inside you are two wolves. One cannot land; the other shoots friendlies. You are a Goon. ❧ ❧

Posted
3 hours ago, Kanelbolle said:

I just copy the trigger and remove the condition from the on i am testing. Other way around i set a condition that will not be possible to avoid it to trigger.

Yeah, I get that... and it is what I do. It would be a lot easier to have the option in the pulldown when working through issues, especially if you have a lot of triggers. Being able to bypass triggers containing Do Scripts or Do Script Files, would just seem easier and quicker.

  • Like 1
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...