Also another thing, it needs to track how many quests were done today.
I am not 100% sure if telegraphOfficeAvailable changes to false after you are done with your 1 quest a day. (will check it soon). But either way we need to know how many quests we finished today.
Lets say I have permanent access to LTT
My script checks telegraphOfficeAvailable and that quest state is unstarted
It then does
To start the quest.
Then it does the quest. Ok, now quest is done.
it checks telegraphOfficeAvailable and sees I have it, it sees the quest state is unstarted (when you finish a quest it goes to unstarted instead of finished).
It then repeats the code snippet above.
Incidentally quest is now erronously listed as started. script is broken until this is manually fixed.
Preference questLTTQuestByWire changed from unstarted to started
Preference lttQuestDifficulty changed from 0 to 3
Unexpected error, debug log printed.
If I had _lttQuestFinishedToday property I could check it and see if it is above 0, if it is then I would know:
1. how much overtime would cost.
2. that I need to use overtime if i want to be able to start a quest again.
I also think that when a quest finishes it should say "finished" instead of "unstarted". And that only when you click the overtime button it should change it from "finished" to "unstarted"
Now, if the script happened to be using a day ticket. Then (_lttQuestFinishedToday == 1 && _telegraphOfficeToday) would together indicate that we are done for the day because we used a day ticket and as such cannot do overtime
At the moment though the script cannot be trusted to use the day ticket. regardless of if telegraphOfficeAvailable changes to false after you are done with today's single quest, it would get stuck in an infinite loop of trying to use more day tickets...
Unless it has its own tracking and is the only script handling ltt of course.