dialog & alias

hey guyzz,

I really wanna learn creating a dialog and wanna know what alias means? anyone knows a tutorial talkin about that?

i'll try to explain it

aliases or custom identifiers are prefixed with $name . Or in some cases without the $ prefix just the alias name

So let's create something simple.

alias say { return this is something about aliases }

Here we've made our own alias called say , we wil prefix it with $ .

Example on how to use our alias.

on *:text:*test*:#:{
 msg # $say
}

Now what have we done ?

If you are in a chatroom and someone says test , your script will respond to the word test using our own made custom identifier.

I'll hope you understand it a bit... Just test the code.

Me?......

The best advice I can give to anyone is read, read, then read, try and read, then re-read the help files. When you think you know it, READ IT AGAIN!!! After that......READ IT AGAIN!......

Start small. It may seem lame or stupid to some, but you need to get a foundation.

Ask questions. Try and be specific!

Get a few add ons and look at the structure. Try to learn what means what, and why it goes there.

Pay close attention to everthing in the code!

I started by asking Rumbaar if I could have permission to edit his advertisement dialog (which he gave). I didn't want to change it really, just make it a little easier for beginers to understand it and get it working. The only thing I really did was save it as a .mrc file instead of a text file, for easier loading.

Then I just started looking at how the script was written, and why it responded like it did. I decided to write an advertisement kicker ( I know! How ironic huh?..LOL). Just to see if I could do it. I wrote it, and had alot wrong. I posted it here and got a ton of help which made me understand things even more.

If you use a preset script now, look at the codes, and learn why a code does a specific thing.

DONT RIP THE CODE! Just look at it. I have learned that people seem to write code a bit differently from one to another. But the outcome is basically the same.

Search the web for tutorials on PHP scripting.

Remember to never rip codes. If you plan to ever release it, people will know.

I am not sure on the conduct with people helping, but I would include all the people that helped. Respect goes a long way.

NOTE! I have to say this, have a mIRC strictly for testing. If you are new and write the wrong thing, you can shut the script down, and it will never load again...DONT ASK! , how I know that..But I do...

I dunno what more to say here....Just try and be patient and test alot.

When all else fails...

READ THE HELP FILES!!! READ THE HELP FILES!!!! ASK QUESTIONS..RE-READ THE HELP FILES!!

PS. I did do one thing that I was advised against..I wanted a nicklist other then the standard mIRC one. I had an added on that I liked but it was pinging the crap out of people. I found where the lines were that caused it, Edited the crap out of it, and it works fine now. Sorry X-Fusion, I know you said they were just for looks, but I just could not look at the basic list anymore...

Yeah read the mirc cookbook ...

mirc cook book, page 1030 is missing!!

mIRC Cook Book page 1030:

Add two cups reading the help files.

Add 1 cup of written code.

Add 222 cups of bad testing.

Loose one mIRC.

Add one new mIRC.

Add a tablespoon of sucess.

Place all ingredients in a large skillet. Simmer over slow heat until code is slightly browned.

Add a 1/2 cup of failure, and 2 table spoons of brackets. Let stand for an hour. Stir with 3 more cups of testing. Add a pinch of failure. Refrigerate for a day.

then serve with a latge trout..