Dr. McKay

Sure, you could use steamstore for this.

No, all you can do is work out what the error code could mean. https://steamerrors.com/15

You're trying to use an IP address that isn't assigned to any interface on the machine you're using.

The internet is not flawless.

As of steam-user v4, steam-client is not used. You'll need to read the docs to see the new way to set an HTTP proxy.

Ubuntu 18.04.2 LTS. Node.js v10.15.2

It works fine for me on Linux (Ubuntu).

What version of steam-user are you using? It's ready to send trades once the callback fires without an error when you call setCookies.

Your best bet is just to handle the error event and if that happens, call logOn again.

That code looks fine. LogonSessionReplaced means the same account was signed into from the same IP with the same logonID. If you don't want it to crash your app, you need to handle the error event.

Yes. That's not supported. Each TradeOfferManager needs its own SteamCommunity instance.

I would assume this is because the x variable has a larger scope and it has since changed. As an example: for (var i = 0; i < 10; i++) { console.log(i); setTimeout(() => console.log(i), 1000); } This would output: 0 1 2 3 4 5 6 7 8 9 // 1 second delay 10 10 10 10 10 10 10 10 10 10 This is because the i variable changes every time the loop increments, and the callback functions reference that variable with its current value when they execute, not with the value it had when the callback was set up. You can work around this by using let instead of var, which will do what you expect.

Yeah, you can use the cluster module to spin up child processes. Usually what I do when I have multiple bots I need to run to do the same task is I have a database table with a row for each bot. The table has a column named like last_heartbeat and the bots update this column with the current time every 10 seconds or so. If the timestamp is recent, then the bot is running. You could also have another column storing the IP address (and port) of the server/process where the bot is running and use that to make HTTP calls to the bot.

The readme is wrong, the limit is actually 20k. There is no way to paginate if that isn't enough. You'll have to write some fancy queries if you need to get more servers.

Yep, that looks correct.