How do I customize mIRC's own output - Revision history

Vliedel: fixed link

2008-09-29T18:17:39Z

fixed link

← Older revision		Revision as of 18:17, 29 September 2008
Line 35:		Line 35:
	Now, let's use $nick($chan,$nick).pnick, instead of plain $nick to include the prefix in nick. The pnick property returns the nickname in a .@%+nick format. It includes the prefixes in front of the nick.		Now, let's use $nick($chan,$nick).pnick, instead of plain $nick to include the prefix in nick. The pnick property returns the nickname in a .@%+nick format. It includes the prefixes in front of the nick.

	Now we can start editing the output. [[$+]] combines parameters, so "a $+ b" would return "ab" and ( $+ $nick $+ ) returns ($nick) and so on.		Now we can start editing the output. [[DollarPlus\|$+]] combines parameters, so "a $+ b" would return "ab" and ( $+ $nick $+ ) returns ($nick) and so on.

	on ^:TEXT::#:{		on ^:TEXT::#:{

Cail: changed link target from wildcardmatch -> If

2006-10-22T15:14:42Z

changed link target from wildcardmatch -> If

← Older revision		Revision as of 15:14, 22 October 2006
Line 4:		Line 4:
	on <level>:TEXT:<matchtext>:<*><?><#[,#]>:<commands>		on <level>:TEXT:<matchtext>:<*><?><#[,#]>:<commands>

	See how it works. <level> matches for [[Access_Levels\|userlevel]] what is specified for [[$nick]]. * is [[wildcardmatch]] for all levels (named, general) what also means for all users, what's also that we should use. <matchtext> is the text what [[:Category:Events\|event]] should trigger on - otherwords, when matchtext is in part of string event is triggered. Again, wildcardmatch to trigger for any text is the perfect match. Last we must specify the window where event should be enabled. # matches for all channel windows and that's good enough for us.		See how it works. <level> matches for [[Access_Levels\|userlevel]] what is specified for [[$nick]]. * is [[If\|wildcardmatch]] for all levels (named, general) what also means for all users, what's also that we should use. <matchtext> is the text what [[:Category:Events\|event]] should trigger on - otherwords, when matchtext is in part of string event is triggered. Again, wildcardmatch to trigger for any text is the perfect match. Last we must specify the window where event should be enabled. # matches for all channel windows and that's good enough for us.

	on :TEXT::#:{ }		on :TEXT::#:{ }

Cail: Changed $replace($nick($chan,$me).pnick,@+,+) -> $replace($nick($chan,$me).pnick,@+,@)

2006-09-18T16:24:06Z

Changed $replace($nick($chan,$me).pnick,@+,+) -> $replace($nick($chan,$me).pnick,@+,@)

← Older revision		Revision as of 16:24, 18 September 2006
Line 61:		Line 61:
	on *:input:#:{		on *:input:#:{
	if (!$ctrlenter) && ($left($1,1) !== $readini(mirc.ini,text,commandchar)) {		if (!$ctrlenter) && ($left($1,1) !== $readini(mirc.ini,text,commandchar)) {
	echo -lmt $chan ( $+ $replace($nick($chan,$me).pnick,@+,+) $+ ) $1-		echo -lmt $chan ( $+ $replace($nick($chan,$me).pnick,@+,@) $+ ) $1-
	.msg $chan $1-		.msg $chan $1-
	halt		halt

Doomie: its Access_Levels not Userlevels (i think :S)

2005-11-23T15:23:24Z

its Access_Levels not Userlevels (i think :S)

← Older revision		Revision as of 15:23, 23 November 2005
Line 4:		Line 4:
	on <level>:TEXT:<matchtext>:<*><?><#[,#]>:<commands>		on <level>:TEXT:<matchtext>:<*><?><#[,#]>:<commands>

	See how it works. <level> matches for [[~~Userlevels~~\|userlevel]] what is specified for [[$nick]]. * is [[wildcardmatch]] for all levels (named, general) what also means for all users, what's also that we should use. <matchtext> is the text what [[:Category:Events\|event]] should trigger on - otherwords, when matchtext is in part of string event is triggered. Again, wildcardmatch to trigger for any text is the perfect match. Last we must specify the window where event should be enabled. # matches for all channel windows and that's good enough for us.		See how it works. <level> matches for [[Access_Levels\|userlevel]] what is specified for [[$nick]]. * is [[wildcardmatch]] for all levels (named, general) what also means for all users, what's also that we should use. <matchtext> is the text what [[:Category:Events\|event]] should trigger on - otherwords, when matchtext is in part of string event is triggered. Again, wildcardmatch to trigger for any text is the perfect match. Last we must specify the window where event should be enabled. # matches for all channel windows and that's good enough for us.

	on :TEXT::#:{ }		on :TEXT::#:{ }

Doomie: tweaked

2005-11-23T14:54:52Z

tweaked

← Older revision		Revision as of 14:54, 23 November 2005
Line 35:		Line 35:
	Now, let's use $nick($chan,$nick).pnick, instead of plain $nick to include the prefix in nick. The pnick property returns the nickname in a .@%+nick format. It includes the prefixes in front of the nick.		Now, let's use $nick($chan,$nick).pnick, instead of plain $nick to include the prefix in nick. The pnick property returns the nickname in a .@%+nick format. It includes the prefixes in front of the nick.

	Now we can start editing the output. [[$+]] combines parameters ~~between each item~~, so "a $+ b" would return "ab" and ( $+ $nick $+ ) returns to ($nick) and so on.		Now we can start editing the output. [[$+]] combines parameters, so "a $+ b" would return "ab" and ( $+ $nick $+ ) returns ($nick) and so on.

	on ^:TEXT::#:{		on ^:TEXT::#:{
Line 41:		Line 41:
	}		}

	What we've done ~~this~~ far, only effects to text ~~what~~ is sent by other people and not ~~your~~ by yourself. If you wanna change the look of your own input you should do the following.		What we've done so far only effects text that is sent by other people and not by yourself. If you wanna change the look of your own input you should do the following.

	First what we need is [[On_input\|on INPUT]] -event to trigger to your own text.		First what we need is [[On_input\|on INPUT]] -event to trigger to your own text.
Line 52:		Line 52:

	$ctrlenter = Identifier to test whether Control+Enter was pressed when the user entered the text.		$ctrlenter = Identifier to test whether Control+Enter was pressed when the user entered the text.
	($left($1,1) !== $readini(mirc.ini,text,commandchar)) = Returns to user specified command prefix from mirc.ini. In other words that we ain't typinc /command. By default is's set to slash "/".
			($left($1,1) !== $readini(mirc.ini,text,commandchar)) = Returns the user specified command prefix from mirc.ini. In other words that we ain't typinc /command. By default it's set to slash "/".

	Because on INPUT it isn't default event use halt instead of haltdef.		Because on INPUT it isn't default event use halt instead of haltdef.
Line 66:		Line 67:
	}		}

	And that's all you need to know how to customize mIRC's ~~own~~ output. Next step is to be creative, use your imagination; use colors, bolds and underlines variations - what looks the best for your eye.		And that's all you need to know how to customize mIRC's output. Next step is to be creative, use your imagination; use colors, bolds and underlines variations - what looks the best for your eye.

	[[Category:Tutorials]]		[[Category:Tutorials]]
	{{Author\|Tovrleaf}}		{{Author\|Tovrleaf}}

Doomie: changed a link

2005-11-23T14:49:36Z

changed a link

New page

== How to replace the <>'s around nicknames with eg. ()'s? ==

First what we'll need is [[On_text|on TEXT]] -event.
on <level>:TEXT:<matchtext>:<*><?><#[,#]>:<commands>

See how it works. <level> matches for [[Userlevels|userlevel]] what is specified for [[$nick]]. * is [[wildcardmatch]] for all levels (named, general) what also means for all users, what's also that we should use. <matchtext> is the text what [[:Category:Events|event]] should trigger on - otherwords, when matchtext is in part of string event is triggered. Again, wildcardmatch to trigger for any text is the perfect match. Last we must specify the window where event should be enabled. # matches for all channel windows and that's good enough for us.

on *:TEXT:*:#:{ }

Next, we must [[haltdef|halt default text event]] to insert our own output for channel. "^" before a level prefix makes event haltable. When default event is haltable it can be halted with using "[[haltdef]]".

on ^*:TEXT:*:#:{ haltdef }

What does this script do? Literally - nothing. It halts the default text event and leaves it like that. Nothing is sent out. Now, let's add our own customised output by using command "[[echo]]".

/echo [color] [-cdeghiNtsaqlbfnmr] [color name] [#channel|[=]nick]

The syntax is kinda confusing. But don't panic. Switches we need are: echo -lmt [[$chan]] [[$nick]] [[$1-]]

Following has been copy pasted from mIRC's own help file:
l = switch makes it apply the highlight settings to the line that's displayed.
$1- = you can use $N- to refer to parameters N and onwards, and
m = switch indicates that the line should be treated as a user message, not an event.
t = switch prefixes the line with a timestamp if global time stamping is on or timestamping is on for that window.

Rest of syntax can be found from [[mIRC]]'s help file, these are the only ones we need for handling this event so I'll leave the rest of it for your own time.

$N-M to refer to parameters $N through to $M. So to refer to a whole line, you would use $1-.

$nick = Returns the nickname of the user associated with an event.
$chan = Returns the name of the channel for a specific event.

on ^*:TEXT:*:#:{ echo -lmt $chan $nick $1- | haltdef }

Now, let's use $nick($chan,$nick).pnick, instead of plain $nick to include the prefix in nick. The pnick property returns the nickname in a .@%+nick format. It includes the prefixes in front of the nick.

Now we can start editing the output. [[$+]] combines parameters between each item, so "a $+ b" would return "ab" and ( $+ $nick $+ ) returns to ($nick) and so on.

on ^*:TEXT:*:#:{
echo -lmt $chan ( $+ $nick($chan,$nick).pnick $+ ) $1- | haltdef
}

What we've done this far, only effects to text what is sent by other people and not your by yourself. If you wanna change the look of your own input you should do the following.

First what we need is [[On_input|on INPUT]] -event to trigger to your own text.
on <level>:INPUT:<*#?=!@>:<commands>

The syntax is kinda same as on TEXT -event's syntax.

To prevent halting anything else than straight output, we should check that user or in this case you, ain't trying to execute a command:
if (![[$ctrlenter]]) && ([[$left]]($1,1) !== [[$readini]](mirc.ini,text,commandchar))

$ctrlenter = Identifier to test whether Control+Enter was pressed when the user entered the text.
($left($1,1) !== $readini(mirc.ini,text,commandchar)) = Returns to user specified command prefix from mirc.ini. In other words that we ain't typinc /command. By default is's set to slash "/".

Because on INPUT it isn't default event use halt instead of haltdef.

Now, use echo to echo text to channel same way we used it with on TEXT -event. Difference is now that we have to send data to server, instead of only receiving it. Dot in front of command makes the command "silent". So the command is actually executed but not to displayed on your screen, ex. "/.msg $nick hello how are you".

on *:input:#:{
if (!$ctrlenter) && ($left($1,1) !== $readini(mirc.ini,text,commandchar)) {
echo -lmt $chan ( $+ $replace($nick($chan,$me).pnick,@+,+) $+ ) $1-
.msg $chan $1-
halt
}
}

And that's all you need to know how to customize mIRC's own output. Next step is to be creative, use your imagination; use colors, bolds and underlines variations - what looks the best for your eye.

[[Category:Tutorials]]
{{Author|Tovrleaf}}

Tovrleaf at 12:04, 24 August 2005

2005-08-24T12:04:24Z

New page

== How to replace the <>'s around nicknames with eg. ()'s? ==

First what we'll need is [[On_text|on TEXT]] -event.
on <level>:TEXT:<matchtext>:<*><?><#[,#]>:<commands>

See how it works. <level> matches for [[Userlevels|userlevel]] what is specified for [[$nick]]. * is [[wildcardmatch]] for all levels (named, general) what also means for all users, what's also that we should use. <matchtext> is the text what [[:Category:Events|event]] should trigger on - otherwords, when matchtext is in part of string event is triggered. Again, wildcardmatch to trigger for any text is the perfect match. Last we must specify the window where event should be enabled. # matches for all channel windows and that's good enough for us.

on *:TEXT:*:#:{ }

Next, we must [[Halting default event|halt default text event]] to insert our own output for channel. "^" before a level prefix makes event haltable. When default event is haltable it can be halted with using "[[haltdef]]".

on ^*:TEXT:*:#:{ haltdef }

What does this script do? Literally - nothing. It halts the default text event and leaves it like that. Nothing is sent out. Now, let's add our own customised output by using command "[[echo]]".

/echo [color] [-cdeghiNtsaqlbfnmr] [color name] [#channel|[=]nick]

The syntax is kinda confusing. But don't panic. Switches we need are: echo -lmt [[$chan]] [[$nick]] [[$1-]]

Following has been copy pasted from mIRC's own help file:
l = switch makes it apply the highlight settings to the line that's displayed.
$1- = you can use $N- to refer to parameters N and onwards, and
m = switch indicates that the line should be treated as a user message, not an event.
t = switch prefixes the line with a timestamp if global time stamping is on or timestamping is on for that window.

Rest of syntax can be found from [[mIRC]]'s help file, these are the only ones we need for handling this event so I'll leave the rest of it for your own time.

$N-M to refer to parameters $N through to $M. So to refer to a whole line, you would use $1-.

$nick = Returns the nickname of the user associated with an event.
$chan = Returns the name of the channel for a specific event.

on ^*:TEXT:*:#:{ echo -lmt $chan $nick $1- | haltdef }

Now, let's use $nick($chan,$nick).pnick, instead of plain $nick to include the prefix in nick. The pnick property returns the nickname in a .@%+nick format. It includes the prefixes in front of the nick.

Now we can start editing the output. [[$+]] combines parameters between each item, so "a $+ b" would return "ab" and ( $+ $nick $+ ) returns to ($nick) and so on.

on ^*:TEXT:*:#:{
echo -lmt $chan ( $+ $nick($chan,$nick).pnick $+ ) $1- | haltdef
}

What we've done this far, only effects to text what is sent by other people and not your by yourself. If you wanna change the look of your own input you should do the following.

First what we need is [[On_input|on INPUT]] -event to trigger to your own text.
on <level>:INPUT:<*#?=!@>:<commands>

The syntax is kinda same as on TEXT -event's syntax.

To prevent halting anything else than straight output, we should check that user or in this case you, ain't trying to execute a command:
if (![[$ctrlenter]]) && ([[$left]]($1,1) !== [[$readini]](mirc.ini,text,commandchar))

$ctrlenter = Identifier to test whether Control+Enter was pressed when the user entered the text.
($left($1,1) !== $readini(mirc.ini,text,commandchar)) = Returns to user specified command prefix from mirc.ini. In other words that we ain't typinc /command. By default is's set to slash "/".

Because on INPUT it isn't default event use halt instead of haltdef.

Now, use echo to echo text to channel same way we used it with on TEXT -event. Difference is now that we have to send data to server, instead of only receiving it. Dot in front of command makes the command "silent". So the command is actually executed but not to displayed on your screen, ex. "/.msg $nick hello how are you".

on *:input:#:{
if (!$ctrlenter) && ($left($1,1) !== $readini(mirc.ini,text,commandchar)) {
echo -lmt $chan ( $+ $replace($nick($chan,$me).pnick,@+,+) $+ ) $1-
.msg $chan $1-
halt
}
}

And that's all you need to know how to customize mIRC's own output. Next step is to be creative, use your imagination; use colors, bolds and underlines variations - what looks the best for your eye.

[[Category:Tutorials]]