You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Had a convo with chase a while back now about what data is given to us. Basically you have a separate set of data that measures stats across all players all the way down to the tiniest detail of # of times a certain menu is used.
Basically, since most players have their API settings set to default (which is no personal data sharing), it would be nice to have the server wide data where the anonymous player data is mixed in.
This way you could do stuff like
"only xx% of players have this cosmetic"
"only xx% achieved this badge"
"X players has [insert color]" crown"
same idea goes for stats within a gamemode (win/loss, kills, etc)
Anything else that could create some cool graphs and stuff about the overall mcci population (like how you shared a bunch after the mcc bedrock event): https://x.com/Noxcrew/status/1824481228466082235
while still respecting the privacy of users who don't want certain data points connected to them.
The text was updated successfully, but these errors were encountered:
Had a convo with chase a while back now about what data is given to us. Basically you have a separate set of data that measures stats across all players all the way down to the tiniest detail of # of times a certain menu is used.
Basically, since most players have their API settings set to default (which is no personal data sharing), it would be nice to have the server wide data where the anonymous player data is mixed in.
This way you could do stuff like
"only xx% of players have this cosmetic"
"only xx% achieved this badge"
"X players has [insert color]" crown"
same idea goes for stats within a gamemode (win/loss, kills, etc)
Anything else that could create some cool graphs and stuff about the overall mcci population (like how you shared a bunch after the mcc bedrock event): https://x.com/Noxcrew/status/1824481228466082235
while still respecting the privacy of users who don't want certain data points connected to them.
The text was updated successfully, but these errors were encountered: