Automator help [spoilers]

[Derpykat5]

I've rigged up a simple automator script that takes most of the busywork out of the eternity phase of reality. Nothing too fancy, just navigates through all the Eternity Challenges and sets up a dilation run.

The problem is with EC10. I've currently got a loop in place to run it 5 times, but I'm at the phase where I can complete EC10-1 faster than the automator can process. The challenge ends and I auto-eternity out of it back to the blank tree before the automator advances from "Start EC10" to "wait eternity", and the automator stalls, so I removed the "wait eternity" line.

For context, the loop currently looks like this:

while ec10 completions < 5{
studies purchase ECtenlast
start ec10
}

Where ECtenlast is my constant that contains the TS string for my EC10 runs.

The problem is though, that I can't complete EC10-3 through 5 in that same amount of time, so if I just remove the "wait eternity" line then sometimes it will execute the study load command at the top of the loop right before the challenge ends, then advance to the "Start EC10" command, which causes the automator to stall in a position where I have no studies purchased but the automator is trying to buy and start EC10, which it cannot do.

You'd think adding a "nowait" command to the "Start EC10" line would fix the issue easily, but Start commands don't support the "nowait" modifier.

Given all of that, my question is; how do I get this loop working correctly?

[Hypertext Eye]

don't use auto eternity for eternity challenges
instead do something like

auto eternity off
while ec10 completions < 5 {
studies purchase ECtenlast
start ec10
eternity
}

[Derpykat5]

Originally posted by Hypertext Eye:

don't use auto eternity for eternity challenges
instead do something like

auto eternity off
while ec10 completions < 5 {
studies purchase ECtenlast
start ec10
eternity
}

The problem with not using the eternity autobuyer is that I need it active to grind up EP and TT in other parts of the run, so I'd need to turn it off and on again around every packet of challenges, which would be annoying. There has to be a better way to do this.

[Hypertext Eye]

Originally posted by Derpykat5:

There has to be a better way to do this.

There isn't

[Derpykat5]

Originally posted by Hypertext Eye:

Originally posted by Derpykat5:

There has to be a better way to do this.

There isn't

Dang. Well at least it works.

[Jadian]

You could work out other ways to finagle things to work, but it'd still amount to adding a few lines to make things sync up.

If you're lining up progress based on your time theorems, ending the loop with something like wait TT > 900 might work for a while, since you'd probably only have that many free after a challenge completion resets the tree?

[Nyu]

Originally posted by Hypertext Eye:

don't use auto eternity for eternity challenges
instead do something like

auto eternity off
while ec10 completions < 5 {
studies purchase ECtenlast
start ec10
eternity
}

this is the cleanest way of doing it. also simple and clear.
anyone calling this annoying, i dont wanne see the code if you ever make a game :(

[Derpykat5]

Originally posted by Nyu:

Originally posted by Hypertext Eye:

don't use auto eternity for eternity challenges
instead do something like

auto eternity off
while ec10 completions < 5 {
studies purchase ECtenlast
start ec10
eternity
}

this is the cleanest way of doing it. also simple and clear.
anyone calling this annoying, i dont wanne see the code if you ever make a game :(

If it were just around the one block, done once, I'd agree, but I have 5 challenge loop blocks and I'd need to turn it off around each loop, then back on again afterwards.

It works, and I implemented that, and it wasn't too much of a hassle, but I just wondered if there was a more efficient solution, and was informed that there wasn't.

[Huillam]

Originally posted by Derpykat5:

It works, and I implemented that, and it wasn't too much of a hassle, but I just wondered if there was a more efficient solution, and was informed that there wasn't.

I don't really understand (no irony here by the way) why it would be even a minor annoyance.
You can copy paste text in and out of the automator and it's not a complex thing to add. A lot less than the loops for example.

[Derpykat5]

Originally posted by Huillam:

Originally posted by Derpykat5:

It works, and I implemented that, and it wasn't too much of a hassle, but I just wondered if there was a more efficient solution, and was informed that there wasn't.

I don't really understand (no irony here by the way) why it would be even a minor annoyance.
You can copy paste text in and out of the automator and it's not a complex thing to add. A lot less than the loops for example.

Well I had to do that not just for the C10 loop, but for the C9, C12, and both C11 loops (I run 2 C11s before dilation and the rest after). I can't just leave the autobuyer off because then I don't get enough EP progression at several points.

So I had to use "Auto Eternity Off" and "Auto Eternity On" 5 times each throughout the script. It's annoying to scroll through the script and type the same two lines over and over again. I'd like to reiterate that it wasn't too much of a hassle.

[Hypertext Eye]

Originally posted by Derpykat5:

So I had to use "Auto Eternity Off" and "Auto Eternity On" 5 times each throughout the script. It's annoying to scroll through the script and type the same two lines over and over again. I'd like to reiterate that it wasn't too much of a hassle.

and how many times did you type "studies purchase X" or "start ec#" in that script? surely it was more than 5 times.

[Derpykat5]

Originally posted by Hypertext Eye:

Originally posted by Derpykat5:

So I had to use "Auto Eternity Off" and "Auto Eternity On" 5 times each throughout the script. It's annoying to scroll through the script and type the same two lines over and over again. I'd like to reiterate that it wasn't too much of a hassle.

and how many times did you type "studies purchase X" or "start ec#" in that script? surely it was more than 5 times.

But that work was already done. I never said anything about the rest of that script not being annoying to write. Quite frankly; it was. But I did it anyway because I couldn't get a better solution. Just like the solution in this thread.

[Huillam]

Originally posted by Derpykat5:

So I had to use "Auto Eternity Off" and "Auto Eternity On" 5 times each throughout the script. It's annoying to scroll through the script and type the same two lines over and over again. I'd like to reiterate that it wasn't too much of a hassle.

I had more than 30 'auto eternity on/off' in my first (working) automator script.
Although I edited it in notepad++ as I did find it easier to read than the automator.
Is your script easy enough to read? For example to make it easier to make changes as I progressed and could compress some challenge completions I made a 'block' (as in skip a line before and after) per challenge. Also made debugging a whole lot easier.

Again I'm not judging, pointing a finger or anything. It's genuine curiosity nothing else. :)

[Derpykat5]

Originally posted by Huillam:

Originally posted by Derpykat5:

So I had to use "Auto Eternity Off" and "Auto Eternity On" 5 times each throughout the script. It's annoying to scroll through the script and type the same two lines over and over again. I'd like to reiterate that it wasn't too much of a hassle.

I had more than 30 'auto eternity on/off' in my first (working) automator script.
Although I edited it in notepad++ as I did find it easier to read than the automator.
Is your script easy enough to read? For example to make it easier to make changes as I progressed and could compress some challenge completions I made a 'block' (as in skip a line before and after) per challenge. Also made debugging a whole lot easier.

Again I'm not judging, pointing a finger or anything. It's genuine curiosity nothing else. :)

The readability of my script is irrelevant.