Jump to content
McKay Development

Dr. McKay

Administrator
  • Posts

    3601
  • Joined

  • Last visited

Contact Methods

  • Website URL
    https://www.doctormckay.com

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

49248 profile views
  1. Probably a GC limitation. You should wait until the item modified event is emitted after adding or removing an item before moving on to the next one.
  2. This is not unexpected. It was always just happenstance that this method worked via steam-user; it uses a method not used by any official Steam app. You should use node-steamcommunity instead, which uses the official method.
  3. I'm traveling right now. I'll be able to push out an update in the next couple days.
  4. Do you have some way to reproduce this? Checking whether steamID is set on a timer is not the proper way to reconnect. This would run you into problems if SteamUser is currently attempting to connect but isn't yet logged on. You only need to call logOn() when your bot starts up, and if the error event is emitted.
  5. Dr. McKay

    API

    That's your access token, aka your steamLoginSecure cookie. It gives complete access to your account. It is your session identifier.
  6. It's the same for everyone.
  7. def_index tells you what an item is (which weapon, which case, etc) and paint index tells you what skin an item is. Everything you need is in items_game.txt in the game's vpk files.
  8. If you aren't planning on making any requests to a domain, then you shouldn't have any issues patching the module to skip that domain's settoken call.
  9. I believe webTradeEligibility is basically just a cache of your trading eligibility status for display purposes on the market. Rather than run the backend checks to generate this message every time you load the page, they just run the check once and then set the cookie for display. The backend checks still get run when you attempt to actually complete a purchase or trade though; you can't bypass restrictions just by fudging the cookie.
  10. You can't get wear from steamcommunity.com, only from the GC.
  11. Yes, cookies are invalidated when you logout. It's possible for a JWT to become invalid before its expiration date for that reason.
  12. Either in the inventory property or your Steam inventory.
  13. I think I've done this, but I guess I didn't add proper support for it to the steam-session package.
  14. Yes, you could, and then things would fall over when Steam goes down and your client reconnects since you'd miss that second loggedOn event.
×
×
  • Create New...