Access Levels - Revision history

Cail: "See Also" sounds better than "Also See", besides it's like that on other places too

2007-02-26T00:36:56Z

"See Also" sounds better than "Also See", besides it's like that on other places too

← Older revision		Revision as of 00:36, 26 February 2007
Line 115:		Line 115:
	Many of the prefixes and controls are sensitive to numerical order of the definitions. The safest thing is to order your definitions starting with the lowest access levels first and increasing numerically down the list, this makes it easier to keep track of which events should trigger first.		Many of the prefixes and controls are sensitive to numerical order of the definitions. The safest thing is to order your definitions starting with the lowest access levels first and increasing numerically down the list, this makes it easier to keep track of which events should trigger first.

	== Also ~~See~~ ==		== See Also ==
	*[[auser]] ;Used to add a users Access Level.		*[[auser]] ;Used to add a users Access Level.
	*[[guser]] ;This acts the same as auser except it looks up a users ident/host via the server.		*[[guser]] ;This acts the same as auser except it looks up a users ident/host via the server.

Saturn: and other small fixes, more commands need to be anchored here though

2006-04-12T18:35:32Z

and other small fixes, more commands need to be anchored here though

← Older revision		Revision as of 18:35, 12 April 2006
Line 58:		Line 58:
	You can prevent an event from being triggered if it was initiated by you by using the ! prefix.		You can prevent an event from being triggered if it was initiated by you by using the ! prefix.

	on !*:JOIN:#: { echo $chan -t $nick ~~join~~ joined $chan }		on !*:JOIN:#: { echo -tc join $chan $nick joined $chan }
	You would be unable to access the above event regardless of your access level.		You would be unable to access the above event regardless of your access level.

Line 64:		Line 64:
	This prefix is the negate of the ! prefix.		This prefix is the negate of the ! prefix.
	Using me: will only trigger the event if you are the user who triggered the event. For example:		Using me: will only trigger the event if you are the user who triggered the event. For example:
	on me:*:JOIN:#: { ~~...~~ }		on me:*:JOIN:#: { echo -t $chan I joined $chan }
	This is the same as the following code:		This is the same as the following code:
	on *:JOIN:#: { if ($nick == $me) { ~~...~~ } }		on *:JOIN:#: { if ($nick == $me) { echo -t $chan I joined $chan } }
	'''''Note:''''' The fact this is a three character prefix makes no difference than any other prefix.		'''''Note:''''' The fact this is a three character prefix makes no difference than any other prefix.

Saturn: and consistency in spacing around brackets

2006-04-12T18:32:50Z

and consistency in spacing around brackets

← Older revision		Revision as of 18:32, 12 April 2006
Line 64:		Line 64:
	This prefix is the negate of the ! prefix.		This prefix is the negate of the ! prefix.
	Using me: will only trigger the event if you are the user who triggered the event. For example:		Using me: will only trigger the event if you are the user who triggered the event. For example:
	on me:*:JOIN:#:{ ... }		on me:*:JOIN:#: { ... }
	This is the same as the following code:		This is the same as the following code:
	on *:JOIN:#:{ if ($nick == $me) { ... } }		on *:JOIN:#: { if ($nick == $me) { ... } }
	'''''Note:''''' The fact this is a three character prefix makes no difference than any other prefix.		'''''Note:''''' The fact this is a three character prefix makes no difference than any other prefix.

Saturn: and added some consistency in use of #channel

2006-04-12T18:31:47Z

and added some consistency in use of #channel

← Older revision		Revision as of 18:31, 12 April 2006
Line 64:		Line 64:
	This prefix is the negate of the ! prefix.		This prefix is the negate of the ! prefix.
	Using me: will only trigger the event if you are the user who triggered the event. For example:		Using me: will only trigger the event if you are the user who triggered the event. For example:
	on me:*:JOIN:#~~channel~~:{ ... }		on me:*:JOIN:#:{ ... }
	This is the same as the following code:		This is the same as the following code:
	on *:JOIN:#~~channel~~:{ if ($nick == $me) { ... } }		on *:JOIN:#:{ if ($nick == $me) { ... } }
	'''''Note:''''' The fact this is a three character prefix makes no difference than any other prefix.		'''''Note:''''' The fact this is a three character prefix makes no difference than any other prefix.

Saturn: added example to me: prefix

2006-04-12T18:30:56Z

added example to me: prefix

← Older revision		Revision as of 18:30, 12 April 2006
Line 63:		Line 63:
	=== The me: prefix ===		=== The me: prefix ===
	This prefix is the negate of the ! prefix.		This prefix is the negate of the ! prefix.
	Using me: will only trigger the event if you are the user who triggered the event.		Using me: will only trigger the event if you are the user who triggered the event. For example:
	~~It would be~~ the same as ~~using~~ the following code ~~in your event~~:		on me:*:JOIN:#channel:{ ... }
	if ($nick == $me) { ... }		This is the same as the following code:
			on *:JOIN:#channel:{ if ($nick == $me) { ... } }
	'''''Note:''''' The fact this is a three character prefix makes no difference than any other prefix.		'''''Note:''''' The fact this is a three character prefix makes no difference than any other prefix.

Zyberdog: added parent category

2006-02-18T00:48:07Z

added parent category

← Older revision		Revision as of 00:48, 18 February 2006
Line 121:		Line 121:
	*[[rlevel]] ;This removes all users from the remote users list with the specified general access level.		*[[rlevel]] ;This removes all users from the remote users list with the specified general access level.
	*[[ulist]] ;This lists users which have the specified access levels.		*[[ulist]] ;This lists users which have the specified access levels.

			[[Category:MIRC Help]]

Albie: changed some stuff around reworded me:

2006-01-28T18:49:03Z

changed some stuff around reworded me:

@@ Line 39: / Line 39: @@
 This treats the word friend as a specific access level and matches the user with the event, and because the user is your friend, you welcome them.
 == Prefixes ==
@@ Line 51: / Line 54: @@
 The above user can't access this ctcp event even though he has an access level higher than 5, because the event is limited only to level 5 users.
 === The ! prefix ===
@@ Line 71: / Line 60: @@
   on !*:JOIN:#: { echo $chan -t $nick join joined $chan }
 You would be unable to access the above event regardless of your access level.
 === The @ prefix ===

Albie at 17:08, 27 January 2006

2006-01-27T17:08:24Z

← Older revision		Revision as of 17:08, 27 January 2006
Line 125:		Line 125:
	*[[rlevel]] ;This removes all users from the remote users list with the specified general access level.		*[[rlevel]] ;This removes all users from the remote users list with the specified general access level.
	*[[ulist]] ;This lists users which have the specified access levels.		*[[ulist]] ;This lists users which have the specified access levels.

	~~== NOTES ==~~
	~~[16:47] <@Saturn> how did the writer of that note come to that conclusion?~~
	~~[16:47] <@Saturn> i'm using a script that uses on me:^*:..~~
	~~[16:51] <@Albie> i copied it out of the help file~~
	~~[16:52] <@Saturn> huh? me: isn't documented~~
	~~[16:52] <@Albie> ah well i have teazles~~
	~~[16:58] <@Microbe> This will combine the * prefix for everyone and the me: prefix, you could assign a bot a userlevel that has the same host as yourself if you only want to trigger certain users.~~
	~~[16:58] <@Microbe> I really can't understand that :)~~
	[16:59] <@Microbe> and there's no explanation still of why there is that 'extra' :*
	~~[16:59] <@Saturn> extra :* ?~~
	~~[16:59] <@Microbe> on me:*:JOIN:#: { echo -s I just joined $chan }~~
	[16:59] <@Microbe> I can't help but considering that as 'extra' :*
	[16:59] <@Albie> only an extra *
	~~[16:59] <@Saturn> so you're still not convinced~~
	~~[16:59] <@Microbe> no matter how you try to convince me :)~~
	[16:59] <@Saturn> there is no extra :*
	~~[17:00] <@Saturn> on ^*:JOIN:#: { echo -s I just joined $chan }~~
	~~[17:00] <@Saturn> is there an extra :* there ?~~
	~~[17:00] <@Microbe> well if I don't understand it, normal users will definately not understand it either~~
	~~[17:00] <@Saturn> answer the question :p~~
	~~[17:00] <@Microbe> no there isn't :)~~
	~~[17:00] <@Saturn> ok, now substitute "me:" for "^"~~
	~~[17:01] <@Microbe> ok, extra ":" then~~
	~~[17:01] <@Saturn> substitute "me:" for "^"~~
	~~[17:01] <@Albie> me: is the prefix, not me~~
	~~[17:01] <@Albie> ..~~
	~~[17:01] <@Saturn> those three characters~~
	~~[17:01] <@Microbe> the prefix MAKES NO SENSE TO ME :)~~
	~~[17:01] <@Microbe> as all other prefixes are like !~~
	~~[17:02] <@Microbe> not !:~~
	~~[17:02] <@Albie> maybe thats why its undocumented, so people who dont understand it, wont use it ;p~~
	~~[17:02] <@Saturn> none of the other prefixes contain text, either~~
	~~[17:02] <@Saturn> just look at it as the prefix "me:" and it all makes sense~~
	~~[17:02] <@Saturn> why the prefix is "me:" is another issue~~
	~~[17:03] <@Microbe> well, imo the main point is not to think of it as a user level~~
	~~[17:03] <@Saturn> it sure looks better than "on me*:text:.." anyway~~
	~~[17:03] <@Microbe> what would be the point of me*: ?~~
	~~[17:03] <@Saturn> that would be the prefix "me" instead of "me:"~~
	~~[17:03] <@Albie> :f~~
	~~[17:03] <@Microbe> "me and everyone whose nick is me*" ?~~
	~~[17:03] <@Albie> no because~~
	~~[17:03] <@Saturn> on !*:text~~
	~~[17:03] <@Saturn> on me*:text~~
	~~[17:03] <@Albie> me: is only a host match~~
	~~[17:03] <@Saturn> see? that totally doesnt make sense~~
	~~[17:03] <@Albie> using me: is not the same as if ($me == $nick)~~
	~~[17:04] <@Saturn> it gets worse when you use named userlevels~~
	~~[17:04] <@Saturn> on mefriend:text~~
	~~[17:04] <@Saturn> on me:friend:text <-- MUCH better, although completely pointless~~
	~~[17:04] <@Albie> a userlevel called me? ;p~~
	~~[17:04] <@Microbe> can you make it, Albie? :)~~
	~~[17:04] <@Microbe> guess yes~~
	~~[17:04] <@Albie> i should think so~~
	~~[17:04] <@Saturn> see the : as improvement of readability~~
	~~[17:05] <@Microbe> ok, now summarize this to the wiki~~
	~~[17:05] <@Saturn> just copy&paste this log :p~~
	~~[17:05] <@Microbe> ;)~~

Albie at 17:07, 27 January 2006

2006-01-27T17:07:44Z

← Older revision		Revision as of 17:07, 27 January 2006
Line 125:		Line 125:
	*[[rlevel]] ;This removes all users from the remote users list with the specified general access level.		*[[rlevel]] ;This removes all users from the remote users list with the specified general access level.
	*[[ulist]] ;This lists users which have the specified access levels.		*[[ulist]] ;This lists users which have the specified access levels.

			== NOTES ==
			[16:47] <@Saturn> how did the writer of that note come to that conclusion?
			[16:47] <@Saturn> i'm using a script that uses on me:^*:..
			[16:51] <@Albie> i copied it out of the help file
			[16:52] <@Saturn> huh? me: isn't documented
			[16:52] <@Albie> ah well i have teazles
			[16:58] <@Microbe> This will combine the * prefix for everyone and the me: prefix, you could assign a bot a userlevel that has the same host as yourself if you only want to trigger certain users.
			[16:58] <@Microbe> I really can't understand that :)
			[16:59] <@Microbe> and there's no explanation still of why there is that 'extra' :*
			[16:59] <@Saturn> extra :* ?
			[16:59] <@Microbe> on me:*:JOIN:#: { echo -s I just joined $chan }
			[16:59] <@Microbe> I can't help but considering that as 'extra' :*
			[16:59] <@Albie> only an extra *
			[16:59] <@Saturn> so you're still not convinced
			[16:59] <@Microbe> no matter how you try to convince me :)
			[16:59] <@Saturn> there is no extra :*
			[17:00] <@Saturn> on ^*:JOIN:#: { echo -s I just joined $chan }
			[17:00] <@Saturn> is there an extra :* there ?
			[17:00] <@Microbe> well if I don't understand it, normal users will definately not understand it either
			[17:00] <@Saturn> answer the question :p
			[17:00] <@Microbe> no there isn't :)
			[17:00] <@Saturn> ok, now substitute "me:" for "^"
			[17:01] <@Microbe> ok, extra ":" then
			[17:01] <@Saturn> substitute "me:" for "^"
			[17:01] <@Albie> me: is the prefix, not me
			[17:01] <@Albie> ..
			[17:01] <@Saturn> those three characters
			[17:01] <@Microbe> the prefix MAKES NO SENSE TO ME :)
			[17:01] <@Microbe> as all other prefixes are like !
			[17:02] <@Microbe> not !:
			[17:02] <@Albie> maybe thats why its undocumented, so people who dont understand it, wont use it ;p
			[17:02] <@Saturn> none of the other prefixes contain text, either
			[17:02] <@Saturn> just look at it as the prefix "me:" and it all makes sense
			[17:02] <@Saturn> why the prefix is "me:" is another issue
			[17:03] <@Microbe> well, imo the main point is not to think of it as a user level
			[17:03] <@Saturn> it sure looks better than "on me*:text:.." anyway
			[17:03] <@Microbe> what would be the point of me*: ?
			[17:03] <@Saturn> that would be the prefix "me" instead of "me:"
			[17:03] <@Albie> :f
			[17:03] <@Microbe> "me and everyone whose nick is me*" ?
			[17:03] <@Albie> no because
			[17:03] <@Saturn> on !*:text
			[17:03] <@Saturn> on me*:text
			[17:03] <@Albie> me: is only a host match
			[17:03] <@Saturn> see? that totally doesnt make sense
			[17:03] <@Albie> using me: is not the same as if ($me == $nick)
			[17:04] <@Saturn> it gets worse when you use named userlevels
			[17:04] <@Saturn> on mefriend:text
			[17:04] <@Saturn> on me:friend:text <-- MUCH better, although completely pointless
			[17:04] <@Albie> a userlevel called me? ;p
			[17:04] <@Microbe> can you make it, Albie? :)
			[17:04] <@Microbe> guess yes
			[17:04] <@Albie> i should think so
			[17:04] <@Saturn> see the : as improvement of readability
			[17:05] <@Microbe> ok, now summarize this to the wiki
			[17:05] <@Saturn> just copy&paste this log :p
			[17:05] <@Microbe> ;)

Albie: Reworded / placed me:

2006-01-27T16:45:44Z

Reworded / placed me:

@@ Line 42: / Line 42: @@
 == Prefixes ==
 You can limit access to an event by specifying special prefixes which determines how an event is processed or triggered by users.
 === The + prefix ===
@@ Line 63: / Line 56: @@
   on *:TEXT:help:#: { msg $nick You have accesed a * level event }
 === The ! prefix ===