oh, right, I did find a couple nitpicks with the actions system: when you don't have enough stats to do something it pauses, which is nice to be able to tell what went wrong, but there doesn't seem to be a way to pause on purpose, nor continue without restarting the loop. when concocting a loop it would be useful to pause at a certain point to look at exactly how much flux you have, and then plan your route accordingly, rather than having to wait for the "chat up locals" tasks to finish again to test if your queue is correct. Furthermore, some actions like adding or removing tasks do not break your current loop, whereas some do, like reordering a task, it would feel very nice for user experience if they were all consistent, and would not break your current loop