Dr. McKay

I really wouldn't recommend that you try parsing item attributes and using them to determine what various items actually are. CS:GO is a complete mess and that's a really good way to go insane. You're far better off keeping track of which items are which IDs before you put them in your storage unit. I'm not aware of any storage unit rate-limits, but I do recommend that you wait for an add/remove request to complete before you issue the next one.

There shouldn't be any problems.

That sounds an awful lot like spam.

Take a look at the examples in the steam-tradeoffer-manager repository. It should be fairly trivial to modify the example to accept all incoming offers into one that declines all incoming offers.

Yes, receivedOfferChanged should be your primary way to see if a trade was completed.

This is just how Steam works, sadly. When you confirm an incoming trade offer, the confirmation request doesn't respond until all items have been exchanged. If a trade offer contains many items, it's very possible that the request will time out (30 seconds) before all items have been exchanged. In this situation, the trade will still complete in the background.

I'm not aware of anyone having been banned merely for using this package. This interacts with Steam primarily using WebAPIs exposed by Valve themselves; it would be pretty weird for Valve to create and expose an API and then ban people for using it.

Fixed in v3.41.4, thanks for the info.

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) '{}'