Script stops running (or it looks like it does)

[malogoss]

My script runs just fine as long as I stay on the script tab. It'll repeat endlessly from start to finish, which is intended.
Then I click another tab and sometimes it's alright. At other times, it messes things up. Since I'm not on the script tab at that point, I can't be 100% sure but it looks like the script is stalled or stopped or paused. It seems to often be the case when I click the Reality/Glyphs tab, for example.

Another example, the Eternity/Time Studies tab does not seem to ever cause a problem. (Edit: I should have shut up, I just clicked that tab and it broke it.)

Anyone else getting the same odd behaviour? Or is there a way to avoid it happening?
thanks

[Huillam]

Does it resume properly when going back to the automator tab?

[Meidi]

There seems to be a problem in the automator that skips the first line under random circumstances, started happening to me when I upgraded it to maximum speed. This first line could be your important one that stalls the whole process if it doesn't proc.
I'd suggest to add a "notify" command as your first line, since it's not important and skipping over it won't ruin your script.

[malogoss]

No, going back to the Automator tab was not resuming it.

And no, the first line was not the issue. It was just stopping when I switched tab, no matter what line of the code it was executing.

But I found what's causing the problem:
When I'm using the block editor, the game freezes or lags for maybe 1/4 of a second when I click another tab, and the Automator stops.
When using the text editor mode, none of that happens.

So I wouldn't say the problem's really fixed, but at least I can avoid it. Don't leave the editor in block mode.

[Nyu]

Originally posted by malogoss:

No, going back to the Automator tab was not resuming it.

And no, the first line was not the issue. It was just stopping when I switched tab, no matter what line of the code it was executing.

But I found what's causing the problem:
When I'm using the block editor, the game freezes or lags for maybe 1/4 of a second when I click another tab, and the Automator stops.
When using the text editor mode, none of that happens.

So I wouldn't say the problem's really fixed, but at least I can avoid it. Don't leave the editor in block mode.

wow its only 1/4 of a secound now? on release my game froze for like 4 to 10 secounds
since that i avoided blockeditor completly.
maybe worth reporting as bug if it stops your automator.

it can also happen that automator go too fast and skip inputs and softlock themself, but that is more a problem if you make minmax scripts early.

[Hypertext Eye]

Originally posted by malogoss:

No, going back to the Automator tab was not resuming it.

And no, the first line was not the issue. It was just stopping when I switched tab, no matter what line of the code it was executing.

But I found what's causing the problem:
When I'm using the block editor, the game freezes or lags for maybe 1/4 of a second when I click another tab, and the Automator stops.
When using the text editor mode, none of that happens.

So I wouldn't say the problem's really fixed, but at least I can avoid it. Don't leave the editor in block mode.

when i started using longer scripts (like thousands of characters), i found the game would hang for a few minutes when entering the automator in block mode only, and would also hang when swapping between block and text mode, so maybe just don't use block mode at all.

[daemonworks]

There's definitely some issues with the automator. I've found it will occasionally get stuck in a conditional loop, with "until eternity" loops are particularly common culprits, though I've also seen it with other while and until loops. I'll just entirely lose the ability to recognise the condition has been met until the script's restarted, and then it'll work perfectly again for some time.

[Hypertext Eye]

sounds like a case of auto eternity triggering before the loop starts, and then it has no cause to trigger within the loop

if you're trying to use the automator to do eternity challenges, it's best to not use auto eternity at all

[Cringe Guy 2086]

if you're using the block automator, try swapping to the text automator and see if that fixes it

[Dwane Dibbley]

Sometimes my script got stuck, probably due to multiple commands trying to execute within same game-tick (simply put something happens too fast). Like completing challange sometime gets stuck on "eternity" command cuz it execute it but not move to next line and its trying to do it again, but cant since tt tree is reseted and autobuyer off so im never able to eternity.
So now im ending ECs always with "eternity nowait" to prevent such stuck and sofar everything was "solvable" somehow. Just check what happened and adjust script to bypass automators errors.