Jump to content
McKay Development

Dr. McKay

Administrator
 View Profile  See their activity

  • Posts

    3596

  • Joined

  • Last visited

 Content Type 

Everything posted by Dr. McKay

  1. Dr. McKay
    A better way to accomplish this would be to watch for the disconnected event: client.logOff(); client.once('disconnected', () => { // logged off; now safe to log on again });
  2. Dr. McKay
    You have to use node-steamcommunity for that: https://github.com/DoctorMcKay/node-steamcommunity/wiki/SteamCommunity#editprofilesettings-callback
  3. Dr. McKay
    No, it's stored encrypted and the way to decrypt it hasn't been published by anyone.
  4. Dr. McKay
    You need to use the current time, not the time from when you first added the authenticator.
  5. Dr. McKay
    That's definitely a proxy issue. Your proxy isn't responding fast enough.
  6. Dr. McKay
    You exceeded Steam's login rate limit.
  7. Dr. McKay
    There isn't such an event. I think you might be able to check if confirmationMethod is set on an active incoming offer to see if it was accepted and awaiting confirmation, although I'm not certain.
  8. Dr. McKay
    That looks fine to me.
  9. Dr. McKay
    If you use steam-session and log into steam-user using a refresh token, you won't need to enter a code every time. Refresh tokens are valid for 200 days.
  10. Dr. McKay
    No, web cookies are shorter-lived than that. But you can always get new cookies if you still have a valid refresh token. For example: let session = new LoginSession(EAuthTokenPlatformType.WebBrowser); session.refreshToken = getMyRefreshTokenFromDatabaseOrWhatever(); let cookies = await session.getWebCookies();
  11. Dr. McKay
    I don't have any plans to directly add automatic sentry file importing to steam-session.
  12. Dr. McKay
    Steam is no longer issuing login keys. steam-user 4.28.0 adds a hack that makes login key code work without any changes, but using login keys is now officially deprecated.
  13. Dr. McKay
    As far as I'm aware, there's no limit of accounts per IP, but there is a rate limit for logon attempts per IP. As long as you don't get rate limited, you should be good.
  14. Dr. McKay
    That's just the GC being slow. It's a complete mess in CS:GO. CM stands for connection manager.
  15. Dr. McKay
    True, though I wouldn't worry too much about it personally. I don't have any plans at the moment for steam-user v5. Be aware that refresh tokens expire after 200 days and I've yet to see a way to refresh them, so you will need to re-auth with your password after that time.
  16. Dr. McKay
  17. Dr. McKay
    https://github.com/DoctorMcKay/node-steam-user#steamguard
  18. Dr. McKay
    I don't see that anything changed on how the request is made to Steam, so probably a temporary Steam issue. How long has it been going on?
  19. Dr. McKay
    I also commented this on your issue: The first argument to loggedOn is a CMsgClientLogonResponse object, not a login key. You get a login key from the loginKey event.
  20. Dr. McKay
    Might've been a temporary Steam issue. It's working fine for me.
  21. Dr. McKay
    Yeah, just store your SteamCommunity and TradeOfferManager objects in global variables.
  22. Dr. McKay
    That's not a good idea. Steam will invalidate your session if your IP changes too much.
  23. Dr. McKay
    If steam-user connects with a WebSocket, it sends pings automatically every 30 seconds and disconnects (and emits the disconnected event) if Steam doesn't reply. If you want to make sure that the pings get sent, you can force the connection protocol using the protocol option. Example: let user = new SteamUser({ protocol: SteamUser.EConnectionProtocol.WebSocket });
  24. 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.
  25. Dr. McKay
    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.
×
×
  • Create New...