Disabled Triggers are not correctly shown in Runtime after stopping the simulation

[sanguinariojoe]

Create a Trigger, disable (uncheck) it in "Runtime", and start the simulation. After stopping such simulation, the Trigger will be checked again.

As far as I can see, the Trigger is still disabled, just wrongly shown in the UI

[gajop]

Actually triggers are all being re-enabled manually after each time we stop (https://github.com/Spring-SpringBoard/SpringBoard-Core/blob/master/scen_edit/command/stop_command.lua#L31-L33)

This is because triggers are special, you can edit them (and even create new ones) while you are testing - you don't need* to stop! All those created triggers will be accessible after you're done testing and stop. This makes them different from most other objects which are reset to their initial state (before testing). I think it's a useful feature to allow scenario logic to be edited on the fly -> it allows for rapid development as you can immediately see the result of the new code

*editing triggers on the fly might run in some issues in case referenced objects aren't available from the start

That said, I understand the confusion. I guess we need to find a way to differentiate between user changes (e.g. disabling triggers for editing) and scenario effects (scenario disabling triggers from an action). The first one should change the initial state of the trigger, while the second one shouldn't.
Things also get a bit more complicated if we allow triggers to generate events/conditions/actions on the fly :)

For now, if you want to work around these issues, I recommend you create an on-start trigger that disables certain triggers.

[sanguinariojoe]

OK