Dr. McKay

TryAnotherCM means the server you connected to isn't accepting connections at this time. Seems like Steam was just down when you tried to log on. Can you try again now?

npm install

You need to update your code for v4. The first argument to all callbacks is now err.

If the steamGuard event is emitted and lastCodeWrong is true, then you should delay 30 seconds before you generate and return a code.

loggedOn won't be emitted unless the logon was successful.

once is your problem. It'll only be fired once, then the listener is removed. Also, promptSteamGuardCode has no function as of v4.

Before you call logOn.

Then you didn't bind the listener at the right time.

I don't understand.

I think you're probably modifying objects that you shouldn't be.

Might you be somehow modifying the SteamID object passed to the user event? Try 4.12.1 and see if that fixes your problem.

Are you up to date?

Not possible currently.

I suggest that you study up on JavaScript asynchronous callbacks.

Surely it's technically possible, just might be more involved than you expect.

https://github.com/DoctorMcKay/node-steam-user/releases/tag/v4.12.0

Doubtful. Yes, provided your persona state isn't "Offline".

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

Nope, methods to create/delete channels aren't yet implemented, but if you need/want them I can see if I can get around to it tonight or tomorrow. Your use-case sounds like an interesting one, so I'd like to enable you to do it.

It's up to Steam when those get emitted. If the data isn't sent, it isn't emitted.

It'll be a lot easier to retrieve your community inventory and just find the item with the matching ID.

As of v3, properties are not converted from snake_case to camelCase. So instead of using defIndex, you need to use def_index.

That is not currently possible.

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

Issue created.