Skip to content
MSN

haltdef and halt

A TG007 community discussion started by DreaM.

Discussion 3 posts
Page 1 of 1
Open
Topic #2712 · 3 published posts · 511 views

hi all, when do I need to use haltdef and halt??

 

for ctcps should I use haltdef | return ??

for ^*:text: should I use haltdef | return too or only halt ??

Please i want to know all cases and not only text: or ctcpreply.

 

any help ?

Halting default text

 

mIRC displays its own default text for various types of IRC Server events, such as users joining or parting a channel, however you can modify or suppress this by using a script.

 

The ^ event prefix

You can prevent the default text for an event from being shown by using the ^ prefix in an event definition. This allows you to show your own custom event messages.

 

on ^1:JOIN:#:echo $chan Joins: $nick | halt

 

This line is triggered by a JOIN event and shows your own custom join event message, /halt prevents the normal message from being shown.

 

The ^ events don't replace your existing events; your normal events are independent and are still processed whether there is a ^ event in a script or not.

 

If you only want to halt the default text without /halting the entire script, you can use the /haltdef command.

 

You can check if a script has already halted the default text by using the $halted identifier; it returns $true if a user has used /halt or /haltdef in a ^ event, and $false if not.

 

The ^ event prefix currently works only on the following types of events: ACTION, BAN, CHAT, DEHELP, DEOP, DEVOICE, HELP, INVITE, JOIN, KICK, MODE, NICK, NOTICE, OP, OPEN, PART, PING, TEXT, UNBAN, USERMODE, VOICE, QUIT, SERV, SERVERMODE, SNOTICE, TOPIC, WALLOPS.

 

Note: Halting the default text for an event affects how mIRC displays the most basic information about IRC events to a user, so it should be used carefully.

 

thank you cleric