Dr. McKay

Make sure your server is able to access api.steampowered.com.

It's not a bad idea to add a short delay. acceptConfirmationForObject has nothing to do with the confirmation checker. It operates immediately. If you're using it, you probably don't necessarily need the confirmation checker.

Socks proxies are currently not supported. You'll need to use an HTTP proxy. I don't believe I've pushed support for HTTPS proxies (HTTP is just as secure for this case). Example: const Steam = require('steam-client'); const SteamUser = require('steam-user'); let client = new Steam.CMClient(); let user = new SteamUser(client); client.setHttpProxy("http://user:[email protected]:12345"); user.logOn(/* options go here */);

It will already retry connection until either it succeeds or error gets emitted.

No.

classid and instanceid can change on an item, yes.

Is steamcommunity up to date?

Yes, it's rate-limited by Steam. I can't tell you what the limit is, exactly, as I don't work for Valve.

No. If the error event is emitted, it's always fatal and it will never retry on its own.

loadInventory is deprecated and won't be updated. If Steam is reporting "Failure" then there's not really any way to know for sure if it means that the user doesn't have that particular inventory or if there was truly a failure somewhere. If the user has ever owned an item for that game and thus the inventory exists but is empty, it will return an expected empty response (no error, empty arrays).

the accept method is to accept an incoming offer, not to confirm an outgoing one. The documentation is clear about this. You can use node-steamcommunity to confirm trades.

Not really, but don't spam it.

Show your code.

No. Steam does not support IPv6 at this time.

You're not meant to use steam-client on its own. You should use it alongside something like steam-user. You can still use it with WebSockets and proxies, doing something like this: const Steam = require('steam-client'); const SteamUser = require('steam-user'); let client = new Steam.CMClient(Steam.EConnectionProtocol.WebSocket); client.setHttpProxy("http://user:[email protected]:12345"); let user = new SteamUser(client); // use user normally...

Not possible.

Yes, you can edit the summary.

No, showcases can't be edited at the moment.

https://steamerrors.com/26

promptSteamGuardCode is an option that must be set in the constructor, not in the logOn call.

1. For authenticating users through Steam's OpenID provider, you can use the attached PHP class. I don't know where it originally came from, but it works well (although it could benefit from being updated to use curl instead of file_get_contents). This particular version of it was edited by me to authenticate the return domain, otherwise you could be vulnerable to spoof attacks. For logging in a bot to Steam, you can use steam-user or steamcommunity. Or if you really want to, you can look at the source of those to see what they do to implement it yourself. 2. It polls however frequently you tell it to. The rate-limit on the API domain is much higher than on the community domain. You can reasonably safely poll every 1-2 seconds, although for sake of being a good citizen, you probably don't want to do that. SteamSignIn.php

loadUserInventory is deprecated. Use getUserInventoryContents instead.

Try installing from npm now; you shouldn't have any issues. You might need to manually specify the version: npm install [email protected]

Show your code.

Because you haven't set a language.