OSBot 2.4.106 - No Interface Mode

[Abuse]

his post / screenshot implies he has them running on the same server tbh

 

No, my post is directed towards Alek, telling him that I've successfully tested this update on 510 simultaneous clients + a screenshot of the current resource usage per client

 

Express your feeling in the spam section, not here

[Hel]

I checked, there's no way there's more then 135. probably around 120~ max there.

 

Look at the scroll bar (25 per section) 25 x 5 = 125.

 

Nice job trying to be an edgy cunt

You know this is an absolutely terrible way to judge how many are running due to background processes, a better way would be to add all of the CPU %'s and average out the 25, (68.4 / 25 = 2.736 CPU% average per client)

100 / 2.736 = 36 clients. but yanno, doing these sort've things are pointless.

[nicksep]

You know this is an absolutely terrible way to judge how many are running due to background processes, a better way would be to add all of the CPU %'s and average out the 25, (68.4 / 25 = 2.736 CPU% average per client)

100 / 2.736 = 36 clients. but yanno, doing these sort've things are pointless.

That's a worse way since it's harder to guess the average of the others, but for all we know they are lower then the one on the bottom, also if your CPU is at 99% that doesn't mean you can't run more processes

[Hel]

That's a worse way since it's harder to guess the average of the others, but for all we know they are lower then the one on the bottom, also if your CPU is at 99% that doesn't mean you can't run more processes

All of the CPU %'s add up to 99. That's the point of that column. A lot of these are made up from background processes. This is a much more accurate way than judging a scroll bar. But thanks for your incorrect input

[FROZRZK]

So can we get the devs some blowjobs? Best xmas ever

[chakal]

Guys, when I connect by cmd with nointerface, the OSBOT config will keep up? like, breaking bot for x minutes and reconecting it after y minutes or it will run 24/7?

Edited December 30, 2016 by chakal

[Hel]

Guys, when I connect by cmd with nointerface, the OSBOT config will keep up? like, breaking bot for x minutes and reconecting it after y minutes or it will run 24/7?

-allow norandoms

[THS]

Wait so, this drastically reduces CPU usage on local (private) scripts? I'm braindead plz halp

[Juggles]

Guys, when I connect by cmd with nointerface, the OSBOT config will keep up? like, breaking bot for x minutes and reconecting it after y minutes or it will run 24/7?

It will run 24/7. Breaks aren't supported right now with it. 

[Lewis]

would love to see some sort of client info on the cmd window.
quite hard to tell when your bots have glitched out without any feedback from client being shown

[Borre]

would love to see some sort of client info on the cmd window.

quite hard to tell when your bots have glitched out without any feedback from client being shown

 

I don't think you should use this feature if you're not 100% sure your script runs without any glitches/bugs.

[Lewis]

I don't think you should use this feature if you're not 100% sure your script runs without any glitches/bugs.

theres plenty of reasons why it might glitch out, without some sort of feedback you couldnt even tell if the script has stopped running on a client.

[Juggles]

would love to see some sort of client info on the cmd window.

quite hard to tell when your bots have glitched out without any feedback from client being shown

 

Alek said this on a past thread

 

This feature is targeted at very serious bot farmers who can completely rely on their scripts without any human intervention.

Don't use this feature if you don't 100% trust your script to work. 

[Vap0r]

Alek said this on a past thread

 

This feature is targeted at very serious bot farmers who can completely rely on their scripts without any human intervention.

Don't use this feature if you don't 100% trust your script to work. 

Agree 100%

I only mainly use this for tutorial island scripts just because I know it'll work 100% of the time, it would be nice to have some sort of way to identify the processes so IF a bot does get stuck all you need to do is kill the process.