Dr. McKay

There shouldn't be any need to cancel it. You already have the offer ID, unlike error 16. When you get 504 just wait a bit, check if it's been confirmed, and if not then confirm it again.

steamcommunity has a sessionExpired event. You can also just automatically relog every hour or so, that's what I do.

err.eresult, provided it's available.

"My library" doesn't have limitations, Steam servers impose limitations. They're not exactly published. If you're getting 429, then you're hitting it.

You might want to try logging into the account in a browser and pulling up https://steamcommunity.com/mobileconf/conf, see if that 504s as well. As for telling Valve what you're using, just say you're using SDA I guess. I don't imagine Valve could be hostile toward that, as it isn't exclusively for bot use.

429 does indeed mean that you're being rate-limited, yes.

No idea, ask Valve.

Right.... you didn't see anything.....

Sorry, it was working if you used setCookies but not if you logged in directly. This is fixed in v3.26.1.

That's the very wrong way to fix this. Increase your poll time.

You're kind of meant to use steam-store for store.steampowered.com requests, but I could see how it would be more useful to have that available in steamcommunity, especially since steam-store doesn't offer the HTTP stuff. This is now available in 3.26.0.

Don't reconnect as a result of disconnected. As per the documentation (please read it!), it will automatically reconnect as long as you haven't explicitly disabled that feature (and even then, if I remember correctly it should emit error instead of disconnected). Why are you waiting 15 seconds to relog after your session expires? You can safely do it immediately. As previously suggested, you should keep track of when you last tried to relog and throttle it to avoid spamming logins. Checking isOurOffer inside of newOffer is unnecessary; it will only be emitted for new incoming offers.

Have you tried adding periods to your sentences? In all honesty, you shouldn't be getting 429s from trade offer polls. The WebAPI doesn't do rate-limiting like that. Where specifically are you getting 429 from?

The most effective way to handle confirmations (in terms of on your end, on the user experience, and on Steam servers) is to just check confirmations manually whenever you send/accept an offer that requires confirmation. Try a couple times if you have to (no more than 3) if it isn't in the list, and if it isn't then just cancel the offer and give the user an error.

The fact that you're asking this indicates to me that it's too hard for you. I suggest that you take some tutorials and get some coding experience before you start trying to build a full site like this.

Well, for one thing, your node version is prehistoric. Update it.

You aren't up to date.

That should be all you need. If steam-user isn't up to date, then InvalidPassword might indicate that Steam is rate-limiting your logins.

Glad you got that resolved. For future reference, you could do community.on('debug', console.log); for debug output.

It's basically your responsibility to manually recheck and handle any double-handles that might arise.

Confirmations work fine for me.

If you need to get items from them, you have them make their inventory public. If you're only sending items, then you can just send offers normally and Steam won't block you.

You're doing that in the wrong place. The example accepts every offer. You need to write your code inside of the newOffer event.

Well, you're only accessing item 0 of the array. You want to use a loop of some kind, or forEach. Please google this is you don't understand it, it's a fundamental concept.

You somehow did it wrong. Couldn't tell you any more without seeing your code.