Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use hours as default playtime unit instead of dd:hh:mm #4558

Open
TPGPL opened this issue Jun 9, 2019 · 4 comments
Open

Use hours as default playtime unit instead of dd:hh:mm #4558

TPGPL opened this issue Jun 9, 2019 · 4 comments

Comments

@TPGPL
Copy link
Contributor

TPGPL commented Jun 9, 2019

It would look more clear with hours as default playtime unit in my opinion. It's also a more wanted variable than dd:hh:mm

@Aergwyn
Copy link
Member

Aergwyn commented Jun 9, 2019

I feel like this was discussed before but I can neither remember nor find it. I personally prefer the current way that shows days as that's easier to comprehend than some big number.

@Joehuu
Copy link
Member

Joehuu commented Jun 9, 2019

Same as closed issue #3969. Not sure if it is concerning.

@nekodex
Copy link
Collaborator

nekodex commented Jun 12, 2019

This is a personal preference thing and there are people on both sides wanting opposite things.

The only real way to "fix" this is by providing a toggle that allows a user to switch between which they personally see.

@Xinnoh
Copy link

Xinnoh commented Jun 19, 2019

I did a twitter poll about this last week and 75% of users preferred to use hours rather than days
that said it should be taken with a grain of salt since it's only 50 people and a twitter vote
https://twitter.com/SinnohOsu/status/1137902135993982976

My opinion is that I also prefer using hours as a measure because most other gaming platforms such as steam use hours as a measure for play time. It makes it easier to get an idea of how much time I've been playing, rather than seeing an arbitrary number of days that has no meaning to me.

@peppy peppy removed this from the Candidate Issues milestone Mar 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants