Commands:
DCC:
.ap:import <oldchan> <*/newchan> (This sets the AP settings of <oldchan> on <newchan> or all chans if *)
.ap:reset <*/chan> (This will reset the AP settings of chan or all chans if * to the default settings)
.ap:disable <*/chan> (This will disable all protections on chan or all chans if *)
.ap:monitor (displays info about followed punishments)
.ap:add <list> <chan/global> <elements>
.ap:rem <list> <chan/global> <elements>
.ap:list <list> <chan/global>
.ap:priv <set/list> <setting> <value> (priv flood settings)
** Available lists: bchans, bnicks, bidents, bwords, adexempts, droneexempts, adwords, bctcrs & greetexempts.
http://www.4shared.com/file/70288152/71 ... n46b9.html works for me?Ikaa wrote:The 4shared link for 4.6.9b seems to be non functional. Is there a mirror? I love this script.
This error can't happen with version 4.6b9 since it does not contain a procedure called adv:kick. Upgrading to the latest version will solve your problem. If you still want to fix it in version 4.5 then please paste the output of '.set errorInfo'Lupo wrote:I've been gladly using your script for a while now as it must be the most complete script for eggdrop out there, but recently i've been getting the following error on an attempt of action :
Tcl error [adv:kick]: expected integer but got ""
I got the same for all kicks and kickbans.
I'm using eggdrop 1.6.19 and the latest tcl installed.
Any help to solve this would be greatly appreciated.
EDIT : i have this both with version 4.5 and 4.6b9
You can edit who is exempted by changing the exmptype settingentropy wrote:Excellent all-around protection script. Thanks!
In my testing, I noticed that +v users on the bot are exempt if they happen to trigger an actionable event (like repeat lines), just like +o users are.
The channel I run this script in has many voiced users due to the way we try to limit abuse (+m chan, everybody gets auto voiced after 20s. We then blacklist abusers so they don't get the auto voice). This helps with fly-by spam and a number of other issues.
I was wondering if theres an easy way to set which user flags will be exempt from action if they trigger one of the settings, and which will be subject to it. I looked through the source but couldn't easily locate where you're doing your if/match.
Maybe in future versions this would be useful as a knob users can configure?
ie> ap:protectedusers omn
to make all non op/master/owner users subject to the protection settings?
Maybe even for more granular settings
ap:protectedusersglobal
ap:protecteduserschan
to protect users by global flags and per channel flags. If something like this existed I could easily enforce my protections on auto voiced users where it doesn't appear that I can now. Just a suggestion Smile
Best protection script available, nice work!
On a side note, it looks like the new version number didn't make it into the loaded/unloaded messages. It still says v4.6b8.
Oh and yes, I forgot to change the version number in the loaded/unloaded message, my bad. Problem fixed in the new links thanks# Set here any additional exempts, you can exempt the following:
# ops: Channel ops
# halfops: Channel halfops
# voices: Channel voices
# +flags|+flags: Users with global or channel specific flags (e.g. +fm friends and masters...)
# -flags&-flags: Users which do not have the specified flags (e.g. -k&-k)
variable exmptype {ops voices +fmo|+fmo}
Hmm, sorry about that... Can't believe I missed it in the script. Thanks!Sir_Fz wrote: You can edit who is exempted by changing the exmptype setting
# Set here any additional exempts, you can exempt the following:
# ops: Channel ops
# halfops: Channel halfops
# voices: Channel voices
# +flags|+flags: Users with global or channel specific flags (e.g. +fm friends and masters...)
# -flags&-flags: Users which do not have the specified flags (e.g. -k&-k)
variable exmptype {ops voices +fmo|+fmo}