-
Posts
3389 -
Joined
-
Last visited
Reputation Activity
-
Dr. McKay got a reaction from venfiw in how to get cookies
shoppingCartGID doesn't get issued until you actually add something to your cart.
-
-
Dr. McKay got a reaction from Cubson in Partially loading inventory?
Native support for what, filtering by item name? No.
-
Dr. McKay got a reaction from Cubson in Partially loading inventory?
No, there isn't any native support in the library for that. It would probably be easier for you to just manually send the request and parse the JSON yourself.
-
Dr. McKay got a reaction from Cubson in Partially loading inventory?
You can use the count URL parameter to filter how many items are returned, like this: https://steamcommunity.com/inventory/76561198006409530/753/6?count=1
-
Dr. McKay got a reaction from venfiw in acceptConfirmationForObject - Cannot Confirm Market Listings
The market listing ID is the creator property.
-
Dr. McKay got a reaction from Tayhayy in Sharing the same steamcommunity across multiple workers
Your assumption is correct.
You could either use IPC to call to the master process and do your steamcommunity work there, or use IPC in the master process to the worker processes to share your login cookies.
-
Dr. McKay reacted to What Comes Around in Getting error in retrieving inventory after some time
Good news, well I mean the error still occurs but I know what's going on. And knowing is good .
As you can see, while the error did look scary being displayed 5-10 times, all accounts do get successful requests from time to time. In fact, more often than not. So the fear factor was just a result of the scale I'm working in. I am not sure why this is the error I get instead of 502, but whatever, it's not catastrophic. Problem solved.
-
Dr. McKay got a reaction from What Comes Around in Getting error in retrieving inventory after some time
The only thing that happens when a session expires is the sessionExpired event gets emitted (potentially multiple times). There isn't any other way to tell.
-
Dr. McKay got a reaction from Tayhayy in [Suggestion] Steam Awards
Created an issue for this: Steam awards · Issue #271 · DoctorMcKay/node-steamcommunity (github.com)
-
-
Dr. McKay got a reaction from Tayhayy in Getting the ID of the account im currently logged in with
My mistake, I didn't pay close enough attention to your callback. The first argument to the callback function needs to be err; the second is user.
-
Dr. McKay got a reaction from Tayhayy in Getting the ID of the account im currently logged in with
Get rid of the object. You should just be doing this: account1.getSteamUser(account1.steamID, function (user) {
-
Dr. McKay got a reaction from Tayhayy in Getting the ID of the account im currently logged in with
You want your ID or your custom url? Those are two different things.
Your SteamID is available as account.steamID. To get your custom URL, you should call getSteamUser() on your own steamID and check the custom URL in the returned object.
-
-
Dr. McKay got a reaction from What Comes Around in How do I avoid this error?
Yes.
Yes.
That's correct. client.steamID gets set just before loggedOn is emitted (meaning it's not null once you connect), and gets set to null just after disconnected / error are emitted.
-
Dr. McKay got a reaction from tf2forever in [Help] Group comment not posting
Sounds like you need to pass a callback and check if Steam is returning an error.
-
-
Dr. McKay got a reaction from Jack Nolddor in upvote a review ?
No, that's not possible and I don't have any plans to enable automated voting.
-
Dr. McKay got a reaction from What Comes Around in How do I avoid this error?
If you haven't disabled automatic reconnection, then you shouldn't ever need to call logOn after the first time (unless the error event gets emitted). So yeah, when you get sessionExpired just check to make sure SteamUser is connected, then call webLogOn() if it is. If it isn't, then it'll automatically log onto web when it gets connected.
-
Dr. McKay got a reaction from What Comes Around in How do I avoid this error?
That error happens when you call logOn while the SteamUser instance is already connected.
-
Dr. McKay got a reaction from Breather in How many bots can I authorize through different node-steam-users objects?
There's no technical limit; your only limitations should be IP addresses and system resources.
-
Dr. McKay got a reaction from What Comes Around in How do I avoid this error?
Before you call webLogOn, check to see if the client.steamID property is null. If it is, then you're not connected to Steam, and that's likely the reason why your web session expired.
-
Dr. McKay got a reaction from What Comes Around in How do I avoid this error?
Correct, when a new client session is established, a web session is automatically negotiated.
-
Dr. McKay got a reaction from Harry in user.logOn never resolves when running on VPS
There is no timeout for connection attempts because when Steam goes down, it can stay down for a while and we want to be able to reconnect automatically.
Add this and you can get some more descriptive output:
client.on('debug', (msg) => console.log(msg));