young tendon
V 0.61.1.6
Hey Sylv, dug into the cause of some weird behaviour of UT seeds with stunthack.
If you've done no other runs in a day the first use of the UT auto complete will reset the** last_official_run_date** in the save file to the current date.
This results in the next run where you actually engage rather than autocomplete, to start on the previous runs_today value.
The save file retains the previous value of an Official run, and when you start a new run per stunthack's snippet, it'll check against the official date and then reset runs_today to 0 if it's not the current date. But it looks like because the autocomplete can progress that, you'll start at whatever you'd previously done as runs. Yesterday's seed for me started at the second run, because the previous official clear had had one go through. Todays run starts on seed 3 because my runs_today is now starting at 2.
I would say that the UT Auto complete should either not reset the last official date, or reset the value **runs_today **to 0 if the last_official_run_date is not the current date when triggering.
Happy to share saves or a recording of the steps leading to the difference and what we found.
formal quail
dim chasm