Jump to content
McKay Development

Dr. McKay

Administrator
  • Posts

    3629
  • Joined

  • Last visited

Everything posted by Dr. McKay

  1. Yeah, that should probably have a GitHub issue made for it.
  2. details is not yet defined.
  3. Not planning to add the feature right now, no.
  4. 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.
  5. community.login()
  6. Create a new SteamCommunity instance.
  7. Yep!
  8. The settings on that account do not allow you to add comments.
  9. Both your node and npm are ancient. Update them both to supported versions (node 6 or later, npm 3 or later).
  10. 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.
  11. It's in the cookies array, which contains strings of format name=value.
  12. 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.
  13. user.steamID
  14. community.steamID
  15. You can provide a custom time offset to steam-totp when generating the code. Current time + 30 should work.
  16. You're trying to reuse a code, which doesn't work.
  17. Just Steam doing Steam things. You need to try again later.
  18. Surely there is more code in your application than just that snippet. Also, provide the entire output please.
  19. That crash is because you're trying to pass undefined to addMyItem.
×
×
  • Create New...