Dr. McKay

Sometimes a trade fails halfway through committing, so it rolls back the items that were already exchanged. That changes the asset ID for those items. There isn't any way to figure out what the IDs changed to without just comparing names and other identifying features.

Officially there's a 100,000 request-per-day limit, but besides that there's no IP/key rate-limit or throttling.

Using node-steam-user, use getPersonas.

logonID doesn't work with node-steamcommunity.

The only conflict you might run into is IP-based Steam rate-limits.

Please update to v1.22.3 and see if the issue persists.

Nobody really knows for sure what causes Steam to kill sessions, but I've noticed that logging in from another place will log out previous sessions. There isn't any way to remember a password. The idea is that you use the oAuthToken you receive in the callback to login in order to resume the session in the future, but I'm not sure how well that works.

I have no idea what you're asking. What's a "cluster bot"? You're trying to run several bots on the same server using the same process, or you're using a Node Cluster, or what?

https://github.com/DoctorMcKay/node-steamcommunity/wiki/Steam-Confirmation-Polling

SteamCommunity doesn't save anything to disk on its own. One of the examples might, but you can change it easily.

Check the appid property of all the items in the offer.

It really depends on what all you'll be doing and how much traffic you'll be generating. Maybe 30 bots per gig of RAM would be a decent estimate. Somewhere around 10 per IP.

I have no idea what you're asking in your first question. I don't believe that I've added anything to steamcommunity currently to check outstanding friend requests. You'd need to use steam-user or similar for that. I'm not here to be your personal one-on-one teacher. I'm providing my code for free and I'd appreciate it if you were patient and didn't private message me if I don't look at your thread immediately on a Sunday.

Are you using the mobile authenticator on an actual phone as well?

Either your identity_secret is wrong or your clock is wrong.

Yes, it will if it changes after unknownOfferSent is emitted.

HTTP 403 is probably indicating that Steam is rate-limiting your IP. Slow down your requests a little and don't spam them all at once. You get "Access Denied" when trying to get an API key if your account is limited.

Codes can only be used once. If you try to login again within a 30-second interval then Steam will reject the already-used code since it hasn't changed yet. If you need to login that frequently, you're doing something wrong anyway.

Need a lot more information. What are the specs of your machines? How many IPs do they each have? What will your bots be doing specifically?

If you're using the mobile authenticator then logging in from a new device doesn't have any trade cooldowns.

If you want some debug logging, then add: community.on('debug', console.log);

Always post the code. Nobody can help you with just that output.

Set a language and the objects in the arrays of items (itemsToGive and itemsToReceive) will have names in them.

Please post your code.

Probably, but I don't see what the use of that is.