Don't you need permission to PM/Notice users on most networks?

thank you neo i thought of using the .txt files but i thought this would be better! Thanks anyways

to make it smaller and prevent flooding, create a text doc named Commands and list the commands available for use then use this..
on 1:text:!Commands:#:if ($isfile(Commands.txt)) { play -p $nick Commands.txt 1500 }

it will maby flood only if u do it alot of times...

that doesn\'t matter. notice or pm, dumping THAT many lines will flood

@Brian: you don\'t really want that many lines sent to somebody. It will just dump all that text and cause flooding and such problems. You need to keep any output as concentrated in one line as possible. If you can\'t keep it in one line, use 2-3 lines, but with a decent timer between them

u did can do it much easyer and in 1 line isn`t too good:
on *:TEXT:!commands:#:{
/msg $nick Thit are me commands
msg $nick
}

and that a phew times under it like thit:

on *:TEXT:!commands:#:{
/msg $nick Thit are me commands
msg $nick !8ball
msg $nick !@Rsnews
msg $nick !calc
msg $nick !gratz
msg $nick !murder
msg $nick !pull
msg $nick !@price
msg $nick !@pest
msg $nick !@Stats
msg $nick !defname so u can use just single commands like !stats !cmb etc...
msg $nick !@
msg $nick !clan
msg $nick !poll votes whits !yes and !no questions
msg $nick !seen
msg $nick !@rs2
msg $nick !togset and !togreturn
}

Again, not quite useful. You could turn this one in a very useful snippet by dynamicaly creating a list of commands, based for example on a text file. You could read and parse through all loaded .mrc files and see what commands do people have access to, and where they are active. If you need any help with how to do this, use the forum\'s mirc scripting section and ask for help.