-
Notifications
You must be signed in to change notification settings - Fork 121
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
Time shown for replay uses the real game time instead of replay lenght #3159
Comments
Agreed; the real time has no meaning when watching a replay. |
@Sheikah45 Do we have anyone for icons creation? Was looking into code, It seems that there is tickDurationLabel that could be used, however it is not initialized every time. Is it related to some sort of lazy loading? Cos it doesnt make sense to me. Anyway is it fine to use this label? It comes from Replay.replayTicks, but I have no idea what is this refering to or what it is about... |
The tick duration is populated by the replay server while the real time duration is populated by the lobby server. So the tick duration is not always present if the replay server hasn't finalized the replay yet. |
As far as icons we use the icomoon SVG generator which I think is detailed in the wiki. Here is the link https://github.com/FAForever/downlords-faf-client/wiki/Adding-Icons. |
Forgot to pass link, |
Is your feature request related to a problem? Please describe.
At one point, the time shown for the replay lists was changed from being the replay length to the real time of the game, to my frustration, as it was more unreliable than the replay length.
Describe the solution you'd like
I'd like for it to return to the previous function that it had: showing replay length instead of real time, as it was a more meaningful metric.
Describe alternatives you've considered
If the reason it was changed to real time was debated, I'd then suggest showing both times, as there should be space for it in the card, both next to each other, and having a different icon for the clock. It could also be a good indicator of replay quality, as I believe replays that have a high variation between the two are more prone to replay desyncs.
The text was updated successfully, but these errors were encountered: