Dr. McKay

That error happens when you call logOn while the SteamUser instance is already connected.

v4.19.10 should fix this issue, although you will also have to add the containsBbCode option, like this: client.chat.sendFriendMessage(sender, response, {includesBbCode: true});

When I try to get my own bot to send that exact message using that exact code, I get RateLimitExceeded (84) every time.

My guess would be that your message is just too long, and Steam is choking on it.

You shouldn't use for...in to iterate over arrays. Please research iterating over arrays in JavaScript.

I wouldn't try it. It might work sometimes, but it tends to be fairly unreliable.

No, InvalidPassword means that your account name or password is wrong. It would be a different error if it were Steam Guard related.

node-steam-user/basicbot.js at master · DoctorMcKay/node-steam-user (github.com)

Should be fixed now.

No, it doesn't work anywhere.

There's no technical limit; your only limitations should be IP addresses and system resources.

Not possible due to the Same-Origin Policy. You'll need to proxy those requests through a server.

I don't know why you're calling client.setSentry() as the first argument to logOn(), but you shouldn't and because you are, you're logging on anonymously. Also, you can't use getOwnedApps before the appOwnershipCached event is emitted.

steamcommunity can do that.

Update to 4.19.7 please.

Correct, when a new client session is established, a web session is automatically negotiated.

Go ahead and try v4.19.6 please.

Okay, this is interesting. Are you running your app on slow hardware, maybe a Raspberry Pi? It looks like Steam is sending back gzipped responses, and for some reason some of these responses are taking multiple seconds to ungzip. This is resulting in the timer for ClientLogOnResponse elapsing while ungzipping, resulting in a relog. But once the account gets relogged, the old ClientLogOnResponse comes in and it thinks it's logged on when it isn't. log.txt

That means that Steam didn't respond to the add-friend request within 10 seconds. I don't know why this would happen other than Steam just being unreliable.

You would want to use a loop to request inventories until Steam no longer reports that more items are available, and use array_merge to combine the result pages.

Searching the market is the only way to get a list of available assets for an app, without using inventories or third-party sites.

Before you call webLogOn, check to see if the client.steamID property is null. If it is, then you're not connected to Steam, and that's likely the reason why your web session expired.

You'd need to use the WebAPI for that.

The way the CS:GO item system works is pretty insane and it's a fool's errand to try to decode item names out of the data sent back from the GC. Your best bet is to keep track of what item IDs correspond to which items before you put them in the casket, then refer back to that mapping when you want to retrieve stuff. The CS:GO game client only removes one item from the casket at a time, and waits until it's removed before removing another one. You probably shouldn't try to remove items much faster than that, or else you might get on Valve's bad side.

Thanks, that's a little helpful but I'm still having trouble tracking down exactly what's happening. Please update to steam-user v4.19.5 and also log the debug-verbose event in the same manner as the debug event.