Jump to content
McKay Development

Dr. McKay

Administrator
  • Posts

    3626
  • Joined

  • Last visited

Everything posted by Dr. McKay

  1. Check the x-eresult header.
  2. Not at the moment.
  3. You should not be sending this stuff in the query string; it needs to go in a POST body.
  4. It's not mentioned in the documentation, but you only get an eresult in the error event if a Steam connection can actually be established. If you don't have an eresult proeprty, you can assume there was a network issue. Only you can properly decide the best course of action for your app, but if your network is down then yeah, probably all you can do is wait and retry until the network comes up.
  5. Update to 2.11.5 and this should work properly. In previous versions it checks if the new value === the old value, which it would in this case since it's the same object reference.
  6. If you can renew it, no reason not to. But I believe that once it's invalid for logins, it's no longer valid for renewing either.
  7. I'm not aware of any usage-count limit. Get a new one.
  8. That's expected behavior. Machine auth tokens are only issued when you log on with email 2FA, but steam-user attempts to read it every time you log on. If a request comes in to read a file that doesn't exist, you should return an error, not an empty string.
  9. If you're using a custom storage engine, don't change the value of the dataDirectory option. If you set it to null, the storage property isn't initialized so you get that error attempting to read 'on' of undefined. steam-tradeoffer-manager uses the same storage scheme as steam-user, but they don't share the same instance. You need to register your save and read events on your TradeOfferManager instance the same way you registered them on your SteamUser instance.
  10. https://github.com/DoctorMcKay/node-steam-user?tab=readme-ov-file#getproductinfoapps-packages-incltokens-callback
  11. You can use NetHook2 for this.
  12. If you're dealing with trades that include CS items, you need to enable the useAccessToken option.
  13. Does the offer contain CS items? If so, you'll need to use an access token. You can get one with steam-session.
  14. TypeScript definitions for steam-tradeoffer-manager aren't maintained by me, so I can't really help you specifically. That said, you can probably suppress the error using (EResult.Revoked as number)
  15. I think you're missing some parens after this.getTimeOffset
  16. I dunno what to tell you; I've never messed with any user stats messages. Everything looks fine, assuming that what you're passing is what the backend actually expects. Are you in-game for the app? That might be necessary.
  17. Your app has crashed because you aren't listening for the error event. Every Node.js EventEmitter crashes the app if an unhandled error event is emitted. The error in question is raised when steam-user fails to retrieve the Steam server list from the WebAPI after 10 retries.
  18. Unless you've edited messages.js to define which protobuf should be used for that message, you'll need to handle encoding the request body yourself.
  19. Are you sure? This shouldn't be possible. Steam caches classid+instanceid pairs indefinitely. The description data should never change. Not really, my best guess is that D just stands for "data". It very likely is a hash to prevent scraping. It's been my experience that any [SM], A, D triplet will work forever to fetch item data.
  20. Probably does, but I wouldn't expect things to go smoothly if you try to use it.
  21. Which line is triggering the error?
×
×
  • Create New...