Dr. McKay

Handle the error event, reconnect, and then only relaunch after your persona data tells you that you aren't in-game anymore.

The easiest way to determine which game a community item belongs to is to check its market_hash_name. All cards/emoticons/backgrounds have their market_hash_names prefixed with the game's appid and a hyphen (e.g. "440-SCOUT").

It shouldn't be possible for the callback to not fire. Please make sure your code is correct.

https://github.com/DoctorMcKay/node-globaloffensive#inspectitemowner-assetid-d-callback Read the documentation, please.

You're saying that the callback isn't being fired, but there are no errors or crashes?

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

It's because that's the way it is.

One is emitted when offers you sent change, and the other is emitted when offers you received change.

They use some form of push notifications that haven't been reverse-engineered yet, and likely never will. Probably Firebase.

That is currently not possible.

https://github.com/DoctorMcKay/node-steam-user#steamguard

Yes.

That's a Steamism. You just have to wait and try again later.

loadInventory is deprecated. Use getInventoryContents instead.

That's certainly a possibility.

Please show your code, including the error message and stack trace.

You only need to spend $5 once.

I don't understand.

Good intel. It should be able to handle private inventories. I'll add that in the next update.

Are you logged in?

As per the documentation: If it's the first emit, accountInfo won't be defined yet. The data is available as an event argument.

You aren't logged into the website in the loggedOn event. Wait for webSession, call community.setCookies, then start the confirmation checker (although I advise against using it, it's better to just confirm as needed).

This issue arising after updating is merely a coincidence. It appears that in today's Steam maintenance, Valve added a new binary KV node type. Please run npm update and let me know if that doesn't fix it.

Yes, it appears that Steam no longer sends back the SteamID when an account is created successfully. I'll update the readme accordingly.

Then why are you trying to check confirmations as part of the login process? Show your code.