Jump to content
McKay Development

Dr. McKay

Administrator
  • Posts

    3631
  • Joined

  • Last visited

Everything posted by Dr. McKay

  1. You need to provide the asset owner's SteamID as well. The linked repository only indicates that S is optional because you need either S or M (M is used for market listings).
  2. Giving an access token to a third-party site is effectively the same thing as giving them your username, password, and mobile auth code. I wouldn't recommend it.
  3. What's there is what Steam reports. I can't help you if the backend is returning bad data.
  4. Why?
  5. No, use steam-session for that.
  6. The third-party typescript definitions haven't been updated for 2.11.0. Just suppress the error.
  7. Cannot reproduce. Are you on the latest version?
  8. Duplicate of several threads here: https://dev.doctormckay.com/forum/9-node-steam-tradeoffer-manager/
  9. That's the point. Enabling useAccessToken disable fetching an API key.
  10. Not that I'm aware of. I've heard, but not personally confirmed, that if you use an access token you still receive CS2 offers as normal.
  11. You need to call setCookies on the TradeOfferManager instance, not on the SteamCommunity instance. TradeOfferManager's setCookies also retrieves your account's API key.
  12. You just need to call setCookies each time the webSession event is emitted. You don't need to create a new TradeOfferManager or SteamCommunity.
  13. Use webLogOn() to get a new web session when that happens. It's a good idea to do that at least every hour or so as well.
  14. You could use the IEconService/GetTradeOffer API method to fetch the trade offer details, which would include the user's SteamID. creator_id is the ID of the trade offer.
  15. The sessionid cookie should indeed be universal. You can use whatever value you want.
  16. That means it couldn't find any pending confirmations that map to an object (trade offer, market listing, or other) with that ID.
  17. You'd need to figure out what requests the help site (help.steampowered.com) makes to change your email, and make those requests yourself using cookies obtained from steam-user or steam-session.
  18. Probably not.
  19. You'll be fine if you store this in your database.
×
×
  • Create New...