Question for you Mud, any look creating a Looping Scripts? . So far attempts have failed
either I'm messing up somewhere along the line or they aren't designed for to loop.
Yes I have made a couple of looping scripts, but there is a mech in place to stop recursive scripts
I've also added a Script [scriptName] command, which allows you to execute another script inside a script. This allows you to write modular scripts, with each one doing only a specific task, and then you can call them as you need them (string them together) allowing for primitive script reuse.
Note the Script command will cause nested execution. The SetSwitch command also has the potential to do this, because the switch may activate another script as part of it's circuit.
In order to stop both excessive ram use and infinitely recursing scripts (script A calls script B which calls script A which calls script B), there is a limit of 20 nested scripts. Once the nested limit is reached, a script cannot execute another script (directly or indirectly) so eventually the nested scripts will unwind.
Sourcecan make simple loopers like so;
1: Script [1]
2: Commit
3: Wait [1000]
4: Script [2]
5: Commit
6: Wait [1000]
7: Script [1]
8: Commit
9: Wait [1000]
10: Script [2]
11: Commit
repeat as necessary, but there is a limit then it can't be looped by switches, buttons, scripts or anything.. will need a manual reboot if no one can find a way round it