when server make notice like :
-->mesra.kl.my.dal.net:#channel- *** Notice -- Server flood protection activated for #channel
the bot make this ban : mode change '+b *!*@*' by Bot!Bot@host.com
how can i fix that bugs or where i can find it ?
This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
What's wrong with this bot?
That's not a bug.
Beside that, the eggdrop Foprum had been the right place for that question. Anyway.
If your bot connects to that IRC Net, services request a password from it.
If your bot is a bit lagged to the IRC Services, they will send the request again.
Your Bot recognises that as a msg flood.
ad a new user to your bot with the hosmask the put is ignoring and give that user global +f.
Mostly the problem should be fixed than.
Beside that, the eggdrop Foprum had been the right place for that question. Anyway.
If your bot connects to that IRC Net, services request a password from it.
If your bot is a bit lagged to the IRC Services, they will send the request again.
Your Bot recognises that as a msg flood.
ad a new user to your bot with the hosmask the put is ignoring and give that user global +f.
Mostly the problem should be fixed than.
Actualy that *sounds* like a anti-notice thing.. something that bans the users that use channel notices while in the channel or something like this anyway. If you want to get ridd of that thing then:
1. remove the *anti-notice* tcl and get another one if you don't know how to change it to suit your needs;
2. ask the author of the script to make a change to suit your needs.
Adding a check to see if that user who triggers the proc has is a known user to the eggdrop and if he/she has a certain flag like friend (+f) or something like this, then adding the irc *services* as a friend to your eggdrop the problem should be solved in minutes if not less.
1. remove the *anti-notice* tcl and get another one if you don't know how to change it to suit your needs;
2. ask the author of the script to make a change to suit your needs.
Adding a check to see if that user who triggers the proc has is a known user to the eggdrop and if he/she has a certain flag like friend (+f) or something like this, then adding the irc *services* as a friend to your eggdrop the problem should be solved in minutes if not less.
Once the game is over, the king and the pawn go back in the same box.
Caesar got it right again 
I had the same problem before. when I changed to the NoticeBan TCL script which can be found in the TCL archieve of this site, the problem was solved.
it occurs because mesra.kl.my.dal.net is not a user which has a host. but in the NoticeBan.tcl it is taken into consideration.
I had the same problem before. when I changed to the NoticeBan TCL script which can be found in the TCL archieve of this site, the problem was solved.
it occurs because mesra.kl.my.dal.net is not a user which has a host. but in the NoticeBan.tcl it is taken into consideration.
Yes bro really that is my problem but i want NoticeBan TCL .Sir_Fz wrote:Caesar got it right again
I had the same problem before. when I changed to the NoticeBan TCL script which can be found in the TCL archieve of this site, the problem was solved.
it occurs because mesra.kl.my.dal.net is not a user which has a host. but in the NoticeBan.tcl it is taken into consideration.
may can u give me code to fix it ?
I told you, you can find it in the TCL archieve.
however, here's the link: http://www.egghelp.org/cgi-bin/tcl_arch ... oad&id=689
however, here's the link: http://www.egghelp.org/cgi-bin/tcl_arch ... oad&id=689
-
Alchera
- Revered One
- Posts: 3344
- Joined: Mon Aug 11, 2003 12:42 pm
- Location: Ballarat Victoria, Australia
- Contact:
It might help to add DALnet as a "friend" globally.
<Natale> [04:28] #Alchera# whois dalnet
<Natale> HANDLE PASS NOTES FLAGS LAST
<Natale> DALnet no 0 f 07:47 (#Ballarat)
<Natale> HOSTS: *!*@dal.net
That solved all my problems in every bot no matter what script they run or what server they connect to. And, as they are all on a botnet, I use netbots with only sentinel, mainserver & repeat sections enabled.
<Natale> [04:28] #Alchera# whois dalnet
<Natale> HANDLE PASS NOTES FLAGS LAST
<Natale> DALnet no 0 f 07:47 (#Ballarat)
<Natale> HOSTS: *!*@dal.net
That solved all my problems in every bot no matter what script they run or what server they connect to. And, as they are all on a botnet, I use netbots with only sentinel, mainserver & repeat sections enabled.
i try that befor but nothing for fix it . now i change NoticBan 2 new version i think that problemAlchera wrote:It might help to add DALnet as a "friend" globally.
<Natale> [04:28] #Alchera# whois dalnet
<Natale> HANDLE PASS NOTES FLAGS LAST
<Natale> DALnet no 0 f 07:47 (#Ballarat)
<Natale> HOSTS: *!*@dal.net
That solved all my problems in every bot no matter what script they run or what server they connect to. And, as they are all on a botnet, I use netbots with only sentinel, mainserver & repeat sections enabled.
