AllProtection.tcl (Stable: v4.8 / Beta: v4.9b4)

Post by **Sir_Fz** » Tue Jan 23, 2007 7:54 pm

AllProtection does not do that. You may have another script doing that, make sure you downloaded the script from the link posted in the initial post.

starpossen · Post by **starpossen** » Wed Jan 24, 2007 4:05 am

I used the link for the latest version provided in this topic, but I will try and disable all other scripts, and see if that helps.

*EDIT* okay, I disabled all other scripts, and so far the bans stay, but now the +l bounces on and off, and I did not touch any setting at all, all I did was restart the bot with only this script enabled.

Post by **Sir_Fz** » Wed Jan 24, 2007 4:01 pm

The +l bounces because you have '-l' in your chanmode channel setting.

.chanset #channel chanmode +nt-ks

for example (the idea is not to have -l there).

starpossen · Post by **starpossen** » Wed Jan 24, 2007 6:33 pm

Yes you're right, that fixed it.
Now, whenever a rule is violated and the bot bans, it unbans right after banning, why is that?

*EDIT* Thought I might add my chansettings:

Code: Select all

channel set #dralla chanmode +tn-kim 
idle-kick 0 
stopnethack-mode 0 
revenge-mode 0 
need-op {  } 
need-invite {  } 
need-key {  } 
need-unban {  } 
need-limit {  } 
flood-chan 10:60 
flood-ctcp 3:60 
flood-join 5:60 
flood-kick 3:10 
flood-deop 3:10 
flood-nick 5:60 
aop-delay 5:30 
ban-time 0 
exempt-time 0 
invite-time 0

-enforcebans -dynamicbans +userbans -autoop -autohalfop -bitch -greet -protectops -protecthalfops -protectfriends -dontkickops -statuslog -revenge -revengebot -autovoice -secret -shared -cycle -seen -inactive -dynamicexempts -userexempts -dynamicinvites -userinvites -nodesynch

I did this while being tired, so I might have been doing some big newb mistakes, yes im a newb still.

Post by **Sir_Fz** » Wed Jan 24, 2007 7:02 pm

I guess that's because you have -dynamicbans set, change it to +dynamicbans.

PS: Next time use .chaninfo #channel to show channel-settings.

AWoL · Post by **AWoL** » Wed Jan 24, 2007 9:32 pm

I currently have AllProtection v4.6b7 loaded into two linked and i have to tell ya man good work, to you and those that helped. It's the total protection package. I have an adult file trading room on and adult irc network, and even with all the inherent protection issues (control codes from the fileserver ads, fast and multiple file requests from users, and the need to restrict co-channeling in certain rooms) this has performed admirably. Only thing I would add is a little 'how to' paragraph to change bword, bidents and bchan default words (.ap:rem, ap:add etc). Great work though keep it up.

Post by **Sir_Fz** » Thu Jan 25, 2007 3:25 pm

# .ap:add <list> <chan/global> <elements>
# .ap:rem <list> <chan/global> <elements>
# ** Available lists: bchans, bnicks, bidents, bwords, adexempts,
# droneexempts, adwords & bctcrs.

For example:

.ap:add bchans global #chan1 #chan2 #chan*

or

.ap:add bwords #mychannel "*word 1*" word2 word3 "word 4 bla*"

Same for .ap:rem.

elisca · Post by **elisca** » Sat Jan 27, 2007 4:00 pm

Sir_Fz wrote:Alright, I have fixed the bugs reported for AllProtection4.6b7. Get the new file AllProtection4.6b7. these bugs include ap:reset and ap:disable commands causing error and the bad channel protection not working (now fixed).

sir i have use it but still get error :
[02:57] Tcl error [::AllProtection::cmd disable]: Unknown channel setting.

Post by **Sir_Fz** » Sat Jan 27, 2007 8:28 pm

You probably have the older 4.6b7, make sure you're using the latest one (the one with a more recent release date).

If you're sure you're using the correct script then provide extra information about the error by showing the output of '.set errorInfo' in partyline.

Zircon · Post by **Zircon** » Sun Jan 28, 2007 5:23 am

Hello starpossen

Your ban-time is set to 0 minutes :

aop-delay 5:30
ban-time 0
exempt-time 0
invite-time 0

That s why the bot unbans right after banning. Set it to another number, like 180 or more. 180 = 180 minutes = 3 hours

ban-time 180

Post by **Sir_Fz** » Sun Jan 28, 2007 8:05 am

ban-time 0 has nothing to do with the bot unbanning, that was an issue caused by some other script and has been resolved.

ban-time 0 means that the bot will not try to unban any bans in the channel which will not stop AllProtection from unbanning bans set by it.

Zircon · Post by **Zircon** » Sun Jan 28, 2007 3:09 pm

Hello Sir_fz

so setting ban-time to 0 desactivates completely the unbanning process. Thanks for pointing that. i thought that setting ban-time to 0 was the problem

elisca · Post by **elisca** » Sun Jan 28, 2007 4:20 pm

Sir_Fz wrote:You probably have the older 4.6b7, make sure you're using the latest one (the one with a more recent release date).

If you're sure you're using the correct script then provide extra information about the error by showing the output of '.set errorInfo' in partyline.

No sir, I have using from the latest one, download from your link on Posted: Sun Jan 07, 2007 9:02 am, here i give you the error information from partyline :

[3:09:38am] ((spitz) [03:12] Tcl error [::AllProtection::cmd disable]: Unknown channel setting.
[3:09:51am] [DNAx] .set errorInfo
[3:09:51am] ((spitz) [03:12] #DNAx# set errorInfo
[3:09:51am] ((spitz) Currently: Unknown channel setting.
[3:09:51am] ((spitz) Currently: while executing
[3:09:51am] ((spitz) Currently: "channel get $c [set ud [lindex $u 0]]"
[3:09:52am] ((spitz) Currently: ("foreach" body line 3)
[3:09:52am] ((spitz) Currently: invoked from within
[3:09:52am] ((spitz) Currently: "foreach u ${ap:udefs} {
[3:09:52am] ((spitz) Currently: if {$u == "ap:level" && !$banthruX(do)} {continue}
[3:09:52am] ((spitz) Currently: set rest [join [lrange [split [channel get $c [set ud [lindex $u 0..."
[3:09:52am] ((spitz) Currently: ("foreach" body line 3)
[3:09:52am] ((spitz) Currently: invoked from within
[3:09:52am] ((spitz) Currently: "foreach c $chans {
[3:09:52am] ((spitz) Currently: if {[validchan $c]} {
[3:09:52am] ((spitz) Currently: foreach u ${ap:udefs} {
[3:09:52am] ((spitz) Currently: if {$u == "ap:level" && !$banthruX(do)} {continue}
[3:09:52am] ((spitz) Currently: set rest [join [..."
[3:09:52am] ((spitz) Currently: ("disable" arm line 5)
[3:09:52am] ((spitz) Currently: invoked from within
[3:09:52am] ((spitz) Currently: "switch -- $cmd {
[3:09:52am] ((spitz) Currently: "add" {
[3:09:52am] ((spitz) Currently: if {$ti == 0} {
[3:09:52am] ((spitz) Currently: if {[validchan $c]} {
[3:09:52am] ((spitz) Currently: if {![info exists aptv($c)]} {
[3:09:52am] ((spitz) Currently: set aptv($c) $l
[3:09:52am] ((spitz) Currently: set unfound $l
[3:09:52am] ((spitz) Currently: ..."
[3:09:52am] ((spitz) Currently: (procedure "::AllProtection::cmd" line 33)
[3:09:53am] ((spitz) Currently: invoked from within
[3:09:53am] ((spitz) Currently: "::AllProtection::cmd disable $_dcc1 $_dcc2 $_dcc3"

Post by **Sir_Fz** » Sun Jan 28, 2007 5:02 pm

Edit: On second thought, I just realized a huge mistake.

Replace all occurrences of

Code: Select all

if {$u == "ap:level" && ....}

with

Code: Select all

if {[lindex $u 0] == "ap:level" && ....}

elisca · Post by **elisca** » Sun Jan 28, 2007 5:14 pm

Sir_Fz wrote:Did you edit anything in the script? Perhaps the case of ap:level in the line 'lappend ap:udefs {ap:level 75}' this is supposed to remain lower-case in case you did change it. Unless you've done something wrong, I don't see why that error should occur.

This error means that the channel setting does not exist, which means it has not been initially set by the script. I don't see how that could happen unless the script has been wrongfully altered.

i just edit variable exmptype 0 and variable notifyusers to my nick.. nothing else. about the channel, i only set whre the bot exist..