Dr. McKay

I don't see anything obvious in your code that would cause that. Though I do notice that if this is your entire code, you don't need to use SteamCommunity or web sessions at all. You aren't making any authenticated requests to steamcommunity.com. Could you add this and see what happens before you get prompted for a code? client.on('debug', (msg) => console.log('[debug] ' + msg));

Promise limitations prevent any arguments besides err from being sent to the callback if an error occurred. If you update to v4.4.3, you'll be able to access this data via the Error object instead, using err.purchaseResultDetails and err.packageList.

You should never call emit on a SteamUser instance yourself. Events are emitted by the module.

That code looks correct. You're obviously doing something else wrong, but I can't tell you what without seeing more code (and a full stack trace).

Yes.

No, there is no way to suppress those messages from coming in when you receive a trade offer. Eventually I'm sure I'll add a method you can use to mark those as read, but for the time being there's no way to clear them in a bot.

You aren't logged into Steam Community until webSession fires.

I'm not sure whether this would cause the issue you're describing or not, but is your Steam profile set up yet? I only ask due to the name of your function.

Your call to chatMessage is correct (although deprecated; you should check out the docs for the new SteamChatRoomClient), but your comparison is wrong. It should be: if (OFFER.state == TradeOfferManager.ETradeOfferState.Accepted)

Yes, steam-client is obsolete with v4. It's built into steam-user now. And user.setHttpProxy isn't going to work. You should use: let user = new SteamUser({ debug: true, singleSentryfile: false, autoRelogin: true, dataDirectory: '/files/clients', httpProxy: proxyUrl });

Don't bother, Valve fixed that exploit long ago.

What error?

Assuming this is happening like you describe, that would be a problem with Steam, not with this module. But what I suspect is happening is that you're logged into that same account with another bot (or with the Steam client) and its persona state is away. If any logged-on session is in an online state (anything but invisible/offline), the account will show up as that state.

That error means you're calling addMyItem/addTheirItem with an undefined argument. It doesn't matter which inventory you check first.

Yes, that means your time is correct. So your secret isn't.

inventory.filter is always going to return every item that matches the filter. If you only want to send some specific amount of metal, you should use slice, for example offer.addMyItems(ref.slice(0, 3)) to send 3.

Be sure to check out the breaking changes: node-tf2node-globaloffensive

They weren't; I've just joined them to one.

If your clock is wrong and you can't fix it, you'll need to use getTimeOffset and account for it.

The next update will hopefully fix this.

Well, it's been over 24 hours now and both my test processes are still low on memory usage: WS: 2019-02-06 00:43:13 - rss: 134.3 MB, heapTotal: 59 MB, heapUsed: 49.5 MB, external: 173.9 KB TCP: 2019-02-06 00:43:27 - rss: 147.6 MB, heapTotal: 57.9 MB, heapUsed: 49.3 MB, external: 81 KB One is connected to Steam using a WebSocket, the other using TCP. Both have just logged on and gone online on Steam, nothing more. Also, neither has crashed. Node v10.15.0.

You should call addMyItem on the entire item object from the inventory, not just on the assetid. Otherwise, Steam has no idea what game you want to trade items from.

I'm using v10 right now. I just set up a couple processes running on my Linux server generating heapdumps hourly. I'll let it run for a day or so and see what I can come up with.

Currently, the only module I've released that supports promises out of the box is steam-user (v4 or later only).