Dr. McKay

What exact issues is it showing?

Check out the steamGuard event. You will want to listen for this, and if lastCodeWrong is true, then wait 30 seconds before generating a new code (or manually specify an offset of at least 30 seconds, but not so much that the code is too far in the future).

I don't really know an awful lot about TypeScript, but my guess would be that something with TS is causing that error. TradeOffer is a function, which should not have any problems being used as a constructor, but maybe TS sees that it's not an ES6 class and decrees that it shouldn't be used as a constructor. What node version are you using?

It's all good. I'm on vacation right now which is why I hadn't gotten around to looking at that yet. I'll see about pushing out an update a bit later.

My mistake; you pass the request into the SteamCommunity constructor, then pass that SteamCommunity instance to the TradeOfferManager constructor as the community property.

Yes, you won't really be able to run more than 10-15 bots on a single IP. You'll need to use proxies or multiple IPs on your machines. You can have steam-tradeoffer-manager use a proxy by setting a request instance with a proxy set using request.defaults to the TradeOfferManager constructor.

Yes, an empty string or other falsy value is effectively the same as omitting the property entirely.

Yeah, the data is only stored locally by the module. It doesn't go to Steam. If you want to pass data to another account with a trade offer, you're best off putting it in the offer message, although be aware that it's very limited in terms of character capacity.

I believe it's only possible for storage units in your own inventory.

serverQuery does not work when logged on anonymously, but getServerList does.

https://github.com/DoctorMcKay/node-steamcommunity/wiki/CSteamUser#getinventorycontextscallback

If the language is specified at all, it's going to retrieve item descriptions from Steam.

That's not currently implemented.

That might help.

You can pass your own request instance to the constructor, with a proxy configured using request.defaults.

The config in your screenshot doesn't look like the config for the command_triggers plugin, but I don't think you could attach two commands to the same trigger with that plugin.

I don't think that's going to be possible with your current setup, but maybe that plugin has an option to spoof who the command came from. Dunno.

Keeping data about item descriptions in memory is going to use memory. You can try lowering assetCacheMaxItems.

The rate-limiting is just really aggressive on the confirmation endpoints. If you're running multiple bots on the same IP, you'll need to use a different IP or a proxy.

Removing the language from the constructor will certainly reduce memory usage if that's a huge concern for you, but of course you'll lose item description data. If all you really need is the items' asset IDs, then that will work.

That could contribute to memory usage for sure.

Does it have tons of trade offers in its near history or something?

It's in the directory pertaining to your platform as documented here, although replace "node-steamuser" with "node-steam-tradeoffer-manager".

https://github.com/DoctorMcKay/node-steam-user#getsteamlevelssteamids-callback

Profiles must be public to use GetPlayerSummaries, regardless of whether you're friends with them or not. You almost definitely don't need a publisher key for whatever you're trying to do, and I don't think it would make a difference in this case anyway.