Jump to content
McKay Development

Dr. McKay

Administrator
  • Posts

    3408
  • Joined

  • Last visited

Everything posted by Dr. McKay

  1. Please read the documentation. An error event is emitted if there's a problem logging on. Also, you should under no circumstances be collecting credentials from users.
  2. Worked fine for me. Note that it won't do anything if you already own those apps.
  3. If you're asking how to check if the bot is connected to Steam, check if user.steamID is not null. If you're asking how to check if the web session is still valid, node-steamcommunity has some stuff for that.
  4. I'd need to see how you're saving it, but it's not unlikely that the cookies are just expiring.
  5. Yeah, that should probably have a GitHub issue made for it.
  6. The way you've written it here is correct. The error indicates that you're trying to access the variable outside of the scope where it was defined.
  7. The settings on that account do not allow you to add comments.
  8. Both your node and npm are ancient. Update them both to supported versions (node 6 or later, npm 3 or later).
  9. There is no guarantee that if an assetid changes, it won't change to an assetid that has been previously assigned to an item. They are only guaranteed unique at one point in time. That said, for Valve games, when an assetid changes it will only increase and will never be an ID previously assigned.
  10. It's in the cookies array, which contains strings of format name=value.
  11. Why do you need the value of that cookie? Why are you logging in twice? Don't do that. The fifth argument to the callback of login is oAuthToken, not YourCookieValue. Use that instead of calling getWebApiOauthToken just after logging in.
  12. You can provide a custom time offset to steam-totp when generating the code. Current time + 30 should work.
  13. You're trying to reuse a code, which doesn't work.
×
×
  • Create New...