Originally posted by Glazbee
This seems quite redundant with Overwolf and Steam in the mix, though looks like a nice little side project.
With being able to opt out, why not add an identifier which does exactly this? Assuming you are using JSON, and your values are stored as so
{"000000000000000000": {"World of Warcraft": 448745524169879, "Cuphead": 64586}}
You could always create a reference to opt-out like so
{"000000000000000000": {"optout": false, "World of Warcraft": 448745524169879, "Cuphead": 64586}}
You can then create something simple like so
optOut(User) {
let optOut == false;
if(user.id == tracker.{$id} && tracker.{$id}.optout == true) {
optOut == true;
}
You will only need to run this section of code when a users game state changes, there is probably a far better way to implement this, but I'm pretty sure the napkin programming would be enough. Which language are you using?
JSON is horribly slow performance wise with the amount of people we already have using it.
Steam only tracks games that are on steam. Never heard of over wolf.
Opt out is per user, not game. So if someone didn't want to partake in the collection of data it would prevent that. The reason it's on the coming soon is because it isn't a high priority.