Dr. McKay

Your password is probably wrong.

If you flood Steam, you'll get rate-limited. If you're accepting many offers at once, add a delay between the requests.

Thanks, live in v3.27.1.

It doesn't look like you're checking the login error.

No. Please read the documentation. Defindexes aren't currencyids. As far as I know, only Spiral Knights uses "currencies" in trading.

I'd suggest taking questions like that to Stack Overflow or similar. Or just search this forum as I'm sure it's been discussed many times here. I'm not really here to teach you JavaScript though.

https://dev.doctormckay.com/topic/289-trading-and-escrow-mobile-trade-confirmations/

You're logging on too frequently.

I assure you that it does.

sessionExpired won't be emitted on the TradeOfferManager, but I believe it will be on the steamcommunity that you pass in.

Firstly, you should slow down your confirmations if you're getting hit with 429s. The automatic confirmation checker, while easy, makes unnecessary requests to Steam. I recommend that you just deal with confirmations manually as needed. Newer versions have a method to automatically accept all confirmations very easily. That said, you can set the local IP in the constructor: https://github.com/DoctorMcKay/node-steamcommunity/wiki/SteamCommunity#constructoroptions

It's not recommended to use for ... in on an array.

Do you know what an array is?

itemsToGive is an array.

I can't reproduce this. I started a trade, put up an item on one side (the request sender), committed the trade, and confirmed it on the sender's side. The recipient briefly showed an active offer, then it immediately went accepted. Maybe it's possible that there's some kind of bug in the module, but I don't have time to test that right now. What happens if you wait 30 or so seconds after you get newOffer and then check its status via offer.update?

You're declining the offer? Don't do that. And just to be super clear, this is happening via real-time trading with trade requests in Steam chat?

Did you confirm it?

You can accept it, but that's unnecessary. All you need to do is accept the confirmation.

You don't need to accept real-time-trade offers. Offers that are created from real-time trades are accepted automatically, you just need to confirm them. The wiki page on GitHub has more information.

Check fromRealTimeTrade and abort if it's true in newOffer.

Trade failures which result in ID changes are infrequent enough that you can fix them manually. Or you could detect when a trade goes InvalidItems and automatically figure out which items in your inventory have unrecorded asset IDs and match the description of the missing items.

classid and instanceid can change whenever they want. And no, they don't include wear for uniqueness.

Yes.

It doesn't work if the trade didn't complete fully, no.

https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Real-Time-Trades