Dr. McKay

You can use steamstore to add phone numbers.

You can use getUserDetails to check whether the trade URL is valid and if the user can trade.

Oh, I see what you're doing. Didn't look at the code super closely. node-steamcommunity doesn't currently support supplying your own cookie jar. I can't officially support this, but if you want to use node-steamcommunity's cookie jar for other purposes, you can do something like this: this.community = new SteamCommunity(); this.jar = this.community._jar; This is liable to break in a future release, but it will work. Also, if you want to supply your own user-agent, you need to supply it to the options object as userAgent. Specifying it as a default header in a passed-in request instance won't work.

Probably because it needs to be this.jar = request.jar()

https://steamapi.xpaw.me/#IPlayerService/GetOwnedGames

At some point, probably.

They're using steamcommunity.com's CSS to render the levels.

Not at the moment.

The chatter's SteamID is available in the event that delivers you the chat message.

How to get a user's SteamID depends on how you know what user you want to trade with.

You would want to go ahead and call GetPlayerSummaries for the steamids you want profile details for.

No, that's not currently possible.

You've cut out the actual error message.

https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/TradeOffer#getpartnerinventorycontentsappid-contextid-callback

You need to retrieve both parties' inventories, find the items you want to trade, and add them to the offer using addMyItem and addTheirItem.

Thanks, I'm not sure how that slipped through the cracks.

That sounds suspiciously like you're trying to JSON.stringify the error object. > let err = new Error('test') undefined > err Error: test at repl:1:11 at Script.runInThisContext (vm.js:123:20) at REPLServer.defaultEval (repl.js:384:29) at bound (domain.js:415:14) at REPLServer.runBound [as eval] (domain.js:428:12) at REPLServer.onLine (repl.js:700:10) at REPLServer.emit (events.js:208:15) at REPLServer.EventEmitter.emit (domain.js:471:20) at REPLServer.Interface._onLine (readline.js:314:10) at REPLServer.Interface._line (readline.js:691:8) > JSON.stringify(err) '{}'

By default, each account gets its own sentry file, so having multiple instances running should make no difference. Although if something in your environment is preventing the sentry files from being written, that could potentially cause some issues.

I don't really know a whole lot about the inner workings of CS:GO, but I'd think that if it's not exposed in the existing profile methods, then it's probably incredibly tricky to retrieve otherwise. I've not seen anything in the protobufs that refer to trust levels.

That's pretty strange. I've never heard of anyone being prompted for a Steam Guard code when they use a loginKey; only loginKeys expiring and getting InvalidPassword back. That said, the way Steam handles loginKeys is kind of weird and they're prone to being rejected. I personally recommend that you just use passwords wherever possible.

What do you mean by an empty object? The err property will always be either null or an Error object. That said, your problem is likely that your Steam account is limited, i.e. you haven't spent $5 yet.

Please read the docs again more closely, specifically the deprecation notice.

That does seem like it's a Steam bug. Did you try restarting your own Steam client, by chance? I wonder if that might have resynced things.

You need to keep track of the asset IDs of items you already have offers out for, and filter them out of your inventory when you're sending additional offers.

getExchangeDetails is 100% the most useful and reliable option. I should probably deprecate getReceivedItems.