Jump to content
McKay Development

Dr. McKay

Administrator
  • Posts

    3658
  • Joined

  • Last visited

Everything posted by Dr. McKay

  1. JavaScript does not have integers. It only has double-precision floating-point numbers, which can only safely represent integers up to 2^53 - 1. Consequently, you can't have a SteamID as an integer, only as a string.
  2. Are you using the same modules to confirm trades on both devices? I'd assume you are, but it can't hurt to make sure. If you're using the same modules, code, and account, then there shouldn't be a problem...
  3. It shouldn't be a problem as long as you aren't also trying to confirm stuff on a phone.
  4. This won't work because you're calling addMyItems on a single item. You should use addMyItem instead.
  5. Sounds like you don't have a network interface set up for that IP.
  6. You're using node-steam-tradeoffers, which I can't support.
  7. You can only cancel an offer once. There's no limit on how many offers you can cancel on your account, though. If you send and cancel a million offers they might take notice.
  8. You aren't calling any changeEmail function, you're only listening for a (nonexistent) changeEmail event.
  9. You can also connect to MySQL using Node: https://www.npmjs.com/package/mysql
  10. That's the correct way to do it. Make sure you aren't trying to do any authenticated stuff before the webSession event gets emitted.
  11. There isn't currently a way to get incoming friend requests using node-steamcommunity. Is this something you need? If you're also using node-steam-user then you can get invites from there.
  12. It may not have anything to do with an avatar, but I couldn't tell you why there's a discrepancy.
  13. That's correct. There's no way, using node-steam-user, to decrypt filenames without parsing the manifest. I don't have any plans to support this as I don't see a valid use-case for that.
  14. The error seems to be originating in the dota2 module, which I can't support.
  15. Currently, profile showcases aren't really supported.
  16. manager.offer doesn't exist. You want this: manager.on('receivedOfferChanged', (offer) => { community.postUserComment(offer.partner.toString(), 'Test'); });
  17. You need to call community.setCookies inside of SteamUser's webSession event in order to get steamcommunity to use a login session.
  18. You need quotes around receivedOfferChanged. That should have just crashed without doing anything.
  19. You need to wait for the disconnected event to know that you're logged off. You can't log back on using the same object until then. My suggestion is to just create a new SteamUser object for each login.
  20. webLogOn() and wait for the webSession event.
  21. Version 6 is not a downgrade. It's 6.0.0, which is a couple years newer than when 0.10 first came out. Later versions of node typically aren't available in repositories. You'll need to install it yourself. If you're on Ubuntu x64, you can use this script: https://www.doctormckay.com/installnode.sh It probably works on other distros too (x64 only) but I've only tested it on Ubuntu.
  22. If you're accepting incoming offers, listen for the receivedOfferChanged event and do something when the state is Accepted. If you're sending offers, listen for the sentOfferChanged event and do something when the state is Accepted.
  23. You need version 6 or later.
  24. What version of node are you running?
×
×
  • Create New...