Jump to content
McKay Development

Dr. McKay

Administrator
 View Profile  See their activity

  • Posts

    3545

  • Joined

  • Last visited

 Content Type 

Everything posted by Dr. McKay

  1. Dr. McKay
    You can use process.exit(0) to terminate the application.
  2. Dr. McKay
    The GetTradeStatus API method will give you the new IDs after the items got traded.
  3. Dr. McKay
    Check the SteamID type. It will tell you if it's a chat or a user. Use chatMessage() to send a message.
  4. Dr. McKay
    Change line 3 to const offer = manager.createOffer(qqdata);
  5. Dr. McKay
    When you're doing things on the market, you need to set the Referer header to an expected value. Also, don't manually set any of those other headers either.
  6. Dr. McKay
    Is everything up to date? All your modules, Node.js, etc?
  7. Dr. McKay
    newEmail, not email.
  8. Dr. McKay
    If you aren't doing anything that involves the server generating an event and pushing it down to the user, there's no need to use websockets. If all you're doing is request/response stuff then ajax is all you need and is much simpler.
  9. Dr. McKay
    socket.io is okay but I don't personally recommend it because I personally think it's a bit too much for what it needs to do. Plain old boring websockets are plenty since there's no real need to support browsers that don't support websockets anymore (they've been standard for years now). I made a websocket library but you can use anything. If you want to protect your server from having its direct IP exposed, you could use Cloudflare. They support websockets even on the free plan.
  10. Dr. McKay
    You would need to get data from a ton of different inventories, or from scraping the market.
  11. Dr. McKay
    You can't do that with just the data available from the community inventory endpoints.
  12. Dr. McKay
    No.
  13. Dr. McKay
    The item ID is wrong.
  14. Dr. McKay
    You can use the url module to parse the URL, then you'd want to check the domain, path, etc.
  15. Dr. McKay
    Make sure all your modules are up to date. Run 'npm update'. And I mean to make sure your timer doesn't exceed 231.
  16. Dr. McKay
    SteamIDs are too large to be represented as JavaScript numbers. You need to make that SteamID a string (wrap it in quotes).
  17. Dr. McKay
    There is no other way to do it. Steam imposes limits on how frequently you can send inspect requests.
  18. Dr. McKay
    Make sure everything is up to date and make sure your code doesn't create any timeouts with a timer of 2^31.
  19. Dr. McKay
    Steam doesn't slow any requests, it will only outright block you with 429. Your proxy just sucks.
  20. Dr. McKay
    It's spelled "length". And also itemsToReceive.
  21. Dr. McKay
    You're making too many requests. You need to limit your requests.
  22. Dr. McKay
    You would want to pass in a node-steamcommunity instance you've created and set the localAddress on.
  23. Dr. McKay
    If you could open an issue on GitHub that'll make me remember to add it.
  24. Dr. McKay
    For the moment you're going to need to scrape.
  25. Dr. McKay
    That's my bad. Update to 3.33.2 please. For future reference, if a module is throwing an error and crashing the application, that warrants opening a GitHub issue.
×
×
  • Create New...