I posted links to BOTH the scripts needed, this one just lets folks use the what/who triggers, there is no other way I know of to bypass the auser without giving folks access to the delete function too.
Only way I know to do it, is to make it a seperate script. I have it loaded seperatly incase I choose to go back to only allowing ausers access to everything, I thought I made it clear in the description.
Now even if I wanted to I cant seem to edit my own posts, so yeah..This will have to do.
Here is a bypass for its auser requirement, it also bypasses the who is's one as well. Best used with both scripts.
On :TEXT::#: {
if ($addon.status != on) && ($addon.status != off) { .msg $chan invalid configurations. | halt }
elseif ($addon.status == off) { halt }
elseif ($1 == What) {
if ($2 == Is) {
if ($hget(whatis.addon, $3) != $null) {
.msg $chan $replace($hget(whatis.addon, $3), , $nick, , $chan, , $address($nick,2), , , , )
halt
}
}
}
elseif ($addon.status != on) && ($addon.status != off) { .msg $chan invalid configurations. | halt }
elseif ($addon.status == off) { halt }
elseif ($1 == Who) {
if ($2 == Is) {
if ($hget(whois.addon, $3) != $null) {
msg $chan $replace($hget(whois.addon, $3), , $nick, , $chan, , $address($nick,2), , , , )
halt
}
}
}
}
Here is a bypass for the scripts auser requirement completly
On :TEXT::#: {
if ($addon.status != on) && ($addon.status != off) { .msg $chan invalid configurations. | halt }
elseif ($addon.status == off) { halt }
elseif ($1 == What) {
if ($2 == Is) {
if ($hget(whatis.addon, $3) != $null) {
.msg $chan $replace($hget(whatis.addon, $3), , $nick, , $chan, , $address($nick,2), , , , )
halt
}
}
}
elseif ($addon.status != on) && ($addon.status != off) { .msg $chan invalid configurations. | halt }
elseif ($addon.status == off) { halt }
elseif ($1 == Who) {
if ($2 == Is) {
if ($hget(whois.addon, $3) != $null) {
msg $chan $replace($hget(whois.addon, $3), , $nick, , $chan, , $address($nick,2), , , , )
halt
}
}
}
}
Firstly, because combining +m and +i is not a good thing 99% of the time, the reason to go +m is to shush trouble makers in the channel while you ban them..etc +i is only if there is a larger issue.
Secondly, because adding $+ is completely and utterly not needed in #$chan line. I have tested it on NNS and 6.35, and others have on 6.34 and not had any issues.
Zerg I tried that, but then the highlight wouldnt work, and that was one the features I wanted for my channel. Its very easy to modify to work with multiple users, but doing so makes it rather hard to get it to allow you to do highlights by %away due to $+ $nick sets it so the away is set as %awayuser, instead of %away user, I guess one could do $nick without the $+ I might try that soon. Love your snippet btw!
Jethro_ exactly it will work if some one types brb gone to the bathroom..etc As designed.
However you didnt mention that with $+ $Nick that if (%away isin $1-) wont work for highlighting, so I have removed the $+ +nick and returned to the older version which seems far more stable.
Your point is duely noted and thank you, but that was on purpose. :)