Dr. McKay

https://github.com/DoctorMcKay/node-steam-user#getownedappsfilter Don't call getOwnedApps until after the ownershipCached event is emitted. Also, it doesn't take a callback argument.

You can't. This is a Node.js module only.

Gotcha.

https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/TradeOfferManager#getofferid-callback

You're treating the symptom, not the cause. There's no scenario where this.partner should be undefined or otherwise invalid unless you're doing something wrong.

steam-session is a Node.js module, not a browser module.

?? What does this have to do with steam-session?

Show how you're creating a trade offer (new TradeOffer(...))

If you don't have the user's SteamID at all in any form, no.

GetTradeHistory does appear to accept an access token to retrieve all trades.

You need to report that you're in CS2 by calling user.gamesPlayed(730), then complete the GC handshaking process before sending any other GC messages. For CS, this is sending ClientHello (4006) with the proper version number and waiting for ClientWelcome (4004) in response. You can check node-globaloffensive for reference.

Contact your proxy provider.

Sounds like someone with control of your network is trying to modify traffic.

I don't believe you can get non-game badges or your account's creation time via steam-user. You'll need to use the WebAPI.

https://github.com/DoctorMcKay/node-steam-user?tab=readme-ov-file#error The 'error' event.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/503

If you're passing an instance of SteamUser in to the constructor, I recommend you don't poll more frequently than every 30 seconds (30000). And you shouldn't be running full updates more frequently than every 2 minutes (120000). In other words, the defaults are fine.

You can't use OpenID with steam-user.

I don't believe I've ever seen this happen.

The inspect request is rate limited. The absolute fastest I've seen it work is once per second, and that may even be too frequent these days.

I suggest you ask the csfloat project, with which I have no relation.

There's no reason to ever call logOn in an interval. If you receive the error event, then just log on again and you'll always be connected.

2.11.4 should fix this for you.

https://steamerrors.com/20

You can't really reliably do it. There are some community endpoints that include app_data on the item description, which does contain def_index, but not all have that. steam-tradeoffer-manager isn't using IEconItems_440 because that's a TF2-specific interface and steam-tradeoffer-manager is meant to work with any Steam app.