| View previous topic :: View next topic |
| Author |
Message |
MenzAgitat
Op
Joined: 04 Jul 2006
Posts: 118
Location: France
|
 Posted: Thu Jul 20, 2006 7:15 pm Post subject: |
 |
|
I never disabled these two commands because I am the only one to have access to the partyline. The errorinfo variable is just not set when I query it. Thank you anyway for trying to help me  |
|
| Back to top |
|
 |
Alchera
Revered One
Joined: 11 Aug 2003
Posts: 3344
Location: Ballarat Victoria, Australia
|
| Posted: Fri Jul 21, 2006 2:47 am Post subject: |
|
|
Do know what is meant by "commenting"? What I pasted are the default eggrop.conf settings - disabled. You have to place a '#' in front of the respective line(s) and then .restart your bot for it to take effect (enable).
That is the reason why '.set errorInfo' does "not exist". 
_________________
Add [SOLVED] to the thread title if your issue has been.
Search | FAQ | RTM |
|
| Back to top |
|
|
MenzAgitat
Op
Joined: 04 Jul 2006
Posts: 118
Location: France
|
| Posted: Fri Jul 21, 2006 8:12 am Post subject: |
|
|
Ok I understand ^^
When I said
| Quote: | | The .set errorinfo command, which I use immediately after an error each time I can, keeps saying to me that the errorinfo variable does exist. |
i meant | Quote: | | The .set errorinfo command, which I use immediately after an error each time I can, keeps saying to me that the errorinfo variable does not exist. |
And i also understood my problem with the .set errorInfo command : I was omitting to capitalize the I when i was typing the command, I didn't know tcl variables were case sensitive. 
suggestion : the bot should be immunized against clone detection. It is hosted by me and when my wife connects to the channel, we are 3 on the same connection so we are detected as clones and the bot kicks himself.
I also got a problem with the bad words list.
Example : If I set it to | Code: | set bwords(global) {
*encul*
*connard*
*salope*
} |
only the badword "connard" makes the bot react and punish, (saying "enculι" or "salope" does nothing). I can't understand why. |
|
| Back to top |
|
|
Sir_Fz
Revered One
Joined: 27 Apr 2003
Posts: 3793
Location: Lebanon
|
| Posted: Fri Jul 21, 2006 6:52 pm Post subject: |
|
|
Ok, next time paste the outcome of .set errorInfo so we can know where the error exactly occurs. I'll check out the clone detection problem, as for bad words protection - never witnessed such a problem and neither did anybody report it, I don't see why it shouldn't work.
_________________
Follow me on GitHub
- Opposing
Public Tcl scripts |
|
| Back to top |
|
|
Domin
Halfop
Joined: 10 Jun 2006
Posts: 72
|
| Posted: Sat Jul 22, 2006 5:28 am Post subject: |
|
|
Remember to delete aplists in scripts dir, since i also had that problem and it seems ap:reset * dont reset that list, but if you delete the file and do a restart it will work.
Btw, thanks for a greate script |
|
| Back to top |
|
|
MenzAgitat
Op
Joined: 04 Jul 2006
Posts: 118
Location: France
|
| Posted: Sat Jul 22, 2006 6:24 am Post subject: |
|
|
Thank you Domin, the problem I have with the badwords list is because aplist is not updated when I restart the bot. 
Sir_Fz maybe you should make a separate command to update global variables in aplists (other than .ap:reset). My bot manages security on 5 channels with different settings for each, and I don't want to reset ALL settings back to default ones each time I add a badword.
Keep up the good work Sir_Fz  |
|
| Back to top |
|
|
Domin
Halfop
Joined: 10 Jun 2006
Posts: 72
|
| Posted: Sat Jul 22, 2006 8:14 am Post subject: |
|
|
I dont think you have to, try eding the apllist file, and then just do a restart (perhaps even a rehash is enough) and see if it dont load the right words now.
Remember to make a backup of the aplist file before you edit so you can restore to original settings
_________________
Regards
Domin @ efnet |
|
| Back to top |
|
|
Sir_Fz
Revered One
Joined: 27 Apr 2003
Posts: 3793
Location: Lebanon
|
| Posted: Sat Jul 22, 2006 9:56 am Post subject: |
|
|
So I understand that the aplists file is not being updated when you add new elements to the lists?
I've tested it on my bot and it seems to be updating just fine, can you explain more on where and when does your problem occur?
_________________
Follow me on GitHub
- Opposing
Public Tcl scripts |
|
| Back to top |
|
|
Domin
Halfop
Joined: 10 Jun 2006
Posts: 72
|
| Posted: Sat Jul 22, 2006 10:07 am Post subject: |
|
|
I first discoverede the problem when updating from b4 to b5 since i did not know that the bot had made the fil aplist, and i couldt not understand that it did not get any of my settings that i had set in the tcl file, even thou i tried .ap:reset global and i tried rehash, restart, and even die and then start the bot again from shell, until i found the aplist file and saw that it was still holding default settings from before i startede to edit the config, i then deletede that file startede the bot again, and did a ap:reset global and i createde a new file with the settings i specifyed in the tcl file and everything was fine
Im running it on eggdrop v1.6.18+RC1
OS: FreeBSD 5.4-STABLE
Tcl library: /usr/local/lib/tcl8.4
Tcl version: 8.4.11 (header version 8.4.11)
Btw, is it possible to add exempts to drone scanner with the ap:add setting since i dont seem to be able to finde that setting.
_________________
Regards
Domin @ efnet |
|
| Back to top |
|
|
Sir_Fz
Revered One
Joined: 27 Apr 2003
Posts: 3793
Location: Lebanon
|
| Posted: Sat Jul 22, 2006 10:32 am Post subject: |
|
|
The aplists file is used to store badchans, badwords, badnicks, badidents and adexempts lists and has nothing to do with the .ap:reset command. The .ap:reset command is used to reset the channel's AP settings to their default values (set in the script) - so I don't see any relation with what you're talking about.
As for adding drone exempts via .ap:add, I'm going to implement it (don't know how I missed it).
_________________
Follow me on GitHub
- Opposing
Public Tcl scripts |
|
| Back to top |
|
|
Domin
Halfop
Joined: 10 Jun 2006
Posts: 72
|
| Posted: Sat Jul 22, 2006 11:19 am Post subject: |
|
|
Well i hardcoded a few badwords in the tcl file, and they dont show up in the aplist even if i do a ap:reset, a rehash, a restart or completly shut down the bot and start the bot again, only way i can get them to change is if i delete the aplist file and start the bot again, then it will create a new aplist with the right settings taken from the tcl file.
That was what i ment, sorry if it dident come out as cleare as it shouldt but english is not my native language.
Sounds nice with the drone settings
_________________
Regards
Domin @ efnet |
|
| Back to top |
|
|
exhuman
Voice
Joined: 22 Jul 2006
Posts: 9
|
| Posted: Sat Jul 22, 2006 2:08 pm Post subject: |
|
|
I using BETA, and i getting this error, i am new in using TCL scripts.
(23:30) · (Cosa_Nostra · [23:55] Tcl error [::RusTeD::parts partmsgs]: can't read "v": no such variable
(23:30) · (Cosa_Nostra · [23:56] Tcl error [::RusTeD::control]: wrong # args: should be "scan nick uhost hand chan"
(23:31) · (Cosa_Nostra · [23:56] Tcl error [::RusTeD::joins bidents]: wrong # args: should be "scan nick uhost hand chan"
(23:31) · (Cosa_Nostra · [23:56] Tcl error [::RusTeD::joins clones]: wrong # args: should be "scan nick uhost hand chan"
(23:31) · (Cosa_Nostra · [23:57] Tcl error [::RusTeD::control]: wrong # args: should be "scan nick uhost hand chan"
(23:31) · (Cosa_Nostra · [23:57] Tcl error [::RusTeD::joins bidents]: wrong # args: should be "scan nick uhost hand chan"
(23:31) · (Cosa_Nostra · [23:57] Tcl error [::RusTeD::joins clones]: wrong # args: should be "scan nick uhost hand chan"
(23:32) · (Cosa_Nostra · [23:58] Tcl error [::RusTeD::control]: wrong # args: should be "scan nick uhost hand chan"
(23:33) · (Cosa_Nostra · [23:59] Tcl error [::RusTeD::control]: wrong # args: should be "scan nick uhost hand chan" |
|
| Back to top |
|
|
Sir_Fz
Revered One
Joined: 27 Apr 2003
Posts: 3793
Location: Lebanon
|
| Posted: Sat Jul 22, 2006 6:38 pm Post subject: |
|
|
Domin, if by "hardcoded" you mean added them in the default variables inside the script then it won't work. AllProtection will override the default settings (for the lists) if they exist in the aplists file, that's why you need to use the .ap:add command to edit lists.
exhuman are you sure you're using my AllProtection script? if yes, then paste the output of .set errorInfo.
_________________
Follow me on GitHub
- Opposing
Public Tcl scripts |
|
| Back to top |
|
|
Alchera
Revered One
Joined: 11 Aug 2003
Posts: 3344
Location: Ballarat Victoria, Australia
|
| Posted: Sat Jul 22, 2006 8:40 pm Post subject: |
|
|
Another "simple" solution:
I also altered the badwords directly in the script, deleted the aplists file and simply rehashed the bot to reflect the changes.
_________________
Add [SOLVED] to the thread title if your issue has been.
Search | FAQ | RTM |
|
| Back to top |
|
|
exhuman
Voice
Joined: 22 Jul 2006
Posts: 9
|
| Posted: Sun Jul 23, 2006 5:38 am Post subject: |
|
|
(15:11) · RuSTeD-FaiTH · .set errorInfo
(15:11) · (Cosa_Nostra · What? You need '.help'
(15:11) · (Cosa_Nostra · [15:36] Tcl error [::RusTeD::joins bidents]: wrong # args: should be "scan nick uhost hand chan"
(15:11) · (Cosa_Nostra · [15:36] Tcl error [::RusTeD::joins clones]: wrong # args: should be "scan nick uhost hand chan"
(15:11) · (Cosa_Nostra · [15:37] Tcl error [::RusTeD::control]: wrong # args: should be "scan nick uhost hand chan"
(15:11) · (Cosa_Nostra · [15:37] #izzat: mode change '+l 6' by Cosa_Nostra!exhuman@lame.conn3ction.us
(15:11) · (Cosa_Nostra · [15:37] #izzat: mode change '-l ' by Cosa_Nostra!exhuman@lame.conn3ction.us
and problem is in limit
(15:02) Mode change: +l 6 by Cosa_Nostra
(15:02) Mode change: -l by Cosa_Nostra
(15:03) Mode change: +l 6 by Cosa_Nostra
(15:04) Mode change: -l by Cosa_Nostra
(15:04) Mode change: +l 6 by Cosa_Nostra
(15:04) Mode change: -l by Cosa_Nostra
(15:05) Mode change: +l 6 by Cosa_Nostra
(15:05) Mode change: -l by Cosa_Nostra
(15:06) Mode change: +l 6 by Cosa_Nostra
(15:06) Mode change: -l by Cosa_Nostra |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
