I'm having an issue where tasks are run immediately. Even when I put up certain conditions for tasks to run they are ignored and everything is read in one straight go. I had a working quest last night but it randomly started running all tasks immediately, and being fed up I restarted from scratch. The fact if it works or not seems to be completely random. What am I doing wrong? I'm guessing it has something to do with how I'm spacing.
Actions should only run once something triggers them (such as your clock timer). I'm not aware of any problems that will cause this occur, but if your test quest is a good way to reproduce, I'll have a look at this in more detail later.
I have rarely seen this in the past. I haven't wanted to report it since I couldn't see a reliable reproduction method. But I can say it's been around since September.
In my case it was with a Prompt action that insisted on happening out of turn.
Looking at your quest above to reproduce, what you've found is a parsing bug.
There are some extra tabs underneath each task that cause each task to become linked to the task before it. Basically the tabs cause each task header to be dropped and become joined to previous task - in this case all the way back startup task. Here's a screenshot showing the tabs under each task block.
I'll work on a fix for this now. If you remove the tabs under each task block it executes OK (tested).
Jay, I hazard this is the same problem you had but you managed to clean up formatting without realising it was part of problem.
I've fixed whitespace handling between task blocks now. It can handle your repro quest above without any problems. This will be in next round of builds.
You can chain timers together as well, e.g. start clock A at startup then start clock B from clock A task. Jay is an expert at this stuff and will be able to help more.
When looking at a timer in the quest debugger: grey=not started, green=running, red=finished.