egghelp/eggheads community

TCL needed help

2004-10-31T11:37:41-04:00

There is nothing complicated between his code and my code. Didn't modify anything in the original procedure, just added an extra proc, so the bot doesn't remove un-necessary modes, i.e. it doesn't remove modes which aren't set in the channel.

That is because when floods happen other people also set modes, and remove modes and I've seen on alot of channels causes a mode flood, so if other people do mode floods, we don't want the bot to do it atleast.

Statistics: Posted by awyeah — Sun Oct 31, 2004 11:37 am

TCL needed help

2004-10-30T19:46:59-04:00

user's code way way too simple, you have complicated it too much for a few changes...

Statistics: Posted by caesar — Sat Oct 30, 2004 7:46 pm

TCL needed help

2004-10-30T08:37:51-04:00

I'm using the locking system on my bot with another script and it works fine for me, plus it is proving to be very effective especially for channel notice and long text floods. So much effective that I've removed sentinel.tcl from my bot as it made the bot alot slower, and replaced it by adding a clone kicker detecting fast joins. I modified the lock timer to be removed after 10secs and it works fine for me.

Here are my settings, if we replace them into this script:

Code:

bind splt - * netsplit:lock proc netsplit:lock {n u h c {r ""}} {  global netsplit_lock  if {![info exists netsplit_lock($c)]} {  if {[botisop $c] && ![string match *m* [getchanmode $c]]} {   putquick "MODE $c +m" -next; utimer 10 [list remove:lock $c]   putquick "PRIVMSG $c :Netsplit detected - Channel has been locked to +m for 10 secs." -next  }  set netsplit_locked($c) "+m.already.locked"  utimer 15 [list unset netsplit_lock($c)] }; return 0}proc remove:lock {c} { if {[string match *m* [getchanmode $c]] && [botisop $c]} {  putquick "MODE $c -m" -next; return  }}

Statistics: Posted by awyeah — Sat Oct 30, 2004 8:37 am

TCL needed help

2004-10-29T13:30:30-04:00

Try delaying the timer interval say, to 30 secs or more and then check

Right now, my coding is...

Code:

bind splt - * netsplit:lock proc netsplit:lock {n u h c {r " "}} { global netsplit_lock if {![info exists netsplit_lock($c)]} { if {![string match *m* [scan [getchanmode $c] %s]]} { pushmode $c +m puthelp "PRIVMSG $c :Netsplit detected, channel will be set to moderated for 30 seconds." utimer 30 [list pushmode $c -m] } set netsplit_lock($c) "#abc" utimer 30 [list unset netsplit_lock($c)] } }

But doesn't work, the bot doesn't set +m to the channel anymore and I see no error in the TCL. What's wrong?

Statistics: Posted by Stealthx — Fri Oct 29, 2004 1:30 pm

TCL needed help

2004-10-29T10:35:08-04:00

Try delaying the timer interval say, to 30 secs or more and then check

Statistics: Posted by awyeah — Fri Oct 29, 2004 10:35 am

TCL needed help

2004-10-29T08:12:33-04:00

When did the split occur?

What do you mean by "when"?

Nope, I do not have any other TCL which send stuff to the server on splits. My bot is only on 3 channels (opped).

Statistics: Posted by Stealthx — Fri Oct 29, 2004 8:12 am

TCL needed help

2004-10-29T06:32:01-04:00

::20:22:31:: <@Bot> Netsplit detected, channel set to +m for 15 secs.
::20:22:32:: * Bot sets mode: +m
::20:22:35:: * Bot sets mode: -m
Although I've set the timer to 15secs.

When did the split occur? Do you have any other scripts sending stuff to the server on splits? Is your bot in many channels that are moded +m by this script? Try adding a flushmode after the first pushmode

Code:

pushmode $c +mflushmode $c

Statistics: Posted by user — Fri Oct 29, 2004 6:32 am

TCL needed help

2004-10-29T01:23:48-04:00

How long did it take to mode the channel -m?

It's depends. Sometime the bot would take up to 15 secs (one or two time) and majority it only took 1-3 secs and the bot would -m to the channel. Just like this -

::20:22:31:: <@Bot> Netsplit detected, channel set to +m for 15 secs.
::20:22:32:: * Bot sets mode: +m
::20:22:35:: * Bot sets mode: -m

Although I've set the timer to 15secs.

Statistics: Posted by Stealthx — Fri Oct 29, 2004 1:23 am

TCL needed help

2004-10-28T15:35:11-04:00

There could be a few more seconds added before the -m is sent due to the internal delay to prevent flooding. Removing the brackets ([]) will not change this. How long did it take to mode the channel -m?

list makes a list (which is what utimer expects - passing it a string like you do now is not a good idea)

Statistics: Posted by user — Thu Oct 28, 2004 3:35 pm

TCL needed help

2004-10-28T08:32:43-04:00

Could anyone see what's wrong with the coding?
Yes...anyone could see it. (Compare your code to mine)

Thanks for your answer but I've change the [ ] to " ", the reason I've changed is because the timer doesn't work. Although it did +m and -m, but definitely not after the time that the timer (15sec) set

Code:

utimer 15 [list pushmode $c -m]

And I don't know the reason why.

Oh btw, what does the "list" means in this code?

Code:

utimer 15 [list unset netsplit_lock($c)]

Statistics: Posted by Stealthx — Thu Oct 28, 2004 8:32 am

TCL needed help

2004-10-28T05:29:41-04:00

Could anyone see what's wrong with the coding?

Yes...anyone could see it. (Compare your code to mine)

Statistics: Posted by user — Thu Oct 28, 2004 5:29 am

TCL needed help

2004-10-28T03:27:48-04:00

Hi guys, I've edited the script but the timer doesn't seems to work, as in the bot doesn't -m after sometime.

Code:

bind splt - * netsplit:lock proc netsplit:lock {n u h c {r ""}} { global netsplit_lock if {![info exists netsplit_lock($c)]} { if {![string match *m* [scan [getchanmode $c] %s]]} { pushmode $c +m puthelp "PRIVMSG $c :Netsplit detected, channel set to +m for 15 secs." utimer 15 "list pushmode $c -m" } set netsplit_lock($c) "#abc" utimer 15 "list unset netsplit_lock($c)"} }

Could anyone see what's wrong with the coding?

Statistics: Posted by Stealthx — Thu Oct 28, 2004 3:27 am

TCL needed help

2004-10-27T12:39:27-04:00

Hehe, yeah I use pushmode with flushmode alot in my scripts, although I never knew it could be as fast as putquick '-next' or putdccraw. I'll modify my current scripts to enforce it as well.

*user* is a revered one now!

Statistics: Posted by awyeah — Wed Oct 27, 2004 12:39 pm

TCL needed help

2004-10-27T10:35:09-04:00

Ps: Congrats for the 1000st post.

thanks

Hmm... anyway pushmode would be slower as well, when dealing with floods and when you want to set locks +m, +i or whatever, we should use a faster queue I suppose, like I intended to do.

putquick is using the same queue as pushmode...if you want to speed it up, just add a flushmode.

Statistics: Posted by user — Wed Oct 27, 2004 10:35 am

TCL needed help

2004-10-27T10:21:40-04:00

Hmm... anyway pushmode would be slower as well, when dealing with floods and when you want to set locks +m, +i or whatever, we should use a faster queue I suppose, like I intended to do.

Statistics: Posted by awyeah — Wed Oct 27, 2004 10:21 am