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

Sydneybabe · Post by **Sydneybabe** » Tue Dec 04, 2007 12:52 am

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

<Tashwini> [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"
<Tashwini> [23:48] Data extracted: maLd|tang`masung|t ~grace@d193-69-36.home3.cgocable.net #anthony *!*@.org
<Tashwini> [23:48] Sending: CHANSERV WHY #anthony maLd|tang`masung|t
<Tashwini> [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"
<Tashwini> [23:48] Origin appears authentic, continuing...
<Tashwini> [23:48] Data extracted: maLd|tang`masung|t SOp #anthony. maLd|tang`masung|t NO
<Tashwini> [23:48] Did not find scheduled check. Ignoring (Status: 1 0
<Tashwini> [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.

Post by **nml375** » Tue Dec 04, 2007 5:04 pm

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 -- {^.....)

Alchera · Post by **Alchera** » Tue Dec 04, 2007 8:06 pm

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

Code: Select all

set tchan [string trim $tchan .]

Post by **nml375** » Wed Dec 05, 2007 11:13 am

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?

Sydneybabe · Post by **Sydneybabe** » Wed Dec 05, 2007 1:28 pm

hi nml375 is the scripts work now

Post by **nml375** » Wed Dec 05, 2007 2:06 pm

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..

Sydneybabe · Post by **Sydneybabe** » Thu Dec 06, 2007 3:08 am

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

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

.. nothing happen removing akick :/

Post by **nml375** » Thu Dec 06, 2007 8:46 am

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: Select all

 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: Select all

 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.

Alchera · Post by **Alchera** » Thu Dec 06, 2007 7:33 pm

nml375 wrote: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.

Alchera · Post by **Alchera** » Thu Dec 06, 2007 10:05 pm

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

<Barry> [13:08] Recieved chanserv-notice "[VERBOSE] Dinotopia!weirdo@jebediah.amishmafia.org => akick #egghelp.org add Henry!*@*" from "ChanServ!service@dal.net" to "@#egghelp.org"
<Barry> [13:08] Data extracted: Dinotopia weirdo@jebediah.amishmafia.org #egghelp.org Henry!*@*
<Barry> [13:08] Sending: CHANSERV WHY #egghelp.org Dinotopia
<Barry> [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"
<Barry> [13:08] Origin appears authentic, continuing...
<Barry> [13:08] Debug2: Bytes of match is:
<Barry> [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,
<Barry> [13:08] Did not find scheduled check. Ignoring (Status: 1 0
<Barry> [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.

Post by **nml375** » Fri Dec 07, 2007 1:57 pm

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..

Alchera · Post by **Alchera** » Fri Dec 07, 2007 4:46 pm

nml375 wrote: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.

Sydneybabe · Post by **Sydneybabe** » Sat Dec 08, 2007 12:02 am

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