Disable checkbox for Actions, Conditions and Triggers for quick debugging/experiments

[virgo47]

It would be cool to be able to "comment out" individual Actions, Conditions and perhaps the whole Triggers with some "Disabled" checkbox. I think "disabled" says it all, of course, the action/condition/trigger would be somehow indicated (a bit harder for triggers that can be coloured by us, but I'm sure there is a way, e.g. different background).

This can make various prototyping much faster and also works around the inherent problem that we can't copy the stuff away somewhere else like we can with real code.

Edited April 15, 2024 by virgo47

[TEMPEST.114]

2 hours ago, virgo47 said:

It would be cool to be able to "comment out" individual Actions, Conditions and perhaps the whole Triggers with some "Disabled" checkbox. I think "disabled" says it all, of course, the action/condition/trigger would be somehow indicated (a bit harder for triggers that can be coloured by us, but I'm sure there is a way, e.g. different background).

This can make various prototyping much faster and also works around the inherent problem that we can't copy the stuff away somewhere else like we can with real code.

 

As an idea, in the mean time, could you add a non-existent flag to the thing you want to disable in it's condition - therefore it will never be true?

But great suggestion.

[Exorcet]

38 minutes ago, Elphaba said:

As an idea, in the mean time, could you add a non-existent flag to the thing you want to disable in it's condition - therefore it will never be true?

Depending on how many things need to be turned off it might be best to setup a "debug mode" with multiple flags. The idea is that one master flag at the top of the trigger list turns debug mode on or off so that you don't have to keep track of flag calls you've added elsewhere in the trigger list.

[virgo47]

8 hours ago, Elphaba said:

As an idea, in the mean time, could you add a non-existent flag to the thing you want to disable in it's condition - therefore it will never be true?

Thanks for the tip, this at least allows me to disable the whole trigger.

My initial idea however came from the Actions list. It's not supercomplicated to create an action, but oftentimes it's annoying, especially if it's a message, sound, script, clickable action or anything that requires more clicking and parameters. To disable such a thing now is to delete and recreate it again. I just expanded the idea to conditions and triggers for consistency, but it is most missing on Actions level, at least as I see it.

[Tippis]

Seems eminently sensible

Commenting out code is made trivial in any kind of scripting and programming for a reason, and the same logic applies to trying to pick apart and test complex triggers. Since all the triggers are just UI for underlying scripts anyway, it might not even be difficult to do in the mission file code.

[MAXsenna]

It would be cool to be able to "comment out" individual Actions, Conditions and perhaps the whole Triggers with some "Disabled" checkbox. I think "disabled" says it all, of course, the action/condition/trigger would be somehow indicated (a bit harder for triggers that can be coloured by us, but I'm sure there is a way, e.g. different background).
This can make various prototyping much faster and also works around the inherent problem that we can't copy the stuff away somewhere else like we can with real code.

Might not be what you're after. But I believe @cfrag made some realtime debugging tool.

Sent from my SM-A536B using Tapatalk