-
Notifications
You must be signed in to change notification settings - Fork 18
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
Carry over statistics to a new map revision [feature] #300
Comments
It turns out that this just calls over to the master server, and doesn't do anything on the resource-server side. This can't be fixed here, so it might be better to simply remove it (until someone can build a proper implementation, at least). |
You mean remove the rating feature, the # played, # viewed and # downloaded counters? |
The played stat.
That is entirely my point: the value is fetched from a completely different website, so there is no way to reassign it. The other stats are difficult to keep track of, because there is no direct link between revisions. Updating one would need to update all of them, which is unreasonably difficult right now. |
What about only displaying stats for the most recent revision. Then only one element has to be updated with influences from the others. |
To clarify: You would get the same stats regardless of which revision you are looking at. Always the total amount. |
Hi,
by uploading a new revision of a map, the "played" statistic gets reset - so it looks like the map has never been played before. This is kind of disheartening ^^. I would like to request this to be changed so that the statistic is accumulated over all revisions.
This applies to the "viewed ", "downloaded" and "rated" as well.
Especially in rating this would be important. Currently this disencourages uploading revisions (if you care for the rating) and rating other maps yourself, since the rating will disappear anyway if the map is improved.
Alternatively to one "played" stat there could also be a "played - total" and a "played - revision" entry.
The text was updated successfully, but these errors were encountered: