What specific data is collected by TH for Dashboard?

[MrOne]

FYI

- salted hash of the battletag (salt is the sender computer's name so there is no way I could brute-hash all known battletags and match those with your hash, because I don't know the sender's machine's name)
- salted hash of the current hero ID (salt is the sender computer's name)
- hero info: sc/hc, hero class, gender
- realm
- server IP
- the stat trackers

Nice to know what happend there, no problem for me, u can collect that data
Question is ... why u collect them, only statistics?

[flupster]

FYI

- salted hash of the battletag (salt is the sender computer's name so there is no way I could brute-hash all known battletags and match those with your hash, because I don't know the sender's machine's name)
- salted hash of the current hero ID (salt is the sender computer's name)
- hero info: sc/hc, hero class, gender
- realm
- server IP
- the stat trackers

Thank you!

If there is a way to collect statistics on "settings" that might be valuable for design desicion like is function X or Y used? I'm no coder so I don't know what possibilties are open to you. I know that collection of usage metrics in mobile application is quite sophisticated nowadays and provide developers with a great tool for validating their design choices. For TH I'm thinking mostly about paragon capture and greyed out items, questions about their "should or should not be on by default" seem to reoccurover the years.

Thanks for all the hard work!

' spelling

[dieudo]

@KJ

Collect all informations that you need, it doesn't matter. We love THUD.

D3 is horrible without your add on

You have our full confidence !

Cheers