Jump to content
McKay Development

Dr. McKay

Administrator
  • Posts

    3629
  • Joined

  • Last visited

Everything posted by Dr. McKay

  1. You're either calling addMyItem or addTheirItem with an undefined item.
  2. Well, for one thing, you're using token to store your TradeOffer, then calling trade.sent(). But your issue is that you aren't listening for the callback, you're just assuming it worked immediately. You need to pass a callback to send() and check the offer ID once it is called.
  3. Either call trade.addMyItem to add items one-by-one, or call trade.addMyItems on the entire pool to add them all at once. addMyItem is for single items. addMyItems is for arrays of multiple items.
  4. GetTradeOffer and GetTradeOffers are the names of the API methods. getOffer and getOffers are the steam-tradeoffer-manager equivalents. tradeID only exists when the offer has been accepted. If you're using steam-tradeoffer-manager you don't need to call the API yourself; you can use getExchangeDetails.
  5. I think that's probably normal. Not all of the fields are actually used by Steam.
  6. The trade ID is the tradeid property on the trade offer (from GetTradeOffers or GetTradeOffer) after it's accepted. It's not an offer ID.
  7. That's old enough there probably isn't a protobuf. You probably just need to send a buffer containing most likely the defindex of the stock item (uint32?) first, followed by your null-terminated new name.
  8. You can use process.exit(0) to terminate the application.
  9. The GetTradeStatus API method will give you the new IDs after the items got traded.
  10. Check the SteamID type. It will tell you if it's a chat or a user. Use chatMessage() to send a message.
  11. Change line 3 to const offer = manager.createOffer(qqdata);
  12. 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.
  13. Is everything up to date? All your modules, Node.js, etc?
  14. newEmail, not email.
  15. 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.
  16. 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.
  17. You would need to get data from a ton of different inventories, or from scraping the market.
  18. You can't do that with just the data available from the community inventory endpoints.
  19. No.
  20. You can use the url module to parse the URL, then you'd want to check the domain, path, etc.
  21. Make sure all your modules are up to date. Run 'npm update'. And I mean to make sure your timer doesn't exceed 231.
  22. SteamIDs are too large to be represented as JavaScript numbers. You need to make that SteamID a string (wrap it in quotes).
  23. There is no other way to do it. Steam imposes limits on how frequently you can send inspect requests.
×
×
  • Create New...