Also, just a bit of information from my experience.... If you have 3 quests ending within the time the time it takes to run the code, but not the same, like task 1 ends, the next two end before the first code is running, it checks it as the next time that's running, and not that you have 2 completed tasks when it's done running the code. So, if I had task 1 end at 1:15am, task 2 ends at 1:16am, and task 3 ends at 1:17am. task 2 and 3 may be completed while task 1 is being replaced by the macro, but when it checks again, it may not run a check for several hours. It would be much better if you had 3 tasks in rapid succession, it would take the time to check again based on the first pass through your active tasks and not at the end of the code. That way it runs again immediately.
Also, it's now making me confirm all of my quests and I don't know why. It pauses the macro right in the middle which would be meaningless if I was running it while I was asleep cause it won't accept the quest until I come back to the computer to press "Yes"
Also, it's now making me confirm all of my quests and I don't know why. It pauses the macro right in the middle which would be meaningless if I was running it while I was asleep cause it won't accept the quest until I come back to the computer to press "Yes"




)
There's an issue in MQ2 where a confirmation box isn't "the one" that we can see. As with the previous answer this is going to take a plug-in or core change to address and work past.