Dr. McKay

You're logging in to an anonymous user account (that's what the a means in [a:1:x]), which implies that your accountName is undefined.

https://github.com/DoctorMcKay/node-steam-user/blob/master/components/cdn.js#L268

https://github.com/DoctorMcKay/node-globaloffensive/blob/master/index.js#L277-L290 This code will probably work.

You could just keep the offer object in memory somewhere and call getExchangeDetails on it again later. Or look it up by trade offer ID. TradeOfferManager doesn't have any way to request the trade status API without having a TradeOffer object first.

I bet that for some reason, immediately after the trade finishes it's not returning the items but after some time they show up. I'd recommend that you set up retries for getExchangeDetails if it comes back empty.

Check the same trade ID using the other bot's API key and see if it properly reports assets_received.

Looks like it's returning assets_given, but not assets_received, so that would be why receivedItems is empty in TradeOfferManager. That's the data that Steam is reporting.

Plug the trade_id (not the trade offer ID) from the offer in question into the GetTradeStatus API and see if it returns any info. If not, then it's a problem on Steam's end and there's nothing we can do about it, sadly.

That code looks like it should work. It's possible that Steam has changed something relating to how avatars are uploaded. I'll look into this when I get a chance, but it probably won't be soon.

No, and you really shouldn't be asking users for their account credentials. API keys are credentials.

No, you can only use a 2FA code once. If you've already used a code, then you'll need to wait for the next code to be generated. You shouldn't be logging into SteamCommunity with an account name and password if you're already using SteamUser. In the webSession event, just call community.setCookies(cookies); That's all you need.

Either your secret is wrong, your clock is wrong, or you attempted to reuse a 2FA code.

If you get an error event indicating you disconnected due to LoggedInElsewhere, just log back in. It won't cause any problems unless you try to launch a game again before you get a playingState notification indicating that you aren't blocked.

You should probably move your gamesPlayed call to the playingState event, and only call it if blocked is false.

Not really. Logging into an account tends to invalidate the session cookies of other logins.