Dr. McKay

It works the same way as for trade confirmations.

Did you copy the sentry file from your Steam installation to use with node-steam-user?

addMyItems will only work with an array of multiple items (which is what inventory is). You need to use addMyItem to add a single item (e.g. a single element from inventory). The inventory[1] syntax retrieves element #1 from the inventory array (an array is essentially a list). Note that since numbering starts at 0, element #1 is the second ordinal element.

That offset-retrieval code won't work. You need to wait for the callback before you try to do anything with that offset.

Does it appear as online/in-game on its direct profile?

Please give 3.21.0 a shot.

Thanks. Looks like there's an expiry time in those packages which is being ignored. Let me take a look at the code.

You probably never called setPersona on the node-steam-user to set it online.

You can never accept an offer you create. Accepting is an action that can only be done by the trade recipient. If this happens when accepting incoming trades, that means they aren't active. They've already been accepted or declined or canceled.

I'd avoid outright saying it. Just say that you have a lot of confirmations on your device for trades that no longer exist, and give that error message that you see in the title.

Please dump your licenses property to JSON and either post it here or PM it to me.

Wrong module. This isn't node-steam-tradeoffers.

You probably need to contact Steam Support.

I honestly have no idea what you're asking. The statistics in Steam groups aren't always up-to-date or correct.

I don't think family sharing applies since it's per-machine. Are you sure that they aren't just free apps?

I'm not available for work.

If Steam is down, you can't log in. I don't understand where the confusion is. Wait for Steam to come back online, and the client will reconnect on its own and emit webSession.

If you're using node-steam-user, it will automatically reconnect when it gets disconnected. You can handle the event where you need a Steam Guard code by setting the promptSteamGuardCode option to false and handling the steamGuard event.

You need to call webLogOn with no arguments, and call it on the same Steam client as the one that's already connected to Steam.

This is what the amount property is for.

Read the second half of this.

That's the correct method to use, but you can't use it if you aren't currently connected to Steam (e.g. because Steam is down). That's what's throwing that error.

The code in your first post will absolutely work. Regarding your second post, are you passing the 64-bit SteamID as a string instead of a number? JavaScript can't handle integers that are that big.

You're trying to relog the web session while Steam is down. Don't do that, and just wait for Steam to come back. It will emit webSession automatically once it reconnects successfully.

Has your web session expired?