Closed luxalpa closed 8 years ago
Please call steamClient.logOn
in place of user.logOn
.
The problem with is, now it immediately closes the connection after opening it, so I can not use other modules that operate on the steamClient.
Output:
Connected.
Logged in!
[Error: Disconnected]
Couple things.
logOnResponse
doesn't indicate that you're logged on. You should check the eresult
property of the first object argument to see if you logged in successfully.steamID
to a valid initial value (76561197960265728). I had forgotten about this, and the documentation incorrect stated that logOn
did this for you. If you update to version 2.1.2, then you can use user.logOn
and it should just work.I tried a few things. First I updated to 2.1.2.
I checked eresult and indeed it gave me the value 5 which stands for invalid password. However, then I changed it back from steamClient.logOn
to user.logOn
and suddenly it works now! Yay!
So thanks for that! At least now there is a working version :D
Sorry, I was slightly unclear. On any version, steamClient.logOn
would work if you set steamClient.steamID
to "76561197960265728"
first. Version 2.1.2 makes user.logOn
work.
According to the readme:
It should be compatible with all node-steam handler modules.
The usage of node-steam's SteamUser causes a zlib error: incorrect header check.
Code:
Output: