Revamp evaluation of custom scheduling commands not to evaluate all the commands at start

[talran]

The custom schedule luas seem to call the RepeatQuest function and keep running through the script (not sure how Assert4SymbolsPendantsBelow functions then) but it messes with schedules that depend on the time another quest finished to decide what to queue next (such as in ROTB where you want to run the correct raid)

Long shot but is there a way to pause without just having to estimate a ttc on each run so that time calculations could be properly done between runs?

My ghetto ass schedule I'm working on is below, which works well for single sets of runs but currently calculates the elements all when it starts and seems to internally queue them up? rotb.zip

Additionally is there anything we can call between queues to check "nightmare mode"? I can tell when it pops, but would love to be able to break out of the current queue'd quest, run that, and then go back to running the main loop. (mostly an issue when you do some off elements)

[talran]

Also don't mind the relative pathing, I use it to work around needing to swap scripts/schedules each version

[Masuzu]

Hello, All the commands in the script are evaluated once so any reference to the current time won't work properly, as was reported in the past by someone who had a very similar use case as yours. Very nice job on the script by the way, very neat! Right now, the time I could invest to update the custom scheduling mode for this use case would rather be spent on other projects but I will see what I can do.

[talran]

Thanks for confirming it for me, and no rush, I can work around it with estimated ttc per boss, and see about keeping an updated copy on another repo so people can use them.

I usually don't work with lua so I wanted to make sure I wasn't running into some odd snapshotting/instancing issue with my own code!