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

Carry over statistics to a new map revision [feature] #300

Open
CH4Code opened this issue May 26, 2017 · 5 comments
Open

Carry over statistics to a new map revision [feature] #300

CH4Code opened this issue May 26, 2017 · 5 comments

Comments

@CH4Code
Copy link

CH4Code commented May 26, 2017

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.

@pchote
Copy link
Member

pchote commented Sep 16, 2018

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).

@CH4Code
Copy link
Author

CH4Code commented Sep 17, 2018

You mean remove the rating feature, the # played, # viewed and # downloaded counters?
They may be inaccurate measures, but measures non the less! That kind of feedback guides map makers (like me) in w what to focus on and is a type of reward.
The rated feature nobody would miss, but the automatic ones?...
Can't be too hard to read and sum a value before re-assignig it o.O

@pchote
Copy link
Member

pchote commented Sep 17, 2018

The played stat.

Can't be too hard to read and sum a value before re-assignig it o.O

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.

@CH4Code
Copy link
Author

CH4Code commented Sep 17, 2018

What about only displaying stats for the most recent revision. Then only one element has to be updated with influences from the others.
You'd still have to iterate the revisions somehow, but only once for a change of any element.
The revisions link lists all revisions of a map, there must be some kind of copyable query behind that.

@CH4Code
Copy link
Author

CH4Code commented Sep 17, 2018

To clarify: You would get the same stats regardless of which revision you are looking at. Always the total amount.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants