|
|
Joined: Aug 2004
Posts: 7,168
Hoopy frood
|
OP
Hoopy frood
Joined: Aug 2004
Posts: 7,168 |
on ^*:text:*founder*:*:{
did $iif(($nick == chanserv) && (%nick isin $1-),-c,-u) Channel_Control 84
.disable #founder.check
halt
}
The above code checks (or unchecks) a dialog box depending on if the founder's nick, as returned from /chanserv info, matches the selected nick (or not). The response from chanserv, on the network where I'm testing this, normally shows in the status window. For the purposes of this script, I'd like to prevent that information from showing, but the script doesn't do that. Any help?
|
|
|
|
|
Joined: Sep 2005
Posts: 2,630
Hoopy frood
|
|
Hoopy frood
Joined: Sep 2005
Posts: 2,630 |
Use haltdef, not halt. on ^*:text:*founder*:*:{
if ($nick == chanserv) && (%nick isin $1-) {
did -c Channel_Control 84
haltdef
}
else did -u Channel_Control 84
.disable #founder.check
}
|
|
|
|
|
Joined: Aug 2004
Posts: 7,168
Hoopy frood
|
|
OP
Hoopy frood
Joined: Aug 2004
Posts: 7,168 |
Thanks for the quick response, unfortunately it doesn't seem to work for information coming via the status window. I'm still seeing the response.
|
|
|
|
|
Joined: Feb 2005
Posts: 342
Fjord artisan
|
|
Fjord artisan
Joined: Feb 2005
Posts: 342 |
You're still seeing the response because this is a NOTICE, and not a MESSAGE. Use on ^*:notice:*founder*:?:{ stuff | haltdef }
Edit:
An "on text" message will never show up in the status window, unless one of your scripts forces it to. Generally, all on text events will go to their proper target, either a channel, or a query/singlemessage window.
Edit the Edit, to clarify:
If this is indeed a message and not a notice, it means you are using another "on text" event, and sending the message to your status window instead of to a query window. You will need to modify this on text event, or merge it with your new on text event.
Last edited by Rand; 07/08/06 03:09 AM.
|
|
|
|
|
Joined: Aug 2004
Posts: 7,168
Hoopy frood
|
|
OP
Hoopy frood
Joined: Aug 2004
Posts: 7,168 |
Thanks. I should've realized that from the colouring of the text.
That's got that resolved...now to find the next problem... LOL
|
|
|
|
|
Joined: Aug 2004
Posts: 7,168
Hoopy frood
|
|
OP
Hoopy frood
Joined: Aug 2004
Posts: 7,168 |
*I hate doing this* The following code works with a single repeating exception. The text from the notices still shows in my status window #rkb.cc.op.check off
on ^*:notice:*list for*:*:{
if sop isin $1- || aop isin $1- || vop isin $1- || hop isin $1- {
set %op $v1
}
unset $+(%,op,.,%op)
.enable #capturelist
haltdef
}
on ^*:notice:*End of List*:*:{
.disable #capturelist
haltdef
}
#rkb.cc.op.check end
#capturelist off
on ^*:notice:*:*:{
if $1 isnum {
set $+(%,op,.,%op) $addtok($($+(%,op,.,%op),2),$2,32)
}
haltdef
}
#capturelist end
|
|
|
|
|
Joined: Oct 2005
Posts: 1,671
Hoopy frood
|
|
Hoopy frood
Joined: Oct 2005
Posts: 1,671 |
Assuming that the necessary groups are being enabled at the correct times, my best guess is that another script is echo'ing the lines to your screen. You could try using the $halted identifier to see if a script has already halted the default text and replaced it with custom text.
-genius_at_work
|
|
|
|
|
Joined: Aug 2004
Posts: 7,168
Hoopy frood
|
|
OP
Hoopy frood
Joined: Aug 2004
Posts: 7,168 |
I'll give it a try, but I don't think so, as the display is the standard format for that type when normally called, additionally I rarely have information echoed to the status window, where this is, since in 6.17 I was using a script that hid the status windows.
|
|
|
|
|
Joined: Aug 2004
Posts: 7,168
Hoopy frood
|
|
OP
Hoopy frood
Joined: Aug 2004
Posts: 7,168 |
I wasn't able to decide where the $halted identifier should go, so I unloaded all the rest of my scripts, and tried again, with no difference.
|
|
|
|
|
Joined: Aug 2004
Posts: 7,168
Hoopy frood
|
|
OP
Hoopy frood
Joined: Aug 2004
Posts: 7,168 |
Got it. The group was being disabled too quickly.
|
|
|
|
|
