Minor issue: .000 milliseconds are never displayed
4 years ago
Washington, USA
EmeraldAly
She/Her, They/Them
4 years ago

Also that link at the end of their message. Didn't notice it the first time. Beep boop?

Netherlands

Shout-out to a Full-Mod not recognizing a bot Kappa

Imaproshaman, Hako and 4 others like this
Netherlands

Thought I would post this here, shoutout to @Volvagia for adjusting this and making it so it now displays the additional trailing zeroes.

A mod can set this up by going into Edit Game -> Edit Category and enable: "Enforce MS" If a community chooses not to set this up category wide, mods can edit runs and add the extra 0's in MS and then re-verifying them.

Edited by the author 4 years ago
Sekanor, just_tako and 6 others like this

Thank you!!

afnannen136 likes this
United Kingdom

so for 0 second long runs can we do 0:00.00

Antarctica

That has been brought up before and the general consensus is that it’s not possible for a run to take zero seconds. Every run takes some time to do. If a game’s timing method is giving you a 0 second time, then you should probably use a different timing method to accurately capture how long the run is taking.

Hako and ShikenNuggets like this

There actually is an option to always show milliseconds!

Go to "Edit game", then "Categories", click on the three dots of the category, click "Edit category" and select "Enforce MS" which is explained as "This will make all times in this category show milliseconds if the game supports it, even if a flat rounded number. E.g. 12:00:00.000"

I hope this is the option you are looking for, @Sekanor!

Sekanor likes this
Canada

@Laika_the_Spacedog This thread was created before this feature existed, and Daravae already mentioned that this had been added.

Edited by the author 4 years ago
Imaproshaman, Hako and 2 others like this

Oops... I thought I had read all answers to see if anybody else mentioned this solution but I obviously missed it. Sorry... 🙈

European Union

Sorry for necroing this thread but the (in principle great!) solution that has been found a year ago features a slight flaw, which I'd like to bring to attention with this post.

The original Prince of Persia leaderboard recently has been adjusted to feature milliseconds for in-game time because of the memory-based autosplitter we have. In order to balance the aesthetics of the board we decided to keep the real-time column (which is irrelevant for competition, yet offers an interesting bit of extra information) free of milliseconds. Because the game runs at 12fps, on average roughly 8% of runs will finish with an in-game time of 000ms (i.e. x minutes x seconds and 0/12 frames) so this is more than just a marginal occurence.

The current problem we have is that

  • the "enforce ms" feature works globally, meaning enforcing ms will do so (a) for all subcategories & (b) for all time columns (RTA, IGT, Time w/o loads) featured on the board so this is not an option for us
  • adding the 000 manually (with the "enforce ms" option turned off) only works in the RTA column, that is, entering "000" in the RTA column leads to this: https://i.imgur.com/y9x2Nv0.png and adding 000 only in the IGT column is treated as entirely redundant: https://i.imgur.com/XWRrTnJ.png

In conclusion, I believe the easiest-to-implement solution here would be to extend the current "manual 000" rule to all possible timing methods (and not just for RTA, as it's handled currently). This would be also be the most useful solution for us personally because it would allow us to clearly mark the runs which have used the autosplitter, i.e. an autosplitter run would be listed as 21m06s RTA/19m37s000ms while an old run would be listed as 21m06s RTA/19m37s, allowing for a clear distinction of the two.

Edited by the author 3 years ago
Pixiuchu, dripping and 4 others like this
Israel

@toca_1 If marking runs with or without an autosplitter is your goal, then you should probably set it up as a new variable to have a clear distinction. I doubt people would see 19:37 and 19:37.000 and will immediately know there is a deeper meaning behind it.

Edited by the author 3 years ago
Gaming_64 likes this
European Union

@Oreo321 "Marking runs with or without an autosplitter" is not our goal, it would rather be an additional feature we would get for free once this is resolved. The problem at hand really is that entering 000 for milliseconds only for IGT currently does not have any effect.

Pixiuchu, Kai., and Oreo321 like this