Dr. McKay

let tag; if ((tag = item.getTag('item_class')) && tag.internal_name == 'item_class_2') { ... }

Please post your solution for others in the future. In this case, the problem was that the first argument to the callback should be err, not offer.

You'll need to retrieve the offer first.

Yes, that's normal. Originally v4 was going to fill in all values not sent by Steam with their defaults (e.g. 0 or empty string) but I decided against that and switched those values back to null (which is how it works in v3). Null means that those values were not sent to us by Steam at all, which is more correct than "assuming" 0 or empty string.

What is the bug?

item_class

Thanks for the info, that's fixed in beta 5. With beta 5, steam-user v4 is now feature-complete (unless there's something major I missed). Now just waiting on some more thorough testing (please post your bugs!) and for me to finish the new chat docs.

I was unable to reproduce this on the v3 branch, but there is indeed a bug in v4 that prevents sentry files from being appropriately confirmed with Steam. It will be fixed in beta 5 to be published later today, but for the time being if you delete your sentry file and login with v3 and provide an email code, v4 should then work.

CEconItem has a getTag method. Filter your inventory to only items with the tag you're looking for.

This is fixed in beta 4. Thanks for the detailed info.

That looks correct enough, though you should probably also check the tag's category.

You should check the item's tags.

You have too many open files. https://askubuntu.com/questions/181215/too-many-open-files-how-to-find-the-culprit

I'm sorry to say it, but if you don't want that behavior then you shouldn't be using steam-tradeoffer-manager. The entire purpose of the module is to keep stateful track of trade offers so that relevant events can be emitted when things change, but what you're asking for is to disregard old offers and only deal with new ones. That's not what steam-tradeoffer-manager is designed to do, and you'd probably be better off using some other library to deal with trade offers if your memory limitations require you to disregard older trade offers.

Beta 3 is now on npm. Now featuring (most of) the docs for the new chat API!

Uhhh, good catch. It should work, but you won't get a response back yet.

Supported in v4 beta 2.

No, none of my libraries would be involved in doing anything like this. You'd probably need to inject something into the game's process to render an item and capture it to an image.

You need cookies to be logged into Steam. You need your identity_secret and to be logged in to confirm offers.

Beta 2 fixes OS capitalization. New chat stuff does not yet have docs, but all the methods have jsdoc. SteamChatRoomClient is available as a chat property of your SteamUser instance, e.g. user.chat.sendFriendMessage(steamID, "/flip")

You need your identity_secret to accept trade offers. There is no way around it. https://dev.doctormckay.com/topic/365-cookies/#user-cookieexpiration

I really don't mind necroing on this forum. You definitely need to put the confirmation acceptance inside the callback to accept, but within that callback it's not a bad idea to add a short delay. Use setTimeout for this.

Automated voting on any content will never be supported.

That looks correct.

The result is the result of the random (same in /flip). In the second line of that block, the resulting random number was 872.