Not sure if this is the appropriate place to request this but would it be possible to give an option in the LB settings to mark milliseconds as optional (not saying it should always say optional next to milliseconds for any LB, but that the option is there for some LBs if mods want it).

Basically my problem is this: I added the possibility to add milliseconds to the times submitted for SMB3 because it can prove important for short categories. Obviously, it should only be used if the run was actually framecounted, and whole seconds are perfectly fine otherwise, particularly for long categories. But since I added it, there's been many submissions with milliseconds that are completely wrong because people just entered whatever livesplit was saying at the end of the run. Just trying to think of a way for people to stop doing this (if they didn't framecount).

If not an "optional" message, maybe hide the milliseconds by default in the submission page and show it only if the runner clicks something, i don't know.

Lightnat0r has been working on changes to the timer code if I recall. I don't know if this specific thought is addressed, but it might at least make something like this easier after the code is refactored.

I'd like to chime in on the decimal topic. As Kirua said, milliseconds really only make sense if you have a proper recording and can do a frame count to verify. However, you can relatively reliably time a run down to the tenth of a second from any VOD. In many games with close competition that would help to break up ties. I know that some communities time RTA runs only down to full seconds, but not all of them do. Having an option to determine the number of decimals would be great. On the SML2 leaderboard I'm using the ugly workaround to display times like "26m 38s 200ms" to achieve the aforementioned resolution. Another flaw, imo, is that flat times, e.g. "26m 33s" for 26:33.0, omit the milliseconds by default. While displaying the zero decimal is technically redundant, generally omitting it still disrupts the homogeneity of the displayed times. While most of this is a cosmetic issue, there's also a practical component: from a board moderator standpoint, I want the times to be as accurate as reasonably possible (tenths are fine in the majority of cases even with frame drops and reencoding shenanigans as long as there's a timer in the recording) while still preventing people from submitting fantasy decimals, like Kirua mentioned. Having milliseconds enabled right now for the purpose to break up ties gives submitters the wrong idea that they can resolve their times down to that level from any recording. That puts the strain on moderators who have to fix those submissions and leads to misunderstandings about timing in general.