Dr. McKay

No, steam-user can't do anything like this.

Issue created.

Great, glad you got it working. As an explanation for why you were getting loggedOn emitting, if accountName isn't specified or is undefined, then steam-user will log onto an anonymous user account.

That looks right. Make sure your config.accountName is set properly.

This isn't how you send a lobby invite. You need to use a separate kind of command which I don't believe is implemented in steam-user at this time.

If the game is telling you that the blueprint is invalid, either you're trying to craft the wrong items or something weird is going on with the GC that we can't do anything about. No, the only ways to update your inventory on steamcommunity.com are to launch/quit a game, complete a trade offer containing items in that inventory, or start a real-time trading session.

Sure, I guess, but there's no way around that. You just need to have enough memory.

Try leaving out the recipe ID.

I have no idea what you're talking about.

As long as you didn't set dataDirectory: null you should be fine.

If you're going to lower the max items value, I would also configure a dataDirectory so that excess items can be stored locally on the disk instead of having to consult Steam every time. Performance shouldn't be impacted too heavily, but it may be noticeable. You'll definitely minimize your impact by configuring a dataDirectory.

This is already done in the module via persisting to local disk with the dataDirectory option (which you can redirect to go anywhere you want, including MongoDB). Update to v2.10.0 and you can override the maximum size of the asset cache, but beware that doing so will negatively impact performance as more and more items will need to be retrieved from the disk for every poll. In practice, for the best performance, you will need more RAM the more trades you make.

One of the descriptions will indicate if an item is uncraftable.

I suspect that you're having problems because you have two newOffer handlers. They will both fire, so you'll be trying to decline all offers that aren't sent by the owner, even if they should be accepted by your trading logic.

Oh yeah, it's an object. Object.keys(client.myFriends).filter(steamID => client.myFriends[steamID] == SteamUser.EFriendRelationship.Friend).length

client.myFriends.length

Unless you want to dive into the code and try to figure out what's wrong, you'll have to wait until I have time to look at it, which probably won't be anytime soon. Sorry.

I've added ban methods in v4.10.0.

The module itself is definitely supported. There are some deprecated methods and such, but only because newer things have replaced them. I did a test myself and I got about a half-second round-trip time, counting from when I hit enter and stopping when my bot responded to me. That doesn't seem unreasonable to me. I just haven't gotten around to adding a feature to ban people from a group chat yet. If that's something you need, I'll see if I can prioritize it.

I don't know why you would call this a "legacy module", but any lag is on your end. Either in your code, or in your connection to Steam.

Auth session tickets were never really tested. It's pretty likely that the code to retrieve and activate them doesn't work properly.

getPlayerCount is an asynchronous method. You need to either handle the Promise, or attach a callback (user.getPlayerCount(504370, function(err, count) { ... })). But you also need to wait for the loggedOn event before you do anything after calling logOn.

The first argument needs to be an enum value, not a string.

Games.join("\n")

No.