Please Disable Ad-Block To View This Website.

If you block ads, this site can not survive!

Ads are very minimal for registered users. If you don't have an account please register now!

DOWNLOAD
 Full Scripts
 Addons
 Snippets
 DLLs
 MTS Themes
 Tutorials
 Misc.
 File Queue
 Download mIRC
INTERACT
 Screenshots
 Challenge
 Top Downloads
 Submit Form
 Forums

SEARCH
Site Search

FRIENDS
Link to us!
PhotoShelf

Home | Comments:
Average Rating:   9   mIRC Scripting Tutorial by MadMonkey
Description:
Amazingly thorough tutorial on making beginning scripters become advanced.

Submitted Review Author's Updates

There is no review for this file yet.
There are no update notes.
Screenshot:
No
Screenshot
Available

Comments:

  Mode:    Create New Post

HawkinsOct 1, 2007 6:49PM
Rating:     8Very good tutorial... Alothough i'm not completely new to scripting for mIRC, there was quite a bit that helped me out with my latest script.
The only bad point i qould give is:
The colour scheme you've used wasn't too kind on my eyes... but was easily remedied when i edited the html....

Thanks :D

Callum027Jan 27, 2007 3:19PM
Rating:     10This is an extremely helpful tutorial. This helped me alot on a script I'm working on, and to clean it up. Thanks! :) 10/10

durulinkNov 7, 2005 9:39PM
thx

KennyboyAug 17, 2004 4:45PM
i read a couple of chapters on this but somehow it got boring or is it my add? jk some other stuff distracted me so i never read it past the commands chapter i think,,,,... But anyway you should make it more interesting than what it is... if i wanted a long page full of stuff i woulda used the mirc help file.....

MadMonkeyJun 23, 2004 2:48PM
Hi guys! =:) Thanks to blue elf and cold for your comments. Some of the errata were due to typos and carelessness. Others due to my oudated knowledge of mIRC. And a few, because of ignorance. I'll sure make the necessary corrections and changes in the next update. Allow me to explain a few things to both blue elf and cold.

##

[quote "blue elf"]...and a lot of the contents can be found in the mirc.hlp.
Blame it on my laziness on topics I am not very enthusiastic in. Wasn't it mainly in the last few chapters?

##

[quote "blue elf"]Actually, $shortfn won't work if the file doesn't exist yet.
I was using /write to create a file. Did you ever try it?

##

[quote "blue elf"]Some errors: "Don't use $isin"
I think I suggested people to use $istok() isntead of $isin in a certain situation in the Scripting Tips.

##

[quote "cold"] Some examples seem to be old, although the author claims that this was updated.
Honestly speaking, you are correct. I originally wrote the tutorial 2 years ago. The recent updates were built on the old tutorial. Some old examples and paragraphs still stayed intact because of my laziness to write a new tutorial from scratch. And I never though there would be such a critical review of the tutorial.

##

Thank you again for the review guy!

blue-elfJun 23, 2004 8:21PM
There's no $isin afaik :P There's only "isin".

MadMonkeyJun 28, 2004 4:26AM
=;P

[TrIpLe]Jun 24, 2004 6:10AM
quote:
MadMonkey said:

quote:
blue elf said:

Actually, $shortfn won't work if the file doesn't exist yet.
I was using /write to create a file. Did you ever try it?
What he was trying to say is that $shortfn() will not work if the file does not exist, ie: if you try something like //write $shortfn($mircdir $+ \s u p dude.txt) it will write to the file 's' in the mIRC directory and then add 'u p dude.txt' to that file because $shortfn() has returned 'c:\mircdirectory\s u p dude.txt'

[edit] fixed tags seeing they fucked up

Text edited by author on Jun 24, 2004 @ 6:12AM


wolfbykeJun 29, 2004 7:15PM
"I never though there would be such a critical review of the tutorial."

Of course there would be an intense review, as there SHOULD be. You are tutoring people, instructing people, on how to do scripting. You have put forth such effort to help people, wouldn't you rather help them with correct information? Otherwise why spend all of that time on the project? Or was it just an exercise in futility? I'm one of the ones struggling to figure all this out and am very greatful to those of you who find this simple enough to actually have time to try tutoring people. I'm glad that cold and blue-elf (who has been an immense help with his own tutorials) took the time to help you, to help us. Your efforts (when they're correct) are truly appreciated, at least by me. :)

MadMonkeyJul 1, 2004 8:29AM
I am already working on an update. =:)

coldJun 23, 2004 12:10AM
I didn't really read this tutorial, just took a quick look, and I've noticed that it contains some mistakes and wrong assumptions (IMHO).

Minor issues, for instance:
- It teaches the deprecated $? instead of $input().
- It teaches /var not using the '=' sign (unrecommended syntax).
- It says the !== operator is the case-sensitive version for !=, but the correct one is !===.
- In "Scripting tips", it says $calc($1+$2) won't work - true, but you only need a space after $1, not before $2 (except for the % operator I guess). $calc(1+$1), $calc($1 +1), $calc(2*%x), $calc($1 +%x)... all these examples work.
- ..etc - there are more things, maybe I can nitpick them later =P

All in all, while this tutorial could help, it could also confuse some people in some parts. Some examples seem to be old, although the author claims that this was updated.



Edit: just clarifying that this comment was typed before blue-elf's was posted, I just delayed to submit it.
He made a good point about the $calc() issue that, even though I strictly avoid using "$*dir<filename>" (instead of "$*dir $+ <filename>"), I wasn't applying the same precaution to $calc(), or even the $N identifiers, before.. that made me think.

Text edited by author on Jun 23, 2004 @ 1:58AM


MadMonkeyJun 28, 2004 4:29AM
I forgot to explain for the !== thing. Blame it on my carelessnes and JavaScript influence. =:D

Axis-Jun 23, 2004 2:30PM
/help

blue-elfJun 22, 2004 11:34PM
Since this is a tutorial aimed at beginners, shouldn't the syntax in the examples be consistent? The format of the HTML is a bit hard to read, and a lot of the contents can be found in the mirc.hlp.

--

I discovered recently write won't write a file in a directory with spaces even if you used $shortfn($scripdirMYFILE.TXT). To overcome this problem use write $shortfn($scriptdir) $+ MYFILE.TXT blah blah blah.

Actually, $shortfn won't work if the file doesn't exist yet.

--

As for the usage of $scriptdir and $mircdir, the proper usage of "$scriptdir $+ filename" should be used. The only reason Khaled is allowing $scriptdir<file> format is to support backwards compatibility - sooner or later, this won't work. So it's better to be safe.

--

Some errors: "Don't use $isin"

---

You wrote:

on *:text:*:?: msg $nick Hi there!
on *:text:Hi:?: msg $nick Hello!

The creator of this script will complain about "on *:text:Hi:?: msg $nick Hello!" being not working. It's obvious it won't work. It will work if it were in a separate file though. As I said the event definition should be specific. (The wildcard means "anything", it nullify all specificities). Look at the example below. Both the event definitions use ON TEXT but they are not the same.


It won't work because mIRC works from the top of the file to the bottom. If the ON TEXT with the Hi matchtext is put on top of the general ON TEXT with the * matchtext, it'll work fine. But, it is not advisable to do this.

---

18). Sometimes you may wonder why an apparently correct expression is not working as expected, especially if it involves some variables or identifier. Chances are, some character involved in the expression is messing things up. For example $calc($1+$2) won't work as expected.

What should be pointed out is to always take care of spaces in mIRC. Same as the $scriptdir above.

---

Another thing that should be mentioned is to make the scripts and variables sensitive to the fact that mIRC is multiserver.

---

Welp, I'm sure there's more. But there's a lot to read so hopefully, the author will enhance this tutorial later.

Text edited by author on Jun 23, 2004 @ 12:00AM




Create New Post

You must be logged in to post messages.