I'm unsure if autostops is broken or this is working as intended

Irrat

Member
I'm not really sure how Auto Stops is meant to work.

If I use run_choice(1) in a choice adventure script, and it hits an autostop, it will early exit everything until a value capture is attempted.
I encountered this issue with autoscend, where the choice handler script detected an error was thrown as it failed to return true.
Notably, at the giant castle top questline, when turning the wheel. Mafia has an autostop for it, and there's nothing to stop it, you can only 'catch'.
But this behavior seems really odd. When it hits an autostop, is it really meant to start exiting everything until a value is required?

In this encounter, we have just executed adv1($location[The Castle in the Clouds in the Sky (Top Floor)], -1, "");
We hit the choice, and the choice adventure script now runs. It gets us all the way to finishing the giants castle quest, where an autostop is then hit.

Code:
void run_stuff() {
   run_choice(1); // Hits autostop
   print("Won't be seen");
}

boolean run_stuff2() {
   run_stuff();
   print("Won't be seen");
   return true;
}

void main() {
  boolean result = run_stuff2();
  print("Will be seen, and the result will be false");
}
If you edit the above script and remove boolean result = , then the last print will not be seen.
 
Back
Top