Jump to content
McKay Development

Dr. McKay

Administrator
  • Posts

    3631
  • Joined

  • Last visited

Everything posted by Dr. McKay

  1. If you're currently being 429'd, you need to wait at least a couple minutes. And you need to slow down to avoid it in the future.
  2. It will absolutely definitely not work.
  3. https://httpstatuses.com/429 You need to stop hitting Valve's servers so hard.
  4. That's a known Steam problem, and there is nothing that can be done about it. https://steamerrors.com/16
  5. Yes, most certainly. You need to wait for the callback of send(). I have no idea why it worked before v2. My guess is that it didn't. The code you just posted would never work.
  6. Hm, there's a bit of a chicken-egg problem here in the module. I'll work on a fix, but for the moment I can only suggest that you disable family view.
  7. https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/releases/tag/v2.0.0
  8. https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/releases/tag/v2.0.0
  9. You would probably want to set a timer to re-check it.
  10. You'll miss out on things like stickers and custom names if you use market_hash_name as your unique field.
  11. You should update to v2, which removed the autoRetry option.
  12. The tag for accepting needs to be allow, not accept.
  13. Don't call parentalUnlock until the callback of setCookies fires Don't try to send an offer until the callback of parentalUnlock fires
  14. Yes, although you don't need to connect the CMClient before you log on with SteamUser. Just call client.bind(ip); and then you can immediately do user.logOn(details);
  15. Not presently, no. If you want your own name and stuff, you can use the GetPlayerSummaries WebAPI method.
  16. That's just how Valve does it. The classid/instanceid can also include some hidden data that isn't displayed in the actual item data, so you'll just have to live with whatever duplicates you get.
  17. https://github.com/DoctorMcKay/node-steam-client#bindlocaladdress-localport
  18. Yes, there is.
  19. 403s indicate that Steam has blocked your IP due to excessive requests. You need to slow down your request rate, or distribute it between multiple IP addresses.
  20. You could try Codecademy to learn JavaScript, and Stack Overflow to ask your general JavaScript questions.
  21. You can't just call webLogOn(), you need to call it as a method of a SteamUser object.
×
×
  • Create New...