egghelp/eggheads community

bot remove the akick and founder only allowed to add akick..

2007-12-08T00:02:33-04:00

wow it works now big thanks to nml375 for the big help and to Alchera for the help also thanks a lot

Statistics: Posted by Sydneybabe — Sat Dec 08, 2007 12:02 am

bot remove the akick and founder only allowed to add akick..

2007-12-07T16:46:32-04:00

Actually, it seems there is two spaces after "#eggdrop.org.". I have no idea why that does'nt show in the output though.
In any case, the fix should be trivial then..
Updating both initial code and debug in a minute or two..

There is indeed two spaces after the channel name and it appears this was truncated by the forum code.

Your fixed code works exactly as expected. Sydneybabe will be happy.

Statistics: Posted by Alchera — Fri Dec 07, 2007 4:46 pm

bot remove the akick and founder only allowed to add akick..

2007-12-07T13:57:37-04:00

Actually, it seems there is two spaces after "#eggdrop.org.". I have no idea why that does'nt show in the output though.
In any case, the fix should be trivial then..
Updating both initial code and debug in a minute or two..

Statistics: Posted by nml375 — Fri Dec 07, 2007 1:57 pm

bot remove the akick and founder only allowed to add akick..

2007-12-06T22:05:50-04:00

I ran the updated code and this is all that happened:

[13:08] Recieved chanserv-notice "[VERBOSE] Dinotopia!weirdo@jebediah.amishmafia.org => akick #egghelp.org add Henry!*@*" from "ChanServ!service@dal.net" to "@#egghelp.org"
[13:08] Data extracted: Dinotopia weirdo@jebediah.amishmafia.org #egghelp.org Henry!*@*
[13:08] Sending: CHANSERV WHY #egghelp.org Dinotopia
[13:08] Recieved chanserv-notice "Dinotopia has SOp access to #egghelp.org. Reason: Identification to the nickname Dinotopia. Channel Frozen: NO" from "ChanServ!service@dal.net" to "Barry"
[13:08] Origin appears authentic, continuing...
[13:08] Debug2: Bytes of match is:
[13:08] 68,105,110,111,116,111,112,105,97,32,104,97,115,32,83,79,112,32,97,99,99,101,115,115,32,116,111,32,35,101,103,103,104,101,108,112,46,
111,114,103,46,32,32,82,101,97,115,111,110,58,32,73,100,101,110,116,105,102,105,99,97,116,105,111,110,32,116,111,32,116,104,101,32,110,
105,99,107,110,97,109,101,32,68,105,110,111,116,111,112,105,97,46,32,67,104,97,110,110,101,108,32,70,114,111,122,101,110,58,32,78,79,
[13:08] Did not find scheduled check. Ignoring (Status: 1 0
[13:08] -ChanServ (service@dal.net)- Dinotopia has SOp access to #egghelp.org. Reason: Identification to the nickname Dinotopia. Channel Frozen: NO

.. and "we" stopped dead in "our" tracks.

Statistics: Posted by Alchera — Thu Dec 06, 2007 10:05 pm

bot remove the akick and founder only allowed to add akick..

2007-12-06T19:33:56-04:00

I guess that's a way of dealing with it, although I generally don't like those solutions :/
Alchera, do you get the same issue with the dot remaining aswell?

I was getting that dot also.

I was curious as to why Sydneybabe was having problems as there was no obvious reason why there should have been.

Statistics: Posted by Alchera — Thu Dec 06, 2007 7:33 pm

bot remove the akick and founder only allowed to add akick..

2007-12-06T08:46:49-04:00

It would seem there is some "garbage" in the string causing problems. stripcodes should've taken care of that, but apparently some non-graphical character remains within the string causing problems with the matching.

Could you try replacing this line:

Code:

 if {[regexp -- {^(.+?) has (SOp|AOp) access to (.+?)\. Reason: Identification to the nickname (.+?)\. Channel Frozen: (YES|NO)$} [stripcodes bcruag $text] match tnick tacc tchan trnick tfrozen]} {

With something like this (will produce large chunk of text to your logs):

Code:

 if {[regexp -- {^(.+?) has (SOp|AOp) access to (.+?). Reason: Identification to the nickname (.+?). Channel Frozen: (YES|NO)$} [stripcodes bcruag $text] match tnick tacc tchan trnick tfrozen]} {  foreach _c [split $match ""] {append _t "[scan $_c "%c"],"}  putlog "Debug2: Bytes of match is:"  putlog $_t

This should show exactly which characters the regular expression is matching against.

Statistics: Posted by nml375 — Thu Dec 06, 2007 8:46 am

bot remove the akick and founder only allowed to add akick..

2007-12-06T03:08:19-04:00

hi nml375 i loaded the script and this is what appear on partyline:

[02:04] Recieved chanserv-notice "[VERBOSE] DramaQueen`!psycho@203.215.124.22 => akick #anthony add *!*@hayz.ulit" from "ChanServ!service@dal.net" to "@#anthony"
[02:04] Data extracted: DramaQueen` psycho@203.215.124.22 #anthony *!*@hayz.ulit
[02:04] Sending: CHANSERV WHY #anthony DramaQueen`
[02:04] Recieved chanserv-notice "DramaQueen` has SOp access to #anthony. Reason: Identification to the nickname deee. Channel Frozen: NO" from "ChanServ!service@dal.net" to "Tashwini"
[02:04] Origin appears authentic, continuing...
[02:04] -ChanServ (service@dal.net)- DramaQueen` has SOp access to #anthony. Reason: Identification to the nickname deee. Channel Frozen: NO
[02:05] Writing user file...
[02:05] Writing channel file...

.. nothing happen removing akick :/

Statistics: Posted by Sydneybabe — Thu Dec 06, 2007 3:08 am

bot remove the akick and founder only allowed to add akick..

2007-12-05T14:06:01-04:00

Well, Alchera's fix would sort any issues with trailing dots (.). The cause for that dot is still unknown however. There might still be an issue with un-escaped character in the regular expression, that I'm gonna tend to in a few seconds..

Statistics: Posted by nml375 — Wed Dec 05, 2007 2:06 pm

bot remove the akick and founder only allowed to add akick..

2007-12-05T13:28:26-04:00

hi nml375 is the scripts work now

Statistics: Posted by Sydneybabe — Wed Dec 05, 2007 1:28 pm

bot remove the akick and founder only allowed to add akick..

2007-12-05T11:13:23-04:00

I guess that's a way of dealing with it, although I generally don't like those solutions :/
Alchera, do you get the same issue with the dot remaining aswell?

Statistics: Posted by nml375 — Wed Dec 05, 2007 11:13 am

bot remove the akick and founder only allowed to add akick..

2007-12-04T20:06:56-04:00

I loaded this into one of my bots and with a "dirty" fix, it works as expected.

Code:

set tchan [string trim $tchan .]

Statistics: Posted by Alchera — Tue Dec 04, 2007 8:06 pm

bot remove the akick and founder only allowed to add akick..

2007-12-04T17:04:48-04:00

Somehow you still get a trailing . in the channelname, which I find very strange. When running the regular expression manually with the same data, I do not get that dot.

Could you triple-check the regular expression in check:why, cause I'm running low on ideas why this is breaking?
(regexp -- {^.....)

Statistics: Posted by nml375 — Tue Dec 04, 2007 5:04 pm

bot remove the akick and founder only allowed to add akick..

2007-12-04T00:52:50-04:00

hi nml375 i load the script and this is what appear on partyline:

[23:48] Recieved chanserv-notice "[VERBOSE] maLd|tang`masung|t!~grace@d193-69-36.home3.cgocable.net => akick #anthony add *!*@.org" from "ChanServ!service@dal.net" to "@#anthony"
[23:48] Data extracted: maLd|tang`masung|t ~grace@d193-69-36.home3.cgocable.net #anthony *!*@.org
[23:48] Sending: CHANSERV WHY #anthony maLd|tang`masung|t
[23:48] Recieved chanserv-notice "maLd|tang`masung|t has SOp access to #anthony. Reason: Identification to the nickname maLd|tang`masung|t. Channel Frozen: NO" from "ChanServ!service@dal.net" to "Tashwini"
[23:48] Origin appears authentic, continuing...
[23:48] Data extracted: maLd|tang`masung|t SOp #anthony. maLd|tang`masung|t NO
[23:48] Did not find scheduled check. Ignoring (Status: 1 0
[23:48] -ChanServ (service@dal.net)- maLd|tang`masung|t has SOp access to #anthony. Reason: Identification to the nickname maLd|tang`masung|t. Channel Frozen: NO

..bot still not removing the akick.

Statistics: Posted by Sydneybabe — Tue Dec 04, 2007 12:52 am

bot remove the akick and founder only allowed to add akick..

2007-12-03T07:22:02-04:00

Problem located, forgot to escape a . in one of the regular expressions. Updating posts shortly..

Statistics: Posted by nml375 — Mon Dec 03, 2007 7:22 am

bot remove the akick and founder only allowed to add akick..

2007-12-03T02:42:33-04:00

hi nml375 i load the script and restart the bot and this is what appear on partyline:

[01:32] Recieved chanserv-notice "[VERBOSE] maLd|tang`masung|t!~grace@d193-69-36.home3.cgocable.net => akick #anthony add *!*@test.com" from "ChanServ!service@dal.net" to "@#anthony"
[01:32] Data extracted: maLd|tang`masung|t ~grace@d193-69-36.home3.cgocable.net #anthony *!*@test.com
[01:32] Sending: CHANSERV WHY #anthony maLd|tang`masung|t
[01:32] Recieved chanserv-notice "maLd|tang`masung|t has SOp access to #anthony. Reason: Identification to the nickname maLd|tang`masung|t. Channel Frozen: NO" from "ChanServ!service@dal.net" to "Tashwini"
[01:32] Origin appears authentic, continuing...
[01:32] Data extracted: maLd|tang`masung|t SOp #anthony. maLd|tang`masung|t NO
[01:32] Did not find scheduled check. Ignoring (Status: 1 0
[01:32] -ChanServ (service@dal.net)- maLd|tang`masung|t has SOp access to #anthony. Reason: Identification to the nickname maLd|tang`masung|t. Channel Frozen: NO

..still the sop bot Tashwini not removing the akick issued by a sop user maLd|tang`masung|t :/

Statistics: Posted by Sydneybabe — Mon Dec 03, 2007 2:42 am