Dr. McKay

steam-gameserver hasn't been updated a ton, but it does still work. You're better off using that than hacking steam-user to login as a server.

If it's possible, then yeah I'll figure out how to make it happen. As far as I'm aware, right now you can't use a sentry file with the new login system.

Ah, my bad. The version with proxy support isn't published to npm yet. I'll go ahead and yolo it.

let session = new LoginSession(EAuthTokenPlatformType.SteamClient, {httpProxy: 'http://127.0.0.1:8888'}); let startResult = await session.startWithCredentials({ accountName: '...', password: '...', steamGuardCode: generateAuthCode('...') }); Works fine for me. What does your proxy variable look like?

This is not a supported use-case.

At the moment, that's not possible if you're using the WebBrowser platform type. But refresh tokens are good for 200 days, so you can just keep using a refresh token until it expires.

It doesn't matter what the value is, it just has to be different. If you try to connect twice from the same public IP using the same logonID, then the first session will be booted. If you don't supply one (seems like webchat doesn't) then it defaults to 0.

It would be helpful if you mentioned what the error you get actually is. I'm going to assume that you're getting LoggedInElsewhere, which would suggest that you need to set logonID to a nonzero value when you log on.

No, it's not possible.

https://github.com/DoctorMcKay/node-steam-session/issues/7 Fixed in v0.0.4

As far as I'm aware, fetching your own inventory does have limits but they're not as strict as fetching others' inventories. IP limit

There haven't been any changes that necessitated changes in how steamcommunity or steam-tradeoffer-manager fetch inventories, but you might need some more proxies now if you're going to load lots of inventories, and you'll want to cache things more aggressively if you can.

Just do community.uploadAvatar("https://...")

It sounds like you might have a really old version of steamcommunity.

Can you share where you've seen this used? Maybe it's a different module that provides that functionality.

https://github.com/DoctorMcKay/node-steam-user/wiki/SteamChatRoomClient#getfriendmessagehistoryfriendsteamid-options-callback Used as steamUserInstance.chat.getFriendMessageHistory()

I think it's probably just hardcoded directly into the Steam client. I haven't seen anything that would deliver category or genre names to the client dynamically. It looks like you can get category names from HTML on the search page under "narrow by feature" (e.g. I see data-param="category2" data-value="50" data-loc="Additional High-Quality Audio" Of course, Steam Workshop is on there twice with IDs 30 and 51, because Valve... Looks like category2 and category3 are both using the same shared "category" values. category1 likely is as well. I haven't seen anywhere on the store site that directly lists genre IDs, but at least there's not too many of them to figure out individually. Product info is internally delivered as VDF, which doesn't have any concept of lists/arrays. So when Valve needs a list of values, they sometimes just encode it as "intended_value" "1" Valve is really good at creating systems that don't return output at all deterministically. Welcome to the adventure of dealing with Steam.

You never set your persona state to online, so Steam won't report that you're im-game.

You can't use arbitrary fonts, just the /commands available in chat messages. Your screenshot is accomplished using /code or /pre.

Yep, and here's the new link for docs: https://github.com/DoctorMcKay/node-steam-user/wiki/Steam-App-Auth#createauthsessionticketappid-callback

The backend is surely not going to appreciate there not being an actual Steam client involved.

Proxy support is already in progress. The error event is only for errors encountered while polling. If your credentials are wrong, then the startWithCredentials promise will be rejected.

https://github.com/DoctorMcKay/node-steamstore#addphonenumbernumber-bypassconfirmation-callback Although I'm not 100% sure this is working right now.

You're not getting any output because you aren't actually logging the code. You need to add console.log(code) to the bottom.

Yep, check out this example: https://github.com/DoctorMcKay/node-steamcommunity/blob/master/examples/enable_twofactor.js