Jump to content
McKay Development


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

540 profile views

sNIP's Achievements

  1. It is not worth it, since almost every time you will have a different ip address with each invocation, also I believe it is hard to manage events (steam message for example). In general it is worth to just use monolith application for steam bots and don't deal with serverless functions.
  2. I am gonna try the luminati proxy and I will return a feedback in the coming months! Thank you for the heads up
  3. Hello everybody, hope you are doing fine in these covid times... My question is: I want to run a limited amount of steam account on the steam network. I was using the ips provided from my VPS provider, but I want to use more flexible solution, like https://luminati.io/, more specific the data center private proxy. If I chose that option, it asks me for a list of targeted domains. Are the domains "steamcommunity.com" and "steampowered.com" enough to satisfy the need of managing trade offers, sending and receiving steam messages and removing friends from the friendlist? What is your experience and can you suggest me a suitable proxy provider?
  4. Good evening, When you stop your trade offer manager instance, then start it again after a long period of time with the latest poll data from the last session, does the updated property corresponds to the time when the offer state was actually changed, but not when the trade offer manager acknowledged that there is a change in the offer. Example: Steam bot is running on Monday, and it have sent one offer that day. Steam bot is shut down Monday evening. Tuesday: Partner declines the offer that the steam bot have sent the previous day. Wednesday: I start the steam bot again, with the poll data saved from Monday, I receive one event from the EventEmmiter's on("sentOfferChanged"), does that event(trade offer) have the "updated" property which should be date object, which also point to Tuesday, when the state was actually changed? Or it is Wednesday, when the bot acknowledged that there is a change?
  5. I tried, but it too much hassle, I just gave up on the multithreading model and can run up to 50 accounts with no issues whatsover right now
  6. Thank you, because Iam switching from each each NodeJS instance, to all instances in one NodeJs
  7. I know I can use localAddress options in both steam community and user. But will I run into problems, if I try to run multiple instances of node-steam-user instances with different localAddress setings on the same nodejs instance? Thanks in advance
  8. Iam not sure if this is relevant but here is my take: community.on("sessionExpired", function(err) { if (err) { console.log("Session Expired: " + err); } if (client.steamID) { client.webLogOn(); console.log("called weblogon: " + thisId); } else { client.logOn(logOnOptions); console.log("called logon"); } });
  9. This is the test that I made with 45 test IPC processes. The test consist of sending and expecting to receive message every 1 second. I have tested the execution of the time a message goes to the child process and then waiting for that message to come back to the parent process. The transaction time doesnt exceed 1 second. It takes average ~80 mb per process. So if I want to save ram, I need to run them in one process(multiple instances of steam user class). My only concern about spawning multiple processes is that I dont know if I will hit an IPC bottleneck. What happens if a parent process have 500 child processes, which he needs to have constant connection to them? Iam not sure if it will be actually OS related. If that is the case, I need to spawn a process which spawns a process.
  10. Currently I have one main nodejs app, which spawns one nodejs process for each account. The communication is done by IPC protocol. So my question is: Is it going to be better if I just create multiple steam user instances and place them in an array or in an object collection?
  11. Dont use confirmation checker, thats how I got like 5 ips blacklisted before I realized what was causing it. I use accept all confirmations on confirmation event. It has 1.7% fail ratio for the event to emit, as much as I know. The other way is to accept all confirmations 10 seconds after the trade is sent, it might fail again but its still a workaround.
  12. Iam using this, it works fine, when I have time, I will look it up, probably after my finals. if(oldState == 12){ return; }
  13. The old state is 12, which is strange because the TradeOfferEnum max number is 12. Is that a debug number?
  14. I will check it, but I believe its the same, because if I keep the app running, it can emit 1000 times before I close it or the trade offer changes it states
  • Create New...