Np, But i'm going to be working off like 5 year old memory here...
basically... in the directory you put this script in, there should be a settings.ini with a section called [badwords] in it...
Make a section called [badwordsadmins] then under that put the nicks you want to be exempt from it as "nick=admin" "nick2=admin" and so on... putting each one on a new line.
Then change the start of the on text from
on @*:text:*:$($readini($+(",$scriptdirsettings.ini,"), Badwords, Channels)): {
var %x 1
to
on @*:text:*:$($readini($+(",$scriptdirsettings.ini,"), Badwords, Channels)): {
if ( $readini($+(",$scriptdirsettings.ini,"), Badwordsadmins, $nick ) == admin ) { halt }
var %x 1
and that *should* fix it to ignore anything from a nick listed in the settings.ini under badwordsadmins... which again should look like
Sorry, I've been out of MIRC scripting for like 5 years now... So I won't be modifying any scripts that I've posted here...
But, here's a tip. For any scripts you find that you want to whitelist people on... just use the access list, and use the = function in that to limit anyone with higher access than your desired access from triggering any of the events...
You could also manually add them to the ini, under an "admins" setting, and at the top of the on text event, just use a readini to check if the nick is in that ini... if it is, just stop the script.
sorry pal, that wouldnt be possible. I designed it to delete the old list for a user when they started listing again. So, each time someone listed, it would be the latest.
However, if you look at the help for ops, it tells you how to add new releases. You will however have to add two items to your searchbot.ini
under
[searchbot]
release.trigger=!releases
release.time=86400
86400 being the number of seconds in 24hours.
Then once logged in as with op access or above you should be able to use the addrelease command. and all users should be able to use !realeases #channel to see that channel\'s releases.... If I remember right. there\'s a lot of stuff that i had added to this script before I stopped working on it. and that stuff never got documented.
yeah, he just didnt explain why. Sometimes, I find people like to know exactly why you tell them not to do something, rather than just saying not to do it.
EVERYTHING that can be done by a script, can be done by a user in normal mirc. All a script does is automates tasks. So Yes, while you can add bans through normal Mirc. He\'s put a different way of adding them in. Also, when you state \'in my script\' its not the same as stating \'in the scripts that came with mirc\'.
odd lindrian. You say its \'not usefull to most of us\' because YOU already have it in your script.... Did you become most of us?
Yoinx
commented on a Snippet, Ban lock - Dec 25, 2006
it should be hiding them, thats what the two raws at the bottom are for. The reason I have it there is to ensure the banlist updates properly.
Yoinx
commented on a Snippet, Ban lock - Dec 24, 2006
Yeah, Sorry... Thats because I never told it to delete the ban.
on me:*:join:#: {
mode $chan +b
.timer 1 2 banlock_build $chan
}
alias banlock_build {
var %x = 1
while (%x <= $ibl($1,0)) {
if ($ibl($1,%x).by == $me) hadd -m banlock $+($1,.,$ibl($1,%x))
inc %x
}
}
on me:*:ban:#: {
hadd -m banlock $+($chan,.,$banmask)
}
on me:*:unban:#: {
hdel -w banlock $+($chan,.,$banmask)
}
on !*:unban:#: {
if ($hfind(banlock,$+($chan,.,$banmask),w,1)) || ($hfind(banlock,$+($chan,.,$banmask),W,1)) {
if ($me isop $chan) || ($me ishop $chan) mode $chan +b $banmask
}
}
raw 367:*: halt
raw 368:*: halt
that should work, though I have no idea why it was giving you problems with soushi.
Yoinx
commented on a Snippet, Ban lock - Dec 24, 2006
thats weird. Soushi isnt your clone is it?
Yoinx
commented on a Snippet, Ban lock - Dec 24, 2006
Something like this:
on me:*:join:#: {
mode $chan +b
.timer 1 2 banlock_build $chan
}
alias banlock_build {
var %x = 1
while (%x <= $ibl($1,0)) {
if ($ibl($1,%x).by == $me) hadd -m banlock $+($1,.,$ibl($1,%x))
inc %x
}
}
on me:*:ban:#: {
hadd -m banlock $+($chan,.,$banmask)
}
on !*:unban:#: {
if ($hfind(banlock,$+($chan,.,$banmask),w,1)) || ($hfind(banlock,$+($chan,.,$banmask),W,1)) {
if ($me isop $chan) || ($me ishop $chan) mode $chan +b $banmask
}
}
raw 367:*: halt
raw 368:*: halt
Yoinx
commented on a Snippet, Ban lock - Dec 24, 2006
I\'ve gotta ask this. Since its the most obvious one...
Why store all these to an ini....
Just loop through the $ibl to find $ibl($chan,x).by where the by address is you... add that address to your hash, and any that you set to the hash as well. Then, you can just search the hash anytime someone tries to do the ban/unbans...
You can also use this same technique to expire old bans everytime you join your channel.
on *:input:#: {
if ($1 == !away) {
tnick $+($me,$chr(124),Away)
describe $chan I am currently away.
}
elseif ($1 == !back) {
tnick $mnick
describe $chan I\'m back.
}
elseif ($1 == !afk) {
tnick $chan $+($me,$chr(124),AFK)
describe I\'m currently AFK at the moment.
}
}
if you wanted to use it this way.
Reasons:
1. Using tnick instead of nick allows you to reference $mnick to get back to the default nick, whereas nick replaces $mnick. Also, using nick you would still have that nick if you were to disconnect and reconnect etc.
2. Describe $chan is the proper way to do actions to a channel from a script.
3. You dont have all the on inputs that you had as, I believe only the first one ever should have worked.
4. You dont have the bracket mismatches.
yeah, people like to script things differently anyway... here\'s how I would do it.
on *:notice:*nickname is registered*:?: {
echo -a registered
if ($nick == nickserv) {
if (!$($+(%,nickservpass.,$network),2)) .timer 1 1 setnickservpass
else msg nickserv identify $($+(%,nickservpass.,$network),2)
}
}
alias setnickservpass {
set $+(%,nickservpass.,$network) $$?=\"Enter Your password for nickserv on $network $+ \"
msg nickserv identify $($+(%,nickservpass.,$network),2)
}
Yeah, I\'ve actually made a much better mp3 player since this, however, it needs images and such, but it needs images, and such... I just havent uploaded it as an addon because it needs some minor rewrites to make it use the images from the script directory instead of the main directory. If anyone is interested in doing the rewrites, I should have it somewhere still.... I think I posted a link to it as \'ymp3\' or something in the forums. Anyone is free to do the rewrites, and add whilefix.dll to the while loops that add the files. And post it, with credits.
I\'m with sean on that one. Besides that, since you would only want to close out pms that come from people, and not the one\'s you initiate. Your code would have been more like:
on ^*:open:?:*: {
.msg $nick I do not recieve querys.
halt
}
and to correct the code you had posted. You need a matchtext.
on *:text:*:?: msg $nick I do not recieve querys.
Also, you dont need the brackets for a single command. Nor do you need the command character in scripts (/). Please think before you post, and avoid trying to be a jerk toward other people\'s scripts when it works for what they made it for. As thats more than I can say for your solution.
Are you sure you want to unfollow this person?
Are you sure you want to delete this?
Click "Unsubscribe" to stop receiving notices pertaining to this post.
Click "Subscribe" to resume notices pertaining to this post.
