Dr. McKay

You should really just use the WebAPI instead.

offers.offer isn't valid. You need to use offers.createOffer which returns an offer object.

It totally works. Just tested it myself. You're doing something else wrong. Maybe you're running two instances of the bot?

Yes, call offer.getExchangeDetails and if the trade was rolled back (the likely scenario in this case) you'll have the post-rollback IDs there.

Not 'ActiveOnly', TradeOfferManager.EOfferFilter.ActiveOnly And also per the docs, just omit the time value if you only want stuff that's active.

Nope, you pretty much just have to check the name for "Case Key".

What you have there will work provided the user does have 350 gems in their first gem stack. It's possible to have multiple gem stacks, so you'd need to iterate the gems array and total up all the amounts to see how much the user has, then add the appropriate amount from each stack if they do.

Yup.

Is everything up to date? What's your poll interval?

Move your client, community, manager, logOnOptions declarations inside of the Bot function.

Yes, you do need to login once.

No, you need to not call webLogOn if you aren't connected.

Pulling one inventory every 2-3 minutes should be fine. A good poll interval for steam-tradeoffer-manager is 30 seconds (30000 ms).

GetFriendList gives you timestamps.

Correct. When you're using steam-user, your "login" is a connection to the CM. It's completely distinct from your web session. When your web session expires but you're still connected you don't need to reconnect. Just get a new web session which requests new cookies from the CM.

It doesn't retry, ever.

It's being called for a reason, and that reason is that your session expired. I assume that you're getting your session from node-steam-user, and you're calling logOn when it expires. That's wrong, you should call webLogOn.

Use both. If the callback returns success then send success immediately. If it returns error 16 (timeout) then wait for receivedOfferChanged.

let sold = JSON.parse(require('fs').readFileSync('TotalSold.json').toString('utf8')); sold.TotalItemsTraded.TotalKeys += something; require('fs').writeFileSync('TotalSold.json', JSON.stringify(sold, undefined, "\t"));

You can only cancel active offers (state 2). State 4 (Countered) means that the trade offer was countered. The offer that's in state 4 is no longer active, and a new trade offer with a new trade offer ID was sent to you with the counter offer.

Not at the moment. You could open a GitHub issue on https://github.com/DoctorMcKay/node-globaloffensive to get it added though I can't promise it'll happen anytime soon.

Without seeing your code nobody can help you.

It wouldn't work for CS:GO.

Probably because you're using some when you mean to use forEach. And also Steam probably has a chat message rate-limit.

Steam doesn't "take care" of anything chat-related except links it feels to be malicious. That said, unless you're doing something utterly insane like eval()'ing chat messages you're fine there.