Dr. McKay

https://steamerrors.com/15

https://httpstatuses.com/429

https://github.com/DoctorMcKay/node-steam-user#chatmessagerecipient-message-type

You don't have to buy games. Just adding $5 to your wallet is sufficient.

The constructor is new SteamCommunity()

If you're using two-factor authentication (via SDA or whatever), then there's no new-device cooldown, so no.
 
But if you aren't, then the answer is still no because "devices" are remembered by sentry files. Your sentry file is saved by steam-user in your appdata directory, so it will always be reused on the same machine (until you reformat or whatever).

Thanks, live in v3.27.1.

You're logging on too frequently.

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

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.

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.

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.

You aren't up to date.

If you do it right, it doesn't really matter how many processes you're using. Databases remain consistent regardless of how many processes are accessing them, provided you're querying correctly.

You can use steamcommunity for that: https://github.com/DoctorMcKay/node-steamcommunity/wiki/CSteamUser#getinventorycontextscallback

https://github.com/DoctorMcKay/node-steam-user#enabletwofactorcallback

https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/TradeOffer#counter

You aren't checking the error. In every callback, if err is truthy, then there was an error and all other arguments are undefined.

This is being discussed in issue #122.

Correct. steam-tradeoffer-manager will handle all that polling for you.

1) I'd keep your login checker code in there. The manager will only notice that your session is gone when you try to send/accept an offer. Normal polling and canceling offers uses the WebAPI and your API key, so the session isn't actually used there.
2) That's more than fine. 5 requests per minute is super low.
3) You're correct, your first snippet generated the code once on boot. It ceased to be valid once you used it.

You probably attached a function to the poll data somewhere else in your code. That taints the entire object and makes it unserializable.
 
Look around for somewhere where you're attaching a function to pollData.

https://github.com/DoctorMcKay/node-steamcommunity/wiki/SteamCommunity#uploadavatarimage-format-callback

Use steamID.toString() instead of JSON.stringify.

The steamID property will be null if you aren't connected. It'll be a SteamID object if you are.