egghelp.org community

[mylde]

Could somebody tell me how i could make my bot op eachother more faster, i use botnetop.tcl and it works normally but that darn thing is so slow. I have set normal auto-op to 0:0 and bop_delay 0

[slennox]

What version of botnetop.tcl are you running?

Increase the bop_maxreq setting and make sure bop_modeop and bop_linkop are set to 1.

[mylde]

# netbots.tcl v4.05 (3 September 2001)

# botnetop.tcl settings
set nb_component(botnetop) 1
set bop_delay 0
set bop_maxreq 20
set bop_modeop 1
set bop_linkop 1
set bop_icheck 0
set bop_hcheck 1
set bop_osync 0
set bop_addhost 0
set bop_log 1

Those are the settings I use in all my bots. Anyway to make opping faster ?

[Yourname]

Read the docs, thats another good way.

_________________
Dormant egghead.

[mylde]

Read the docs, didn't find anything new. Delay is zero and there ain't no other place that should affect the speed, or is there ?

[slennox]

The script should be operating at its fastest with the settings you pasted. Now it would be helpful to define "slow". How long in seconds is taking a bot or bots to get opped?

It would probably be most useful to paste the channel screen from start to finish of a typical situation of bots being opped, and mark down how long it took each op to occur.

[ This Message was edited by: slennox on 2002-03-10 18:50 ]

[mylde]

Test 1

1612:46 *** Mylde sets mode: +o Donkey1
1612:56 *** Donkey1 sets mode: +nt
1612:58 *** Donkey1 sets mode: +ooo Sheep Cow Dog 1613:01 *** Dog sets mode: +o Cat

so it took 15 seconds for all bots to get opped. It´s long time considered the fact that protectops ops the bot instantly if someone deops it. But if someone lame takeover dude kick the bot it get opped after 15 seconds.

Test 2

1618:51 *** Cat has left #plahplah (Cat)
1618:55 *** Cat has joined #plahplah
1619:03 *** Dog sets mode: +o Cat

Took 8 seconds, not much but still the auto-op is much faster. /msg op plah is too very fast, it ops instantly too.

Maybe it's the lag between the networks, but all the bots have connections greater than 8 Mbps.

Btw. What are the ways to make bots ops eacother if the hub bot is offline. Well, i´ll check that with search

[slennox]

Here are my results

[20:09] *** Now talking in #test1234
[20:09] *** devlin.openprojects.net sets mode: +n
[20:10] *** Joins: fenrus (~pennsy@soft.nu)
[20:10] *** Joins: GG1 (~pennsy@soft.nu)
[20:10] *** Joins: bottus (ferals@techmonkeys.org)
[20:10] *** slennox sets mode: +o bottus
[20:10] *** bottus sets mode: +t
[20:10] *** bottus sets mode: +oo GG1 fenrus [6 secs]
[20:11] *** slennox sets mode: -o GG1
[20:11] *** bottus sets mode: +o GG1 [5 secs]
[20:11] *** fenrus sets mode: +o GG1 [5 secs]
[20:12] *** bottus was kicked by slennox (slennox)
[20:12] *** Joins: bottus (ferals@techmonkeys.org)
[20:12] *** fenrus sets mode: +o bottus [5 secs]
[20:12] *** GG1 sets mode: +o bottus [5 secs]

It needs to be kept in mind that the autoop, protectop and /msg op features are inherently fast since they require no communication at all between the bots - a bot just sees the join, deop or msg and reacts instantly, and they are slowed only by eggdrop's queue. botnetop.tcl is hampered by a larger number of factors including botnet communication, extensive verification, and the time it takes the bot to 'sync' the channel after joining (plus internal delays built into the script to wait for this to occur).

I do see some tweaking that can be done to the internal delays. It's possible (with bop_delay set to 0) the extended delay you're experiencing is the result of bots taking longer to sync than the internal delay provides for, causing a 'miss' condition that results in the bot waiting for its need bind to trigger before a request occurs.