By ITSOVER9000 on Nov 20, 2011Basically, the only reason I made this was because instead of having to type the long .pnick version in a script, I can type if ($isowner/$isadmin(Nick) == Yes) {
stuff
}
instead of having to type if ($left($nick($chan,$nick).pnick,1) == ~/&) {
stuff
}
Well, that's it.
alias isowner {
if ($1) {
if ($left($nick($chan,$1).pnick,1) == ~) {
return Yes
}
else {
if ($1 !ison $chan) {
return $1 is not on this channel.
}
else {
return No
}
}
else {
return $!isowner(NickName)
}
}
}
alias isadmin {
if ($1) {
if ($left($nick($chan,$1).pnick,1) == &) {
return Yes
}
else {
if ($1 !ison $chan) {
return $1 is not on this channel.
}
else {
return No
}
}
else {
return $!isprotect(NickName)
}
}
}
I'll quote this below to defuse the "confusion:"
Version History of mIRC 5.61
Fixed lock dialog password bug.
Improved support for IRCX servers:
Added property $nick().owner, isowner if comparison, and q\r property to $nick(#,N,aohvrq,aohvrq) where q is for owners.
Added on OWNER/DEOWNER events, work the same as on OP/DEOP, and $mode().owner/deowner properties.
Jethro
why dont you use "isadmin"?
There is no such thing as "isadmin" operator, Mr. Dean.
i hate when lame ppl comment on my posts, with lame answers... i said to him, there is already an operator called isprotect... i asked him, if he could change the name of his identifier to "isadmin" instead "isprotect" since it may confuse the other ppl with the "isprotect" operator...
the isprotect operator works... i think you dont know how to use it...
from the mIRC help file
isprotect if v1 is a user in your protect list for channel v2 (v2 optional)
Protect
If you are on a channel and you have channel Op status, any users that match the nicknames in the protect list will be automatically protected. mIRC does this by kicking or de-opping anyone who tries to kick or de-op your protected users.
the isprotect, on mIRC is an operator for conditions, in this case it will check if v1 is a protected nick on your protect list... i just give you a tip, for, why not use isadmin, instead isprotect, since it may confuse the other ppl...
