A very unusual trigger for the ctcp action bind

[awyeah]

Hi,

A very unsual thing has happened.

Code: Select all

<ChanGaZEe> ACTION gives Sudhir aSuperTightHuggingReallySuperEroticGropingFondlingEarthShatteringSonicBoom2,8OhGawdIfYouStopI'llKillYouBetterThanHeavenYetHotterThanHellWatchWhereYaStickYerHandsSuperHugeDon'tYaDareStopTouchingMeKneesAreShakingEarthIsTremblingMyHeartHasStoppedBeatingWasThatTheGroundMovingPassionate WetDeepLingering***KISS!!!
* adapter sets mode: +b *!*@202.163.95.90
* ChanGaZEe was kicked by adapter ( Channel Long Action Flood Kick  - You exceeded the limit of 300 bytes of an action, by typing an action of *322* characters. It would be appreciated if you made a long story, short. - (Kick #1002))

This guy typed a text instead of an action
but still it triggered one of my binds, which is

Code: Select all

bind ctcp - ACTION my_procedure

How can this be avioded.
This is a text and should be detected by the pubm bind
rather than the ctcp bind.

How can I fix this, so the ctcp - action bind does not
trigger this?

[user]

This is a text and should be detected by the pubm bind
rather than the ctcp bind.

Nope..that's 1.5 ctcp (\001bla\001 + \001 (the second one should be considered a normal privmsg)), so unless you left something out, your client is the one messing up, not the eggdrop.

[awyeah]

Umm... thanks for the info.