Dr. McKay

Right. If you were using node-steam-user then just using offer.partner would work, but since you're using node-steam you need to convert it to a string.

Run npm update and it should go away.

I assume friends is not node-steam-user?

Once you're logged in, you need to use the same IP for all your requests.

Yes, the exterior is available in both the tags and the market_name.

offer.addMyItem(inventory) inventory here is an array of items. If you want to grab the first item from your inventory then use inventory[0].

You need to confirm the offer. https://dev.doctormckay.com/topic/289-trading-and-escrow-mobile-trade-confirmations/

It does not.

That looks right to me. Are you friends with the people you're requesting data for?

client.setPersona(SteamUser.EPersonaState.Offline); That says offline to me.

That shouldn't be possible. All I can figure is that you aren't grabbing the same item, or else it's already left your inventory.

I'm not sure I'm following. An offer is accepted, you call getReceivedItems and save its ID. Then you load your inventory and the ID of the item in your inventory is different?

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

Like, actually online? You used setPersona to mark it as online?

Show all your code please. And indent it properly so it's readable.

Is your bot online?

What's invalid about that response?

sent is an array of TradeOffers.

You can use webLogOn at any time, but if you spam Steam then Valve is not likely to be happy. You shouldn't create an interval inside of an event callback. Create it outside the callback, in the root level of the module (the part that has no indentation). Keep track of the last time you called webLogOn (a timestamp) and don't call it if it was less than say a minute ago.

Use setInterval but outside of any event callback. Also, you need to keep track of the last time you called webLogOn and abandon if it was too soon ago, as sessionExpired can be emitted at any frequency (perhaps several times a second).

You will always get an err in sessionExpired. It's not indicating that there was an error in the session expiring or anything, it's just the Error that made us aware that the session has expired. Also, I'd suggest keeping the login interval as well.

What version are you using?

Yes. As per the documentation, you cannot use this with a limited account.

You're correct regarding the behavior of setTimeout and setInterval. The problem is, if you create a new interval every time you get a new web session, then you end up with many auto-repeating timers.

That will create a new interval every time your session expires. Either use setTimeout or create the internal outside of that event callback. Also, you may want to listen for the sessionExpired event.