Dr. McKay

The confirmation checker doesn't have any events like that. Those belong to steam-tradeoffer-manager. You should just call acceptConfirmationForObject whenever you send or accept an offer that needs confirmation, and that's it.

It's possible but steam-user won't help you as it has nothing to do with HTTP. Also, as far as I know there aren't any modules at all that do the queue so you'd have to implement it yourself.

At the moment, that's not possible. You could create an array or queue somewhere and push offers into it as the event is emitted, then when you're ready to process them go through that array.

What's in your tradelink variable?

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Math/round

This is exactly the reason.

Are you friends with them? I believe you need to be friends and they might even need to be online.

That's a scam.

It probably failed because you're trying to get an encrypted appticket for an app that doesn't have it enabled.

Add another call to getInventoryContents inside the callback of the first one.

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

That API method doesn't do what you expect. Specifically, it doesn't return market prices nor does it work for Steam Community items.

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

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

Move the token outside the SteamID parenthesis.

Make sure that your bot account has permission to kick users. That error is coming from Steam so there isn't much else I can tell you.

Make the token expected.

Well done, Valve. I'm not seeing that on my own inventory history page. Possible it's just a transient issue?

There is already an existing thread for this (and this isn't the right forum anyway).

Have you sent/accepted the offer already?

No, because having two clients logged into the same Steam account does trickery with your online status.

I think strictly speaking, the leading SteamID isn't part of the ticket. Some implementations just expect the SteamID to be sent preceding the actual ticket. Therefore, I don't believe I should be including that leading SteamID in the ticket I return.

What exactly is happening?

Thanks for the info. I've merged the pending pull request and published an update.

I don't really think this can be done with a bot. The bot would need to go online in order to receive chat messages, which would override your persona state from the proper Steam client.