-
Posts
3628 -
Joined
-
Last visited
Everything posted by Dr. McKay
-
You must be sending the wrong ID to OPSkins then.
-
That was originally in there, dunno where it went.
-
Marketability isn't the same as tradability.
-
That error happens when you're trying to list something that isn't in your Steam inventory (or isn't tradable).
-
How would you get the name of the game someone is playing if they're not in-game?
-
You should use GetPlayerSummaries to get what game someone is playing.
-
There's nothing in the steamcommunity module to get a user's games. Generally it doesn't include stuff for things you can do with the WebAPI.
-
Question about getting logged off after some time (days)
Dr. McKay replied to mar71n's topic in node-steam-user
That's pretty much the right way to do it. -
Unless you're conducting tens of thousands of trades a day, that should be fine.
-
That should work.
- 6 replies
-
- node.js
- node-steam-user
-
(and 2 more)
Tagged with:
-
It shouldn't matter if your IP keeps changing.
-
It's just normal polling. It polls (requests) the API on a timer to see if anything has changed. The only possibly more efficient way to do it is to connect to Steam as a client and listen for new incoming trade offers messages and items received messages. They don't tell you details about the trades though, so you need to hit the API anyway. And since they're not foolproof you need to poll on a timer anyway.
-
Not really, just google http proxies.
-
I highly doubt you'll find any free proxies that work with Steam.
-
HTTPS proxies are not supported, only HTTP proxies. Your 400 Bad Request is coming from the proxy, so you're probably not using the correct proxy address/port.
-
7 days trade ban, how check how many days left? CEconItem{}?
Dr. McKay replied to Ryzl's topic in node-steamcommunity
It's in owner_descriptions, which is only available if you loaded your own inventory. -
Most likely OfferLimitExceeded is coming from the actual call to offer.send(), not from confirming it. There's also a limit on how many offers can be awaiting confirmation, maybe you hit that.
-
Issues with getting post-trade assetid's
Dr. McKay replied to Eradicate's topic in node-steam-tradeoffer-manager
itemsToReceive always contains the pre-trade data. You can use offer.getExchangeDetails to get post-trade data. -
I believe you only need steamLogin, steamLoginSecure, sessionid, and steamMachineAuth cookies (the latter not being necessary if the cookies were obtained through a CM).
-
You could always use node-steamcommunity's getUserInventoryContents, which is what steam-tradeoffer-manager calls anyway.
-
I don't understand what you're trying to do here. Why manually make the request instead of using getUserInventoryContents? What do you mean by "not having to cache anything"?