During a rando race, closed the game to install a mod that I had forgotten, re-opened the game, and loaded back into the rando file. Before I loaded back in, the timer state was Running, but the auto-splitter's state was waiting to start. When I loaded back in, the start split RandoWake triggered (separate issue https://github.com/AlexKnauth/hollowknight-autosplit-wasm/issues/76), causing the auto-splitter to reset and start the timer over again.
The state should be moved outside the process-until-closes block so that it can be preserved through a game re-start.
During a rando race, closed the game to install a mod that I had forgotten, re-opened the game, and loaded back into the rando file. Before I loaded back in, the timer state was Running, but the auto-splitter's state was waiting to start. When I loaded back in, the start split
RandoWaketriggered (separate issue https://github.com/AlexKnauth/hollowknight-autosplit-wasm/issues/76), causing the auto-splitter to reset and start the timer over again.The state should be moved outside the process-until-closes block so that it can be preserved through a game re-start.