Saving current splits on window reload

[vjeux]

Context: I'm using livesplit one to keep track of a long running challenge (I try to solve 400 puzzles that last between a few minutes to an hour each) which works well except for when I close the window, everything is wiped when I reload. Sadly this is a managed computer that requires restarting Chrome fairly frequently and I lose all the current splits.

Proposal: Would it be possible to periodically (every couple of seconds while the timer is running) save the current splits to localstorage and when you load the page, then use localstorage data.

I'm happy to do the implementation as well if someone is able to tell me how to serialize/deserialize the state of livesplit-core.

Thanks!

[CryZe]

I actually do have an inprogress implementation for this, so this is definitely something that I want to have and is going to happen. Seems like there wasn't an issue already, at least not in this repository.

[vjeux]

@CryZe <3 Anything I can do to help?

[CryZe]

I don't think there's currently anything that you can do.

[vjeux]

@CryZe I'm happy to put a $200 bounty if this gets fixed. This is really annoying to lose progress every time I restart Chrome (or my computer).

[Zikoat]

I'd also put a 100$ bounty on this.
My use case is that i am running this on my phone, and am tracking how fast i am at my morning routine. When i turn off my screen and then reopen the website, then it should keep the progress from last time i opened it. I am not quite sure how the core is implemented and integrated into the frontend, but my first thought is to either register a webworker which keeps track of the timer, or save the current splits into localstorage. I might try a workaround with some extensions to keeps the website running in the background in the meantime.
Sadly not proficient with Rust, so i'll have to wait for @CryZe to fix.