Dr. McKay

You also realize that in order to join a VAC-secured server, you'll need to implement VAC? And that you'd be fully insane to try to implement VAC.

You realize that you'll need to implement the game server's protocol yourself, correct?

That is currently not supported. What do you need it for?

https://github.com/DoctorMcKay/node-tf2#backpack

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

You can use node-tf2 to get and craft your inventory.

You could use update.

You're saying that sometimes newOffer isn't emitted for an offer?

It's not really recommended to manipulate poll data. TradeOfferManager's job is to emit newOffer once per incoming offer. Errors can be frustrating but it's your responsibility to make sure that they're dealt with properly. You could use offerList to check for offers that should have already been accepted (probably want to keep a list of offers you've attempted to accept and the timestamp so you don't try to accept an offer too frequently).

Spamming threads won't get you (free) help any faster.

That's known as spam, and I won't help with it.

Up to you. Maybe make sure key and metal aren't 0.

You have two threads. Why?

You aren't assigning anything to BuyKey and FromRef1. forEach doesn't return anything. Also, further on down you're using = when you want to use ==

What's with the nested listeners on newOffer? And on separate emitters?

Why are you constantly using commas when you mean to use &&?

every will stop executing as soon as it reaches an entry that doesn't return true. Also, return will stop executing the function immediately. You want forEach, and don't return if the name matches the desired value. Instead, use that check in an if.

I'm not really at liberty to say much about that, but to my knowledge it isn't possible through the steamcommunity.com data.

There are multiple ways to do this. You could loop the item arrays and increment counters when you find matching items. You could use filter to filter the arrays for particular items and check the length of the resulting arrays.

The constructor is new SteamCommunity()

I'm not sure what you're asking.

I've already told you what can cause that error. I suggest that you double-check everything.

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).

You're not using steam-tradeoffer-manager.

Then Steam is either down or you've had too many failed login attempts.