Dr. McKay

Do not edit the module. const SteamUser = require('steam-user'); let user = new SteamUser(); user.logOn({ accountName: 'your_account', password: 'your_password', logonID: 12345 });

14000000D81B906BE8187273F69B60320100100105DE505F180000000100000002000000D62F504A883AAB9D8B8A130001000000 is the hexadecimal representation of the ticket. You CRC32 the binary, not the hex.

Just set logonID to some number when you log on, and use a different number for each instance of the account.

You can use setTimeout to delay some action.

I can't offer you any support for node-steam.

Not possible.

Not as far as I'm aware.

Steam changed how wallet codes are redeemed. GitHub issue here. I will fix this as soon as I can, hopefully in the next day or two.

No.

The friendMessage event you're using is deprecated and you should use the SteamChatRoomClient version instead, but that should still work and I don't really see any reason why it wouldn't. What kind of behavior are you seeing and what console output are you getting?

No.

Have you tried making any requests after you set your cookies to invalid values? It can't know the session has expired until it tries to make an authenticated request and Steam redirects us back to the login page.

No.

I don't see any reason why that shouldn't work. All I can figure is that you have an acceptConfirmationForObject call somewhere happening before you get your cookies.

Can I see your TradeOfferManager constructor?

Steam should not allow a trade offer to be canceled while it is in the middle of committing. Those cases are most likely because Steam ran into an error while committing the trade and rolled back the items it had already transferred.

You're correct, there will only be a tradeID if the recipient attempted to accept the offer. A situation where there might be a tradeID but the trade did not happen is an error in Steam when attempting to commit the trade, or an escrow cancellation. I believe that if Steam has an error and rolls back, the trade offer state will go to InvalidItems since the rollback will change the item IDs (for most games). But if it's an escrow cancellation, the trade offer state will be Canceled and escrowEnds will not be null, which allows you to differentiate between cancellations by the sender and escrow cancellations. There's no way to tell which side canceled the trade in escrow though, but you presumably know whether you did it or not.

Unfortunately not.

The GC can get confused if you disconnect. It may work better for you if you quit CS:GO with gamesPlayed([]), wait 5 seconds or so, then log off.

Sorry, the docs are unclear on this. You want to do this: csgo.on('accountData', (accountData) => { console.log(accountData); }); The accountData property only gets set after all accountData event listeners have returned.

No, it needs to actually connect to the Steam network so it's not going to work with OpenID. You can't, you need to retrieve the image from the community site.

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

Interesting, I wasn't aware of that behavior.

You need parenthesis to actually call the send method, like offer.send()

Have you tried deleting them one by one?