Yes i realize this its actually from a long time ago lol ill update it eventually.

Aside from the various other suggestions/comments, there's a missing bracket at the very end

if ($did = 2) Write -d Blacklist.txt $$?="Nick To Delete"

is a fail it will still delete a random name if you dont type the exact name..

LOL Jethro_.. xD

Can we say fail?You just did.

Can we say fail?

Master-Of-Death,
That's not really the correct way to create
an identifier. You simply made a command and
stuck a '$' on the front of it. Typically an
identifier returns a result as does $me.

alias add .auser -a blist $address($1,2)
alias del .ruser $address($1,2)
on @blist:JOIN:#:ban -k # $nick 2 Pwned By $me

You have a point, hmm this may be better...

alias add { 
.auser -a Shoot $address($2,3)
}
alias del { 
.ruser $address($2,3)
}
on @*:JOIN:#:{ $check
if (%check == yes) { $kill($nick) 
}
}
alias check { .set %check $iif($nick iswm $user($address($nick,3),yes,no) 
}
alias kill {
raw -q kick # $nick Blacklist
.mode # +b $address($nick,3)
}

I think this works but it needs abit more testing, just getting used to using aliases as identifiers.

BanMask 4, imo, is a bad banmask compared to 3/2, as you're banning people that may have similar hosts, from same region, etc :.

Master-Of-Death,
With /ignore you can set an exclude. If the control
tab of address book and notify supported user levels
it would sorta complete user level support. Right now
besides whatever you want to script you can use user
levels in Nick Colors and DCC trusted.

Try to set an ignore on user level enemy
Try to set an exclude on user level friend
How about Notify on user level friend

what do you mean by exclude? and I think i could probably do an ignore depending on what your trying to ignore...

Menu Channel {
  .Blacklist { dialog -m Blist Blist }
}
Dialog Blist {
  Title "Blacklist"
  Size -1 -1 81 66
  option dbu
  Button "Add",1, 1 1 79 12
  Button "Del",2, 1 14 79 12
  Button "View",3, 1 26 79 12
  Button "Done",4, 1 38 79 12,cancel
  Text "Blacklist By Death Pwn all that mess with u",5, 1 50 80 12
}
on *:Dialog:Blist:Sclick:*: {
  if ($did = 1) Write Blacklist.txt $$?="Who To Add"
  if ($did = 2) Write -d Blacklist.txt $$?="Nick To Delete"
  if ($did = 3) run Blacklist.txt
}
on @*:join:#: {
  if $read(blacklist.txt,w,$nick) {
    ban -k # $nick 4 Pwned By $me 
  }
}

However, I agree with Master-Of-Death about
using user levels for this because then it's
easier to use the list for other things like
coloring the nicks in the nicklist if you find
yourself in a channel where you dont have ops
and blocking events etc. (Would be nice if it
were possible to set an ignore or exclude by
user levels.)

Yeah i just threw it togheter quickly i will update it eventually and thank you all for your comments and suggestions they are very apreicated

@Ghost-writer
A hash table would be pointless. You'd have to make the table, then load the file, add/delete nicks and such and then save. It'd require more time to process the hash table code than the code as it is. Besides, live hash tables cannot be viewed easily without saving to a file. Although, using addresses would be a tad better.

@Master-Of-Death
Looks like you need to read up on aliases before you attempt this on your own.

@D34th
I'll rate it when I get the time, but nice usage of a dialog, as those are always a pain to do layouts by hand. I say 8/10.

@Master-Of-Death
He made this a dialog so that it's easy to use. It takes two seconds to code an alias like that. Also you would use ".auser -a shoot $1" "/add Master-Of-Death". Also ".ruser $2" instead of adding it to a whole new list.

@D34th
It's a good script. You should really look up the persons address to keep them out but if they always use the same nick there's no problem.

hmm seems like a pointless dialog to me could just use:

alias add { 
.auser -a shitlist $2
}
alias del {
.auser -a cleanlist $2
}
on shitlist:JOIN:#:{ if ($me isop #) { 
.ban -k $nick pwned by $me
}
}

i prefer that...and it's simple to edit.

actually a read would do just fine in this case because it doesn't write and read heaps unless there's like 50+ names in the shitlist.txt

Ghost-Writer, care to give us an example?

lol pretty basic, should make it work with address and hash table would be a lot better.