Active Chatter v3.66.b by awyeah (20/09/07 - fixed all bugs)

[awyeah]

Just done with a new script earlier. Thought of mentioning it here, before I send it to egghelp's tcl archive later.

Active Chatter v3.47.b

# #
# ########### #
# DESCRIPTION #
# ########### #
# #
# This script voices users who have said a certain number of lines on a #
# channel (active chatters). Additionally, it devoices users who are #
# idling for more than a certain amount of time on a channel (unactive #
# chatters). #
# #

You can download this script by clicking on the link below:
Active Chatter v3.47.b

[LivingSouL]

i dont know what's wrong

Tcl error [autovoice:devoice:idlers]: invalid channel: (#davao)

why is that?

[awyeah]

The devoice thing might be having some bug.

Type:

Code: Select all

.tcl set errorInfo

in partyline after you receive this error, and then paste me the complete info for the part of the script which triggered it.

To use the .tcl command in partyline, make sure you have added a hash infront of these 2 lines in your bot configuration file; to comment them:

unbind dcc n tcl *dcc:tcl
unbind dcc n set *dcc:set

like this:
#unbind dcc n tcl *dcc:tcl
#unbind dcc n set *dcc:set

and then restart your bot

[awyeah]

i dont know what's wrong

Tcl error [autovoice:devoice:idlers]: invalid channel: (#davao)

why is that?

This could also be if you have chosen setting 1 for the channels and defined your channels, but the bot is NOT currently on one of those defined channels, then it would show this error also.

Anyway for that I will update the script and upload it again.

*** Script fixed and uploaded

[LivingSouL]

your fixed script has an error on line 260 missing close brace

[LivingSouL]

with the new uploaded script, i set 2 for the first settings, and this one poped up..

Code: Select all

[19:57] Tcl error [autovoice:devoice:idlers]: can't read "chans": no such variable
[19:58] Tcl error [autovoice:devoice:idlers]: invalid channel: {#davao}

and can't use the .tcl set errorInfo even if i commented the 2 lines u said.[/code]

[YooHoo]

and can't use the .tcl set errorInfo even if i commented the 2 lines u said.

the correct syntax is .set errorinfo, not .tcl set errorinfo

[nml375]

Actually, either works just aswell as the other, as long as the corresponding command (.set or .tcl) has been enabled. Also keep in mind that there is one capitalized i in the variable... that is "errorInfo" and not "errorinfo".

As for using .tcl and/or .set, a full restart is required once edited your config-file.. a simple .rehash won't do as this won't wipe the old tcl-environment (and thus not restoring those bindings).
Also make sure the "owner" and "must-be-owner" variables are set accordingly:

Code: Select all

# Un-comment the next line and set the list of owners of the bot.
# You NEED to change this setting.
#set owner "MrLame, MrsLame"
...
# If you enable this setting, only permanent owners (owner setting) will be
# able to use .tcl and .set. Moreover, if you want only let permanent owners
# use .dump, then set this to 2.
set must-be-owner 1

[awyeah]

with the new uploaded script, i set 2 for the first settings, and this one poped up..

Code: Select all

[19:57] Tcl error [autovoice:devoice:idlers]: can't read "chans": no such variable
[19:58] Tcl error [autovoice:devoice:idlers]: invalid channel: {#davao}

and can't use the .tcl set errorInfo even if i commented the 2 lines u said.[/code]

Thanks well, i'll test it myself this time (fix it) and get back to you regarding this error.

[awyeah]

Okay, I fixed the script tested it this time on my bot. Didn't encounter any errors when I ran it for like 2hours.

You can download the updated script from the link above now.

*** Script fixed and uploaded

In the next version:

I am planning to use ctcp FINGER replies from users to check idle times for devoicing voiced users, rather than "getchanidle" which sets to 0, once the bot cycles or parts. I think this would be more accurate.

[nml375]

The downside with ctcp finger-replies is that the reply is in no way standardized, and entirely rely on the client to provide accurate information (which, of course, could easily be circumvented with the scripting-capabilites available in most clients these days). Not all clients will respond to ctcp-finger requests either.
I'd suggest you stick with getchanidle, as this will always return the least-idle time for any user in the channel.

[awyeah]

Yes that is a problem however, as you can change ctcp replies based on if you use scripts, or if you know how to script yourself as well.

There is another way to script around it, but only the idea of that in my mind is too complex just to write it, heh.

I guess then getchanidle would be the ONLY (easier) solution then.

[CosmicD]

I like the concept because I've seen it on other channels. However: there, the bot behaves intelligently. Which means that if a certain voice user is being kicked or banned, the bot will voice him immediately for being an active chatter , and this state will be cancled at 0:01.

I wonder if something like that can be implemented in this script as well...

[awyeah]

The active chatter (+v) flag is only given if a person has said more than X (x is a number) number of lines on a channel. My script only counts channel messages and NOT channel actions or channel notices.

Furthermore, if a user is kicked from the channel, parts the channel, quits irc or any of the mention (meaning is not on the channel anymore) his stats will be set to 0.

Eg: If you type 20 lines, and part the channel and then rejoin back in the channel (and haven't said anything yet after you joined), you would have typed 0 lines in the bots record.

Furthermore, the unactive chatter (-v) flag uses getchanidle and devoices all voices who have been idle (haven't said anything in the channel) for more than X number of minutes.

This is basically the concept behind this script.


-------
For scripts kicking voiced users, you can change your scripts NOT to kick voiced users, by adding a line like this in the start of the procs.

Code: Select all

if {[isvoice $nick $chan]} { return 0 }

To normal users on IRC the bot might look intelligent like, AI (with this script) but the script has a very simple and clear concept.

*** If a voiced user is kicked and if he rejoins you can voice him again, you just need to bind on kick, check if the user was voiced, and add him to an array (remember to remove the nick from the array with a timer whenever you like). Then bind on join and check the array for the nick, if it matches, voice that user.

--------------
For the latest version of this script:

I was thinking to maybe integrate the number of X lines said, within a certain amount of time. Say voice the user if he says 30 lines in less than or equal to 60 minutes (lines:minutes --> 30:60).

But I tested it, and unfortunately if the script is activated on a large number of channels, or if some of the channels are very active (have alot of users talking), the bot would be running alot of timers --->> will slow it down and saturate alot of memory -->> which is bad.

-->> so have to think of another method to accomplish this.

[awyeah]

Active Chatter v3.66.b

20/09/07: Fixed some bugs reported.

Uploaded activechatter.tcl v3.66.b on my script website:
http://channels.dal.net/awyeah/