egghelp.org community

[samhain]

[Sir_Fz]

It does not send 0, it sends minutes/60 (i.e. that is converted to hours). No one else complained about such a problem, I can't help you with this. Perhaps another Undernet AllProtection user can help you with this
_________________
Follow me on GitHub

- Opposing

Public Tcl scripts

[samhain]

yeah i really need to get rid of this problem..... but the strange thing is that the bantime is set to 2400 so even if it converts it to hours it should work but it doesn't place that ban.

[Sir_Fz]

Zircon uses my script on Undernet and he always reports bugs/errors/suggestions. He can help you with your problem. Send him a private message.
_________________
Follow me on GitHub

- Opposing

Public Tcl scripts

[AskMe]

i need your help again...

i put your script on windrop and it work perfect...

now i have install it on eggdrop and have sone prob...

[Sir_Fz]

What Windrop version are you using?
_________________
Follow me on GitHub

- Opposing

Public Tcl scripts

[Zircon]

Hello samhain

For me, it s fully working banning through X. And i just tested now again. I m having the same setting as you : ap:notcl: {1:3 2400 kb 2}

I sent a notice to the channel, here is the result :

-KickTesT:#Culture- (#Culture) test test test test test test test test test test
KickTesT kicked from #Culture by Anti-Flood: Notice not allowed. (1 lines in 0.0 secs) :: Banned 2400 minutes
#Culture: mode change '+b *!*@bas4-montreal28-1177918235.dsl.bell.ca' by X!cservice@undernet.org

And on Cservice, i saw that ban with these info :
Duration : 1 days, 16:00:00 [40 hour(s)]
Reason : Notice not allowed. (1 lines in 0.0 secs) :: Banned 2400 minutes

So it s working. By the way, in the settings of AllProtection, the ban-time is expressed in minutes. Since u r specifying 2400, it means 2400 minutes = 40 hours = 1 day and 16 hours, u can see this info in the ban duration displayed by Cservice.

So my suggestion is to download again AllProtection, and not edit the settings related to ban-time and punishment. And instead of that, change all the settings via the partyline. U ll have more latitude. In the partyline, u can do like this :

.chanset #channel ap:notcl 1:3 2400 kb 2
Replace #channel by the name of ur channel, or just put * if u want to appy this setting to all ur channels. By the way, if you want to ban for 100 days, then it s : 2400 hours x 60 = 144000 minutes, and then :
.chanset #channel ap:notcl 1:3 14400 kb 2

Hope this will help

[AskMe]

my windrop 1.6.18 (the script is ok)

my eggdrop 1.6.18 (and this is where the script give me the error)

i remove the bot from a chan and now i have this error

[samhain]

thanks Zircon.... I'll try that... thanks for your valueable suggestion

[Zircon]

You are welcome samhain, and by the way, i went through ur copy of AllProtection. I noticed that all the ban-times you specified are 24. This wont work, coz ban-time are in minutes in AllProtection. Since 24 minutes is less than an hour, X cannot ban. The minimum duration for banning with X is 1 hour. So the minimum ban-time that u should use with AllProtection if you want to ban with X, is 60. Anything bigger than 60 will work.

[samhain]

I tried 2400 too but it didn't work, but lets see what happens

[Sir_Fz]

[samhain]

thanks zircon for helping me the script works fine now....
I was wondering about

join-flood protection sometimes on undernet we face netsplits and the users joins again in shape of a flood most of the joinflood protection script have this problem thats why i do not enable that option.... do you think allprotection script has this problem too if users after netsplits join the channel in shape of a flood the script will ban those users and consider those users as a joinflood?

[Zircon]

Hello samhain

To avoid this problem, i changed the variable "wait-split" in the config file. In your conf file, u have this :

[samhain]

ahh problem solved thanks Zircon