Polymorphism Posted August 24, 2017 Posted August 24, 2017 (edited) Been doing lots of testing with mass bot launching, currently doing 2-14 at once. Generally there is a small break between, however, I do notice lots of "Inactivity/multiple bots" errors, as well as the game applet staying black. In yall's experiences, what causes this error the most often? Not likely any of the 'reason' the client says, as i have ensured those bases are covered. Also, this error occurs for my buddy when he is launching on his VIP OSBot account. For those that cannot read, this is not my account I'm talking about. I am well aware of non-vip restrictions....DUH Also, what timeout between client launches is optimal? Edited August 25, 2017 by Polymorphism
Artifex Posted August 24, 2017 Posted August 24, 2017 (edited) Dont start to much at once! Do one after one or maybe two at same time! Wait ~5 seconds thats how i do! Edited August 24, 2017 by Artifex
kazemaru Posted August 24, 2017 Posted August 24, 2017 dont bot and you wont get that. also how can you launch 2-14 bots without vip? isnt this already the answer on your question?
Polymorphism Posted August 25, 2017 Author Posted August 25, 2017 (edited) 8 hours ago, Artifex said: Dont start to much at once! Do one after one or maybe two at same time! Wait ~5 seconds thats how i do! It's 2 bots together(variable delay due to creation), up to 7 times. They don't launch at the same exact time, sometimes within seconds of each other, sometimes 3 mins. On average I'd say the 2 in 1 group that do get launched are at least 10s apart, and on average each group are 12s apart Edited August 25, 2017 by Polymorphism
d0zza Posted August 25, 2017 Posted August 25, 2017 I've never had that error when I've had VIP and I've never needed a timeout between client launches.
Polymorphism Posted August 25, 2017 Author Posted August 25, 2017 50 minutes ago, d0zza said: I've never had that error when I've had VIP and I've never needed a timeout between client launches. This is software on a clients server, whom has vip status here.
Butters Posted September 9, 2017 Posted September 9, 2017 This really gives me a headache. OSBot likes to eat quite a few resources during launch. Depending on the CPU power you have, I can launch about 18-20 bots with 60+ second sleeps without a problem. As the CPU usage spikes later bots tend to fail producing the error mentioned. So I started monitoring cpu usage and extending the sleep time if needed. 1
