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

Allow a new type of data (kind of?) #50

Open
SpraxDev opened this issue May 30, 2019 · 1 comment
Open

Allow a new type of data (kind of?) #50

SpraxDev opened this issue May 30, 2019 · 1 comment

Comments

@SpraxDev
Copy link

Sorry for the title, I couldn't come up with a better one.

Anyway, we are having a discussion about whether ViaVersion should add bStat or not: ViaVersion/ViaVersion#1343

Some of us would love to see a graph that shows X% of the users are using Minecraft-1.8.8 and another Y% are using 1.12.2. But because multiple servers can have the same players this would need some action on the backend. So would it be possible to come up with a method that would allow creating such graphs? And of course, keeping the players anonymous?
I've never had the time to really work on the topic hashes but would cryptographic ones of the UUIDs be enough for such a thing?

@Bastian
Copy link
Owner

Bastian commented May 30, 2019

But because multiple servers can have the same players this would need some action on the backend.

This is already a problem with the existing player charts. There's no way (that I know of) that would allow bStats to solve this issues without tracking specific players. Even if you hash the UUID of a player it does not really help in terms of privacy.

Besides that, it would also require a lot more power on the backend to perform these kind of checks. The current implementation is very simple: bStats just needs to increment a number when it receives a request from a server. If it had to perform a check for each player on the server, it would require a lot more processing power.

Given that

  1. I don't know a way to implement it without being able to track to players across servers
  2. It will significantly increase the load of the bStats server
    I don't think that it is worth implementing it. In the overall data it should not matter if a player gets counted twice occasionally. Players are usually not on multiple servers at the same time. As it can also happen that a player does not get counted at all (because the servers only report the player count at a given time), the error gets even less as the average is still correct.

A Drilldown Pie chart (like the Operating System one) should fit perfectly for this use-case.

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

2 participants