MasterOfData

Could certainly be done if you have a pre-determined task. Wouldn't even really need to communicate outside of a clan chat or something. I've seen people with orchestrated walking bots where they all follow each other by making a huge grid.

nice

Yeah resting accounts is important. You could try out some of our accounts from mod-rs. They're generally pretty well rested and made from safe IP addresses. Might help you make it a bit further along.

Just looking for something to use as like a "profile picture" on OSBot/Discord/Etc. Obviously gotta be dope and match the name. Let me know what you're thinking for $.

Configs did change, specifically with requesting a username.It's no longer hard coded config values.

Great work! @MGI is there any chance you could sneak in the ability to spin up the bot in mirror mode via the CLI?

Messaged on Discord, but memory management hits your CPU more if you aren't effectively managing memory or you're imposing a very low ceiling on the bot. Letting the bot use as much memory as it needs (assuming you're not doing stupid shit) should decrease the overhead of things like garbage collection. It's worth noting that this is really empirical and should be fine-tuned based on optimization. Decrease the number of bots you're running from 45 to say 20 and increase the memory ceiling. Play with that for a while and observe the CPU impact per process. Try and increase / decrease the number of bots and the memory you allocate for each bot. It's really an experimental process and is generally not so easy to predict.

That's pretty solid. First you have 2000 accounts to begin with. lol But the rest would just be spinning up concurrent requests on concurrent IPs. I'm sure you could scale indefinitely with enough IPs

Nice! I'm not sure how you effectively stress tested 5k accounts per hour without making assumptions though?

For those that are able, here is the new link:

Yeah that's a good point. I received a PM request to move this to VIP+ so I'm going to go ahead and do that as a google doc spreadsheet that is available upon request.

Nice! Good choice. PHP is incredibly antiquated. If you need any help, I'd be happy to help clean things up. Same with your account unlocker if you'd like

I'm going down the web GUI root here with rest endpoints to drive bot statistics (data analytics), account create/unlock (complete, built into the client) etc. Can spin up new accounts with a click of a button on the web GUI. Only thing left is getting an always-running python server on my EC2 instance to poll for new accounts and spin them up an OSBot client in their own execution thread. Neat thing I've done is to have an SQS queue for bots to request mules. When the mule has > (some X) M GP it'll send me a text message to come on and clean out the mule. 100% autonomous solution. Happy to help anyone that gets stuck! I'm familiar with most languages. Btw: Don't use PHP. lol use React/Redux/JS front end and restful APIs. Python or Node are much better back ends (serverless here with lambdas) Also my hosting is free fiddy with the AWS free tier. Literally $0 overhead.

Here are the statistics I've collected so far ID - Botted Tutorial Island? - Hours online - With Breaks? - Break Length - Ban duration - Single Ban / Ip Sweep? - Was previously locked? (Manually created accounts, account older than 1 week) Account 1 - No - 85 - Yes - Varied - Perm - Single Ban - No Account 2 - No - 105 - Yes - Varied - Perm - Single Ban - No (Botted accounts through and through, account younger than 1 week) Note: I logged these accounts out after a short ~ 6 hour botting session. Went to login ~ 24 hours later and they were all 4 banned (on two different IPs) Account 3 - Yes - 15 - No - N/A - Perm - Unsure - Yes Account 4 - Yes - 30 - No - N/A - Perm - Unsure - Yes Account 5 - Yes - 6 - No - N/A - Perm - Unsure - Yes Account 6 - Yes - 10 - No - N/A - Perm - Unsure - Yes Note: These accounts were all Pay2Play All bots ran the same (made by me) script which had success in the past. I did accidentally share the IP for all of the last 4 accounts for a short while when I accidentally ran the client w/o a proxy (I'm a dumb ass, I know)

I'm going to establish this thread as a free sharing of information on ban statistics. Folks seem hesitant to share it, which is silly, so I will be collecting lots of my data and sharing it here. What do I hope to learn? - If an account is immediately locked or locked for suspicious activity, is it more likely to be banned early? - Does having an account locked out of the gate seem to imply that it was operating on a flagged IP? What do I have to share? I'll be posting stats that I collect such as: Account Length - Botted Tutorial Island? - Hours online - With Breaks? - Break Length - Ban duration - Single Ban / Ip Sweep? - Was previously locked? I'll start sharing in my next post EDIT: I run all p2p botting scripts. I've heard this decreases ban odds, but as you can see, my statistics have been abysmal.