Dr. McKay

Not at the moment. If it doesn't work for you, assuming you're trying to use it correctly, then it's probably disabled. If you paste your code I can tell you if I see any glaring issues with your implementation.

It wouldn't surprise me if they've disabled that.

The answer to both your questions is "who knows, it's Valve".

When you're using a loginKey, you shouldn't send a password. That might have something to do with it.

Use a ?count=x parameter to specify how many items you want it to return. I think the limit might be 2000. If you still get more_items: 1 in the response then you need to make another request with a parameter in the URL start_assetid=.

I'm not going to help you bypass Steam bans.

Not presently, if it's actually been disabled.

It's likely that Valve disabled the message used to change your email via the CM since it goes through the help site now.

Use shared_secret, not secret_1.

bot.steamID

Determining from node-tf2 if an item is tradable is a task. There are like 4 different ways something can be untradable. There could be a flag, there could be one of several attributes, there could be a specific origin (achievement item). You're probably better off just getting your inventory from Community.

Get your inventory contents.

That's generally true, but you'll probably come across some item someday with a different classid and it will break all your stuff.

Classids can change whenever they want.

If Steam doesn't report and licenses for the app, I see no reason why it would appear to be owned.

Can you please log into that account in the Steam client, open the Steam console (Win+R -> steam://nav/console), and type this: licenses_for_app 578080 Then paste the output here.

Not via any of my modules, you'd have to do it yourself.

Your best bet is to just write a bot in Node.js and call to it from PHP.

No new features really (yet), just added support for using the new-chat protocol for player-to-player chats. Hopefully I'll be able to get v4 finished up and pushed out this week, at which point I can start adding features.

Update steam-user to 3.28.2 please.

Looks like maybe there was a condition which ended up in your Steam client connection being disconnected just before your web session was negotiated.

You should use the WebAPI to check if a user is in a group.

What do you mean by "proxy isn't valid"?

As you discovered, calling client.on('friendMessage#' + variable, ...) only creates a listener for the SteamID contained in variable at the time the listener was added. If you need to change the SteamID you're listening for, you need to just listen for friendMessage and check the SteamID in the event.

You shouldn't install steamcommunity globally. Install it locally in the directory where your project lives.