Jump to content
McKay Development

Dr. McKay

Administrator
  • Posts

    3631
  • Joined

  • Last visited

Everything posted by Dr. McKay

  1. You're firing off getUserDetails and accept at the same time. The accept request is probably getting processed by Steam before the details one, and thus Steam no longer believes the offer is active when the details request gets processed.
  2. node-steam is not node-steam-user. I won't delete your thread, but I can't help you either.
  3. I'm not 100% sure, but I think steamLogin got dropped when Steam (finally) went HTTPS-only. So yeah, steamLoginSecure alone should work.
  4. A delay in getting a web session would have nothing to do with this. It's probable that Steam was just being slow when you were trying.
  5. All my modules do send a cookie requesting English text, but I guess it's not always respected.
  6. I tested it personally before pushing and login didn't take any longer than usual.
  7. The error language is probably controlled by your Steam account language.
  8. Should be fixed in the latest commit. Remember that the v4 branch is still pre-alpha. There are going to be bugs.
  9. That's not an appropriate fix because that prevents intentional attachment of multiple handlers for a single message. Pull the latest v4 commit and you should get fixes for gamesPlayed and your duplicate handler issue, but I wasn't able to replicate any Steam Guard issues.
  10. Then you have the wrong time or the wrong secret.
  11. https://github.com/DoctorMcKay/node-steamcommunity/wiki/SteamCommunity#getconfirmationstime-key-callback
  12. All of that data is already available. As long as you're set to online, myFriends contains the list of who all your friends are, and users contains their profile data, updated in real-time.
  13. What exactly are you trying to do?
  14. Given that your steam-user seems to be temporary, you could just create a new one every time.
  15. You would need to add support directly to steam-user by editing it. You can't just call underscore-prefixed methods from outside of the module and expect things to work. Take a look at the commit history to see what it takes to add support for a new message. Why do you want to use this, anyway? You can already get your friends list from steam-user.
  16. I would assume it's because this code is being called multiple times and is attaching a new listener to loggedOn every time.
  17. You need to go into that node-steam-user-4 folder and run npm install
  18. Are you on the latest v4 commit? That sounds like a bug I fixed a couple weeks ago.
  19. You don't, you use sendFriendMessage.
  20. You probably aren't in any groups.
  21. getGroups
  22. Yes, it posts all device changes. If you're using an HTTPS webhook it's possible that Mono doesn't have the appropriate CA certificates. I've had trouble with getting it to post to some HTTPS endpoints properly.
  23. Yes, because ignorant coders will almost definitely start passing API keys that don't belong to the account they're signed into, and start posting GitHub issues asking what's going on. If you know what you're doing, you can set the apiKey property directly with the correct key, but please make sure you actually know what you're doing.
  24. Chat history is temporary for all chats, even group chats.
×
×
  • Create New...