Dr. McKay

You need to call manager.createOffer each time to get a fresh offer.

You can only perform one craft at a time; sending that many craft requests will get dropped. You should call craft(), then wait for the craftingComplete event before you craft again.

No, steam-user isn't compatible with Steamworks in any way. You could write an app that logs into Steam and fetches leaderboard data (leaderboards aren't presently available in steam-user though so you'd need to implement that yourself), but you wouldn't be able to reuse any of your existing C# code. Have you tried using steamcmd? I have no idea if it works with Steamworks apps the same way as the proper Steam client.

No, you have to do it one-by-one with around a 1-second delay between requests. If you're trying to get data for items in your inventory, there's no need to inspect them as all the data is available in the inventory array.

Update the module to the latest version.

Dunno, maybe your cookies are wrong.

Depends on why you're not connected. If you disconnected because Steam went down or you otherwise lost connection, SteamUser will automatically attempt to reconnect. Unless you messed with the autoRelogin option, the only situation where you'd need to call logOn again is if the error event got emitted.

Get rid of {encoding:"base64"}. You don't want a base64 string, you want a Buffer.

Cookies go in the Cookie header. Check that MDN link I posted.

No to both of those. I try to respect some of the more important abuse-prone things to avoid drawing Valve's wrath.

Valve made a change on the server side.

Cookies go in headers, not in the request body. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cookie

This is likely the same issue as this thread: node-csgo-cdn likely needs to specify the branch name (public).

Yes, a classid should change if a name does, although you won't necessarily get a different classid if an item has a different name but is otherwise the same item, e.g. name tags.

Valve removed the API call to cancel and decline offers. This is fixed in 2.10.5.

No, you can't run the same account under multiple processes without bad things like that happening. You can use steamstore to get your wallet balance: https://github.com/DoctorMcKay/node-steamstore#getwalletbalancecallback

That sounds like your cookies are invalid or expired.

That's pretty much expected. It's not 100% clear what causes Steam to invalidate cookies, but initing a session is known to invalidate old ones.

The post parameters go in the post body, yes. Referer should be the only extra header you need.

You're sending all the post parameters as cookies.

You would need to download the picture from your link and use that.

You have to load inventories separately, but you can mix and match items added to a trade from different games.

You could manually construct an object, like this: let assetIds = [1, 2, 3, 4, 5]; offer.addTheirItems(assetIds.map(id => ({appid: 730, contextid: 2, assetid: id}))); Steam needs to know which game you want to access items for, so the appid and contextid are required.

addTheirItem does not take a number argument. Re-read the docs.

As far as I know, not all content servers require auth tokens anymore and maybe the backend is no longer returning empty auth tokens for servers that don't require one. Or maybe they've fully moved all content servers away from requiring auth tokens. I'll have to do a little research to see which is the case. In the meantime, you could try editing cdn.js and replacing line 230: // Replace this: let {token} = await this.getCDNAuthToken(appID, depotID, vhost); // With this let token = ''; try { token = (await this.getCDNAuthToken(appID, depotID, vhost)).token; } catch (ex) { }