search

seishun / node-steam

Interface directly with Steam servers from Node.js
MIT License
1k stars 180 forks source link

SteamID returning zero when Steam Community is down #356

Closed tayler-king closed 8 years ago

tayler-king commented 8 years ago

When the Steam Community was down earlier, for some unknown reason node-steam returned the account as 76561197960265728. Of course this is the 64-bit int, plus the account id - but the account id was zero, so it just returned 76561197960265728 instead of the actual steam id.

Sorry for the minimal message, github is screwed for me right now - no styling or scripts are loading.

seishun commented 8 years ago

Was the SteamClient logged on at the time?

tayler-king commented 8 years ago

I believe it was logged on, although no sure way of checking. I'd assume so, otherwise I would've expected an error rather than a 0 for the account id.

On Mon, Apr 25, 2016 at 6:42 PM Nikolai Vavilov notifications@github.com wrote:

Was the SteamClient logged on at the time?

— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/seishun/node-steam/issues/356#issuecomment-214455538

seishun commented 8 years ago

It probably wasn't. '76561197960265728' is the initial SteamID value that's automatically set when calling logOn.

tayler-king commented 8 years ago

Au right. Hmm, not sure why it didn't error that the account never logged in - strange. On Mon, 25 Apr 2016 at 21:29, Nikolai Vavilov notifications@github.com wrote:

It probably wasn't. '76561197960265728' is the initial SteamID value that's automatically set when calling logOn.

— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/seishun/node-steam/issues/356#issuecomment-214502192