Dr. McKay

You are never giving TradeOfferManager login session cookies. You need something like: client.on('webSession', function(sessionID, cookies) { manager.setCookies(cookies, function(err) { if (err) { throw err; } }); }); You also need to renew the web session when it expires.

Please post in the correct board next time. I've moved your topic. An ID event is a special kind of event specific to steam-user where both the base event and the event suffixed with the SteamID of the relevant account are emitted. For example, if I sent you a chat message, both friendMessage and friendMessage#76561198006409530 would be emitted. Listening for the latter event is mostly useful for when you only care about one specific user. For example, you might hardcode a listener for friendMessage#yoursteamid to listen for admin commands (or perhaps something like on('friendMessage#' + config.adminSteamID)).

It might be better for you to just learn how to work with Steam Guard first. If you're using email-based Steam Guard, then it will only prompt for a code once as long as you run it on the same machine (and you're using node-steam-user).

Not presently. Why do you need to disable it?

The next update to node-steamcommunity will give a different error message if your PIN is being rejected due to a rate-limit. There's currently no way to unlock your Family View session through node-steam-user.

GC messages go through the CM, but other than that they have no relation. Therefore, GC communication is out of scope for steam-user. You may want to check out node-globaloffensive. You could fork it and add whatever messages you need if they aren't there already.

Either your secret is wrong or your clock is wrong.

That doesn't make any sense.

You need to keep track of which asset IDs you've already sent offers for and not send them again. You can either keep track in your code (which I recommend), or you can use https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/TradeOfferManager#getofferscontainingitemsitems-includeinactive-callback

How so?

item.appid == 753 You need to provide a language to get most details.

First, you should make sure the appid is 753. Secondly, did you provide a language to the constructor?

Show your code.

15 seconds is a really bad idea.

You can't, and there's no need. It'll give you error 403 if the inventory is private.

A proxy is not a magical 429-be-gone. I advise that you don't use the confirmation checker at all (or if you do, set it very high, like 5 minutes). Using acceptConfirmationForObject should work fine.

this.client.users[steam_id] is undefined? When are you calling this? Very soon after logon? Some time after?

You need a license before you can play any game. Some older free to play games (like TF2) are in package 0, which is automatically granted to all Steam accounts (except anonymous ones). Newer free to play games have what are called "free on demand" packages, which you need to request ("demand") prior to playing. You can use the requestFreeLicense method I just added in v3.19.0 for that.

Please show the code you're using to look them up in client.users.

Friends do count as users we've encountered. That said, to be 100% safe it might be better to do it your way and check if the user's data is present and request it if not, but that shouldn't be necessary for friends (then again, this is Steam we're talking about).

There is not, because there's no way to kick a user from a group via the Steam client and thus there's no message to do so via a client connection. You can do it with node-steamcommunity: https://github.com/DoctorMcKay/node-steamcommunity/wiki/CSteamGroup#kicksteamid-callback

Update to v3.30.6 and this should be fixed.

You shouldn't need to do the accept on a timeout. You said the confirmation checker is going slow, once every two minutes? That should be fine for 15 accounts, probably even if they all hit it at once. Would it really hurt to try disabling the automatic check for a bit?

1. Is the bot itself online on Steam? You can't get some persona data unless you're online. 2. Since it appears that you're only sending stuff to friends, there's no need to use getPersonas to get up to date data. There is a property (I think it's users?) which contains up to date persona data for all friends, provided you own state isn't offline. Steam sends updates for friends automatically.

Strange, that really shouldn't be doing that then... How frequently are you sending offers that need confirmation? Also, could you use SteamCommunity's HTTP post hook to see which specific request is failing, whether it's the request to load the confirmation list or the one to actually approve it?