Jump to content
McKay Development

Dr. McKay

Administrator
  • Posts

    3565
  • Joined

  • Last visited

Contact Methods

  • Website URL
    https://www.doctormckay.com

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

48555 profile views
  1. Seems like a backend change that access token refreshes for SteamClient tokens are authenticated now. I've updated the docs to reflect it: https://github.com/DoctorMcKay/node-steam-session?tab=readme-ov-file#refreshaccesstoken
  2. You've got some problem with your proxy being unable to connect to Steam, it seems.
  3. The string you pass to httpProxy needs to start with http:// createConnection is not a valid option for the SteamUser constructor. To use a SOCKS proxy, you should use the socksProxy option.
  4. It may not be enabled on that phone, but it's enabled somewhere.
  5. I'd guess your refresh token is probably expired or now invalid.
  6. You clearly already have MFA enabled if it's asking for an MFA code.
  7. Can't be done. You can get a web logon nonce from https://steamcommunity.com/chat/clientjstoken but that's not the same thing as a refresh token for the client; you have to send that as web_logon_nonce in the CMsgClientLogOn message.
  8. You would need to download and parse items_game.txt, look up the sticker by its sticker_id, then fetch your appropriate language file to translate the localization key into an actual name.
  9. It's a Date object. You can use its UTC methods to manipulate the object in UTC/GMT.
  10. Market confirmations have existed for a very long time. You can use node-steamcommunity to accept them.
  11. It's fine in this case, don't worry about it.
  12. Those xml endpoints are pretty unreliable and anything that uses them should probably be considered deprecated. Using the WebAPI for anything that it covers is going to be your best bet.
×
×
  • Create New...