You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a Spellless Hitless attempt, the runner accidentally entered the wrong save file during the Watchers split, and the autosplitter split Watchers too early. That's not a bug but it's setup for the bug.
The runner did a manual undo split, and then got hit 2 times on Watchers. When they beat watchers, the autosplitter did not split, which is an unfortunate consequence of the autosplitter not knowing when the runner does a manual anything. (unless they're using the unstable version with my fork of the timer)
When they manually split Watchers, the 2 hits were displayed in the per-split hit count for the Watchers split, but then they also wrongly counted towards the next split, Enter Fog Canyon.
This might be a bug I already fixed in the unstable version, I'm not sure:
Test whether this also happens on unstable
Either way, keep this issue open until it's fixed in stable.
The text was updated successfully, but these errors were encountered:
In a Spellless Hitless attempt, the runner accidentally entered the wrong save file during the Watchers split, and the autosplitter split Watchers too early. That's not a bug but it's setup for the bug.
The runner did a manual undo split, and then got hit 2 times on Watchers. When they beat watchers, the autosplitter did not split, which is an unfortunate consequence of the autosplitter not knowing when the runner does a manual anything. (unless they're using the unstable version with my fork of the timer)
When they manually split Watchers, the 2 hits were displayed in the per-split hit count for the Watchers split, but then they also wrongly counted towards the next split, Enter Fog Canyon.
This might be a bug I already fixed in the unstable version, I'm not sure:
Either way, keep this issue open until it's fixed in stable.
The text was updated successfully, but these errors were encountered: