Dr. McKay

Try using process.nextTick(() => client.logOn(logInOptions)) when error is emitted. You're going to need to generate a new 2FA code, though.

When error is emitted, that means you're logged off. You'll need to log on again.

Please read the v4 release notes. The first argument to callbacks is now err.

What version of steam-user are you using?

It's possible with globaloffensive. But please don't call it "float value".

173.208.103.160 is not an IP address assigned to any interface on your system. Is that a proxy IP? If so, just use the proxy option and don't set localAddress. Please read the v4 release notes.

Are you up to date?

const Request = require('request'); const SteamCommunity = require('steamcommunity'); let community = new SteamCommunity({"request": Request.defaults({"proxy": "http://1.2.3.4"})});

There is no way to get description data including market_hash_name in steam-tradeoffer-manager without specifying a language. You would need to load your inventory separately, or use GetAssetClassInfo.

It's in the user event in steam-user.

It's not possible.

When did you remove the language? Some changes were made in August 2017 to reduce memory usage.

It's entirely possible that it's some kind of rate-limit in Steam to prevent comment spam.

Why is adding it back not an option?

Most definitely.

Since updating to 4.4.4, my memory-leak test setup isn't doing too badly. Just ~150 MB per instance.

Why would you need to use it that frequently? You get real-time notifications (through events) when friend messages are received.

When I have time.

relog is only meant to be used when you're connected. When error is emitted, that means you got disconnected and SteamUser won't attempt to automatically reconnect. You should be able to just log back on immediately with your login key. Also, if you want some more descriptive debug output (actual message names and not just numbers), add "debug": true to your constructor options.

8901 is ClientPICSChangesSinceRequest, so I suppose it stands to reason that Steam is sending a whole lot of product data in a single message, which is transferring really slowly, thus blocking the pong frames from being received in a timely manner. But it would have to be a looooot of data, and in my experience really large PICS changes responses are broken up into multiple messages, so pong frames should make it through. ‍‍¯\_(ツ)_/¯ That would explain your timeouts, but not why the login key is being rejected for session resumption. Perhaps Steam doesn't believe that you've disconnected yet? Or maybe Steam saw the WS close frame and treated it as a logoff and thus invalidated the login key. But that wouldn't explain why it was being rejected when you were using rememberPassword. Perhaps using the previous session ID is invalid when trying to use a remember-password login key and not for session resumption purposes. So again, ‍‍¯\_(ツ)_/¯ Maybe to fix this, websocket13 should avoid tearing down a connection for failure to respond to ping while data is actively coming in. Dunno. But to (finally) answer your question, you should be able to work around this quite well by adding "protocol": SteamUser.EConnectionProtocol.TCP to your constructor options. Plain TCP doesn't use pings to make sure the connection is still alive.

Blocked = 429 for some period of time I don't know off-hand, probably at least 5 minutes. Your best bet is to find some third-party pricing API.

I will add the ability in the next release.

The WebSocket ping timeout means that the Steam server did not send respond to a ping we sent in a timely manner (or more accurately, it didn't respond to 3 consecutive pings within 10 seconds). If Steam isn't down, that means you have network issues. As for why you're being prompted for another app code, I have absolutely no idea. I tried replicating the issue with fake errors and it just re-logged with no issues each time. Maybe try removing or dividing by 1000 your logonID? It's a 32-bit int.

The older events are deprecated, but they will keep working until at least v5. Though I recommend switching to the new events.

getChatMessageHistory is only going to get messages for a chat room.