next »

[Mariodu62]

What is <set name="lines_per_second">50</set> for

Can you please tell me how to set it...

Thx
 

[Nocturnal1982]

This is a setting for how many lines per second the bot will read of the log file.

On a very chaotic server with MANY people, you might find that there's a delay, this is due to lines per second. That is, if the log file actually manages to spit out more than 50lines per second which i doubt unless you're looking at some huge servers with tons of stuff happening.

The more lines per second you add, the more CPU it uses.

Keep it to 50, if you feel it's slow sometimes, bump it up to 100.

[Mariodu62]

Ok,
Thanks, we have a very chaotic server with many players and fordiden ammo, so i need to increase this number.
 the bot use less than 1% of the proc (Windows server 2008 R2) so i can do that.

Thx again

[Nocturnal1982]

Windows 2008 R2 was a complete failure for my part, i absolutely hated the performance it gave me. Windows 2003 and windows 7 gave me 4 times the performance :|

But yeah, you can easily bump it up i think

[Mikobiko]

Windows 2008 R2 was a complete failure for my part, i absolutely hated the performance it gave me. Windows 2003 and windows 7 gave me 4 times the performance :|

But yeah, you can easily bump it up i think

The performance on R2 is way past 2k3. If its slower, something else was wrong.

Sent from my DROID2 GLOBAL using Tapatalk

[GrossKopf]

If you make an adjustment to this number, let us know what you are using. It would be interesting to know how the different values affect the performance and reliability of B3.

[Mariodu62]

i've done an new adjsutment...

i putted 1000 lines per second, because sometimes there is flood in the gamelog file COD WaW.(More than 150 lines for a player) and read every 0.1 s.

So now all  plugins work fine. The problem was with "antinoob" before.

The BOT is now a FIREDAEMON PRO service affected to one core. The bot use less than 0.5 percent of the core.

I5 2500, 16 Gb ram

this how i set the bot

      <plugin config="@conf/plugin_censor.xml" name="censor" />
      <plugin config="@conf/plugin_spamcontrol.xml" name="spamcontrol" />
      <plugin config="@conf/plugin_admin.xml" name="admin" />
      <plugin config="@conf/plugin_adv.xml" name="adv" />
      <plugin config="@conf/plugin_status.xml" name="status" />
      <plugin config="@conf/plugin_punkbuster.xml" name="punkbuster" />
      <plugin config="@conf/plugin_welcome.xml" name="welcome" />    
      <plugin config="@b3/extplugins/conf/plugin_antinoob.xml" name="antinoob" />
      <plugin config="@b3/extplugins/conf/wideban.xml" name="wideban" />
      <plugin config="@b3/extplugins/conf/aimbotdetector.xml" name="aimbotdetector" />
      <plugin config="@b3/extplugins/conf/plugin_pingkicker.xml" name="pingkicker" />
      <plugin config="@b3/extplugins/conf/rotationmanager.xml" name="rotationmanager" />
      <plugin config="@b3/extplugins/conf/xlrstats.xml" name="xlrstats" />
      <plugin config="@b3/extplugins/conf/plugin_ctime.xml" name="ctime" />
      <plugin config="@b3/extplugins/conf/autoreg.xml" name="autoreg" />



I'm just a little bit desappointed because !die and restart doesn't work

[MordyT]

you need to start b3 with the -r (or --restart) in the command line. See this: http://wiki.bigbrotherbot.net/installation:running_b3

[Mariodu62]

i tried but i use windows...

[82ndAB.Bravo17]

Do you mean that you use the windows .exe version?

[MordyT]

even if you use windows you can enable the command. You just need to modify the shortcut used to start B3.

[Mariodu62]

thx,

Yes it's the .exe

 i did it and it's always the same way..

Error during processing

for !die and !restart

The b3 bugs and need to be stop... and restart manually

[MordyT]

you need to edit the shortcut and add the --restart in the start up line. Yes, the shortcut to b3_run.exe

[Mariodu62]

I understood that,

I've done it, but it doesn't work .

There was an error processing your command

for !die command erreur 222
for !restart command erreur 221

111012 15:10:33   BOT       'Stop reading.'
111012 15:10:38   BOT       'Shutting down event handler'
111012 15:10:38   INFO   "STDOUT 'Exiting: 222'"
111012 15:10:38   INFO   "STDOUT '\\n'"
111012 15:11:00   DEBUG   'StatusPlugin: Writing XML status to c:\\wamp\\www\\status_cod5_1282.xml'
111012 15:12:00   DEBUG   'StatusPlugin: Writing XML status to c:\\wamp\\www\\status_cod5_1282.xml'


need enter in windows b3 to die

[MordyT]

Please post a b3.log showing the issue then.