Dr. McKay

I don't understand what you mean by that.

Your issue is probably that you aren't urlencoding the payload. I'm not super familiar with the fetch API you're using but I would be very surprised if it didn't have a mechanism to send an application/x-www-form-urlencoded request payload without having to encode it manually as you're doing. And yes, Steam login cookies that you acquire from any source can be used on all Steam properties.

You need to specify Origin and Referer manually, but all the other headers you're specifying should be left out as they're HTTP protocol-level headers that request will set on its own.

That's not possible.

There shouldn't be any special considerations with the rsa key request.

Get rid of the curly braces around requestoptions. And also quit using the confirmation checker as it's been deprecated for years.

In your instance, steam-user (client) is for logging into Steam and for receiving item/trade notifications and steamcommunity and steam-tradeoffer-manager are for interacting with the econ service (which is all over HTTP).

I don't see why you'd want to specifically use the oauthlogin method. What's wrong with logging in via community or user normally?

Check the myFriends property for users who've invited you.

You would need to download the game files from the CDN, parse items_game.txt, unpack the vpks, and figure out how to attribute texture files correctly to given items. Have fun.

None of those messages are going to work for your needs, since they're only for requesting the logged in user's inventory. You can't request other users' inventories that way. Using the HTTP endpoint is pretty much the only way.

You would need to also bind the local address on node-steamcommunity and additionally pass that community instance to the steam-tradeoffer-manager instance in the constructor.

Well, you're logging in twice and only once with an auth code. Of course the login attempt without a code is going to fail.

The transfer requests are just to set cookies on all the Steam domains, so logging in on community also logs you in on store and vice versa. But it's the same cookies on all domains.

I guess you're not using the correct shared secret. I don't know why you'd need to instantiate that sid variable, but that input format is correct regardless.

I would just look at what node-steamcommunity does to login: https://github.com/DoctorMcKay/node-steamcommunity/blob/master/index.js#L57

If there's no release date in the data returned from getProductInfo, then that data wasn't put into that system. The only other way to get the release date would be to scrape it from the game's store page.

Your first screenshot is an error event. If you don't add a listener for the error event and it gets emitted, it will crash your app. It looks to me like the Steam server you connected to exploded... has this happened frequently?

It's game_server_ip and game_server_port in the user event.

That data comes from the game server directly, not from Steam. You'd want to use something like this for that.

You'll get 1200.

I don't believe it does, but I don't know why you'd want to call that very frequently in the first place.

Do not use prefix-underscored methods. They are internal to the module and could change at any time.

https://github.com/DoctorMcKay/node-steamcommunity/blob/master/examples/edit-group-announcement.js#L17

It doesn't look like you ever passed cookies to your steamcommunity instance. You'd want something like this: client.on('webSession', (sessionID, cookies) => { community.setCookies(cookies); });