lotsofs / livesplit.outputtofile Goto Github PK

When you reach 24 hours, the text file shows "00:00:00" again (tested by setting "Start Timer At" in the "Edit Splits" splits editor menu to "23:59:56.00").
When you reach 25 hours, the text file shows "01:00:00" (tested by setting "Start Timer At" in the "Edit Splits" splits editor menu to "24:59:56.00").
When you reach 100 hours, the text file shows shows "04:00:00", (tested by setting "Start Timer At" in the "Edit Splits" splits editor menu to "99:59:56.00"). 100 hours is 4.16667 days.
I don't know how you'd fix that stuff, but yeah, I was just curious what happens.

Also, the text file still shows "00:00:00" before you start the timer. It'd be nice if the text file showed "00:05:00" like LiveSplit does instead of "00:00:00" while the timer is not running if I set "Start Timer At" in the "Edit Splits" splits editor menu to "5:00.00".

It'd be nice to have access to the timer (with seconds). People like Joshimuz could use it instead of an external app for marathons for example.

gabrielthomasjacobs commented on Jan 13
This project might be a better fit when trying to get the current time data. https://github.com/LiveSplit/LiveSplit.Server

You used a RadioButton instead of a CheckBox for the timer option, so we can't turn it back off unless we edit the LSL file in a text editor and change OutputTimer from True to False.

It'd be nice to have a reversed split index which shows how many splits are left in the run, similar to CurrentSplit_Index which shows how many splits you've completed. People could use this for keeping track of progress during races when different people use different routes for example.

The splits should get cleared to a dash like other things

It'd be nice to have access to the completed runs counter which shows only how many runs you've completed, similar to AttemptCount which shows how many runs you've attempted.