Dr. McKay

You're calling logOff on a new SteamUser instance. You have to call it on the same instance that's already logged on.

You can't. The cell ID isn't linked with your account, it's just used for connecting to servers. I have no idea. No. I don't believe such an event exists beyond probably an email.

You're almost definitely being rate-limited by Steam to prevent spam.

client.myFriends is useless before friendsList is emitted.

You should not do that. Use removeMyItem and removeTheirItem instead.

That might work, but I wouldn't recommend using it as you'd be calling decline on offers that might have already been accepted. I would use offerList and check the creation time of the offers. I don't understand the question. sentOfferChanged is being emitted multiple times for the same offer with state 3? That looks correct. Actually, no. That's a bug. As a workaround you can use getUserDetails on the original offer that you're countering. Also, you should never reassign itemsToGive or itemsToReceive. Use the add(My/Their)Item(s) methods instead. You can't. You need to call it once per appid/contextid.

The inspect link is under actions. You will need to replace %owner_steamid% and %assetid%.

Replace user.value == 2 with client.myFriends[sid.toString()] == SteamUser.EFriendRelationship.RequestRecipient

You won't be able to get the wear, no, but you should be able to get the inspect link. It won't be in getReceivedItems, but it'll be everywhere else, provided you set a language.

What is the error?

It's the ID of the item in your inventory. If you open your Steam inventory and right-click an item and hit copy address/link/URL, you'll get blahblah#753_6_xxx, the asset ID is the xxx.

Inviting people to a Steam lobby is not currently possible. friendOrChatMessage is deprecated. Please try using the new SteamChatRoomClient stuff. That said, this shouldn't happen so I've made an issue to look at later. Yes, but it's pretty difficult.

Sure. Retrieve your trade offer list and cancel everything that's active.

The value is a single-precision float. A double will give you the wrong value. It sounds like whatever you're using to display it is truncating the number of decimals, so you should go check that.

Get rid of the Convert.ToDouble call.

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

There is no event emitted when you send a trade offer via the bot as obviously you should know when you send a trade offer. If you want to detect trade offers sent from the bot's account but not from TradeOfferManager, you can use unknownOfferSent.

I wouldn't expend the effort, no. It could just be an EResult, or it could be something really complex. Protobuf v6 shouldn't have anything to do with it as these aren't protobuf messages.

You could handle the NameBaseItemResponse, sure, but you'd have to figure out what the byte stream means.

I need the full error, and I need to know what line corresponds to the line number it's triggering on.

You need to do it like the other message, with a ByteBuffer. Replace the second writeUint64 with writeUint32 and put the item's defindex in there. But it probably won't work.

Base quality ("stock") items do not have IDs. In TF2, there's a separate GC message used to rename a stock item (NameBaseItem). The value exists in CS:GO's GC message enum, but that doesn't necessarily mean anything as it was just copied and pasted from TF2 and the message may not do anything on the backend. I believe the buffer you should send with that message is a 32- or 64-bit (dunno which, exactly) defindex, followed by the C string.

Yes, v2 came with many breaking changes. I think probably all you need to do is get rid of the coerceToLong calls.

I'm confused. When does it work and when doesn't it?

client.on("friendMessage", function (steamID, message) { if (steamID == AdminID && message.indexOf('!key') == 0) { var GetKey = message.replace('!key ', ''); client.redeemKey(GetKey, function (err) { if (err) { // key not activated } else { client.chatMessage(steamID, "Key activated: " + GetKey); } }); } });