How do I reop or unban myself - Revision history

Saturn: typo, thanks FIQ

2011-01-01T14:16:34Z

typo, thanks FIQ

← Older revision		Revision as of 14:16, 1 January 2011
Line 28:		Line 28:
	You might have seen the { } format before. Inside those, we can list as many commands as we want. Let's say your channel has [[Q]]. One of the commands we need would be: ''msg Q op #mychan''. Instead of #mychan, we can use another identifier. [[$chan]] returns the channel all this happens on, so let's change the command to ''msg Q op $chan''. This way you can use the same command for more than 1 channel.		You might have seen the { } format before. Inside those, we can list as many commands as we want. Let's say your channel has [[Q]]. One of the commands we need would be: ''msg Q op #mychan''. Instead of #mychan, we can use another identifier. [[$chan]] returns the channel all this happens on, so let's change the command to ''msg Q op $chan''. This way you can use the same command for more than 1 channel.

	Now we have another problem. If we'd use on 1:OP:#mychan:{ msg Q op $chan }, it would send the message if someone else gets deopped too. That's why we're gonna limit it using an [[If-Then-Else\|if-statement]]. The if-statement basically checks something. If what it checks is true, it executes some commands. If not, it either does nothing or goes to an else part. For now we won't use else parts.		Now we have another problem. If we'd use on 1:DEOP:#mychan:{ msg Q op $chan }, it would send the message if someone else gets deopped too. That's why we're gonna limit it using an [[If-Then-Else\|if-statement]]. The if-statement basically checks something. If what it checks is true, it executes some commands. If not, it either does nothing or goes to an else part. For now we won't use else parts.

	What we wanted to check was if it was you who got deopped. As the help on the [[On_op\|op]]/[[On_deop\|deop]] event says, [[$opnick]] returns the person/nick who get's opped/deopped in those events. We'll need to use another identifier: $me. $me simply returns your own nickname. The if-statement we need would become ''if ($opnick == $me) { commands }''. The == is an operator meaning 'equal to' and that's exactly what we want: "if (the person who gets deopped is equal to myself)"		What we wanted to check was if it was you who got deopped. As the help on the [[On_op\|op]]/[[On_deop\|deop]] event says, [[$opnick]] returns the person/nick who get's opped/deopped in those events. We'll need to use another identifier: $me. $me simply returns your own nickname. The if-statement we need would become ''if ($opnick == $me) { commands }''. The == is an operator meaning 'equal to' and that's exactly what we want: "if (the person who gets deopped is equal to myself)"

Albie: replaced L with Q

2008-04-06T21:24:57Z

replaced L with Q

← Older revision		Revision as of 21:24, 6 April 2008
Line 1:		Line 1:
	This tutorial will help you create a script that gives you some basic protection. Whenever someone deops you in your channel, it will automatically ask ~~[[L]] or~~ [[Q]] to reop you again. Also, when someone bans you, it will attempt to unban you again. Difficulty: easy		This tutorial will help you create a script that gives you some basic protection. Whenever someone deops you in your channel, it will automatically ask [[Q]] to reop you again. Also, when someone bans you, it will attempt to unban you again. Difficulty: easy

	First we'll look at how [[mIRC]] scripting actually handles these things. Whenever something happens (a message, a mode change, a kick and so on), your script can react to this. What you need are the so called [[:Category:remote\|remote]] [[:Category:Events\|events]]. You can read more about them by typing /help remote in a mIRC window. I suggest you do that right now.		First we'll look at how [[mIRC]] scripting actually handles these things. Whenever something happens (a message, a mode change, a kick and so on), your script can react to this. What you need are the so called [[:Category:remote\|remote]] [[:Category:Events\|events]]. You can read more about them by typing /help remote in a mIRC window. I suggest you do that right now.

Albie: replaced L with Q

2008-04-06T21:24:08Z

replaced L with Q

← Older revision		Revision as of 21:24, 6 April 2008
Line 26:		Line 26:
	}		}

	You might have seen the { } format before. Inside those, we can list as many commands as we want. Let's say your channel has [[L]]. One of the commands we need would be: ''msg L op #mychan''. Instead of #mychan, we can use another identifier. [[$chan]] returns the channel all this happens on, so let's change the command to ''msg L op $chan''. This way you can use the same command for more than 1 channel.		You might have seen the { } format before. Inside those, we can list as many commands as we want. Let's say your channel has [[Q]]. One of the commands we need would be: ''msg Q op #mychan''. Instead of #mychan, we can use another identifier. [[$chan]] returns the channel all this happens on, so let's change the command to ''msg Q op $chan''. This way you can use the same command for more than 1 channel.

	Now we have another problem. If we'd use on 1:OP:#mychan:{ msg L op $chan }, it would send the message if someone else gets deopped too. That's why we're gonna limit it using an [[If-Then-Else\|if-statement]]. The if-statement basically checks something. If what it checks is true, it executes some commands. If not, it either does nothing or goes to an else part. For now we won't use else parts.		Now we have another problem. If we'd use on 1:OP:#mychan:{ msg Q op $chan }, it would send the message if someone else gets deopped too. That's why we're gonna limit it using an [[If-Then-Else\|if-statement]]. The if-statement basically checks something. If what it checks is true, it executes some commands. If not, it either does nothing or goes to an else part. For now we won't use else parts.

	What we wanted to check was if it was you who got deopped. As the help on the [[On_op\|op]]/[[On_deop\|deop]] event says, [[$opnick]] returns the person/nick who get's opped/deopped in those events. We'll need to use another identifier: $me. $me simply returns your own nickname. The if-statement we need would become ''if ($opnick == $me) { commands }''. The == is an operator meaning 'equal to' and that's exactly what we want: "if (the person who gets deopped is equal to myself)"		What we wanted to check was if it was you who got deopped. As the help on the [[On_op\|op]]/[[On_deop\|deop]] event says, [[$opnick]] returns the person/nick who get's opped/deopped in those events. We'll need to use another identifier: $me. $me simply returns your own nickname. The if-statement we need would become ''if ($opnick == $me) { commands }''. The == is an operator meaning 'equal to' and that's exactly what we want: "if (the person who gets deopped is equal to myself)"
Line 36:		Line 36:
	on 1:DEOP:#mychannel:{		on 1:DEOP:#mychannel:{
	if ($opnick == $me) {		if ($opnick == $me) {
	msg L op $chan		msg Q op $chan
	}		}
	}		}

	This will do what we need. If you get deopped on your channel, it will ask L to reop you. Have a look at the spaces in front of some of the lines. mIRC automatically adds them when you click OK or the { } button in the remote dialog. The { } button is really useful, because it lets mIRC check if you have placed the { and } brackets correctly. When you'll write bigger scripts, you'll start using it a lot.		This will do what we need. If you get deopped on your channel, it will ask Q to reop you. Have a look at the spaces in front of some of the lines. mIRC automatically adds them when you click OK or the { } button in the remote dialog. The { } button is really useful, because it lets mIRC check if you have placed the { and } brackets correctly. When you'll write bigger scripts, you'll start using it a lot.

	We'll now create another event. We want it to unban you whenever you get banned on your channel. Let's start with having a look at what actually happens. When someone bans, he sets a banmask, for example !milk@.cows.net. This mask contains wildcards, which means it bans dynamically. A wildcard, *, can be replaced by anything: bill!milk@white.cows.net will for example be banned.		We'll now create another event. We want it to unban you whenever you get banned on your channel. Let's start with having a look at what actually happens. When someone bans, he sets a banmask, for example !milk@.cows.net. This mask contains wildcards, which means it bans dynamically. A wildcard, *, can be replaced by anything: bill!milk@white.cows.net will for example be banned.

Albie: changed iswm link

2005-11-30T13:12:22Z

changed iswm link

← Older revision		Revision as of 13:12, 30 November 2005
Line 58:		Line 58:
	If we want your full address, we can use [[$address]]($me,5) or [[$ial]]([[$me]]). (Again, click the identifiers mentioned for more detailed information on what they can do.)		If we want your full address, we can use [[$address]]($me,5) or [[$ial]]([[$me]]). (Again, click the identifiers mentioned for more detailed information on what they can do.)

	We only used the == operator in if-statements until now. Now have a look at the [[~~Iswm~~\|iswm]] operator. It literally means is wildcard match. ''if (ac iswm abc)'' would be true, ''if (ac iswm abc)'' wouldn't.		We only used the == operator in if-statements until now. Now have a look at the [[If-Then-Else#The_Operators\|iswm]] operator. It literally means is wildcard match. ''if (ac iswm abc)'' would be true, ''if (ac iswm abc)'' wouldn't.

	Now, we can use this to check if the banmask matches your address; to check if 'you are banned':		Now, we can use this to check if the banmask matches your address; to check if 'you are banned':

Doomie: its Access Levels not Userlevels

2005-11-24T21:03:22Z

its Access Levels not Userlevels

← Older revision		Revision as of 21:03, 24 November 2005
Line 73:		Line 73:

	- [[Kick]] someone who deops your friend		- [[Kick]] someone who deops your friend
	- Only allow people with [[~~Userlevels~~\|level]] 20 or higher to [[ban]]		- Only allow people with [[Access Levels\|level]] 20 or higher to [[ban]]

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

Doomie: access levels not userlevels

2005-11-23T15:26:52Z

access levels not userlevels

← Older revision		Revision as of 15:26, 23 November 2005
Line 14:		Line 14:
	(on OP and on DEOP events work in a similar way.)		(on OP and on DEOP events work in a similar way.)

	The ''1'' in the example is a [[~~Userlevels~~\|userlevel]]. Userlevel 1 means the event always triggers, no matter what level the deop'ing user has, as mIRC per default assigns all users with level 1. The ''#mirc,#irchelp'' are obvioulsy channels the event should work for. Finally, the ''/msg $nick Please don't...'' part is the command that should be executed. ''$nick'' is an identifier. It returns something. If fishbot would have done the op, then mIRC would read the line as /msg fishbot Please don't... In words:		The ''1'' in the example is a [[Access Levels\|userlevel]]. Userlevel 1 means the event always triggers, no matter what level the deop'ing user has, as mIRC per default assigns all users with level 1. The ''#mirc,#irchelp'' are obvioulsy channels the event should work for. Finally, the ''/msg $nick Please don't...'' part is the command that should be executed. ''$nick'' is an identifier. It returns something. If fishbot would have done the op, then mIRC would read the line as /msg fishbot Please don't... In words:

	If someone with level 1 or higher (everyone) ops someone in #mirc or #irchelp, message him with Please don't abuse your Op status.		If someone with level 1 or higher (everyone) ops someone in #mirc or #irchelp, message him with Please don't abuse your Op status.

Zyberdog: added links, changed /help refering to wiki-refering.

2005-11-22T16:49:58Z

added links, changed /help refering to wiki-refering.

New page

This tutorial will help you create a script that gives you some basic protection. Whenever someone deops you in your channel, it will automatically ask [[L]] or [[Q]] to reop you again. Also, when someone bans you, it will attempt to unban you again. Difficulty: easy

First we'll look at how [[mIRC]] scripting actually handles these things. Whenever something happens (a message, a mode change, a kick and so on), your script can react to this. What you need are the so called [[:Category:remote|remote]] [[:Category:Events|events]]. You can read more about them by typing /help remote in a mIRC window. I suggest you do that right now.

As you can see, the helpfile recommends you read through documents on [[:Category:Commands|Commands]], [[:Category:Aliases|Aliases]], [[:Category:Variables|Variables]] and [[:Category:Identifiers|Identifiers]]. Although it is always a good idea to do so, you might not fully understand what they do and how they work, so understanding all this is not required for this tutorial.

Besides this, you'll see two other things in the help file. One is a list with events, the other is a note at the end: Note: You should never load or use a script that you don't understand. Whatever you do, keep this in mind! Lots of users have their Q accounts compromised and other data lost, just because they run a false script.

Back to our problem. We want to get our ops back when someone removes it, so the event we need is the DeOp event. Click on it in the list. The [[On_op|on OP]] and [[On_deop|on DEOP]] events trigger when a user on a channel is opped or deopped. Sound like it's exactly what we need. Have a look at the format and the example below it:

Format: on <level>:OP:<#[,#]>:<commands>
Example: on 1:OP:#mirc,#irchelp:/[[msg]] [[$nick]] Please don't abuse your Op status

(on OP and on DEOP events work in a similar way.)

The ''1'' in the example is a [[Userlevels|userlevel]]. Userlevel 1 means the event always triggers, no matter what level the deop'ing user has, as mIRC per default assigns all users with level 1. The ''#mirc,#irchelp'' are obvioulsy channels the event should work for. Finally, the ''/msg $nick Please don't...'' part is the command that should be executed. ''$nick'' is an identifier. It returns something. If fishbot would have done the op, then mIRC would read the line as /msg fishbot Please don't... In words:

If someone with level 1 or higher (everyone) ops someone in #mirc or #irchelp, message him with Please don't abuse your Op status.

To use such an event, you'll need to paste it in [[:Category:Remote|Remote]]. Go to Tools -> Script editor or hit Alt + R. Should the field not be empty, then go to File and select New. If you'd want to use this event, you'd paste it in the large text field and press OK. For now, just press OK without pasting.

Let's say your channel is #mychannel. As we want this event to work for all userlevels too, we can make the biggest part of the event: on 1:DEOP:#mychannel:/command. The event can trigger more commands too. We're gonna change the format for that a bit:
on 1:DEOP:#mychannel:{
command1
command2
}

You might have seen the { } format before. Inside those, we can list as many commands as we want. Let's say your channel has [[L]]. One of the commands we need would be: ''msg L op #mychan''. Instead of #mychan, we can use another identifier. [[$chan]] returns the channel all this happens on, so let's change the command to ''msg L op $chan''. This way you can use the same command for more than 1 channel.

Now we have another problem. If we'd use on 1:OP:#mychan:{ msg L op $chan }, it would send the message if someone else gets deopped too. That's why we're gonna limit it using an [[If-Then-Else|if-statement]]. The if-statement basically checks something. If what it checks is true, it executes some commands. If not, it either does nothing or goes to an else part. For now we won't use else parts.

What we wanted to check was if it was you who got deopped. As the help on the [[On_op|op]]/[[On_deop|deop]] event says, [[$opnick]] returns the person/nick who get's opped/deopped in those events. We'll need to use another identifier: $me. $me simply returns your own nickname. The if-statement we need would become ''if ($opnick == $me) { commands }''. The == is an operator meaning 'equal to' and that's exactly what we want: "if (the person who gets deopped is equal to myself)"

Now, let's just put the if statement we just made inside the event:

on 1:DEOP:#mychannel:{
if ($opnick == $me) {
msg L op $chan
}
}

This will do what we need. If you get deopped on your channel, it will ask L to reop you. Have a look at the spaces in front of some of the lines. mIRC automatically adds them when you click OK or the { } button in the remote dialog. The { } button is really useful, because it lets mIRC check if you have placed the { and } brackets correctly. When you'll write bigger scripts, you'll start using it a lot.

We'll now create another event. We want it to unban you whenever you get banned on your channel. Let's start with having a look at what actually happens. When someone bans, he sets a banmask, for example *!milk@*.cows.net. This mask contains wildcards, which means it bans dynamically. A wildcard, *, can be replaced by anything: bill!milk@white.cows.net will for example be banned.

With help from the helpfile, we can easily create the following event:

[[On_ban|on @1:BAN]]:#mychannel:{
if ([[$bnick]] == $me) {
mode $chan -b [[$banmask]]
}
}

Click the parts above you don't understand to see more information on them.

This event will work in some cases, but unfortunately by far not in all. ''$bnick'' only works when a nick is specified inside the banmask, like: ''nick!*@*.*''. There is another possibility though.

If we want your full address, we can use [[$address]]($me,5) or [[$ial]]([[$me]]). (Again, click the identifiers mentioned for more detailed information on what they can do.)

We only used the == operator in if-statements until now. Now have a look at the [[Iswm|iswm]] operator. It literally means is wildcard match. ''if (a*c iswm abc)'' would be true, ''if (ac* iswm abc)'' wouldn't.

Now, we can use this to check if the banmask matches your address; to check if 'you are banned':

on @1:BAN:#mychannel:{
if ($banmask iswm $ial($me)) {
mode $chan -b $banmask
}
}

That will do the trick.

When you fully understand how these events work, you should also be able to create events that do these things:

- [[Kick]] someone who deops your friend
- Only allow people with [[Userlevels|level]] 20 or higher to [[ban]]

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

Tovrleaf at 09:11, 25 August 2005

2005-08-25T09:11:04Z

New page

This tutorial will help you create a script that gives you some basic protection. Whenever someone deops you in your channel, it will automatically ask [[L]] or [[Q]] to reop you again. Also, when someone bans you, it will attempt to unban you again. Difficulty: easy

First we'll look at how [[mIRC]] scripting actually handles these things. Whenever something happens (a message, a mode change, a kick and so on), your script can react to this. What you need are the so called [[:Category:remote|remote]] [[:Category:Events|events]]. You can read more about them by typing /help remote in a mIRC window. I suggest you do that right now.

As you can see, the helpfile recommends you read through documents on [[:Category:Commands|Commands]], [[:Category:Aliases|Aliases]], [[:Category:Variables|Variables]] and [[:Category:Identifiers|Identifiers]]. Although it is always a good idea to do so, you might not fully understand what they do and how they work, so understanding all this is not required for this tutorial.

Besides this, you'll see two other things in the help file. One is a list with events, the other is a note at the end: Note: You should never load or use a script that you don't understand. Whatever you do, keep this in mind! Lots of users have their Q accounts compromised and other data lost, just because they run a false script.

Back to our problem. We want to get our ops back when someone removes it, so the event we need is the DeOp event. Click on it in the list. The on OP and [[On_deop|on DEOP]] events trigger when a user on a channel is opped or deopped. Sound like it's exactly what we need. Have a look at the format and the example below it:

Format: on <level>:OP:<#[,#]>:<commands>
Example: on 1:OP:#mirc,#irchelp:/msg $nick Please don't abuse your Op status

([[On_op|On OP]] and on DEOP work in a similar way. The helpfile has only one entry for both of them.)

The 1 in the example is a [[Userlevels|userlevel]]. Userlevel 1 means the event always triggers, no matter what level the deop'ing user has. the #mirc,#irchelp are obvioulsy channels the event should work for. Finally, the /[[msg]] [[$nick]] Please don't... part is the command that should be executed. $nick is an identifier. It returns something. If fishbot would have done the op, then mIRC would read the line as /msg fishbot Please don't... In words:

If someone with level 1 or higher (everyone) ops someone in #mirc or #irchelp, message him with Please don't abuse your Op status.

To use such an event, you'll need to paste it in [[:Category:Remote|Remote]]. Go to Tools -> Script editor or hit Alt + R. Should the field not be empty, then go to File and select New. If you'd want to use this event, you'd paste it in the large text field and press OK. For now, just press OK without pasting.

Let's say your channel is #mychannel. As we want this event to work for all userlevels too, we can make the biggest part of the event: on 1:DEOP:#mychannel:/command. The event can trigger more commands too. We're gonna change the format for that a bit:
on 1:DEOP:#mychannel:{
command1
command2
}

You might have seen the { } format before. Inside those, we can list as many commands as we want. Also, we don't have to use the / character in front of commands. Let's say your channel has [[L]]. One of the commands we need would be: msg L op #mychan Instead of #mychan, we can use another identifier. [[$chan]] returns the channel all this happens on, so let's change the command to msg L op $chan. This way you can use the same command for more than 1 channel.

Now we have another problem. If we'd use on 1:OP:#mychan:{ msg L op $chan }, it would send the message if someone else gets deopped too. That's why we're gonna limit it using an [[If-Then-Else|if]]-statement. Type /help /if now. if (v1 operator v2) { commands } The if-statement basically checks something. If what it checks is true, it executes some commands. If not, it either does nothing or goes to an else part. For now we won't use else parts.

What we wanted to check was if it was you who got deopped. As the help on the op/deop event said (/help on deop), [[$opnick]] returns the person who get's opped/deopped in those events. We'll need to use another identifier: $me. $me simply returns your own nickname. The if-statement we need would become if ($opnick == $me) { commands }. The == is an operator meaning 'equal to' and that's exactly what we want: "if (the person who gets deopped is equal to myself)"

Now, let's just put the if statement we just made inside the event:

on 1:DEOP:#mychannel:{
if ($opnick == $me) {
msg L op $chan
}
}

This will do what we need. If you get deopped on your channel, it will ask L to reop you. Have a look at the spaces in front of each line. mIRC automatically adds them when you click OK or the { } button in the remote dialog. The { } button is really useful, because it lets mIRC check if you have placed the { and } brackets correctly. When you'll write bigger scripts, you'll start using it a lot.

We'll now create another event. We want it to unban you whenever you get banned on your channel. Let's start with having a look at what actually happens. When someone bans, he sets a banmask, for example *!milk@*.cows.net. This mask contains wildcards, which means it bans dynamically. A wildcard, *, can be replaced by anything: bill!milk@white.cows.net will for example be banned.

With help from the helpfile, we can easily create the following event:

on @1:BAN:#mychannel:{
if ($bnick == $me) {
mode $chan -b $banmask
}
}

Use the helpfile if you don't understand parts of the event, just like we used it before. (/help [[on ban]], /help [[prefixes]], /help /[[mode]])

This event will work in some cases, but unfortunately by far not in all. [[$bnick]] only works when a nick is specified inside the banmask, like: nick!*@*.*. There is another possibility though.

If we want your full address, we can use [[$address]]($me,5) or [[$ial]]([[$me]]). (Again, use /help $address or /help $ial if you want more info.)

We only used the == operator in if-statements until now. Now have a look at the iswm operator. It literally means is wildcard match. if (a*c iswm abc) would be true, if (ac* iswm abc) wouldn't.

Now, we can use this to check if the banmask matches your address; to check if 'you are banned':

on @1:BAN:#mychannel:{
if ($banmask iswm $ial($me)) {
mode $chan -b $banmask
}
}

That will do the trick.

When you fully understand how these events work, you should also be able to create events that do these things:

- [[Kick]] someone who deops your friend
- Only allow people with [[Userlevels|level]] 20 or higher to ban

[[Category:Tutorials]]