Dr. McKay

No, that's not right.

Looks like your reverse proxy is performing MitM.

I don't think it is on the v2 branch.

You'll probably need to wait until steam-user 3 comes out (whenever that happens, I don't have a timeframe yet) which adds official support for new chat.

The first problem I see is that you aren't handling the callback to offer.accept, which could fail. Secondly, you can use the fs module to read from a file. If it's newline-delimited, you could call split("\n") to get an array containing each line in the file.

No, you'd need to use the WebAPI.

Do something like this: let isEachItemATradingCard = theirItems.every((item) => { if (item.appid != 753 || item.contextid != 6) { // AppID is not "Steam" or contextid is not "Community" return false; } let tag = item.getTag('item_class'); if (!tag || tag.internal_name != 'item_class_2') { // Not a trading card // You could also check that tag.localized_tag_name == 'Trading Card' but that would only work for English return false; } return true; // all checks passed });

It's in the tags property of the item object.

I believe the only way to do that is to use the WebAPI.

I don't believe it's currently possible with new Steam chat.

Is your account limited?

This sounds a lot like spam.

Plain trading sites are generally okay.

People generally use the request module to make HTTP requests.

There's a separate secret that's used for confirmations; it's not the same as the one you use to login.

If you called login without providing an account name or password, then you've logged into an anonymous account. You can do a few things from anonymous accounts, but not all that much. If you want to login to a Steam account, you need to enter the account's name and password. It doesn't matter what account you use, but it needs to be one that exists. If you're creating a bot, most people create a separate, dedicated Steam account for it.

If you try to use two different devices to accept confirmations, you tend to miss confirmations on one device or another. It's not a good idea at all. That said, the error you're getting isn't due to this. It's because your app is either using the wrong secret, or the clock is wrong.

Can you try calling manager.doPoll() yourself?

node-steamcommunity is a Node.js module. It does not work in the browser, even if you use something like browserify.

steamcommunity.com/gid/

Attach a callback to setCookies and see if you get an error back.

Can you add this code and provide the output? manager.on('debug', console.log);

Added, sorry it took a while.

Automating reports/commendations is one thing I won't help with.

I don't believe it was ever officially supported, so I wouldn't be surprised if they removed the backend code for it.