JoshR

I personally made my own msg alias to go along with my theme. image of my theme Also made custom notice/me/describe alias'. But yes, if you plan on using your custom msg alias, just remove the "!".

You should know the "!" prefix has it call upon the built-in alias opposed to any custom alias. So just to make sure they don't have any custom msg alias, i would prefix it with a ! to call the built-in and a . to silence it. so you don't get the double message effect on your end. That is my reasoning for the "!". as for the switches for echo, anytime i was applying a switch, such as "-<switch>N" i didn't notice it was working unless i had the -<switch>N at the end of the list of switches. So i apologize for my mistake. . And for the coding style, i know we each have our own method, but then to go back, he shouldn't have said i had goofy looking code. :\

Haha thanks, and nice avatar. makes me laugh when i see it.

I didn't mean to come of as c-ock-y, i was just saying that clean and cropped code should be readable and not just crammed together. Sorry for coming off like that . and i know 3 years might not be much, But i do know people who have only scripted for less then a year and know more then i do. So in technicality, 3 years is alot for mSL scripting . Thank you for the heartfelt welcoming by the way

Travis, the since you have no other switches with parameters that follow, place the i4 at the end. And the indentation only works if the line is overlapping. So if it has to extend to a new line, it will indent 4 characters. otherwise, it's left alone. and the !.msg just simply uses the built msg alias ( the "!" does that ) and makes it so it doesn't show in your window, or so it's hidden ( the "." does that ). That's what actual mIRC scripting language ( mSL for short ) looks like. It takes a while to get ahold of most of the tricks, i've been scripting mSL as a hobby for 3 years. and PHP for 6 months. aswell as xhtml/CSS/html

Sorry for bumping, but this may help those in need of visual aid of hash tables My hash table dialog. Again, sorry for bumping, just thought it could be useful.

Not all networks have the same nick length, so you must accommodate that. You can do so by retrieving the raw on connect. and using a variable. or a hashtable. Would prefer a hashtable so you can access it quicker. Also, your on INPUT will return the basic mIRC format when using a /command on *:INPUT:*:{ if ($left($1,1) == /) && (!$ctrlenter) { return } else { haltdef !.msg $active $1- echo -ai<# characters to indent> $me $1- } } That should take care of the / problem. Also, to keep it perfectly aligned, i suggest use the i parameter in echo, like i showed in the above.