Quote:
Originally Posted by BAILOPAN
That's pretty awesome, voogru. I'm curious as to how you discovered this -- observation with some trial and error?
out of boredom I went and looked up the first few steamids to see how many were definitely valve employees:
Code:
steam_0:0:1 (alfred)
steam_0:1:1 (ErikJ)
steam_0:1:2 (alfred)
steam_0:0:5 (greg coomer)
steam_0:0:6 (john cook)
steam_0:1:7 (taylor sherman)
steam_0:0:8 (chris bokitch)
steam_0:1:9 (lyncho?)
steam_0:1:10 (eric smith)
|
A bit of trial and error.
I got the friendID for these two ID's:
STEAM_0:1:1182 (76561197960268093)
STEAM_0:1
0679 (76561197960327087)
I noticed that the 2 friend ID's were identicle up until 11th number.
76561197960 268093
76561197960 327087
Then I tried this:
76561197960327087 - 76561197960268093 = 58994
Result was higher than expected, so I cut it in half for giggles.
58994 / 2 = 29497
Hmm.. not too far from 30679..
29497 + 1182 = 30679 DING DING DING DING
and
30679 - 29497 = 1182 DING DING DING DING
To get the first number, I then did:
76561197960268093 - (1182 * 2) = 76561197960265729
But, I use the 76561197960265728 number and then just increment it by what the auth server is.
There does not appear to be a STEAM_0:0:0 ID, but there is a STEAM_0:1:0 ID.
Now with this knowledge, I also have the option of storing steamid's as 64 bit ints rather than strings.
My question to valve is where the hell did they pull out a number like 76561197960265728.
A friend of mine pointed out when it's converted to hex it's 110000100000000, but no idea if that is significant or not.